The CRM field-quality register
Admit a CRM record to a revenue review only after grain, ownership, validation, freshness, uniqueness, evidence, and exceptions are visible together.
| ID | Record grain and field | Owner and rule | Observed test state | Exception and review | Dashboard disposition |
|---|---|---|---|---|---|
| Q-01 | Opportunity / close date | Sales operations / required for open opportunities | Current; date falls inside declared review window | None | Admit |
| Q-02 | Opportunity / stage evidence | Sales manager / open stage needs recent evidence | Stale; no recent evidence recorded | Owner assigned; review by 2026-09-13 | Hold |
| Q-03 | Account / account ID and domain | CRM administrator / unique match key | Duplicate candidate; two records map to one entity | Merge decision due 2026-09-12 | Hold |
| Q-04 | Lead / lead source | Marketing operations / required value from approved list | Invalid value; source is outside the allowed list | Mapping owner assigned; review by 2026-09-10 | Hold |
| Q-05 | Opportunity / amount and currency | Deal owner / numeric amount with declared currency | Valid and current; source lineage recorded | None | Admit |
| Q-06 | Contact / consent status | Privacy steward / required for outreach, out of scope for revenue count | Not applicable to this revenue review | Excluded from this report; separate rule applies | Exclude from report |
Swipe or scroll horizontally if the table is wider than your screen.
Reference & Evidence
Source: Author's synthetic CRM quality register grounded in HubSpot (2026). The source supplies bounded governance dimensions; IDs, states, rules, and dispositions are illustrative author synthesis.
Each line is a claim from the register this journal publishes against, resolved from the register at build time.
- C The guide's own definition: "CRM data governance is a framework of rules, roles, and processes for managing customer data in a company"'s CRM, and "It defines who owns different types of records, who can a"ccess them HubSpot. (2026) ·
HUB26-C1 - C The scope is narrower than data governance at large: "CRM data governance focuses specifically on customer and revenue data inside the CRM", and "This includes contact records, company information, deal stages, contact history, and any custom properties used to track customer relationships" HubSpot. (2026) ·
HUB26-C2 - C The four pillars are the guide's: "Effective CRM data governance rests on four core pillars: ownership, quality, compliance, and security" HubSpot. (2026) ·
HUB26-C3 - C The controls are named as practices: "Setting up deduplication rules to catch duplicates at entry", "Making critical fields required so that records aren"'t created incomplete, and "Using validation rules to enforce formatting standards" HubSpot. (2026) ·
HUB26-C4 - C Ownership is a named role: "every dataset and record type in a company"'s CRM "has a designated data steward who is accountable for its quality and maintenance", and the guide contrasts a central model with a "Decentralized model: Individual teams manage their own data standards and fields with minimal central oversight" HubSpot. (2026) ·
HUB26-C5
Grades: A, verified against the printed page of the primary source · B, primary source, text layer only · C, authoritative secondary · D, reported.
Related exhibits
-
How are governance, quality, hygiene, and adoption different?
From the essay What is CRM data governance? Revenue control before reporting
-
Which fields make a quality rule reproducible?
From the essay What is CRM data governance? Revenue control before reporting
-
What should happen when a rule fails?
From the essay What is CRM data governance? Revenue control before reporting