Back to the guideField and handover map — fictional example
Copy the table into your document. Example references are fictional names, not actual files. The acceptance below describes a fictional situation.
| Fact | Primary place and link | What to pass on | Who maintains changes |
|---|
| Contact | CRM · D-042 / client C-010 | Project contact: Jane | Sales owner Alex |
| Accepted scope and price | Proposal Q-042 v2 + confirmation dated 2026-10-10 | One new page, two revision rounds; illustrative price $800 | Alex after client confirmation |
| Tasks and blockers | Project P-042 → D-042 | Petra: outline due 2026-10-16; delivery due 2026-10-23 | Petra |
| Scope change | Change record CH-042 linked to D-042 | No confirmed change yet | Alex agrees; Petra updates the plan |
| Billing | Billing register → D-042 | No invoice issued yet; no payment claimed | Alex / bookkeeper |
Handover and check
D-042 → P-042; Q-042 v2, explicitly accepted by the fictional client on 2026-10-10. Petra can open the brief and source copy but lacks access to photos. First task: page outline by 2026-10-16. Agreed delivery remains 2026-10-23; Petra checks the effect of missing photos. Contact Jane, coordinated by Alex. Status: awaiting acceptance; acceptance date blank. Alex obtains photos by 2026-10-12; Petra then confirms capacity and acceptance. A second D-042 handover attempt finds P-042 instead of creating another project.