Every content operation has a quality standard. Almost none of them could tell you what it is.
What they have instead: a style guide that describes formatting preferences. A brief template that describes what information to include. A review process that catches errors. These are useful. They are not an editorial standard.
An editorial standard is a clear, shared, consistently enforced answer to the question: what does good look like here?
Not good in the sense of technically correct. Good in the sense of worth a reader’s time. Good in the sense of reflecting the best thinking the organization can do on a subject. Good in the sense of being the piece, on this topic, that a reader would choose over any of the alternatives.
Why most organizations don’t have one.
Setting an editorial standard requires someone willing to make a judgment call about quality — not just about compliance — and defend it. It requires a definition of good that is specific enough to be applied and consistent enough to be trusted.
This is politically difficult. “Good” is subjective. Different stakeholders have different opinions about what good looks like. The CMO thinks good is brand-aligned. Legal thinks good is liability-free. The founder thinks good is persuasive. The SEO manager thinks good is rankable.
All of these things matter. None of them is the editorial standard.
The editorial standard is the one that asks: is this good for the reader? Is this what the reader came for? Does this leave the reader better informed, better equipped, or more capable than they were before they read it?
That question is not subjective. It is answerable. But it requires an editor with the authority to answer it and the standing to enforce the answer.
What setting the standard actually looks like.
The editorial standard is not written. It is demonstrated.
You build the standard by identifying the pieces in your existing archive — or, if the archive doesn’t have them, in the broader landscape — that meet it. The pieces that are genuinely good. That say something specific and true. That were worth the reader’s time.
You annotate them. Not with rules — with observations. What makes this piece work? What would make it worse? What did the writer do here that another writer might have missed? The annotations become the vocabulary for editorial feedback, and the feedback builds the standard in the writers who receive it.
This is the function the style guide can’t serve. A style guide describes constraints. A standard describes aspiration, and aspiration requires examples, not rules.
The maintenance problem.
Setting a standard is easier than maintaining it.
Maintaining an editorial standard requires saying no to content that doesn’t meet it. Under deadline. Under pressure from stakeholders who want the piece published regardless. After three rounds of revision that have brought the piece to acceptable but not good.
The organizational pressure to just publish the thing is significant, and it is constant. Every week there are pieces that are almost good enough, and someone whose job is calendar management wants them in the queue, and the path of least resistance is to pass them through.
The editorial gate is the mechanism. But the gate only works if the person keeping it has the authority to close it and the organizational protection to use that authority without consequence.
This is why the editorial function cannot be distributed across a review chain. When multiple people have approval authority, the standard converges toward the lowest common denominator — whatever everyone can agree on, which is always less specific, less interesting, and less useful than what a single editorial judgment would produce.
The feedback system.
The editorial standard is transmitted through feedback. Not through the style guide, not through the brief template, but through the specific, referenced, consistent feedback that tells writers what good looks like in the specific context of this piece.
Good editorial feedback is not “this doesn’t work” — it is “this doesn’t work because it’s more hedged than our voice usually is; look at how we handled the same uncertainty in this piece.” It references the standard rather than stating an opinion. It is calibrating rather than correcting.
When feedback is consistent and specific and referenced to examples, writers internalize the standard. They arrive at their drafts already asking the right questions. The standard becomes self-propagating — which is the only scalable version of an editorial standard that actually works.
What it costs to not have one.
The cost of operating without an editorial standard is invisible for a while and then suddenly apparent in a content audit. The archive is large. The authority is low. The voice is inconsistent. Nothing has compounded. Individual pieces are fine; the body of work is not.
The content quality plateau is always an editorial standard problem. Not always fixable by setting a standard retroactively — some archives are too large and too diffuse to recover — but always caused by the absence of one at the outset.
Start with the standard. Everything else follows from it. If you want a concrete starting point rather than a principle to operationalize from scratch, these ten questions are the version of “what does good look like here” we run every draft against before it publishes.
Jacob Clifton is principal at Clifton Creative.