Document formatting
Templates in Microsoft Word that survive real projects
Every firm has a "template" — usually last year's report with the client's name half-replaced. A real template is different: it is a .dotx file where the formatting lives in named styles, the boilerplate is marked for replacement, and a new document starts clean every time. Here is how to build one.
The one rule: styles, not formatting
Almost everything that goes wrong with Word documents — mystery indents, headings that won't join the table of contents, numbering that restarts at 1 in the middle of a report — comes from formatting text directly instead of through styles. In a proper template:
- Every paragraph carries a named style: Heading 1–4, Body Text, Caption, Table Text, List Bullet, List Number.
- Fonts, spacing, and indents are defined once, in the style — never applied by hand.
- Multilevel numbering (1, 1.1, 1.1.1) is attached to the heading styles through a single list style, which is the only configuration that keeps numbering stable in long documents.
- The table of contents, list of figures, and list of tables are fields that build themselves from those styles.
Do this and a 300-page report reformats in minutes. Skip it and every deliverable is an archaeology project.
The template library an A/E/C firm actually needs
| Template | Core contents |
|---|---|
| Technical report | Cover, signature/seal page, executive summary, numbered headings, figure and table captions, appendix scheme (A, B, C with per-appendix page numbers), references section. |
| Proposal | Cover letter, compliance-friendly heading structure that can mirror an RFP's outline, project sheets, resume blocks, cost tables. |
| Resume (marketing) | The same person in several lengths: full page, half page, one paragraph, one line — plus an SF330 Section E version for federal work. |
| Project description | One master sheet per project with the facts (client, dates, fee, role, outcomes) and prewritten versions at several lengths. |
| Letter / memo | Letterhead as a first-page-only header, correct margins for window envelopes, memo variant with distribution block. |
| Meeting minutes / field report | Fixed metadata table (project no., date, weather, personnel), numbered observation entries, photo layout pages. |
Details that separate professional templates from amateur ones
- Save as .dotx, not .docx. A template opened by double-click should create Document1, not open itself for accidental editing.
- Mark what must change. Use content controls or highlighted
[BRACKETED PROMPTS]for every field the author must replace, then make the final QC pass a search for "[" — it finds every forgotten prompt in seconds. - Different first page, different sections. Covers and dividers belong in their own Word sections so headers, footers, and page numbering behave. Roman numerals through the front matter, Arabic starting at page 1 of the body.
- Fields for repeated facts. Project number, client name, and document title should each be typed once (document properties or a bookmark) and referenced everywhere else with fields.
- Table styles. Define one or two table styles in the template so every table in the deliverable matches without anyone touching border menus.
- Test by destruction. Paste ugly text from email and old PDFs into the template, then fix it using only styles. If the fix requires manual formatting, the template isn't finished.
Government forms as templates
Federal and state forms (the SF330 family, grant applications, agency report shells) are a special case: the layout is prescribed, so the template's job is to reproduce the printed form faithfully — fixed-height table rows, the form's own block numbering, and locked cells where the form's captions live. See the SF330 guide for the standard example, and always verify you are reproducing the current edition of any government form before submitting.