What a style guide is for and what it is not
A style guide exists so that decisions are made once. Without one, every writer decides afresh how to spell the product, whether to write a number in words, how to capitalise a heading and what counts as a source, and every editor corrects the same choices again on the next draft. Readers notice the result even when the team does not: a library where one page calls the product one thing and the next page another reads as several organisations, and inconsistency in small things makes a reader less willing to trust the large ones.
The content governance guide names style as one of three standards every page is held to, beside accuracy and accessibility, and makes the point this tutorial rests on: a short guide with examples does more than a long one nobody opens. Governance decides that standards exist and who owns them. This tutorial writes the style standard itself.
It helps to be clear about what the guide is not, because most style guides that fail have tried to be several documents at once.
| Document | The question it answers | Where it is covered |
|---|---|---|
| Editorial style guide | How do we spell, name, format, link and source things in this house? | This tutorial |
| Brand identity and voice | Who do we sound like, and how does tone change by situation? | Brand identity and voice |
| Brand guidelines | Which logo, colours, type and imagery, and how are they used? | Brand guidelines template |
| Writing craft | How do people read on screens, and how do we write for that? | Writing for the web |
| AI voice pack | How does a drafting tool learn to sound like us? | Brand voice guide for AI drafting |
| Content brief | What is this one piece for, and how will it be judged? | Writing a content brief |
The style guide links to the first four of those rather than restating them. A writer who needs the voice principles follows a link to them; a writer who needs to know whether the feature name takes a capital letter finds the answer in the style guide in seconds.
Before you start
- Governance decided. You need to know who owns standards and who settles disputes. The roles in the content governance guide (content owner, editor, subject reviewer, approver, publisher, governance owner) tell you who will own the style guide and who can overrule it.
- A run of recent edits. Collect drafts with the editor's tracked changes, the comments left on them and the review criteria from recent briefs. These are the raw material: every repeated correction is a rule waiting to be written.
- The questions writers ask. Search the team's chat and email for "how do we write", "is it", "should I" and similar questions. Freelancers' questions are especially useful, because they arrive without house habits.
- The brand voice principles, if they exist. The style guide will link to them, so check they are current and findable.
- An afternoon and a reviewer. The first version is a working draft, not a finished manual. Someone who writes for the team every week should read it before it is published.
The steps
Work through the steps in order. The first step produces the list of problems; the next seven turn them into rules; the last two make the rules usable and keep them in use.
Collect the questions writers ask and the corrections editors repeat
Go through the edits and questions you gathered and write each one down as a problem, not yet as a rule: "the course name is capitalised three different ways", "dates appear in two formats", "nobody knows whether to link the regulator or the news story about it". Group them by topic: spelling, names, numbers and dates, headings and lists, links, sources, accessibility, and words. Count nothing yet beyond noticing which problems recur; a problem that appears once may be a slip, and one that appears in several writers' work is a missing rule. The list sets the scope of the guide. If nobody has ever got something wrong, leave it to the reference you adopt in the next step rather than writing a rule for it.
Choose the spelling variant and the reference
Decide which variety of English the house writes in and record it as a house choice, with the reason (where the readers are, what the product interface already uses). Then choose one reference dictionary or published style manual to settle everything the guide does not cover, so that writers have somewhere to look before they ask. Which reference you choose matters less than having exactly one: two references in use produce the same inconsistency the guide is meant to remove. Write down the deliberate exceptions, such as a product term the house always spells one way regardless of the variant, and any words the reference allows two ways that the house has settled.
Name the product, its features and competitors one way
List every product, plan, feature and programme name with its exact spelling, capitalisation and spacing, and whether it can be shortened after first use. Add how the company itself is named in running text. Then decide how competitors are referred to: by name or by category, and in what tone. These are the decisions no published reference can make for you, and they are the ones readers notice most, because a product spelled two ways on one page looks careless. Mark retired names as retired, with the current name beside them, so that old habits and old pages can be corrected. Where product names change often, keep the list in one place that the product team updates and link to it from the guide.
Set rules for numbers, dates, money and units
Decide when numbers are written as words and when as numerals, how large numbers are separated, and how ranges and percentages are written. Choose one date format and write the month as a word if your readers are in more than one country, so that nobody reads the day and the month the wrong way round. Decide how money is shown: the currency symbol or code, its position, and what happens when a page quotes more than one currency. Do the same for units and for times. Each of these is a house choice with no single right answer, which is exactly why it needs writing down. Put the right and wrong examples beside each rule, because number rules are easier to copy than to describe.
Set heading, list and link rules
Base these rules on how people read. Nielsen Norman Group's research, as the writing for the web guide sets it out, finds that most people scan a page before they read it, picking out headings, first words and anything visually distinct. So the rules are about making the scanned parts carry the meaning. Headings say what the section contains, use one capitalisation style, and are real headings nested in order with no skipped levels; the headings and content structure guide covers the hierarchy. Lists are for parallel items, not chopped prose. Link text says where the link goes and makes sense read on its own, which rules out "click here". Add how page titles are written, including the Title TagThe HTML title element that names a page and usually supplies its title link in search results. the publisher sets, so that titles follow the same capitalisation rule as headings.
Write the sourcing and citation rule
This is the rule that protects the site's credibility, and it is short. Take it from the outbound links guide: cite the source of the claim, not a page that repeats it; place the citation where the claim is made, not only in a list at the end; write descriptive Anchor TextThe visible, clickable words of a link. that tells the reader what they will get; and treat a claim nobody can link to as a claim to rephrase as opinion, attribute to first-hand experience, or remove. Add which kinds of source the house accepts first (primary sources and official documentation before summaries) and who decides when a source is disputed. Sources placed at the claim are one of the visible signs of trust the E-E-A-TExperience, Expertise, Authoritativeness, Trust. framing describes, and the rule is also what an editor checks first when a draft comes back.
Add the accessibility rules
Several accessibility requirements are met or failed by the writer alone. The Web Content Accessibility Guidelines describe content that is perceivable, operable, understandable and robust, and the writing for the web guide draws the writer's rules from them: headings that are real headings, in order, with no skipped levels; link text that makes sense out of context; Alt TextThe text alternative to an image, read by screen readers and used by search engines. that says what an image conveys, or marks the image as decorative when it conveys nothing; abbreviations expanded at first use; and no instruction that relies on colour, position or shape alone. Write each as a rule with an example. Conformance requirements vary by jurisdiction and sector, so the guide states the house rules and links the guidelines as the shared reference rather than claiming conformance.
List the words to avoid and what to write instead
Turn the vocabulary corrections from your first step into a table with two columns: the word or phrase to avoid, and what to write instead. A ban without a replacement leaves the writer stuck; a replacement shows what the house means. Include inflated words that have plain equivalents, internal jargon readers do not use, terms that are inaccurate for your product, and claims the business cannot support. Where the brand's voice principles already include a word list, link to it and keep only the editorial items here, so that the two lists do not drift apart. Avoid adding rules about sentence length or readability scores: no single figure fits every reader, and the writing for the web guide's advice is to vary sentences and read the draft aloud.
Put a right and a wrong example under every rule
Go back through every rule and add one example of the rule followed and one of it broken, ideally taken from your own recent drafts with the names changed where needed. Examples carry the judgement a rule leaves out: "write dates in full" is read differently by different writers, while a right and a wrong date side by side is read the same way by everyone. The brand identity guide makes the same point about voice principles and their "this, not that" examples. If you cannot write a clear wrong example for a rule, the rule is probably not doing anything and can go.
Publish it where writers work and name an owner
Put the guide where writers already are: in the shared drive beside the briefs, pinned in the team's chat, linked from the content management system's editor and from the brief template. A guide that has to be searched for is not used. Give it one named owner, usually the editor or the governance owner, who answers questions, settles disputes and makes changes. Add a change log at the top and a review date. Then link it from every brief, and send it to every new writer and every freelancer with their first brief, so that the first draft already follows it; the guide to working with freelance writers lists the style guide among what goes out with every commission.
Keeping the guide alive
A style guide decays like any other content. Products are renamed, new formats appear, writers find questions the guide does not answer and editors start correcting things the guide does not mention. The routine that keeps it current is small, and it belongs in the governance calendar rather than in anyone's memory.
| Habit | What it does | Who does it |
|---|---|---|
| A question channel | Writers ask style questions in one place, so recurring questions become visible | Writers; the owner answers |
| A change log | Each change is dated with what changed and why, so writers can see what is new | The owner |
| A review date | The whole guide is re-read against recent edits and product changes on a set date | The owner, with an editor |
| Brief link | Every brief links the guide, and the brief's review criteria include it | Whoever writes the brief |
| Onboarding | New staff and freelancers receive the guide and a short walk-through | The editor |
| Retiring rules | Rules nobody breaks any more, or that no longer apply, are removed | The owner |
The question channel is the best input. When the same question keeps coming back, it becomes a rule with a right and a wrong example, and the change log records it. When a rule is changed, the old pages that break the new rule are not rewritten all at once; they are corrected when they next come up for review in the content inventory, unless the old wording misleads readers, in which case the pages are fixed straight away as a correction rather than a style change, following the guide to updating and correcting published content. Where a retired name has left older pages contradicting newer ones, the diagnosis of conflicting information across your pages separates it from the other reasons pages come to disagree.
When the brand publishes in other languages, this guide becomes the base each language inherits from, and the tutorial on writing a localisation style guide records only what changes in each target language.
Keep the style guide separate from the voice guide and the AI voice pack even when the same team owns all three. The AI guide's advice to keep voice and facts apart applies here as well: a style rule about how the product is named can be shared with a drafting tool, but prices, claims and specifications belong in the brief's source material, where they can be checked.
A language school's first style guide (illustrative)
Lanternmoth Language School writes a house style guide from a month of edits
Lanternmoth Language School, an invented language school, publishes course pages and a blog written by one part-time content writer and two teachers, edited by a freelance editor. The editor keeps making the same corrections, so she exports a month of tracked changes from 14 drafts and finds 112 edits. Most fall into five groups: course names (the beginner course appears as "Beginners", "beginner's" and "Level One"), how levels are written ("A2", "a2" and "elementary"), dates ("3/4" read as both March and April by students abroad), prices (fees shown in two currencies with the symbol on either side), and links ("click here for timetables" on 9 of the 14 drafts). The school writes a style guide of four pages with 18 rules, each with a right and a wrong example: "Right: Beginner Spanish (Level A1). Wrong: beginners spanish, level one." "Right: 3 April 2027. Wrong: 3/4/27." "Right: €240 (about £205), with euros first. Wrong: 240€ / GBP 205." "Right: see the spring timetable. Wrong: click here." Its accessibility section adds alternative text for classroom photographs and a ban on "the red box below". The editor owns the guide, with a change log and a review date each term, and every brief now links it. In the next month the editor counts 41 edits across 12 drafts, and none of them is a course name.
Common mistakes
- Writing the guide from a blank page. Rules invented in a meeting answer questions nobody asks; rules taken from repeated corrections answer the ones that cost editing time.
- Restating voice and visual identity. Copying the brand guidelines into the style guide creates two versions that drift apart. Link to them instead.
- Rules without examples. A rule read differently by each writer is not a rule. Put a right and a wrong example under every one.
- Bans without replacements. A list of forbidden words leaves writers stuck. Say what to write instead.
- Two references. Allowing more than one dictionary or manual brings back the inconsistency the guide was meant to remove.
- Readability formulas as rules. A score threshold or a fixed sentence length is no substitute for reading the draft aloud and checking it against the reader in the brief.
- No owner and no change log. The guide freezes on the day it is published, writers stop trusting it, and editors go back to correcting from memory.
- Kept away from the brief. A guide that freelancers receive only after their first draft has been edited arrives too late. Send it with the brief.
