Case Studies

Tracing an Inherited Workday Adaptive Planning Forecast Model One Path at a Time

Tracing an Inherited Workday Adaptive Planning Forecast Model One Path at a Time

Platform: Workday and Workday Adaptive Planning

Scope: review of an existing forecast model built by an earlier team

The business problem

The finance team forecast revenue in the planning model with confidence. The model also had sheets for headcount, direct cost, overheads, shared services and allocations, built by an earlier team. Finance did not know how to forecast those lines with it, or how a number travelled from revenue to the management P&L.

Existing architecture

Revenue is driver-based and split across several sheets, one for each billing method. Below revenue sit headcount inputs, operating metrics, direct costs, shared services and overhead sheets, with allocations to region and line of business, and summary reporting.

Why it happened

The model was broad and not documented. Nobody could say which accounts were loaded from Workday, which finance entered, and which the model calculated. The sheets existed. The path through them was unknown.

Design decision

We avoided an immediate rebuild and began with one representative revenue path. We separated loaded source values, planner-entered drivers, assumptions and calculated accounts, recording each conclusion as confirmed, plausible or still unverified.

Implementation approach

  1. Pick one programme and its exact intersection: level, region, line of business, line item and revenue category.
  2. On each sheet in the path, record the intersection, the input accounts, the loaded accounts, the formula accounts, the assumptions used, and where the output goes next.
  3. Mark each important account as loaded, input, assumption, formula or output.
  4. Follow revenue drivers into headcount and operating metrics, then direct cost, then allocations, then the P&L.

Controls and validation

We marked each finding with its evidence status. One formula was confirmed directly in the tenant. Others were marked likely or unknown until inspected. We did not describe the integration as confirmed until the data sources and loaders were inventoried.

Outcome

One representative revenue-driver path was mapped and a downstream review approach was agreed. The rest of the path, through payroll, allocations and the management P&L, is the next stage of the review.

Lessons learned

Scope of the outcome

Representative revenue calculation path traced; full downstream mapping was outside the documented result.


EPMLogic | Implementation insight based on an anonymized scenario. Exact operational amounts and client details are intentionally omitted.

Workday Adaptive Planning
Related Insights

More from the architecture desk.

Diagnosing Workday Adaptive Planning Access Issues Layer by Layer
Case Studies

Diagnosing Workday Adaptive Planning Access Issues Layer by Layer

Platform: Workday and Workday Adaptive Planning with single sign-on Scope: user access requests for department budgeting...

Read more
How to Trace and Maintain a Project-Based Net-Zero Sweep
Case Studies

How to Trace and Maintain a Project-Based Net-Zero Sweep

Platform: Workday Adaptive Planning Scope: a net zero sweep on one revenue account, by project The...

Read more
Finding Why a Workday Adaptive Planning Elimination Posted to the Wrong Fund
Case Studies

Finding Why a Workday Adaptive Planning Elimination Posted to the Wrong Fund

Platform: Workday Adaptive Planning Scope: internal allocation eliminations in a fund-based planning model The business problem...

Read more