How English Works | The Template

A blank page asks too many questions at once.

What goes first?

How many sections?

Where does the date go?

Which heading level?

What information is mandatory?

What formatting should I use?

What should every report in this organisation have in common?

A template answers some of these questions before the writer begins.

A template is a future document with its reusable decisions already made.

It contains empty places where specific content will later arrive.

Title.

Date.

Executive summary.

Findings.

Recommendation.

Approval.

The template does not know the answers.

It knows the recurring questions.

Quick Read

One-sentence answer: a template works when it preserves the reusable structure, styles, labels, placeholders and document rules that should remain consistent across repeated outputs while leaving the writer enough freedom to supply truthful, context-specific content.

GOV.UK guidance on OpenDocument Format says organisations often use many templates derived from a smaller set of root templates. It recommends naming and versioning templates properly, using styles rather than manual formatting, making templates accessible to assistive technology and tracking template identity in document metadata.

GOV.UK’s accessible-document guidance also stresses structural headings, meaningful titles, real list styles and document hierarchy because reusable formatting should preserve meaning for screen readers and other tools rather than only visual appearance.

Those principles reveal the template’s core architecture:

slots: where variable content will go;
labels: what kind of content belongs in each slot;
order: how recurring sections are sequenced;
styles: how headings, lists, tables and body text carry consistent structure;
defaults: what value or format appears unless deliberately changed;
mandatory sections: what every instance must contain;
optional sections: what appears only when relevant;
version: which template generated the document.

The Template Is Not the Form

A form and a template can both contain labels and empty spaces.

The receiver is different.

Form:

Name: ______
Email: ______
Reason for request: ______

The form collects structured input from a respondent.

Template:

Executive Summary
[Summarise the decision problem, evidence and recommendation in 300–500 words.]

The template helps an author create a future document.

form = capture data from the respondent
template = scaffold output for the author

The Template Is Not the Checklist

A checklist asks:

Did you include the executive summary?

A template places:

Executive Summary

into the document before the writer reaches that question.

The checklist protects memory after or during work.

The template shapes the workspace before work begins.

checklist = remember the requirement
template = pre-install the place where the requirement belongs

A Placeholder Is a Tiny Instruction

Placeholder:

[Insert recommendation here]

This tells the writer almost nothing.

Stronger placeholder:

[State the recommended option, give the two main reasons, identify the principal risk, and name the decision required.]

The placeholder has become micro-guidance.

Good templates use placeholder language to preserve recurring thinking requirements, not merely to mark blank space.

Defaults Quietly Shape the First Draft

A template can contain defaults.

Default date format.

Default heading hierarchy.

Default approval status.

Default audience.

Default wording.

Defaults reduce repeated decisions.

They also create a strong behavioural pull.

What the template pre-fills is more likely to survive than what the writer must invent from nothing.

This is useful when the default represents the normal case.

It is dangerous when the default quietly carries an assumption that should be reconsidered for every document.

Mandatory and Optional Sections Need Different Signals

A template may contain:

Purpose
Scope
Evidence
Recommendation
Risks
Appendix

Are all six required?

If Appendix is optional, the template should not make its absence look like an error.

Useful label:

Appendix — include only where supporting detail is needed.

Or:

Risks — required for decision papers.

Template English should distinguish required structure from available structure.

Styles Carry Structure, Not Just Decoration

GOV.UK’s document guidance strongly recommends using real heading, list and table styles rather than manually making text look like headings, bullets or labels.

Why?

Because structural styles can be understood by:

screen readers;
search tools;
PDF generators;
document converters;
automatic tables of contents;
future templates and automation.

Manual bold text can look like a heading to the eye while remaining ordinary body text to the machine.

Visual similarity is not structural equivalence.

A good template therefore stores semantic structure inside its styles.

Root Templates Create Families of Documents

GOV.UK’s ODF guidance notes that organisations often use many templates derived from a smaller set of root templates.

Think of:

Root report template → research report template → evaluation report template → individual report

This inheritance saves work.

It also creates dependency.

If the root template changes:

which child templates inherit the change?
which documents remain on the old root?
which local overrides should survive?
how will writers know the difference?

Template architecture can therefore become a small version-control system.

Naming and Versioning Matter Because Templates Reproduce

A bad filename:

Report Template FINAL new latest 2.docx

Which future documents will it generate?

GOV.UK recommends proper naming and versioning schemes for templates.

Useful metadata can include:

template name;
template ID;
version;
owner;
effective date;
superseded version;
root template;

A template error multiplies because every new document can inherit it.

Templates Can Carry Accessibility Upstream

Accessibility is much cheaper when it is built into the template before hundreds of documents are created.

A template can pre-install:

correct heading hierarchy;
accessible list styles;
table structures;
readable font sizes;
language settings;
alt-text reminders;
meaningful title locations.

GOV.UK explicitly says templates should be suitable for assistive technology and that styles should preserve structure.

This creates an upstream principle:

If a quality requirement appears in every document, solve as much of it as possible in the template once.

Templates Can Preserve Good Questions and Bad Assumptions Equally Well

This is the central danger of templates.

Once a recurring structure exists, people stop asking why it exists.

A field remains because it has always been there.

A section is completed because the template contains it.

A paragraph is copied forward because deleting it feels riskier than understanding it.

Templates reduce repeated thinking by storing previous thinking.
That is useful only if the previous thinking still deserves to survive.

Every template review should therefore ask:

Which sections still serve a real job?
Which placeholders produce useful content?
Which defaults create bias?
Which fields exist only because an old system needed them?
What important new question has no slot?

A Template Can Create False Completeness

A report fills every section.

Every placeholder is gone.

The document looks complete.

But perhaps the actual problem required a section the template never imagined.

This creates a subtle trap:

template completeness ≠ intellectual completeness

Writers should be allowed to add material when the case demands it.

The template should support recurring quality, not punish relevant thought for appearing outside the predefined boxes.

Templates Need Escape Hatches

Useful escape language can say:

Add additional sections where the issue cannot be represented accurately within the standard structure. Keep the required decision, evidence and risk sections unchanged.

This preserves the invariant core while allowing unusual cases to carry unusual structure.

The principle resembles guidelines:

standardise what needs consistency; leave freedom where context genuinely matters

Templates Can Shape Organisational Attention

If every proposal template contains:

Cost
Timeline
Risks
Recommendation

but no section for:

Accessibility
Equity
Long-term maintenance
Evidence quality

the organisation has quietly made some questions easier to remember than others.

This is not neutral.

A template is a recurring attention policy embedded in a document shape.

Changing the template can therefore change the questions people routinely ask before making decisions.

Template Instructions Should Disappear from the Final Document

Placeholder:

[Explain the two main risks. Delete this instruction before publication.]

If the final report still contains the instruction, the template has leaked into the published object.

Useful safeguards include:

distinct placeholder styles;
automated checks for bracketed instructions;
pre-publication checklists;
content controls that prompt before export.

The template is scaffolding.

Some scaffolding should remain as structure.

Some should disappear once the building stands.

Examples Inside Templates Can Become Accidental Defaults

A placeholder contains a worked example:

Example risk: staffing delay may move launch by two weeks.

Future authors begin writing staffing delay in every risk section.

The example has stopped illustrating the slot and started seeding the answer.

Good templates use examples carefully.

They can help novice authors understand the expected resolution.

They can also contaminate independent analysis.

An example should teach the shape of the answer without becoming the answer everyone copies.

Template Updates Need Propagation Rules

A root template changes.

What happens to:

child templates;
documents currently in draft;
published documents;
archived records;
automated document-generation systems?

Not every old document should be rewritten simply because a new template exists.

But new documents should stop inheriting a known defect.

Template governance therefore needs a propagation policy.

template version changes the future by default; it should not silently rewrite the past

Primary School: Build a Story Template Without Writing the Story

Give children a blank story scaffold:

Where are we?
Who is here?
What changes?
What problem begins?
What choice does the character make?
How does the story end?

Ask students to use the same template to create very different stories.

Then ask:

Which parts of the stories are similar because of the template, and which remain creative?

The lesson is reusable structure without identical content.

Lower Secondary: Audit the Hidden Questions

Give students a report template.

Ask them to list every question the template makes easy to answer.

Then ask:

What question is missing?
Which section seems unnecessary?
Which default could bias the writer?
Which placeholder gives too little guidance?

This turns template reading into information architecture.

Upper Secondary: Audit Reusable Structure

What recurring job does this template support?
Which sections are mandatory?
Which are optional?
Do placeholders teach useful thinking?
Are defaults safe?
Do styles carry semantic structure?
Is accessibility built in?
Which root template does this derive from?
Is the version current?
Does the template permit unusual cases to remain truthful?

This turns templates into a lesson in defaults, structure, accessibility and institutional memory.

Ten Failure Modes of Template English

Blank-slot vagueness. Placeholders mark space without explaining what belongs there.
Mandatory-optional confusion. Writers cannot tell which sections may be removed.
Default bias. Pre-filled values or wording quietly survive when the case should be reconsidered.
Visual-only structure. Manual formatting looks correct but loses semantic hierarchy for machines and assistive technology.
Root-template drift. Child templates inherit outdated structure or fail to inherit important fixes.
Version ambiguity. Writers cannot identify which template is current.
False completeness. Filling every slot creates the illusion that the analysis is complete.
Example contamination. Worked examples seed future answers instead of merely demonstrating format.
Scaffolding leak. Placeholder instructions remain in the final document.
Template tyranny. The reusable structure prevents a genuinely unusual case from being represented accurately.

How to Build a Better Template

Start from a genuinely repeated document job.

Which decisions repeat across every document?
Which sections are invariant?
Which content varies?
What placeholders would improve thinking?
Which defaults are safe?
Which styles carry semantic structure?
What accessibility can be built upstream?
How are optional sections signalled?
What root-template and version rules apply?
How can unusual cases escape the scaffold without losing required structure?

Then perform the empty-template test:

Before any content is written, what assumptions, priorities and questions has this template already placed into the author’s mind—and do those deserve to be reproduced every time?

The Deeper Idea: Templates Are Reusable Memory for Future Writing

Every blank document can begin from zero.

Or an organisation can remember:

which sections usually matter;
which questions should be asked;
which styles preserve structure;
which metadata should travel with the document;
which accessibility decisions should already be solved.

The template stores those memories in advance.

past document decisions → reusable template → future document structure

This is powerful because good thinking can propagate.

It is dangerous because bad assumptions can propagate too.

That is why template design belongs to how English works.

It is the craft of deciding which parts of yesterday’s writing deserve to exist before tomorrow’s writer has written a word.

Reader Checklist

What recurring document is this template creating?
Which slots are required?
Which are optional?
What do placeholders teach?
What assumptions do defaults carry?
Are styles structurally meaningful?
Is accessibility built upstream?
Which template version applies?
What happens when the root template changes?
Can the author represent a case the template did not anticipate?

Research and Further Reading

Final idea: a template is good when it remembers the right recurring decisions without deciding tomorrow’s content before tomorrow’s evidence arrives.