Corporate performance management connects plans, actual results, forecasts, and decisions. A useful monthly review explains what changed, whether the explanation is supported by evidence, and what someone will do next.
The term often overlaps with enterprise performance management (EPM). Oracle’s explanation of EPM includes planning, budgeting, forecasting, reporting, and financial consolidation and close. Here the focus is a compact management review that a small organization can run without buying a large planning platform.
Keep the budget, forecast, and actuals distinct
A budget is the approved plan or target for a defined period. A forecast is the current estimate of what will happen, based on stated assumptions. Actuals are recorded results using an agreed accounting basis and cutoff. Replacing the original budget with the latest forecast makes it harder to see how expectations changed.
Keep versions with dates, owners, and assumptions. For a year-end estimate, use actual results for completed months plus a forecast for the remaining months, without counting a month twice. A rolling forecast keeps a chosen forward-looking horizon as periods close. Neither method makes uncertain demand predictable; both make assumptions available for discussion.
Business intelligence tools help query and display information. A performance-management process adds planning assumptions, ownership, review decisions, and follow-up. Employee performance appraisal is another use of the phrase “performance management”; it is not the subject here, and a company-level variance is not by itself evidence of an individual’s performance.
Worked monthly review: more jobs, lower profit
Fictional teaching example: a service company reviews one month in USD. All jobs are comparable, revenue is recognized for the same period, and direct cost is modeled per completed job. This simplified management model excludes tax, interest, depreciation, working capital, and other accounting adjustments. It is not a complete financial statement.
On a small screen, scroll the table sideways to read all columns.
| Measure | Budget | Actual | Actual minus budget |
|---|---|---|---|
| Completed jobs | 400 | 440 | +40 |
| Average revenue per job | $250 | $235 | −$15 |
| Revenue | $100,000 | $103,400 | +$3,400 |
| Direct cost per job | $150 | $160 | +$10 |
| Total direct cost | $60,000 | $70,400 | +$10,400 |
| Contribution after direct costs | $40,000 | $33,000 | −$7,000 |
| Fixed operating cost | $25,000 | $26,000 | +$1,000 |
| Modeled operating profit | $15,000 | $7,000 | −$8,000 |
Revenue rose 3.4%, but modeled profit fell $8,000, or 53.3% relative to the $15,000 budget. More jobs did not offset lower revenue per job and higher direct cost per job. A positive variance means only “actual is larger” in this table: it is favorable for revenue in isolation and unfavorable for cost in isolation. Business context can still change that interpretation.
Download the editable monthly performance example (Excel). Amber cells contain invented inputs; formulas calculate results and a revenue bridge. Replace the assumptions with comparable figures and keep the model’s exclusions in view.
Explain the revenue difference with a bridge
For this single-category example, separate the $3,400 revenue increase into two components. Value the volume change at the budget price: (440 − 400) × $250 = +$10,000. Then value the price change at actual volume: 440 × ($235 − $250) = −$6,600. Together they equal +$3,400 exactly.
This particular convention assigns the interaction between price and volume to the price component. Another convention can allocate that interaction differently, so label the method when comparing reports. If the business sells different kinds of jobs, an average price can also change because the mix changed. Analyze comparable categories before claiming that every price was reduced.
The arithmetic identifies where to investigate; it does not establish the cause. Check whether discounts, job mix, credits, or a cutoff issue explain the lower revenue per job. Examine scheduling, overtime, subcontracting, or material costs to explain the direct-cost increase. Keep an explanation such as “more low-priced jobs” separate from evidence that verifies it.
Turn the review into a small set of decisions
Give each material issue an owner, action, due date, and expected evidence. In the fictional company, the commercial lead could review discounted work by job category, while the operations lead checks the jobs with unusually high direct cost. Set the next forecast from supported assumptions instead of copying the budget because it is the target.
Use both outcome measures and operational measures. Profit and revenue describe results; queue age, rework, and unfilled appointments can help explain how the next period is developing. Avoid treating any operational indicator as a guaranteed predictor. A faster process that creates more returns may worsen the outcome it was meant to improve.
Keep cash separate from profit. A profitable month can still create a cash shortage if collections arrive later than supplier and payroll payments. Add a cash forecast when timing matters; the sample workbook deliberately does not estimate bank balances. Choose tools according to the decisions, number of contributors, version control, and reconciliation needs.
Make the numbers comparable and reviewable
Write down each measure’s definition, unit, period, source, owner, and treatment of corrections. Compare like with like: the same business scope, currency, tax treatment, and accounting basis. Freeze a reviewed version, then label subsequent adjustments so that people can reproduce the conversation.
When combining systems, decide the level of detail before joining data. Microsoft’s star-schema guidance explains the roles of fact and dimension tables and the importance of consistent fact-table grain. In practice, joining each invoice total to several job-detail rows can duplicate revenue. Reconcile totals to the source before building an attractive dashboard.
AI can draft a variance narrative from approved tables or flag a mismatch for review. Require it to show the figures used and distinguish calculation from proposed explanation. Verify its arithmetic independently and prevent it from presenting a hypothesis as a confirmed cause. The review is complete when the numbers reconcile and the resulting decisions have owners—not when the commentary sounds confident.