Markdown Editor

Business Glossary Template

Governed business terms: inclusion rules, definition-writing rules, term lifecycle, owner, steward, status, full entry format, change requests, review

डेटा इंजीनियरिंग और गवर्नेंसमानकISO 704:2022 principles; DAMA-DMBOK 2nd Edition Revised (name only)businessglossary
एडिटर में खोलें.md डाउनलोड करें

उपयोग कैसे करें: Use it when teams argue about what a business term means or when reports disagree on a KPI. Fill the inclusion rules and the first ten contested terms with owners first. The main pitfall is one term covering two concepts, which keeps the disagreement alive under a single name.

प्रीव्यू

Business Glossary: [Organisation or domain name]

Governed list of business terms with, for each term, an approved definition, an accountable owner, a steward, a status, related terms and links to the data and metrics that implement it. Definition-writing rules follow the principles of ISO 704:2022 (terminology work), restated in original words; the glossary role is described in the Metadata Management knowledge area of DAMA-DMBOK (2nd Edition Revised), cited by name only. Replace every [bracketed] value and every row marked Example. Worked examples use Corvid Commerce, a fictional SaaS retailer.

Document control

FieldValue
Document ID[GLOS-BUS-001]
Version[0.1]
Status[Draft / In review / Approved]
Register owner[@head-of-data-governance]
Approvers/reviewers[@governance-council-chair], [@domain-data-owners]
Scope[Domains and languages covered]
Catalogue location[Link to the glossary in the catalogue tool, if exported]
Last updatedYYYY-MM-DD
Classification[Internal]

Revision history

VersionDateAuthorChange summary
0.1YYYY-MM-DD[@name]First 20 terms from the revenue reporting workshop
[x.y]YYYY-MM-DD[@name][Terms added, changed or deprecated]

1. Scope and rules for inclusion

A term is included when at least one of these is true:

  1. It names a KPI, a reported figure or a dimension used across more than one team.
  2. It appears in a contract, policy or regulatory report.
  3. Two or more teams use it with different meanings today.
  4. A data product or certified dataset implements it.

Out of scope: product feature names, internal project code names, and technical terms that belong in a data dictionary.

2. Definition-writing rules

IDRuleWeak (Example)Better (Example)
DR-1Define the concept, not the word's history or value"Net revenue is our most important growth signal""Order value after discounts, excluding sales taxes and shipping, for valid orders in a period"
DR-2Start with the broader category, then the distinguishing characteristics"Something a customer does on the site""A customer visit to a storefront that contains at least one page view"
DR-3One sentence where possible; put rules and examples in separate fieldsLong paragraphs mixing formula, exceptions and ownersShort definition; exceptions in the Notes field
DR-4No circular definitions: do not use the term, or a term that depends on it, in its own definition"An active customer is a customer who is active""A customer with at least one valid order in the last 90 days"
DR-5Use other approved terms and link them"Order (excluding the bad ones)""Order with status not Cancelled (see Valid order)"
DR-6State the time reference and unit where they matter"Customers who came back""Customers with a second valid order within 30 days of the first"
DR-7Avoid negative definitions unless the concept is a negation"Not a test account""A customer account created through a public storefront"

3. Term lifecycle

StatusMeaningWho can move it on
CandidateProposed; definition draft; may lack ownerAnyone proposes; steward picks up
UnderReviewOwner and steward named; definition circulated to affected teams for at least [10] working daysSteward
ApprovedOwner approved; may be used in certified data and reportsOwner
DeprecatedKept for history with a pointer to the replacement termOwner, informed by the council

4. Glossary entries

4.1 Summary

IDTermDomainStatusOwnerStewardLast reviewed
BT-001 (Example)Valid orderSalesApprovedHead of sales operationsSales data steward2026-10-12
BT-002 (Example)Net revenueFinanceApprovedFinancial controllerFinance data steward2026-10-12
BT-003 (Example)Active customerGrowthUnderReviewHead of growthGrowth analyst2026-10-20
BT-004 (Example)SellerMarketplaceCandidate[To be named]Marketplace analyst2026-10-25
BT-010 (Example)Gross merchandise valueMarketplaceApprovedHead of marketplaceMarketplace analyst2026-10-12
[BT-nnn][Term][Domain][Status][@owner][@steward]YYYY-MM-DD

4.2 Full entry format

BT-002 Net revenue (Example)
FieldValue
DefinitionOrder value of valid orders in a period after discounts, excluding sales taxes and shipping, in euros
Synonyms (allowed)Net sales
Deprecated or forbidden terms"Revenue" on its own in finance reports; "GMV" (a different concept, see BT-010)
Broader termRevenue
Related termsBT-001 Valid order, BT-010 Gross merchandise value, Refunds (reported separately)
Notes and rulesRefunds are not deducted; they are reported separately as Refunds (MET-REV-006). Orders in other currencies are converted to euros at the daily reference rate of the order date
ExamplesAn order with goods of 120.00 EUR before tax, a 20.00 EUR discount, 20.00 EUR VAT and 4.90 EUR shipping contributes 100.00 EUR; a later refund on it does not change this figure
Implemented inMetric MET-REV-001 (data/metric-definition); semantic model entity orders; dataset urn:corvid:dataset:sales:orders
OwnerFinancial controller
StewardFinance data steward
Status and dateApproved, 2026-10-12
Source of definitionFinance reporting policy FRP-04, section 2
Translations[Language: term] (translations name the same concept; they do not change the definition)
[BT-nnn] [Term]
FieldValue
Definition[One sentence following section 2]
Synonyms (allowed)[Terms]
Deprecated or forbidden terms[Terms and why]
Broader term[Term]
Related terms[BT-nnn]
Notes and rules[Rules, exceptions]
Examples[Example]
Implemented in[Metrics, datasets, reports]
Owner[@owner]
Steward[@steward]
Status and date[Status], YYYY-MM-DD
Source of definition[Policy, contract or law, with section]
Translations[Language: term]

5. Change requests and conflicts

IDTermRequest or conflictRaised byDecisionDecided byDate
GCR-001 (Example)BT-003 Active customerGrowth counts 30 days; finance counts 90 daysFinancial controllerTwo terms: "Active customer (90 days)" approved; growth metric renamed "Recently active customer"Governance council2026-10-20
[GCR-nnn][BT-nnn][Request][@name][Decision][@name]YYYY-MM-DD

6. Review and quality checks

CheckRuleFrequency
Owner coverageEvery Approved term has an active owner and stewardMonthly
Review ageApproved terms reviewed at least every 12 monthsMonthly report
CircularityNo definition uses its own term or a term that depends on itOn every change
UsageApproved terms linked from at least one metric, dataset or report; unused terms reviewed for deprecationQuarterly

7. References

ReferenceVersion or date checkedUse
ISO 704:2022, Terminology work: Principles and methods, https://www.iso.org/standard/79077.html4th edition (2022); checked 2026-10-30Principles behind the rules in section 2, restated in original words
DAMA-DMBOK, 2nd Edition Revised, DAMA International2024; checked 2026-10-30Named only as the reference that places the business glossary in metadata management

Standard and licence note

Structure aligned with the principles of ISO 704:2022, Terminology work: Principles and methods (4th edition): one concept per entry, definitions by broader category and distinguishing characteristics, and no circularity. These principles are restated in original words; no ISO text or definitions are reproduced. Official text: ISO, purchase or licensed access: https://www.iso.org/standard/79077.html (also sold by national standards bodies). DAMA-DMBOK (2nd Edition Revised, 2024) is cited by name only. The rules, lifecycle, entry format and examples are original, and Corvid Commerce is fictional. This template is original text written for this collection. Check the current editions before use. Template licence: MIT.

संबंधित टेम्पलेट