Drift and stale-definition detection
A control loop for finding GTM fields, rules, workflows, and reports that no longer match the business definition they claim to implement.
On this page
Drift is the quiet failure. The workflow runs, the report loads, and the field slowly stops meaning what its name says.
Five drift checks
| Object | Check |
|---|---|
| Field | Values match the dictionary and allowed set |
| Rule | References fields that still exist and have authority |
| Workflow | Trigger, exit, and owner still match the specification |
| Metric | Query matches its population and denominator |
| Training | Users are taught the current definition |
Run the checks after a schema change, workflow release, ownership change, or business definition change.
Definition registry
id: customer-status
owner: customer-operations
source_of_truth: account.lifecycle_status
allowed_values: [prospect, customer, former-customer]
used_by: [routing-v2, renewal-report, context-layer]
last_reviewed: 2026-08-23
next_review: 2026-11-23The registry creates a dependency list. When customer-status changes, the owner knows which rules and reports need review.
Detect stale artifacts
Search for definitions with no owner, old review dates, fields no longer populated, rule versions no longer referenced, and reports with zero or unknown values rising. Compare configuration exports to the registry where the platform makes that possible. Record “checked and still valid” as an outcome.
Correct without hiding history
Create a new version when meaning changes. Migrate only when the mapping is explicit. Keep the old definition and its reporting boundary available long enough to explain the transition.
Use evidence from the system
Combine scheduled checks with signals from normal use. Watch for fields whose completion drops, values that stop changing, unknown outcomes that rise, overrides that cluster, workflows with shrinking eligible populations, and reports that no longer reconcile to source records. A definition can be current on paper while its implementation has drifted.
Assign every finding one state: confirmed valid, correction planned, migration in progress, accepted exception, or retired. Include the owner, affected records and reports, decision date, and next check. Do not let an audit become a spreadsheet of observations with no disposition.
Set a review rhythm
Review high-consequence definitions and active controls quarterly, and after changes to lifecycle, routing, territory, products, consent, or source systems. Review lower-risk entries on a longer rotation. Use a small set of known records to retest the definition and its implementation. When a correction ships, compare the old and new results before removing the old path.
Related: CRM field dictionary, History and snapshot design, and Quarterly data, workflow, and reporting audits.
Related guides
FAQ
- What is definition drift?
- Definition drift is a gap between the documented meaning of a field, outcome, rule, workflow, or metric and what the system or users currently do. The configuration can still run successfully while the meaning has changed.
- How often should GTM definitions be reviewed?
- Review high-change or high-consequence definitions on a stated cadence and after a material business change. The cadence matters less than recording the owner, evidence, and next review date.
Get the next guide
New guides and the occasional note on GTM tooling. Don't worry, I won't drop you into a three-month nurture.