Skip to main content

Rolling Forecast Best Practice

To maintain a well-organized and efficient Adaptive Planning instance, I highly recommended to always use a single, continuously updated plan version, I like to call it “Rolling Forecast”. In Adaptive, this will be set as your default version. And it will show in bold in your version Dropdown.

This version will have the greatest and latest forecast inputs (and formulas logic)!


This approach of using always the same input version ensures clarity, consistency and ease of deriving locked versions!


How to Implement This Best Practice

Set Rolling Forecast as the Default Version

  • In Adaptive Planning, mark your Rolling Forecast version as the default one.
    • Menu > Modeling > Model Management > Versions > Select your latest forecast and set it to default on the right Pane.

  • It appears bold in the version dropdown, making it easy for all users to identify it.

Keep the Version Clean and Fast

  • Limit historical actuals overlay – Instead of keeping many years of actuals, consider keeping only the past 2 or 3 years in your Rolling Forecast version, to not overload it.
    • Note that this will NOT delete your actuals. You just hide prior years in that version.
    • Use the Actuals version for historical data – If you need to refer to older actuals, you can always pull them directly from the Actuals version
  • Remove old GL accounts and levels – If accounts or organizational levels are retired, exclude them from your Rolling Forecast version to keep it relevant and efficient.
    • For Levels, go to Menu > Modeling > Levels and on the Right Pane, select for which versions Adaptive should be available.

  1. Maintain a Single Forecasting Version

    • Use Rolling Forecast as your go-to version for ongoing updates.
    • Continuously refine this version with the latest financial and operational inputs.
    • Ensure that all formulas and logic are kept current within this version.

  2. Lock Versions for Key Planning Milestones

    • Once your forecast is finalized for a planning cycle, create a new version derived from your Rolling Forecast and lock it.
    • Examples of locked versions:
      • Annual Plan (FYXX) – After finalizing your yearly forecast.
      • Quarterly Forecast (Q1, Q2, etc.) – To reflect the latest forecast for a given quarter.
      • Monthly Outlook – If needed for short-term planning updates.

  3. Use Locked Versions to Generate Scenarios

    • From your locked versions, you can create scenario-specific versions to analyze different outcomes.
    • For example:
      • Annual Plan – Revenue Scenario A (Optimistic growth case)
      • Annual Plan – Revenue Scenario B (Conservative case)

Why This Approach Works

✔ Eliminates Version Confusion – Everyone works off a single, up-to-date Rolling Forecast until it’s locked.
✔ Reduces Formula Maintenance – Instead of updating multiple versions, you only maintain formulas in one place.
✔ Improves Forecast Accuracy – Ensures consistency in assumptions and calculations across all planning scenarios.
✔ Enhances Flexibility – Enables quick scenario analysis without disrupting your core forecast.
✔ Easier Navigation – The bold default version makes it clear which version should be used for updates.
✔ Faster Processing – Removing outdated accounts, levels, and unnecessary historical overlays keeps calculations efficient and speeds up processing.

By following this best practice, you keep your Adaptive environment structured, efficient, and easy to navigate—resulting in smoother planning cycles and better decision-making!

Would you like to add a checklist or additional performance optimization tips?

Labels:

Popular posts from this blog

Adaptive's API

To integrate data in Workday Adaptive Planning, customers typically use the integration module to connect with ERPs, SFTPs, AWS S3, Snowflake, SalesForce, Excel, and Google Sheets, etc.  You can also use third party platforms such as Tray.ai , Boomi , Matilion etc. which leverage Adaptive's APIs in a user friendly setup.  And lastly, you can write your very own scripts (C#, Python, Powershell...) to make these API calls.  Most  common Adaptive's API use cases Import Data from ERPs Actual summaries and transaction details (by supplier, employee...) Assets, amortization, depreciation Payroll details and taxes Import Sales data from CRMs or datalakes Pipeline, churn, opportunities and customers  Billings, bookings, revenue, ARR Import Headcount data from an HRIS Current headcount and terminations Hired, not started Wages and compensation plans Benefits and other demographics Import Other data: Exchange Rates Weather Meta data: currencies, attributes, dimensions suc...
Read more

One (perfect) Headcount Planning Process in Workday Adaptive for FP&A

FP&A: The Perfect Headcount Planning Process in Workday Adaptive for non Platform customers: Streamlining integration, reconciliation and budgeting This article is for companies that are not on the Workday Platform  (HCM, FINS, Adaptive) and are missing out on the integrated cycle of hiring, planning, reconciliation, and system-wide alignment that Workday offers. I sometimes hear complaints (luckily not too much) about Workday HCM, Adaptive or FINS... but the truth is, no other tool on the market currently offers a complete solution that spans the entire hiring process—from budgeting and requesting to hiring, reconciling, and publishing plans across systems. Workday is the only one with this capability right now!  I’m not paid by Workday to write this… But after working with several HRIS, ATS, and ERP systems, I can confidently say that Workday stands out for its customizable workflows, overall ease of use, and seamless communication across all three systems -- assuming yo...
Read more

Adaptive REST API Calls for Platform Customers with User Sync Enabled

How to Make Adaptive REST API Calls for Platform Customers with User Sync Enabled If you’re a platform customer (HCM + FINS + Adaptive) or using Workday HCM or Financials alongside Adaptive and want to create custom scripts leveraging Adaptive’s REST API (XML), you’ve likely encountered a key requirement: providing Adaptive user credentials (username and password). For standalone customers or those not using user sync, this typically involves creating an integration user in Adaptive. Easy peasy.  But what if you’re using user sync? How do you supply credentials for API calls in the XML input? In this article, I’ll guide you through the steps to generate the necessary credentials when user sync is enabled. I’ll also share helpful links to official documentation to ensure a smooth integration process. 1. Overview The process allows Workday-synchronized users to make API calls to Adaptive Planning using Workday credentials . The key steps involve: Generating an OAuth token using Work...
Read more