Keep Research Definitions in One Controlling Place

A definition copied into a checklist, a training slide, and a dashboard note creates three maintenance obligations. When the controlling procedure changes, one copy is usually missed. A reader can then follow a perfectly legible explanation that no longer represents the approved process.

Create one controlling place for research definitions. Keep it small and link to the policies that govern actions. A glossary should explain a term, not quietly rewrite contact rules, retention requirements, or commercial authority.

Separate meaning from permission

A definition says what supported evidence means in this workflow. A policy says which actions are permitted and who may approve them. A procedure says how to perform the check in the current tool. These should reference one another without becoming interchangeable.

For example, research complete can mean the bounded assignment reached an accepted outcome, including a documented unknown. It must not automatically mean contact approved. If a checklist uses the term, it should link to that definition and separately apply the relevant contact-control policy.

The W3C: SKOS Reference, Documentation Properties distinguishes documentation such as definitions, scope notes, examples, and change notes. You do not need a semantic-web implementation to use that organizational idea in a small register. The fields below are a practical adaptation, not a claim that a plain spreadsheet formally implements SKOS.

A filled fictional definition card

An invented team creates the following entry:

• Term ID: RES-014; preferred term: research complete.

• Meaning: the agreed question has an accepted supported answer, supported exclusion, or bounded unresolved handoff.

• Scope: internal account-research assignments under the current completion procedure.

• Not implied: current buying interest, permission to contact, perfect data, or approval of a commercial commitment.

• Example: operating sites confirmed, proposed site labelled unverified, and the requester accepts the current-coverage answer.

• Counterexample: all fields contain text, but the company identity remains unsupported and no reviewer has accepted the handoff.

• Owner: research operations lead; controlling procedure: named completion standard; review trigger: a material change in accepted outcomes.

The card links to the actual policy location rather than reproducing its entire text. Its example is labelled fictional so it cannot be mistaken for customer evidence.

Resolve overloaded words instead of forcing one meaning

Owner may refer to record steward, current research assignee, relationship coordinator, or budget approver. Create distinct terms when the responsibilities differ. Do not choose one preferred meaning and assume everyone will infer the others from context.

Keep familiar alternatives as search terms where useful. A colleague searching verified lead should reach a clarification explaining which narrower status the team actually uses. Do not endorse the vague phrase merely because it is common.

For metrics, link the definition to the calculation version. If accepted work changes meaning, the dashboard owner needs to know that historical comparisons may require review. A vocabulary change can have consequences beyond wording.

Route changes to the right authority

Require a proposed change to identify the confusing case, intended meaning, affected procedures, and approving owner. A typo fix can be lightweight. A change that broadens who may act or what counts as complete needs the responsible policy or process owner.

Publish a concise change note and effective date. Keep a retired term pointing to its replacement so old documents remain interpretable. Do not delete the old meaning from history when reports or decisions used it.

If two policies conflict, the glossary must not silently choose the convenient one. Mark the conflict and route it to their owners. A definition writer cannot resolve an authority dispute by editing a sentence.

Replace copies with references

Review templates, training slides, dashboards, and onboarding notes for copied definitions. Replace them with a short label and a link where practical. For necessary offline copies, include version and review information so users can recognize when they are stale.

Test retrieval with a new teammate. Ask what research complete permits, who a relationship owner is, and where to resolve an exception. If the answers require asking the glossary author, improve the entry or link structure.

A useful definitions register is not the biggest document in the research system. It is the place that makes the other documents agree on meaning while leaving policy decisions with the people authorized to make them.

Continue with Create a Lead Data Dictionary Your Sales Team Will Actually Use or Create a Useful Sales Research Service-Level Agreement.