← Every exhibit

Table Table 2 Revenue operations & AI

Which fields make a quality rule reproducible?

Field in the quality registerRule to declareEvidence to preserveFailure if hidden
Record grainOne contact, account, lead, opportunity, or another named unitObject type and stable record IDA count mixes units and double-counts entities
Field definitionWhat the field means and when it is populatedData dictionary version and example statesTwo teams use the same label for different facts
Data owner and stewardWho approves meaning and who handles daily qualityNamed role, not only a team inboxA defect has no accountable decision-maker
RequirednessWhen the field is mandatory and when it is not applicableRule version and exclusion conditionA blank hides both omission and legitimate scope
Allowed valuesWhich values, formats, units, and currencies are validValidation rule and rejected-value logA filled field is counted as valid without a test
FreshnessHow recent the value must be for this decisionLast changed and last reviewed timestampsA complete record survives after its evidence expires
Duplicate ruleWhich identifier or combination makes records uniqueMatch key and merge decisionOne customer appears as several pipeline entities
Data lineageWhere the value came from and what transformed itSource, transformation, and destinationA number cannot be traced back to its input
Stage evidenceWhat observable event supports the current stageEvent ID, timestamp, or documented evidenceA label is treated as a commercial transition
Close-date ruleWhich date boundary and movement rule applyCurrent value, prior value, and change reasonA forecast movement is mistaken for new demand
Exception reasonWhy a failed rule is temporarily treated differentlyReason, owner, expiry, and review dateThe exception becomes a permanent hidden rule

Swipe or scroll horizontally if the table is wider than your screen.

Cite Embed

Reference & Evidence

Source: Table from this essay. Sources and interpretation are given in the article.

Related exhibits