Project Initiation Documentation (PID)
The PID for the estate project. It brings together the documents that define how the estate is run.
- Project Mandate & Brief
- Business Case
- Project Organisation & Roles
- Product Breakdown Structure and Asset Register
- Stage Plans
- Risk, Issue and Quality registers
- Communication Plan
Quality management approach
- Build every site locally before pushing; the build fails on personal contact data, banned phrases and (here) any link to the hosted wiki.
- Verify live after each deploy at 390 px and desktop.
- Independent privacy sweeps across all public sites.
Change control approach
- Git: fetch and rebase before every push; no force-push; serving branches only; no history rewrite without the Executive.
- Cloudflare: add-only and reversible; every change logged with its undo step and a before-state export.
- Hosted wiki: back up each page before editing, re-read it just before saving, change only the intended text, one change-log row per change set; wait 30 minutes after another worker’s edit.
- Dormant assets (e.g. calls) are not touched without the Executive.
Risk management approach
Risks are scored 1–5 for probability and impact, reviewed at each highlight report and escalated to the Executive when the score is 15 or more, or when the response needs spending or an outward step.
Configuration management approach
Each asset is a Configuration Item with an ID (CI-nnn). Its record is the Asset Register and the machine-readable asset-register.json; both live in Git on the projects branch.
Tolerances
| Area | Tolerance |
|---|---|
| Time | A stage may slip one week before an exception report |
| Cost | Nothing beyond free plans and existing paid storage without the Executive |
| Scope | Adding a site is within tolerance; removing or retiring one needs the Executive |
| Risk | Any privacy exposure on a public page is fixed at once and reported |
| Quality | No deploy that fails its build check |
Project controls
- Highlight report at least weekly, and after major changes.
- Six-hourly research updates continue for the evidence workstream.
- End-stage report at each stage boundary.