Start with the decisions your team repeats
A small website can develop an uneven voice even when only a few people edit it. One page says “contact us,” another says “get in touch,” and a third calls the same service by a different name. A short editorial style guide helps contributors make those everyday choices without reopening the discussion each time. It is a working reference, not a statement of everything your organization believes about writing.
Before drafting rules, look at a handful of pages that people edit often: a service page, an article, a contact page and a form or confirmation message. Note the choices that vary or cause hesitation. Which terms name your services? Do headings describe the content beneath them? Are calls to action direct? Use those observations to choose a few topics for the guide. If a rule will not help someone write, edit or approve a page, it probably does not need space in the first version.
Define voice in terms someone can apply
Words such as “friendly” and “professional” are a start, but they leave room for different interpretations. Translate them into visible choices. For example: “Use everyday words, address readers as ‘you,’ and explain unfamiliar terms on first use.” Say what to avoid as well: “Do not use jokes in instructions or promise an outcome we cannot guarantee.” A pair of short before-and-after examples can make these choices clearer than a long description of your brand.
Match the tone to the task. An article introduction may have room for warmth, while an error message needs to say what happened and what the visitor can do next. You can keep a consistent voice across both without making every sentence sound alike. If several audiences use the site, name the primary reader for each kind of page rather than trying to invent one tone that fits every situation.
Set rules for the copy visitors scan and use
Give headings, links and buttons a small set of practical rules. Headings should tell readers what a section covers, not merely decorate the page; “How to request a repair” is more useful than “Next steps.” Link text should make sense when read on its own, so prefer “Read the application requirements” over “click here.” Button labels should describe the action, such as “Send request” rather than “Submit,” when that wording fits the task.
Include guidance for details that can affect understanding. Decide how to write dates, times, addresses and abbreviations where they appear on your site. Ask writers to put the most useful information early in a paragraph and use lists when a sequence or set of options would otherwise be hard to follow. These rules support readers who scan, use assistive technology or arrive with limited time. They also give editors specific checks to make before publishing.
Keep a small terminology list with examples
Most sites have a few names that must stay consistent: a program, a product, a team or a type of appointment. Record the preferred term, any terms to avoid and a brief reason when the distinction is not obvious. If “appointment” and “consultation” describe different things, define each one. If they mean the same thing on your site, choose one for navigation and page copy.
Keep this list selective. A guide filled with ordinary dictionary entries becomes difficult to check. Prioritize terms that appear across multiple pages, affect search and navigation, or regularly lead to corrections during review. Add one example sentence where context matters. Contributors can then see how a term works in copy, rather than guessing from a bare list.
Make the guide part of publishing
Aim for a guide that a contributor can read quickly and consult while editing. Give it a clear home near your content templates or publishing checklist. A useful first version might cover voice, common page elements, terminology and a short pre-publication check. It does not need to settle every edge case before it can help.
Choose one person or role to maintain the guide and provide a simple way for editors to suggest changes. When the same question comes up twice, consider adding a rule or example. When a rule no longer matches the site, revise it rather than asking people to remember an exception. Periodically compare the guide with a few recently published pages: if contributors keep missing a rule, it may need a clearer example or a better place in the editing workflow. The goal is not perfect uniformity. It is copy that helps visitors recognize where they are, understand what they need and take the next step.
