Documentation Revenue Goal Year Goals Workflow
Detailed guide

Year Goals Workflow

The year-goal publication workflow for turning calculator outputs into approved annual targets used across planning and performance views.

Year Goals Workflow is the handoff from modeling to operational commitment. Calculator values can change frequently, but approved year goals establish the fixed planning benchmark used by portfolio and reporting views. This page ensures that what the team measures against is deliberate, traceable, and role-controlled.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Create next-year target records before annual planning sessions start.
  • Update unapproved targets when assumptions change materially.
  • Add brief notes describing why a target differs from calculator output or prior year.
  • Lock the selected year once leadership alignment is complete.
  • Validate approved status before monthly performance reviews and variance conversations.
  • Re-open planning discussions through calculator assumptions instead of repeatedly editing locked targets.

Put it into practice

  1. Open Revenue Goal and switch to the Year Goals tab so you are editing published annual baselines instead of raw calculator assumptions.

    InteractionsRevenue Goal page: click Year Goals in the top tab rail.
    Open workflow: Revenue Goal

  2. Review existing rows first: year, amount, approval state, and notes should confirm whether you need a new record or an update to an unapproved one.

    InteractionsPlanned Revenue Goals by Year table in the Year Goals tab.

  3. Use Add Year to create a new planning year and populate Revenue Goal from calculator suggestion only after calculator assumptions are validated.

    InteractionsYear Goals tab: click Add Year, then use the calculator suggested amount link when appropriate.

  4. Add concise notes explaining target logic, then save. Notes should capture rationale that future reviewers can understand without revisiting assumptions from scratch.

    InteractionsAdd Year or Edit form: complete Notes field before saving the year record.

  5. Approve and lock the intended year when alignment is complete so downstream pages stop drifting with live calculator edits.

    InteractionsYear Goals table row actions: use Approve on the selected year.

  6. Confirm downstream alignment in At A Glance by checking that yearly pacing and Difference metrics now reflect the approved baseline.

    InteractionsOpen At A Glance and review top summary cards for the same year.
    Open workflow: At A Glance

What to review

Year Goals tab context

Separates annual baseline management from calculator assumption modeling so plan publication is controlled and explicit.

Planned Revenue Goals by Year table

Shows year, target amount, approval state, and notes; this is the authoritative list for annual goal baselines.

Add Year form

Creates a new year target record with amount and rationale notes before approval.

Calculator suggestion helper

Copies current calculator output into the year goal amount field so publication aligns with modeled assumptions.

See guide: Revenue Goal

Edit Year Goal action

Allows controlled updates to unapproved year records while preserving year-level planning lineage.

Approve and lock control

Marks a year as approved and prevents casual edits so downstream planning can trust one stable baseline.

Downstream pacing linkage

Approved year goals feed portfolio pacing checks in At A Glance and should be verified before interpreting yearly gaps.

See guide: At A Glance

Guardrails

  • Approved year goals should be traceable to explicit calculator assumptions or documented strategic adjustments.
  • Only one planning baseline should be treated as authoritative per active year period.
  • Year-goal records should include sufficient notes when values diverge from calculator output.
  • Lock state should be respected; edits should occur through controlled update paths before approval.
  • At A Glance pacing interpretation is only valid when the intended year is approved and selected.
  • Create, edit, approve, and delete year goals should be restricted to planning owners and finance/accountable leadership roles.
  • Broader teams may need view access without publication rights to prevent accidental target drift.
  • Approval actions should be auditable and aligned with ownership of annual operating commitments.

If it starts drifting

  • If yearly pacing looks wrong, confirm the year is approved before questioning downstream charts.
  • If a target cannot be edited, verify lock state and role permissions first.
  • If calculator and year-goal values differ unexpectedly, inspect notes and last update context before overwriting.
  • If duplicate years appear in planning discussions, reconcile to one approved baseline and archive confusion in notes.
  • If teams keep changing annual targets mid-cycle, tighten approval governance and separate scenario planning from published goals.