RevOps case / 04 · Target grain, versions & YTD logic

Designing a target model with explicit period semantics

A fictional RevOps case: one annual number, four possible year-to-date answers, and the model that decides which one is true.

Fictional scenario

Independently created. Contains no employer or client implementation detail, internal names or figures.

01The outcome

One published target per grain and period, with a declared phasing, a version history, a precedence rule and an owner—so YTD performance is reproducible and every change is visible.

The reality

The same account shows 90 % in one report and 101 % in another, because targets are loaded as numbers without phasing, version or owner.

Architecture question

What makes a target measurable during the year—and who decides when it changes?

Key decision

Treat targets as versioned, owned data published from planning at a declared grain and phasing, frozen per period, and read—never edited—by the CRM and the data platform.

ContextAnnual targets are agreed per account and product line in a planning spreadsheet, then loaded into the CRM and the data platform by different people. Some teams phase them linearly, others by last year’s seasonality. Mid-year revisions overwrite the original numbers. Year-to-date performance—the basis for segments, recovery plans and bonuses—depends on which copy a report reads.

Systems and partiesPlanningData platformCRMERP

02The reality · current state

How the business is steered today.

  • Two reports show different YTD performance for the same account and month
  • Mid-year revisions overwrite targets, so past months are re-measured retroactively
  • Accounts without a target silently disappear from performance reports
  • Signed targets and the finance budget are mixed in one column
  • Nobody owns publication; anyone with access can edit targets in the CRM
  • Targets in local currency are compared with actuals at a different rate

03Operating loop

Each step with what happens, who owns it and how often.

  1. 01Set

    Targets agreed at the declared grain: account × product line × year.

    Owner
    Sales leadership with finance
    Cadence
    Annual
  2. 02Phase

    Spread over months with a declared phasing—linear or seasonal—stored with the target.

    Owner
    Commercial planning
    Cadence
    Annual
  3. 03Publish

    One version published to the data platform and the CRM, with an effective date.

    Owner
    Commercial planning
    Cadence
    Per version
  4. 04Freeze

    Frozen per period at a declared date; later changes need approval.

    Owner
    Commercial planning
    Cadence
    Monthly
  5. 05Revise

    A revision creates a new version from an effective date; past months keep theirs.

    Owner
    Sales leadership, approved by finance
    Cadence
    Quarterly, if needed

The outcome of the last step changes the first one next period.

04Key dimension · Target grain, versions & YTD logic

A target is data plus governance

Each dimension has a grain, an owner and a rule. The lifecycle makes every change a version rather than an overwrite.

Target dimensions: grain, owner and rule
DimensionGrainOwnerRule
Account × product lineMonthCommercial planningThe authoritative grain; everything else aggregates from it
SalespersonMonthDerivedSum of the owner’s accounts—never set separately
Team and regionQuarterDerivedAggregated; a top-down gap is shown as unallocated
Business unitYearSales leadershipTop-down; must reconcile with the account sum
SubsidiaryYearFinanceLocal currency, converted at the planning rate
PeriodCalendar monthCommercial planningPhasing declared per target: linear or seasonal

Target lifecycle: every change is a version

  1. DraftCommercial planning

    Working numbers; not visible in the CRM

  2. ProposedSales leadership

    Top-down and account sums compared; gaps explained

  3. SignedSales leadership with finance

    The commercial commitment for the year

  4. PublishedCommercial planning

    Versioned and effective-dated; read by the CRM and the data platform

  5. FrozenAutomatic, per period

    Closed months cannot change

  6. RevisedSales leadership, approved by finance

    A new version from an effective date; history kept

Performance is always measured against the version that was in force for that month. That single rule removes most “why did last quarter change?” conversations.

05KPI contracts

Every measure with an owner, a cadence and an action.

KPI contracts: definition, owner, cadence and required action
MetricDefinitionOwnerCadenceAction
Performance to YTD target(Invoiced + open orders) ÷ phased target in force, year to dateSales operationsDaily; provisional until period closeFeeds segmentation and recovery
Target coverage of the customer baseShare of active accounts with a published targetCommercial planningAt publicationAssign targets or document exclusions
Unallocated gapTop-down target − sum of account targets, by unitSales leadershipQuarterlyAllocate, or accept the gap explicitly

06Accountability

Who owns what, decides what—and escalates to whom.

Commercial accountability: role, ownership, decision rights and escalation
RoleOwnsDecidesEscalates to
Commercial planningGrain, phasing, publication and freezeWhen a version is publishedSales leadership
Sales leadershipThe signed target and its revisionsWhether a revision is requestedExecutive team
FinanceBudget, currency and planning ratesApproval of revisions affecting the budgetCFO
Sales operationsYTD definitions in every KPIWhich version and phasing a KPI readsGovernance forum

07The trade-offs

Credible options, judged against these premises.

Rejected

Load a spreadsheet of annual numbers into the CRM

One team, no mid-year changes

Cost: No phasing, no versions, no owner
Rejected

Let each report phase and convert targets itself

Exploratory analysis

Cost: Different YTD answers for the same account
Selected

Versioned targets published from planning, read everywhere

Targets that drive segments, plans and reviews

Cost: A publication process and a planning owner

08The second layer

Questions that change the design.

Semantics

  1. Calendar or fiscal year?
  2. Linear or seasonal phasing?
  3. How are partial months treated?

Versions

  1. What happens when a target changes mid-year?
  2. Signed target or budget—which does each KPI use?
  3. Which target takes precedence?

Gaps

  1. What happens to accounts with no target?
  2. Which currency and rate apply?
  3. Who owns publication, and when is it frozen?

09Decisions & outputs

What the work produces.

  1. 01Target grain model
  2. 02Phasing rules
  3. 03Version and freeze lifecycle
  4. 04Precedence rules
  5. 05YTD definition
  6. 06Publication process