ADR / 012

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.

Reference pattern

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

  1. D01

    YTD performance must be reproducible

  2. D02

    Revisions must not rewrite the past

  3. D03

    One owner must be accountable for publication

  4. D04

    Segments, plans and reviews depend on the same target

03Options considered

Options considered: when each would be the right choice, what it costs, and the verdict under these premises
OptionRight whenCost / trade-offVerdict
Targets edited directly in the CRMOne team, one version, no revisionsNo history, no owner, silent overwritesRejected
Each report reads the planning spreadsheet and phases it itselfThe analysis is exploratory and nobody acts on the numberDifferent YTD answers for the same accountRejected
Versioned targets published from planning, read everywhereTargets that drive segmentation, recovery and reviewsA publication process and a planning ownerSelected

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.

  1. Reporting

    YTD performance can be reproduced for any past month.

  2. Versioning

    Revisions are visible as versions, not silent changes.

  3. Data quality

    Accounts without targets are a reported gap, not a disappearance.

  4. Ownership

    Planning gains an explicit publication responsibility.

06Revisit when

The decision holds while its context holds. Challenge it when:

01

Targets are set once a year and never revised.

02

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.

  1. Data case / 01Designing a governed commercial performance data modelA governed commercial performance model: orders, invoices, targets and customer context conformed at a declared grain, with explicit time, version, correction and currency semantics—so every metric is computed once and reproduces the same business meaning everywhere.Data & IntegrationsRevenue OperationsSystems & CRM ArchitectureArchitecture case · 12 min

Decisions this one depends on, or constrains.

  1. ADR / 002Place commercial KPIs by action horizonChoose CRM, data platform or warehouse from latency and actionability—not from one universal source-of-truth claim.Proposed patternAnalytics · CRM · Data
  2. 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.Proposed patternRevOps · Pipeline · CRM