Build a Small Claims Glossary Before Definitions Drift

In one draft, customer means a paying organization. In the next, it includes everyone who opened a trial account. The approved company description just says customers, so both writers believe they are following precedent, and the numbers in the two drafts cannot both be right.

Write a claims glossary, and keep it small. Pick the handful of terms that keep reopening review, and give each a definition, its exclusions, one counterexample, an owner and a usage pattern. The glossary sits upstream of a press release fact-check: it settles what a word covers before anyone checks the number beside it.

Begin with a handful of terms from actual edited drafts. Search for comments asking what a word includes, which team owns it, or whether two expressions mean the same thing. Put those disputed words on a working list. You do not need to catalog every technical noun in the business to improve the next assignment.

Terms that change what a claim means, such as active customer, deployment, partner, available, trained and operational, because each implies a population, status or capability.

A preference between two harmless synonyms can remain in the style guide. Reserve the claims glossary for distinctions that could change what a reader reasonably understands to be true.

Ask the relevant business owner to supply the working definition and its source. Communications should help make it readable and test its implications. If sales and operations use different meanings, retain the distinction until the owners resolve it. A writer should not silently choose a company-wide definition merely to simplify the copy. When two teams use one word for different counts, you get the same metric reported at two different scopes.

The UK Government Data Quality Framework↗ advises organizations explaining data quality to their users to provide clear definitions of the terminology they use¹, and to document and share metadata to minimize ambiguity and make data easier to reuse¹. A small claims glossary applies that idea to the language around company facts. The entry format below is an editorial proposal, rather than a prescribed government template.

The format already exists for spelling and usage. The GOV.UK A to Z style guide↗² is a public example of short alphabetical entries a writer can check mid-draft. A claims glossary applies that format to the words that carry facts.

A good entry gives the meaning, what it excludes, a usage pattern, one counterexample, a named owner and the date it took effect.

Consider this hypothetical entry for active customer. The company sells subscriptions to organizations, and its account data includes paid, trial and suspended accounts. The glossary needs to tell a writer which of those count, without pretending to establish the current customer total.

The term is a common one to get wrong in public. In the United States, SEC guidance on key metrics↗ in the MD&A section of company filings names active customers among the metrics it covers³, and says the SEC would generally expect such a metric to come with a clear definition of the metric and how it is calculated³. A glossary entry gives the communications team the same anchor, and where a filed definition exists, the entry should match it. This is general guidance, not legal advice; check the rules that apply to your organization with counsel.

Meaning and exclusions

Term: active customer organization. Meaning: an organization with at least one paid subscription in force on the reporting date. Count each organization once under the approved account-grouping rule. Exclude free trials and accounts whose subscriptions have ended. Suspended subscriptions: ask the account-data owner until a rule is confirmed. This last condition should remain visibly unresolved, rather than disappearing into a footnote.

Usage and a counterexample

Usage pattern: [confirmed number] active customer organizations as of [date]. Source for the value: [dated report and relevant table]. Counterexample: the same count described as individual users. One customer organization may have several users, so the expression would change the unit. Allowed shorthand in later paragraphs: customers, only while the organization-level meaning remains clear.

Ownership and change history

Definition owner: [role and named contact]. Definition source: [policy or reporting note, version and passage]. Effective date: [confirmed date], which may differ from the day the policy file was shared (see why an upload date says nothing about when a fact was true). Communications wording accepted by: [owner and decision]. Open question: [suspended-subscription rule and next action]. Previous definition: [link, if any]. Public use of a particular count requires its own clearance; this entry defines the term.

Give two writers the entry and a few sample cases; if they sort the cases differently, the entry needs another sentence or a counterexample.

Give two writers the entry and a few example account descriptions. Ask which belong in the count and which require clarification. Use fictional records if real account information is unnecessary. If the writers disagree, inspect the definition with its owner. The exercise tests whether the entry is usable, rather than whether the writers can guess the author's intention.

Next, give them a draft paragraph. Can they use the short form without changing the unit or losing the date? Does a nearby phrase such as people using the service imply something broader? Add one well-chosen counterexample when it resolves a recurring mistake. Avoid adding layers of instructions that nobody can remember during a deadline edit.

Place the glossary where the team prepares briefs and reviews claims. Link relevant entries from the recurring facts in a library of approved company facts kept current, rather than duplicating definitions into several independent documents. The glossary should make a decision easier at the point of writing, with a route to the source for anyone who needs more detail.

Add an entry only when a real draft raises a question the glossary cannot answer, and record the old and new meaning when a definition changes.

When a definition changes, preserve the old and proposed meanings, the owner's decision and the effective date. Identify current drafts that depend on the old wording, and check any fact recorded under the old meaning side by side with its replacement, as described in telling apart two facts that share a metric name. A new definition can make a historical comparison invalid even if neither reported value was wrong. Keep that consequence visible when writers reuse the term.

A small glossary requires judgment about what to leave out. Entries that never resolve a question add maintenance without much editorial value. Keep the contested terms that change real copy, confirm their owners and add another only when a documented misunderstanding shows why it belongs.

QuoteIt records each fact with its subject, value, scope and period beside its source passage, which is where a glossary definition does its work: the scope says which meaning of customer the number used.