Change control
Change control is the governed process for proposing, reviewing, releasing and recording modifications to the revenue system, its fields, definitions, automations and stage criteria.
Revenue systems accumulate change from many hands: an admin adds a required field, a marketer edits a lifecycle rule, an analyst modifies a metric. Each is individually reasonable and collectively corrosive, because each has downstream consumers the author cannot see.
Effective change control is proportional. It does not gate everything; it gates the shared substrate, definitions, stage criteria, required fields, routing rules, with review by the functions that consume them, a recorded rationale, and a release note that makes the change visible to reporting.
Where it breaks
A picklist value is renamed in production on a Friday and every historical report segmented by it breaks silently.
Related terms
- Revenue operations (RevOps)
- Revenue operations is the governing function that enforces coherence across marketing, sales, customer success and finance by owning shared definitions, data models, process boundaries and change control.
- Metric definition
- A metric definition is the governed specification of a measure, its formula, source fields, filters, grain, owner and known limitations.
- Revenue data model
- The revenue data model is the set of objects, relationships and required fields that every revenue-facing process reads from and writes to.
- Runbook
- A runbook is the documented set of reviews and maintenance tasks required for named decisions, with owners, evidence, outputs, and retirement conditions.
Field notes on this
- You just inherited RevOps. Start with a charter.
Being told to "own revenue operations" is not a mandate. Until authority is written down, every decision you make is reversible by whoever objects loudest.
- Why four teams report four different revenue numbers
A reconciliation problem may be definitional, technical, or both. Test the metric contract before buying another data platform.