FP&A and Forecasting Capability Assessment

Which statement best describes how the annual operating budget is produced today?

The budget is the objective-setting baseline that the COSO risk assessment component presumes: without specified objectives (Principle 6), variances cannot be defined and risk to the plan cannot be assessed. Classify the process by what actually happens, not by what the policy manual says - a budget that exists but is never compared to results is closer to no budget at all.

Official small-business guidance on budgeting, accounting basics, and financial projections.

Official guidance: SBA guidance for managing finances

• SBA guidance for managing finances

Is the annual budget approved before the fiscal year it covers begins, and is each department's plan owned by the manager accountable for delivering it?

Two failure modes dominate here: a calendar problem, where the budget is approved after the year starts and the first quarter runs unmeasured, and an ownership problem, where managers treat the budget as finance's document. Test ownership by asking who explains a department's variance at the monthly review - if the answer is the finance team, the budget is not owned.

A budget approved late or imposed without owner accountability cannot function as a performance baseline; fix the planning calendar and the ownership model before investing in tools. COSO 2013, Principle 6.

Official guidance: SBA guidance for managing finances

How is the forecast model itself built and maintained?

A driver-based model earns its keep when an assumption changes: one input moves and the full statement flow updates. COSO Principle 13 expects decisions to run on relevant, quality information; a forecast assembled from fragile linked files fails that test even when the arithmetic happens to be right. Judge the structure by the worst month of the year, not the best.

Use the interactive tool above to see how this applies to your situation.

Official guidance: SBA guidance for managing finances

Following a material change in assumptions, could the team deliver a complete reforecast - profit and loss through cash - within five business days, without manual rework across multiple files?

This is the practical stress test of model architecture: COSO Principle 9 expects the entity to identify and assess significant change, which is impossible if re-planning takes longer than conditions take to move. Time the last real reforecast from trigger event to reviewed output - memory flatters, the calendar does not.

Consolidate to a single driver-based model with one owner and version control; cadence and scenario work layered on a fragile model only multiplies the rework. COSO 2013, Principles 9 and 13.

Official guidance: SBA guidance for managing finances

When the forecast is refreshed, is each refresh reconciled to the latest month-end close, and does the horizon roll forward so leadership always sees at least the next four quarters?

Two disciplines are tested together: anchoring each refresh to reconciled actuals so the forecast cannot drift from the ledger, and rolling the horizon so the fourth quarter ahead is planned with the same care in month two as in month eleven. A fiscal-year-end horizon quietly starves next year's decisions - hiring, pricing, capital - of any forward view.

Install a rolling reforecast cadence reconciled to the close; a forecast that is stale or that ends at year end stops informing decisions precisely when they are being made.

Official guidance: SBA guidance for managing finances

Which statement best describes the monthly variance review against budget or forecast?

The dividing line is the action loop, not the report: COSO Principle 17 expects deficiencies to be communicated to the parties responsible for corrective action and followed to resolution. Test it by pulling three months of variance commentary and asking what changed as a result - if the honest answer is nothing, the loop is open.

Close the loop: commentary without assigned, dated corrective actions is reporting, not control - and the same variances will recur. COSO 2013, Principle 17. Stand up a monthly owner-level variance review with thresholds and assigned actions; an unread report controls nothing. COSO 2013, Principle 17. Institute routine budget-versus-actual analysis; without it the budget cannot function as a control and the forecast is never tested against reality.

Official guidance: SBA guidance for managing finances

Which statement best describes scenario planning and headcount integration in the forecast?

COSO Principles 7 and 9 expect risks and significant change to be identified and analyzed - in planning terms, that means a maintained downside case and sensitivities, not a one-time stress memo built for a financing. Headcount belongs inside the model because it is usually the largest controllable cost and the slowest to reverse; a plan that cannot say which hires the downside case defers is not integrated.

The risk assessment component (Principles 6 through 9) frames objective-setting, risk analysis, and response to change that scenario planning operationalizes.

Official guidance: SBA guidance for managing finances

• COSO Internal Control - Integrated Framework

When results go to the board, lenders, or investors, do they see a consistent bridge from the last forecast to actual results, with forecast accuracy tracked over time and changes in outlook communicated before they arrive as surprises?

Governance runs on trajectory, not snapshots: a board that cannot see how the last forecast resolved into actuals cannot calibrate how much weight the next one deserves. The test is whether a director could state the company's recent forecast accuracy from the materials alone - and whether bad news has ever reached the board first through the financial statements.

The core planning stack is in place; the remaining gains come from measuring forecast accuracy and deepening decision support. Build the forecast-to-board bridge: a standing reconciliation of prior forecast to actuals, tracked accuracy, and a no-surprises communication protocol. COSO 2013, Principles 14 and 15.

Official guidance: SBA guidance for managing finances