Part 3 of 5

The three tenets of a content style guide

The three tenets of a content style guide

A good content style guide covers three distinct but interconnected areas. Think of them as three lenses through which to look at the same challenge: how do we make sure our content is consistent, high-quality and recognisably ours – whether it's created by a human or generated by AI?

The three tenets are:

  1. Cultural – getting people on board, building ownership and creating the organisational conditions for your guide to succeed
  2. Editorial – defining your voice, tone and style so that every piece of content sounds like you
  3. Technical – choosing where your guide lives, how people access it and how machines consume it

Most organisations jump straight to the editorial. That's understandable – it's the exciting bit, the part where you define your voice and make decisions about language. But a style guide that's editorially brilliant and culturally neglected will gather dust. And one that's editorially and culturally strong but technically weak – buried in a PDF, disconnected from your tools, invisible to your AI – will never reach its potential.

All three tenets matter. And increasingly, the technical dimension is the one that separates a good style guide from one that's genuinely transformative – because it's the technical choices that determine whether your guide can serve AI tools as well as human teams.

The cultural tenet

Before you write a single word of your style guide, you need to think about people. Specifically: how do you create an environment where a style guide is welcomed, used and maintained – rather than resented, ignored and forgotten?

This is the tenet that most style guide projects skip. And it's the one that most often determines whether the guide succeeds or fails.

Content principles

Content principles are the foundation. They're the big, philosophical commitments that underpin everything else – statements about what your organisation believes about content and communication. Not rules. Beliefs.

For example:

  • "We write for our audience, not for ourselves."
  • "Clarity is more important than cleverness."
  • "Every piece of content should earn the reader's time."

Principles matter because they give people a framework for making decisions that the style guide doesn't explicitly cover. No guide can anticipate every situation. But if your team has internalised a set of shared principles, they'll make consistent choices even when the guide is silent.

Principles are also your best tool for getting senior stakeholder buy-in. Asking a leadership team to help define what the organisation believes about content is engaging, strategic and empowering. Asking them to weigh in on capitalisation conventions is not.

Ownership and buy-in

A style guide imposed from above will always feel like someone else's rules. A style guide co-created with the people who'll use it feels like shared infrastructure.

This doesn't mean everyone needs to write the guide. It means the right people need to feel heard. Content creators should be consulted on practical detail – they know what questions come up daily, where guidance is missing and what would actually help. Senior stakeholders should shape the principles. And everyone should feel that the guide exists to make their lives easier, not harder.

The language you use matters. "The comms team's style guide" is something imposed. "Our style guide" is something shared. A subtle distinction, but a powerful one.

Cultural readiness for AI

There's a newer dimension to the cultural tenet: preparing your organisation for AI-assisted content creation. Many teams are already using AI tools to draft, edit or generate content – but without shared expectations about how that should work.

A style guide can bridge this gap. It's the place where you define not just how humans should write, but how AI-generated content should sound. It sets the expectation that AI output is a starting point, not a finished product – and that the same quality standards apply regardless of who or what produced the first draft.

Getting cultural buy-in for a machine-readable, AI-integrated style guide means helping people see it not as a threat to their craft, but as a tool that protects it. The guide ensures that the organisation's voice – something humans defined and care about – is preserved even as content creation is increasingly augmented by machines.

The editorial tenet

This is the heart of your style guide: what your content should actually look and sound like. It's where you define voice, tone, style and the specific editorial conventions that make your content recognisably yours.

Voice

Your voice is your organisation's personality on the page. It's the set of characteristics that make you sound like you, regardless of who's writing or what they're writing about. Voice is consistent. It doesn't change from one piece of content to another – it's the constant thread that runs through everything.

Defining your voice means articulating those characteristics explicitly. Not vaguely ("we're friendly and professional" – so is every other organisation) but specifically enough that someone who's never written for you before could pick up the guide and produce content that sounds right.

Good voice definitions use spectrums rather than absolutes. "We're warm but not gushing. We're confident but not arrogant. We're witty but not flippant." This gives writers – and AI tools – the boundaries within which to operate.

This matters even more when AI is involved. A human writer absorbs voice by reading examples, talking to colleagues and developing an intuitive feel for what sounds right. An AI tool can't do that – it needs explicit, structured definitions. The more precisely you articulate your voice, the better your AI tools will be able to replicate it.

Tone

If voice is your personality, tone is your mood. It flexes depending on context, audience and purpose. You might be playful on social media but measured in a crisis. Encouraging in onboarding content but direct in a policy document. Conversational in a blog post but precise in a technical specification.

The key distinction: voice stays the same; tone adapts. Your style guide should define the range of tones available and give guidance on when to use each one. This is another area where precision helps AI – rather than saying "be appropriate," spell out what appropriate means in different contexts.

Consider mapping your tone against specific channels and content types:

  • Social media – conversational, engaging, occasionally playful
  • Customer service responses – warm, helpful, solution-focused
  • Formal communications – measured, confident, respectful
  • AI-generated outputs (chatbots, automated emails) – clear, friendly, recognisably human

Style conventions

This is the practical, granular detail that turns a general sense of "how we sound" into specific, repeatable decisions. It covers things like:

  • Capitalisation – sentence case or title case for headings? Do you capitalise job titles?
  • Punctuation – serial comma or no? En dashes or em dashes? How do you handle quotation marks?
  • Numbers – spell out one to ten, use numerals for 11 and above? Or a different convention?
  • Formatting – how do you handle bullet lists? Bold text? Hyperlinks?
  • Terminology – what's in your approved word list? What alternatives should people avoid?
  • Inclusive language – guidance on accessibility, gender-neutral language, cultural sensitivity

The goal isn't to have a rule for everything – that way lies madness and a 200-page document nobody reads. It's to have clear, concise guidance on the decisions that come up most often and the ones where inconsistency is most visible.

An A–Z word list is one of the most-used sections of any good style guide. It settles the daily arguments: is it "email" or "e-mail"? "Fundraiser" or "fund raiser"? "Website" or "web site"? Having a single, searchable reference for these decisions saves a remarkable amount of time and eliminates a remarkable amount of bickering.

Writing for different contexts

Your style guide should acknowledge that different content types have different needs. Web copy is different from print. Email is different from social media. A fundraising appeal is different from a product description.

Rather than trying to cover every possible format in exhaustive detail, focus on the principles that apply across contexts (your voice, your core style conventions) and add specific guidance for the formats your organisation uses most. This might include:

  • Web writing – plain language, front-loaded sentences, scannable structure
  • Social media – platform-specific conventions, hashtag and emoji usage, character limits
  • Email – subject line guidance, tone for different email types, sign-off conventions
  • UX writing – microcopy, error messages, button labels, accessibility considerations

The technical tenet

The cultural tenet gets people on board. The editorial tenet defines what good looks like. The technical tenet determines whether any of that actually reaches the people – and the machines – that need it.

This is the tenet that's changed most dramatically in recent years. A decade ago, the technical question was simple: what format should the guide be in? Today, it encompasses where the guide lives, how it's structured, who can access it and whether AI tools can read it.

Format and platform

Your style guide needs to be online. Not as a nice-to-have. As a baseline.

An online guide is searchable, linkable, always up to date and accessible to anyone who needs it. A PDF is none of these things. If your guide currently exists as a static document, the single most impactful thing you can do is move it online.

The platform matters too. Your guide should be easy to update (so it actually gets updated), easy to navigate (so people actually find what they need) and easy to brand (so it feels like part of your organisation, not a generic wiki page).

Structure and findability

A style guide is only useful if people can find what they're looking for. That means thoughtful information architecture:

  • Clear navigation – logical categories, intuitive labels, not too many levels of hierarchy
  • Search – fast, accurate, tolerant of different search terms for the same concept
  • Cross-referencing – related topics linked together so people discover guidance they didn't know they needed
  • Exemplar content – real examples that show what good looks like in practice, not just rules about what to avoid

Structure and machine-readability

Here's where the technical tenet intersects with AI. If your style guide is going to serve AI tools as well as human teams, it needs to be structured in a way that machines can parse.

That means moving beyond prose. A beautifully written paragraph about your voice is lovely for human readers, but an AI tool needs structured data: attributes, values, examples and rules it can query programmatically.

The best approach is both. Human-readable guidance and machine-readable structure, in the same place. Your voice definition as a warm, engaging narrative and as a set of structured attributes. Your tone guidance as helpful prose and as a lookup table of contexts, audiences and appropriate registers.

This dual approach – human-readable and machine-readable in the same guide – is the direction that the most forward-thinking style guide platforms are moving in. It's the technical foundation that makes everything else possible: consistent AI-generated content, automated quality checks, integration with your content tools and a style guide that genuinely serves every content creator in your organisation, human and machine alike.

Access and permissions

Who can see your style guide? The answer should almost always be: everyone who creates content on your behalf. That includes permanent staff, freelancers, agencies and – increasingly – AI tools.

Openness is a strength. A style guide that's locked behind an internal login is a style guide that freelancers can't access, that agencies don't reference and that AI tools can't query. Make it available. If there are genuinely sensitive sections, restrict those. But default to open.

Analytics

If your style guide is online, you can track how it's being used. Which pages get the most visits? Which search terms return no results? Where do people spend the longest? This data tells you what's working, what's missing and where to focus your next update.

Don't underestimate the power of analytics for demonstrating value, too. Being able to say "our style guide had 2,000 visits last month, and the most-searched term was 'tone of voice for social media'" is a compelling argument for continued investment.

Explore and learn

Everything you need to know about content style guides