Govern targets as versioned data with a publication and freeze point
Publish targets from planning at a declared grain and phasing, freeze them per period and revise them as new versions—so year-to-date performance is reproducible.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01Context
Targets are agreed in spreadsheets and loaded into the CRM and the data platform by different people. Phasing differs by team, mid-year revisions overwrite earlier numbers, and accounts without targets drop out of reports. The same account shows different year-to-date performance depending on the report, and segments built on that performance flip without anything having happened.
02Decision drivers
- D01
YTD performance must be reproducible
- D02
Revisions must not rewrite the past
- D03
One owner must be accountable for publication
- D04
Segments, plans and reviews depend on the same target
03Options considered
| Option | Right when | Cost / trade-off | Verdict |
|---|---|---|---|
| Targets edited directly in the CRM | One team, one version, no revisions | No history, no owner, silent overwrites | Rejected |
| Each report reads the planning spreadsheet and phases it itself | The analysis is exploratory and nobody acts on the number | Different YTD answers for the same account | Rejected |
| Versioned targets published from planning, read everywhere | Targets that drive segmentation, recovery and reviews | A publication process and a planning owner | Selected |
Every option is right under some premises. The verdict applies to the context above.
04Decision
Set targets at one authoritative grain (for example account × product line × month) with a declared phasing. Publish each version from planning with an effective date; the CRM and the data platform read the published version and never edit it. Freeze each period at a declared date. A revision creates a new version from its effective date; closed months keep the version in force at the time. Every KPI declares which target (signed or budget) and which phasing it uses.
05Consequences
What this choice changes elsewhere in the system.
- Reporting
YTD performance can be reproduced for any past month.
- Versioning
Revisions are visible as versions, not silent changes.
- Data quality
Accounts without targets are a reported gap, not a disappearance.
- Ownership
Planning gains an explicit publication responsibility.
06Revisit when
The decision holds while its context holds. Challenge it when:
Targets are set once a year and never revised.
A planning platform provides versioning and publication natively.
07Where this decision is applied
The decision says why this path was chosen; each case shows how it takes part in a larger architecture.
08Related decisions
Decisions this one depends on, or constrains.
- ADR / 002Place commercial KPIs by action horizonChoose CRM, data platform or warehouse from latency and actionability—not from one universal source-of-truth claim.
- ADR / 011Define pipeline stages by business state and exit criteria, not probabilityA stage says what is true about the deal and what must happen to leave it. Probability and forecast category are derived from that—never typed in its place.