How To Write A Content Style Guide People Actually Follow

Most style guides fail the same way. Someone writes forty pages covering Oxford commas, capitalisation of job titles, and the correct rendering of the brand name in six contexts. It is circulated once, praised, and never opened again, because nobody consults a document to find out whether to hyphenate something.

The guides that get used are short, opinionated about a handful of things that actually vary, and silent about everything a competent writer already handles.

Cover Decisions, Not Grammar

Grammar is settled by whichever dictionary and reference you nominate in one line. What needs a guide is the set of choices where reasonable people at your company disagree, and where inconsistency is visible to a reader.

The list is usually short.

Person and tense. Second person and present tense, or not. This one choice does more for consistency than fifty rules about punctuation.

How you refer to the product. Whether the product does things or the user does things. “Wrivio rewrites your text” and “you rewrite your text with Wrivio” produce different documents.

How you talk about competitors. Named or not, and what you will not say.

Claims you never make. The most valuable section, and the one most guides omit.

Formatting conventions that affect structure. Heading case, whether headings assert or label, whether you use before-and-after examples.

One or two house prohibitions. Ours is em dashes. Having a distinctive rule or two is useful beyond the rule itself, because it gives the guide an identity and makes it memorable.

Write Rules That Can Be Checked

An unenforceable rule is a preference with formatting.

Before:

Our tone should be professional yet approachable, striking a balance between authority and warmth. Avoid overly formal language while maintaining credibility with our audience.

After:

Second person, present tense. No exclamation marks in body text. State conclusions rather than presenting options; if we genuinely do not know, say so explicitly. Every claim with a number needs the source in the same sentence.

Every rule in the second version can be verified by reading a draft, and three of them can be checked by grep. The first version cannot be applied by anyone who does not already write the way you want, which means it teaches nobody.

The test for any candidate rule: could an editor point at a sentence and say the rule was broken? If not, cut it.

The Claims Section Is The Load Bearing One

This is where a style guide earns its existence, and it is usually missing because it lives in someone’s head in legal or product.

Write down the sentences nobody may publish. Not principles, sentences. “Do not write that Local mode is encrypted; it does not transmit anything, which is a different claim.” “Do not describe the product as GDPR compliant.” “Do not state a macOS release is planned.”

That section prevents more rework than the rest of the document combined, and it is the part freelancers and new hires need most, which is why it also belongs in every content brief.

Keep It To One Page

The constraint is the feature. A one-page guide gets read in full by everyone who writes for you; a forty-page one gets skimmed by nobody and cited only in arguments.

If something does not fit, it is probably either grammar, which the reference handles, or an edge case, which judgement handles. Adding it costs you the readership of the rules that matter.

Make It Executable Where You Can

Some rules can move out of the document and into the pipeline. A grep for banned characters. A link checker. A build step that fails on a missing description. Anything automated stops being a rule anyone has to remember.

The same applies to standards you should not be inventing yourself. Nominate an external reference and link it rather than paraphrasing it: for images, the W3C’s images tutorial settles more questions than a page of house rules would.

For the rest, a rewrite instruction is the practical middle ground.

A Wrivio Context for house style could say:

Rewrite this to match our house style: second person, present tense, no exclamation marks, no em dashes, and no sentence that states something is important without saying why. Keep every figure, product name, date, and stated limitation exactly as written. Do not add claims about encryption, compliance, or platform availability, and do not soften any stated limitation.

Press Ctrl+Shift+Space, paste a section, and check the diff. Encoding the prohibitions directly into the instruction is the point: the rule is enforced at the moment of writing rather than discovered during review, which is when it is expensive.

Review It When It Is Wrong, Not On A Schedule

Style guides do not need annual reviews. They need amending the moment an argument reveals an ambiguity, and the person who had the argument should make the edit that day.

A guide that changes three times a year in response to real disputes stays accurate. One that gets a scheduled review becomes a document about the last review. If the rules keep failing on the same kind of content, that is usually a signal the underlying editorial standard is unclear rather than the wording, and the fix belongs upstream in the brief.

Common Questions

How long should a style guide be?

One page for the rules people apply daily. Anything longer should be a reference appendix that nobody is expected to read end to end.

Should it cover grammar and punctuation?

Only where you deviate from your nominated reference. Name a dictionary and a style reference in one line and spend the space on decisions that actually vary.

Who should own it?

Whoever edits most. Ownership by committee produces a document that grows and never says anything, because every reviewer adds and nobody removes.

How do I get people to follow it?

Make the rules checkable, automate what can be automated, and keep it short enough to read. Rules that cannot be pointed at in a draft do not get followed regardless of how they are communicated.

Download Wrivio for Windows to enforce house style at the moment of writing, with the prohibitions built into the rewrite instruction.