6-lesson course · about 2 hours
Know why the forecast moved: model logic, an assumption, or a scenario
For CFOs, controllers, FP&A teams, accountants and finance operations professionals
Everything for Finance teamsA focused 2-hour course for FP&A analysts: keep assumptions in one register, run scenarios as named versions of it, and log every driver change with its effect, including AI-drafted entries you check.
What you’ll be able to do
By the end, you can…
How it works
A tutor that meets you where you are
- Lessons that adapt to your levelSix lessons across two modules. Later lessons are written for your level as you reach them, so the examples and depth match how you already work with forecast models.
- An AI tutor you can ask anythingAsk questions by typing or out loud: how to structure your register, why a scenario switch moved a line, or how to split the effect of two changes made at once.
- Quizzes and flashcards for each lessonShort quizzes and flashcards tied to every lesson help you check your understanding and remember the register fields, log structure and tracing steps.
- Progress tracking and a certificateSee where you are across the course, pick up where you left off, and receive a certificate of completion when you finish.
Curriculum
The curriculum
The course runs in two modules: first you give assumptions and scenarios their own place in the workbook, then you log, check and trace every driver change. Each lesson builds on the one before.
Module 1Give Assumptions and Scenarios Their Own Place3 lessons
1Split the Workbook into Logic, Inputs and Outputs
- Distinguish a logic change, an assumption change and a scenario switch in a given forecast movement
- Spot driver values hardcoded inside formulas, such as =B5*1.04
- Restructure a forecast workbook into separate input, calculation and output areas
2Build an Assumptions Register
- Build an assumptions register with value, unit, source, owner and effective date for each driver
- Write a source entry that shows whether a driver is confirmed or provisional
- Link model formulas to register entries so each driver has a single home
3Define Named Scenarios as Versions of the Register
- Set up base, upside and downside scenarios as named versions of register values
- Build a scenario selector that switches the model's active values without overwriting any of them
- Write scenario names and descriptions that state what differs from the base case
Module 2Log, Check and Trace Every Driver Change3 lessons
4Log Each Driver Change and Its Effect
- Write a change log entry with driver, old value, new value, effect, scenario and date
- Calculate the effect of a single driver change by comparing a key output before and after it
- Separate the effects of several simultaneous changes by applying them one at a time
5Draft Change Log Entries with AI and Check Every Claim
- Prepare a structured input that an AI assistant can turn into a change log entry
- Check every number, direction, unit, period and scenario name in an AI-drafted entry against the model's outputs
- Confirm an AI tool is approved for nonpublic financial data before sharing any figures, and keep customer identifiers out of every prompt
6Trace a Forecast Movement Back to Its Cause
- Trace a forecast movement between two versions using the scenario selector, the register and the change log
- Decide whether a movement comes from model logic, an assumption or a scenario choice
- Reconcile logged effects to the total movement and spot an unexplained remainder
Who it’s for
Made for you if…
Made for: CFOs, controllers, FP&A teams, accountants and finance operations professionals
FP&A analysts maintaining driver-based forecasts in Excel or a planning tool
You want assumptions out of formulas and scattered tabs, and into one place where anyone can see the value, source and owner of each driver.
Analysts who present forecast movements to controllers, CFOs or budget owners
When someone asks why the number changed since last week, you want to name the driver, the assumption, the scenario and the effect without an hour of digging.
Analysts starting to use AI assistants for finance documentation
You want a clear way to let AI draft change log entries, check each claim against the model, and keep nonpublic data and customer identifiers out of unapproved tools.
Questions
Good to know
What do I need to know before starting?
You should have working knowledge of a driver-based forecast model, including linked formulas and input cells, experience running at least one what-if or scenario comparison, and familiarity with using an AI assistant to draft text.
How long does it take?
About 2 hours across six self-paced lessons.
Does it work in Excel or only in a planning tool?
The course is written for analysts who maintain driver-based forecast models in Excel or a planning tool. The structure it teaches (separate inputs, a register, named scenarios and a change log) applies to either.
Does the course cover building a forecast from ledger data?
No. Building the forecast from source data, ledgers or chart-of-accounts mapping is out of scope, as are reconciling actuals, currency translation and consolidation. The course starts from a forecast model you already have.
Does it teach statistical forecasting methods?
No. Statistical forecasting and probability models are not covered. The focus is on organising assumptions, scenarios and driver changes so movements are easy to explain.
How does the course handle data safety when using AI?
Lesson 5 covers confirming an AI tool is approved for nonpublic financial data before you share any figures, and keeping customer identifiers out of every prompt. The course does not recommend or approve specific AI or planning software.
Will it help me write management commentary?
Writing management commentary and presentation narrative is not covered. The course gives you a checked change log that explains each driver change and its effect, which you can then draw on.
Do I get a certificate?
Yes, you receive a certificate of completion when you finish the course.