Every contractor knows the moment someone announces, “I’ve created a new template.” You open a blank file:
-
-
- styles.
- structure.
- numbering logic.
- metadata.
- revision table.
-
A white page and misplaced confidence.
This is the story behind Death by Template — and why technical authors must defend documentation infrastructure.
The scenario
When a manager left, he left his PA adrift. However, a new manager reassigned her to another team.
During a Teams call, she asked:
“Why were the templates redesigned without my knowledge?”
She assumed I had redesigned the templates without permission.
The previous templates were unstable. Broken numbering. No style hierarchy. No automated controls. They could not scale.
Managers had already signed off on over fifty documents that had used the new controlled template.
She wanted to create her own version.
So I asked the obvious question:
“Do you know what’s involved in building a compliant template?”
The answer suggested she did not.
What is a template?
In many organisations, “template” means:
A document you type into.
In professional technical authoring, a template means:
-
-
-
Structured style hierarchy (Heading 1–9 mapped correctly)
-
Multilevel numbering linked to styles
-
Automated tables of contents
-
Controlled headers and footers
-
Revision history tables
-
Document metadata fields
-
Cross-reference compatibility
-
Accessibility compliance
-
Stable formatting for version control
-
Reusable front matter and boilerplate
-
-
A proper Word template is a lightweight infrastructure, engineered, not decorated.
The blank template
Later that afternoon, she sent the new template.
It was a blank Word document with no:
-
-
- predefined styles.
- cover page.
- numbering schema.
- structured bullets.
- defined body text formatting.
-
When I called her for clarification, she confirmed the template.
When I explained what was missing, the tone shifted, and I hinted she was out of her depth. She said she would check with her manager.
I never heard from her again.
Why “Death by Template” happens
This scenario is common across engineering, IT, defence, and infrastructure environments.
Templates are seen as cosmetic
People focus on fonts and margins.
They ignore:
-
-
- Structural logic
- Style discipline
- Automation
- Version resilience
-
Documentation becomes fragile because no one respects the architecture.
Governance Is Invisible
Once 50 documents receive successful sign-offs, people ignore the template until its formatting fails;
People undervalue infrastructure that works.
Authority outpaces expertise
Well-meaning staff assume that creating a template is straightforward.
They underestimate:
-
-
- The complexity of Word’s style engine
- The risk of manual formatting
- The cost of rework
- The audit implications of inconsistency
-
A blank file is not governance.
They bring technical authors in too late.
In many organisations, documentation is reactive.
Templates are “fixed” by non-specialists until someone realises:
-
-
- Numbering collapses at section 3.2.4
- Cross-references break
- TOCs misbehave
- Audits question consistency
-
Then a technical author is called in.
The Contractor’s perspective
As a senior technical author working across regulated and high-control environments, I see the same pattern:
-
-
- Templates designed without structured styles
- Manual formatting instead of enforced formatting
- No metadata control
- No document governance policy
- And then confusion when consistency fails.
-
A template is not a blank canvas, but a controlled system.
If you allow anyone to redesign it based on preference rather than architecture, the documentation quality will erode.
The real risk
Poor templates do not just look untidy; they are also inefficient.
They create:
-
-
- Audit risk
- Rework costs
- Version control confusion
- Loss of traceability
- Inconsistent client-facing documentation
- Increased onboarding time for new staff
-
In regulated sectors, it is operational risk.
How to avoid death by template
If you manage documentation governance, ensure:
-
-
- Someone who understands Word’s style architecture designs templates.
- Link multilevel numbering to headings.
- Control Document properties.
- Standardise Revision tables
- Consider Accessibility standards
- A template change control process exists.
- Managers understand the difference between formatting and structure.
-
Regard templates as infrastructure, not personal design projects.
Final Thought
If you’re a solo technical writer, upholding documentation standards means more than just formatting.