Assumptions are the main way to set repeatable forecast logic on a row. Overrides are for one-off cell edits.
Use an assumption when you want a rule to drive a line over time. Use an override when you need one specific monthly cell to break from that rule.
Add or edit an assumption
Turn Assumptions on to show the row-level controls. To add one, use Add assumption on a row that has none; to change an existing one, click its method summary. The editor opens inline, right on the row.
Choose the right method
- Fixed - a repeated amount
- Growth - a growth rate over time, with an optional seed value
- % Of - a ratio against another source
- Days - timing logic for working-capital-style rows
- Manual - direct per-period values inside the assumption row
- Formula - custom calculation logic using drivers and supported references
Use date ranges intentionally
Each assumption has a start and end period, and one row can hold multiple assumptions covering different ranges. That is how you model one approach for the early forecast and a different approach later.
Use Override for one-off monthly edits
Override mode is for cell-by-cell exceptions.
Important: Override only works when monthly columns are selected.
If Override looks grayed out, select M in the period-column control first.
With M selected, turn Override on, click a forecast cell, and type the new value. Clear an override later from the cell context menu.
Use Override for exceptions. If the pattern should continue over time, make it an assumption instead.
Update many rows at once with Batch
Use Batch from the toolbar when many rows need the same method and date range.
The batch flow is:
- Click Batch in the top toolbar.
- Choose the statement in the modal.
- Select the accounts or sections you want to update.
- Choose the method and configure it in the footer.
- Set the date range.
- Click Apply Method.
Use the Delete tab in the same modal when you need to remove assumptions in bulk.
Watch out for
- Most assumption mistakes come from applying the right method to the wrong months. Check the date range.
- If the logic belongs to a schedule (employees, contracts, loans, and similar), build it in Schedules rather than cramming it into a statement-row assumption.