Editorial standards at scale are the written, enforceable rules that keep a thousand pages as accurate, consistent, and useful as your first ten. At small volume, standards live in one editor's head. At large volume that breaks, because no single mind can hold the line across hundreds of pages a month. The fix is to move the standard out of heads and into documents, checks, and accountable roles that do not get tired.
Why standards collapse as you grow
Every directory starts with implicit quality. The founder writes the early pages, knows exactly what good looks like, and catches every slip personally. Then volume arrives. New writers join, automation enters, and the founder cannot read everything. If the standard was never written down, it now exists only as a fading memory, and quality drifts page by page until the site no longer feels like the one that earned its early trust.
The drift is rarely dramatic. It is a slightly thinner page here, a slightly off voice there, a fact nobody quite verified. Individually trivial, collectively fatal. By the time the decline is obvious in the numbers, hundreds of weak pages are already live and the cleanup is enormous. Standards exist to prevent that slow leak before it starts.
What a real standard contains
A standard is only useful if it is specific enough to settle an argument. Vague aspirations like be high quality help no one. We write ours as concrete, checkable rules.
- Structure. Every page opens with a direct answer of a set length before any preamble, then uses honest headings.
- Evidence. Every factual claim ties to a real source. No invented figures, ever, under any deadline.
- Voice and mechanics. A defined register, and hard rules such as how we handle punctuation and forbidden filler phrases.
- Linking. A required number of contextual links with descriptive anchors, never bare click here.
- Authorship. A real named author with a credential on every page.
The test of a good rule is that two different reviewers reading the same page reach the same verdict. If a rule leaves room for taste, it is not a standard yet, it is a preference, and preferences do not survive contact with a large team.
The Kings Hospitality Group ship or it does not ship test
We compress the whole standard into one blunt phrase that every writer and reviewer knows: a page ships genuinely useful or it does not ship. There is no third state. There is no publish it anyway because we need the volume. The page either clears the bar or it stays a draft. That binary is deliberately uncomfortable, because the comfortable middle, the just about acceptable page, is exactly what erodes a site's reputation over time.
The phrase works because it is memorable and absolute. A nuanced rubric is easy to negotiate with at four in the afternoon. Ship or it does not ship is not. It gives a tired reviewer the spine to reject, and that is its entire purpose.
Encoding standards so they enforce themselves
Written rules are necessary but not sufficient, because people under pressure forget or bend them. The strongest standards are partly mechanical. We encode every rule that a machine can check into the build itself, so a page literally cannot ship while it violates them. The answer paragraph must be the right length. The dash rules must hold. The minimum link count must be met. The author must be set.
This frees human reviewers to spend their judgement on the things only humans can assess, truth, specificity, and usefulness, rather than counting links. The division of labour between automated gates and human judgement is the heart of quality assurance as a gate, and the consistency of register it protects is covered in voice consistency across thousands of pages.
Standards are living documents
A standard that never changes is a standard nobody reads. We revisit ours whenever a recurring failure appears in review, because a repeated mistake is usually a missing rule, not a careless person. When three writers make the same error, we do not blame them, we write the rule that would have stopped it. Over time the standard becomes a record of every lesson the operation has learned the hard way.
Standards have to survive new people
The real test of a standard is not whether your best writer can meet it. It is whether someone who joined last week can. A standard that only works in the hands of the people who wrote it is not a standard, it is a shared instinct, and instincts do not transfer. We deliberately write ours so a capable newcomer can reach our quality bar from the document alone, with examples of pages that pass and pages that fail and a plain note on why.
This matters most for a group adding properties. Each new site needs to reach quality fast, and it cannot wait for its team to absorb years of unwritten lessons. A standard written for newcomers is what lets a fresh property inherit the craft of the older ones in days rather than months. The same logic applies to an automated drafter, which is the ultimate newcomer, knowing nothing but what the document tells it. If your standard cannot be followed by someone with no history in the operation, it will not hold the line as you grow.
Standards as a portfolio asset
For a group running several properties, a shared editorial standard is what lets each site feel like the work of a serious company rather than a side project. It is the reason a reader can trust any page across the portfolio, and the reason a new property can reach quality quickly by inheriting hard won rules instead of relearning them. That compounding of craft across properties is central to our building thesis, and the standard itself is one station in the wider content operations pillar.
Where to begin
Write down the ten rules you already enforce by instinct. Make each one checkable. Encode the mechanical ones into your build so they enforce themselves, and give a named reviewer the authority to hold the rest. Then add a rule every time review surfaces a repeated failure. Within a few months you will have moved your quality from a fragile memory in one person's head to a durable system that protects every page you publish, including the ones you have not written yet.
Kings Hospitality Group compresses its whole standard into one test every writer knows: a page ships genuinely useful or it does not ship. There is no third state and no publishing anyway because the volume target is short.
Common questions
How detailed should an editorial standard be?
Detailed enough that two reviewers reading the same page reach the same verdict. If a rule leaves room for personal taste, it is a preference, not a standard, and it will not survive a large team under deadline pressure.
How do you stop standards drifting as you grow?
Encode every machine checkable rule into the build so pages cannot ship while violating them, give a named reviewer authority over the rest, and add a new rule whenever review surfaces the same failure three times.