Skip to main content
Shakewell

Explainer

A Template Is Not a Content Model

“We have a template we follow” is the most common sentence in enterprise publishing — and the most quietly misleading. A template is a starting condition. A standard is something that can say no.

The Illusion

A Suggestion With a Logo

The template earns its reputation honestly: documents made from it start out looking alike. But look at what it can actually refuse — nothing. Any style can go anywhere. Manual formatting overrides everything. Required sections can vanish, forbidden content can appear, and the numbering that starts at 6.1 can be hand-typed to 6.5 by someone in a hurry. The .dotx describes the document you intended; it has no mechanism for rejecting the one you got. Twenty authors and two years later, the “standard” is twenty dialects that share a font.

None of this is authorial carelessness. Enforcement was never in the tool's vocabulary — Word's styles pane is a palette, not a rulebook, and every organization running a template-as-standard is really running an honor system with good typography.

The Alternative

Rules the Editor Can Refuse to Break

A system built to hold its shape under load
In a content model, conformance isn't reviewed in — it's the only thing the editor can produce.

A content model is what the template wishes it were: a machine-enforceable definition of the document type. What an amendment may contain, where a warning may sit relative to its step, which sections are mandatory, what numbering does when nobody touches it. In a structured authoring environment the model is live at the cursor: the editor offers what is valid at this position, and the nonconforming document isn't caught in review — it's unwritable. Overrides exist, but they are declared and recorded, so an exception is a decision instead of a drift.

The gap between the two is invisible right up until something needs the structure — a migration, a publishing pipeline, an accessibility audit, an AI project trying to chunk two decades of drifted documents — and then the honor system presents its bill, priced per document. Aerospace codified the lesson long ago: S1000D is, at heart, a content model with a community — proof that when documents matter enough, the industry stops suggesting and starts specifying. Defining your model is an editorial act, not a technical one — which is exactly why the people who know the documents should write its rules, and the system should be what finally holds them.

FAQ

Questions We Hear

What can a Word template actually enforce?

Starting conditions. A .dotx hands the author a page size, a set of styles, and some boilerplate — and from the first keystroke, everything is optional. Authors can apply any style anywhere, override formatting manually, delete required sections, add forbidden ones, and hand-type numbering. The template describes the intended document; it has no mechanism to reject an unintended one. It's a suggestion with a company logo.

What is a content model?

A machine-enforceable definition of what a document type is allowed to contain and in what arrangement: an amendment contains one rule schedule and multiple schedule items; a warning must precede its step, never follow it; this section is mandatory, that element may not carry tables. In a structured authoring system the model is live — the editor only offers what is valid at the cursor's position, so a nonconforming document isn't caught in review; it's unwritable in the first place.

Why does the difference only show up late?

Because templates fail silently and gradually. Every document drifts a little — a pasted style here, a hand-numbered list there — and each drift is invisible until something needs the structure: a migration that expected consistent headings, a publishing pipeline that parses sections, an accessibility audit, an AI project trying to chunk the content. Then twenty years of quiet divergence presents its bill all at once, usually priced per document.

Who should define the content model?

Your editorial owners, with an implementer holding the pen. Deciding what an amendment or a procedure may contain is an editorial act — the people who know the documents make the rules, and the system enforces them. That's the configuration work we do with clients when standing up structured authoring: the tool supplies the enforcement; the organization supplies the law.

Get In Touch

Ready to Stop Suggesting?

If your standard is a template and your enforcement is hope, we'll help your editorial owners turn the rules they already have into rules the system holds.