Handover document family

01The family

Each template is one HTML file that prints to A4, one page per sheet. Open it in a browser and print to PDF, or run google-chrome --headless --print-to-pdf. Example Co. and Example Shire are fictional; every number is example data.

02Shared parts

1. Cover: ink, the wordmark, a mono document label, one Forest rule, the title and who it is for. Meta in two columns.
2. Running header and footer: wordmark and document label at the top; client, confidentiality and "Page n of N" at the foot.
3. Sections: mono number, then a heading in Manrope 600. Body at 12.5pt, 68ch at most.
4. The four owned items, logic first, in every scope and runbook, with Forest markers counted as one use.
5. "What it still depends on" as a standing section, including running costs.
6. Slots in dashed mono, such as [Fee and milestones]. A document doesn’t go out with a slot open.

03Council variants

1. Example Shire Council. Resident issues replace enquiries, and wards replace sites.
2. Operators are officers by role: Coordinator, Customer Service; Manager, Community Services.
3. The proposal carries a quotation request reference slot and a 30-day timeline, never six weeks.
4. Costs during the proof are approved by the Council before work starts. Review follows the budget cycle.
5. "In confidence" in the footer. The client’s own classification marking replaces it if they ask.

04Pages

05Rules

1. No fee, range or figure in a template. The fee goes into the proposal’s section 07 once a scope is agreed.
2. Forest at most three times per page: the slash, the owned markers and one focal row.
3. No client logos without written clearance. The client is named in text.
4. Every figure and table follows the figure system and is numbered per document.
5. Smallest text is 9pt (12px) mono.