Many content teams use AP Style because it’s the path of least resistance. It’s well-maintained and widely recognized, and it answers many of the small mechanical questions that slow editors down, such as whether or not to use a serial comma or spell out “percent.” For a team producing content across multiple writers and vendors, having a shared reference for those preferences is genuinely useful.
The problem shows up a layer deeper. AP Style was built for newsrooms. Its job is to make copy neutral and mechanically uniform across reporters who aren’t trying to sound like each other. That’s the opposite of what a brand content team needs. You want your content to sound like it all comes from the same organization, not just the same grammar handbook.
Teams that treat AP as their only style reference tend to end up in a specific kind of trouble: the copy is clean, but the voice drifts from piece to piece. One writer uses “clients,” another uses “customers.” A freelancer capitalizes the product name differently than your in-house team does. Nobody’s wrong by AP standards, but everybody’s inconsistent.
This article covers how to run AP Style and an in-house style guide as two layers of the same system. AP handles general language conventions. Your in-house guide records the brand decisions AP was never designed to make. The practical question is: where does each one apply, and what happens when they disagree?
The AP Stylebook started as an internal reference for the Associated Press. Its purpose is to standardize the mechanical and grammatical choices that reporters across bureaus would otherwise make differently. Over the decades, it became the default style reference for journalism, PR, and a large share of marketing teams.
Content teams adopt it for a simple reason: it removes ambiguity from a large number of low-stakes decisions that would otherwise eat up time in review. When a new writer joins the team or a freelancer picks up a brief, pointing them to AP gives everyone a shared starting point without building one from scratch.
AP is strongest for details that are frequent but easy to mess up with inconsistency. For example:
These aren’t glamorous details, but they likely come up in every piece of content your team publishes. Having a single answer for each one means editors spend less time debating and more time catching the things that actually affect quality. For a team running hundreds of blog posts a month through a few editors, that efficiency adds up fast.
AP also updates annually, which matters more than it might seem. Style conventions shift. AP’s guidance on topics like hyphenation and inclusive language has changed meaningfully in recent years. A maintained external standard saves your team from having to track those shifts on its own.
AP doesn’t tell you how your brand should sound. It doesn’t tell you whether to address the reader as “you” or keep things in third person. It has nothing to say about whether your blog posts should read at a seventh-grade level or a twelfth-grade level.
This isn’t a gap in AP; it’s by design. AP is a publication standard for organizations where individual voice is intentionally suppressed. Your content team has the opposite goal: you want every piece to carry your signature, recognizable voice. AP can’t do that work because it was never meant to.
An in-house style guide for content teams picks up where AP stops. It records the decisions your team has made about how your brand communicates: the words you use, the ones you avoid, the tone you aim for, and the rules that differ by content type or channel.
The best in-house guides stay short because the guide only needs to cover the calls that actually come up in production and cause rework when they’re made inconsistently. A 40-page brand style guide that nobody reads is worse than a two-page one that every editor keeps pulled up on their screen.
Voice is the area where distributed teams break down fastest. A small in-house team can calibrate informally, but once you add freelancers or agency partners, informal calibration stops working. People default to their own instincts, and the output starts to read as though it came from six different companies.
An in-house guide should define voice in terms editors can apply under a deadline. That means concrete boundaries, not abstract adjectives. “Conversational but not casual” is a starting point, but it doesn’t help an editor decide whether “Let’s dig in” is acceptable as a paragraph opener or too informal for your brand. Specific examples of what’s in and out of bounds are more helpful for brand voice consistency than paragraphs of descriptive language.
Include a short list of voice patterns to avoid. If your brand doesn’t use rhetorical questions in body copy, say so. If you prefer active constructions over passive ones, give a before-and-after example. These small, concrete rules prevent drift when a new writer picks up a brief for the first time.
Terminology is the highest ROI section of most in-house guides. It’s where inconsistency is most visible to readers and most painful to fix retroactively.
In your style guide, you can document the correct spelling and capitalization of every product and service name your content references. You might include incorrect variants you’ve seen in production so that editors know what to watch for. For example, if your platform’s onboarding feature is called “QuickStart” (one word, capital S) and writers keep writing “Quick Start” or “Quickstart,” that belongs in the guide.
You can cover competitor names too; getting a competitor’s product name wrong looks careless. You may also document any terms your legal or compliance team has flagged, such as claims you can’t make or names that require trademark symbols in certain contexts.
People and titles matter here as well. If your CEO prefers “co-founder” over “Co-Founder,” or if your company uses “team member” rather than “employee” in external content, you should write those preferences down so your team can apply them everywhere.
A blog post and a help center article serve different readers in different moments. The tone and structure should reflect that.
Your in-house guide should specify differences by content type. A blog post might allow the first person and a conversational register, whereas a help center article might require the second person and no editorial voice at all. Meanwhile, a landing page might have strict rules about sentence length and CTA phrasing.
Without these distinctions written down, writers might default to a single voice across content types, and editors spend cycles pulling pieces back toward the right register. Documenting the rules by content type cuts that rework significantly, especially when multiple writers are working across the same content pipeline.
The “AP Style vs. in-house style guide” comparison isn’t really a versus so much as a question of which reference governs which decisions. Most of the time, it’s straightforward: AP covers general conventions, and your in-house guide covers brand-specific preferences. The tricky part is the gray area – the decisions where AP has an answer but your brand has a different one.
The last column is where most consistency breakdowns happen. AP’s position on the serial comma is not to use it, but many brands use it anyway. AP has conventions for title capitalization, but your brand might use sentence case across all headings. Both are valid choices, but if your in-house guide doesn’t explicitly state the departure, editors will split – with some following AP and others following what they’ve seen in recent published pieces.
For numbers, dates, abbreviations, and basic punctuation, AP is almost always a good default. These are high-frequency, low-context decisions. Adopting AP’s conventions here saves your team from having to write and maintain rules that already exist in a well-maintained external standard.
The overlap gets interesting with capitalization and titles. AP’s rules for capitalizing job titles, for example, are specific and consistent, but they may conflict with how your organization refers to internal roles in marketing content. If your VP of Product wants the title capitalized in a case study, AP says no. Your in-house guide can say yes, however, as long as it says so explicitly.
Tone is the clearest divergence. AP doesn’t prescribe tone because it exists for neutral reporting, but your in-house guide must.
Reading level is another. AP doesn’t target a grade level. If your content strategy calls for an eighth-grade reading level across blog posts and a tenth-grade level for white papers, those targets live in your in-house guide, not AP.
Inclusive language is an area where AP has moved toward more prescriptive guidance in recent years, but your organization may have its own standards that go further or differ in specifics. Document where your choices align with AP and where they diverge.
SEO conventions such as heading structure, keyword placement rules, meta description formats, and URL slug standards do not fall under AP’s scope. They belong in your in-house guide, often organized by content type.
Legal and compliance notes are non-negotiable. If your legal team requires specific disclosures, restricted claims language, or trademark usage rules, those override everything else. They belong in the in-house guide with clear flags so editors don’t have to guess.
Even teams with two solid style references can run into trouble. Here’s what to watch for.
This is the most common mistake. A team adopts AP, enforces it in review, and assumes that consistent mechanics will produce consistent content. The copy comes back clean; the grammar and punctuation are both solid, but the voice wanders. One piece reads like a textbook, the next like a blog from 2015, and the next like corporate boilerplate. The editors catch mechanical errors because they have a standard to apply, but they can’t catch voice drift because nobody wrote the voice standard down.
This is the opposite mistake: a team builds an in-house guide that tries to cover everything, including the hundreds of mechanical conventions AP already handles. The guide grows to 30 or 50 pages, so writers skim it once and never open it again, while editors can’t find what they need quickly. The guide becomes a reference nobody references.
A better approach is to use AP as the base layer for general conventions and keep the in-house guide focused on the decisions AP doesn’t address. A shorter in-house guide that editors actually use will outperform a longer one that sits in a shared drive untouched.
When two editors work on the same content program without clear precedence rules, they’ll each make different calls on the gray area questions. Editor A follows AP’s convention on the serial comma, while Editor B follows the in-house preference. Neither is wrong, but both are costing you rework.
The in-house guide needs a precedence statement – something as direct as:
That one sentence, backed by a quality control process that checks for it, can eliminate a category of editorial disagreement that eats hours every week.
Style guides go stale faster than most teams expect. A product rename or a shift in target audience – say, from mid-market to enterprise – can leave six-month-old guidance out of step with how the team actually works.
The fix is a review cadence. Quarterly at minimum, with a named owner responsible for flagging changes and updating the guide. Without ownership, updates happen reactively rather than proactively. For a deeper look at building a guide that stays current, see How to Create a “Living” Style Guide.
Subscribe to Beyond the Margins and get your monthly fix of editorial strategy, workflow tips, and real-world examples from content leaders.
Δ
Knowing what each guide should cover is one thing. Keeping the system working as content volume grows is another. Here’s how to make it stick.
The operating principle is simple:
Put the precedence statement at the top of your in-house guide, and make it unambiguous. Then, list every AP exception in one place so editors don’t have to hunt for them.
Keep the in-house guide focused on the repeat decisions that actually drive rework in your editorial workflow. If a question comes up once a year, it doesn’t need a rule, but if it comes up every week, it does. Voice boundaries, product naming, capitalization exceptions, heading conventions, and CTA formatting are all calls that, left undocumented, generate the most back-and-forth between writers and editors.
Build content-type templates that reference both layers. A blog post template might say:
This gives writers a single starting point rather than two separate documents to reconcile.
One person or a small group should be responsible for maintaining the in-house guide and reviewing it on a regular cadence. Quarterly works for most teams. The review should check for:
Without a named owner, the guide drifts out of sync with reality, and editors start making judgment calls that should be documented calls.
When you bring on new writers or editorial vendors, onboarding should include both layers. Hand them the AP Stylebook and your in-house guide together. Walk them through the precedence rules and the highest-impact exceptions. The first few pieces from a new writer will tell you whether the guide is clear enough or whether a section needs reworking.
AP Style and your in-house content style guide aren’t in competition. They handle different parts of the same problem. AP gives your team a maintained, reliable standard for the mechanical questions that come up in every piece of content, while your in-house guide records the brand decisions that make your content sound like yours.
The teams that produce consistent content at volume are the ones that use both AP and an in-house style guide, have clear precedence rules, keep the in-house guide short enough to actually use, and review it regularly enough to keep it current. The ones that struggle are usually missing one of those things.
If you get the precedence right and keep the guide alive, the system should do what it’s supposed to: minimize judgment calls and rework and create content that holds together across writers and editors.
If you already follow AP Style, an in-house guide, or a mix of the two, Proofed’s editors will apply your rules consistently across everything you publish. If you don’t have a style guide yet, we can help you create a living style guide that grows with your content. Schedule a call with our team to find out how it works.
AP Style is a published standard that covers general language mechanics such as numbers, dates, punctuation, and abbreviations. An in-house style guide records the decisions specific to your organization – brand voice, approved terminology, content type rules, and any deliberate departures from AP. Most content teams need both, with each one governing a different set of decisions.
No. AP was built for newsrooms, where individual voice is intentionally suppressed, so it stays neutral on how a brand should sound. Decisions about tone by content type belong in your in-house guide.
If your content needs a recognizable voice, yes. AP will keep your mechanics consistent, but it won’t stop the voice from drifting between writers or settle questions about your own product names and terminology. An in-house guide picks up where AP stops, and it can stay short. It only needs to cover the decisions AP doesn’t make for you.
An in-house guide should cover brand voice rules that editors can apply under deadlines, approved terminology and naming conventions, tone and structure rules by content type, reading level targets, SEO conventions, and any legal or compliance language requirements. These are the decisions that cause rework when different writers make them inconsistently.
Set a clear precedence statement at the top of your in-house guide, such as “Follow AP Style for all general language conventions unless this guide specifies an exception.” Then, list every exception in one place. Editors should never have to guess which reference governs a given decision.
Lost your brand voice?
Let’s talk about the support you need.
We use cookies to give you the best possible experience with Proofed. Some are essential for this site to function; others help us understand how you use the site, so we can improve it. We may also use cookies for targeting purposes.