A Capital Budget Can Look Healthy While Its Forecast Is Not
A hands-on MREF budgeting lab separates approved budget, available funding, contractual commitments and forecast final cost. Its unfinished approval path also shows why a convincing project summary is not automatically evidence of a working financial control.
A Capital Budget Can Look Healthy While Its Forecast Is Not
A facilities project can show little invoiced expenditure and still be heading beyond its approved budget. It can also show an increased budget without having received additional funding. These are not contradictions. They are different financial questions represented by different records, and a project review becomes unreliable when it treats them as interchangeable versions of the same balance.
Mohamed Chihaoui's MREF capital budgeting lab, published on October 22, walks through those distinctions on Maximo Real Estate and Facilities 9.2.3. Its chiller replacement scenario follows funding from a source through a program to a capital project and its cost codes. The figures are demonstration artifacts, not a customer outcome, a project estimate or a benchmark for replacement work.
The most instructive part is not a perfect success story. The newly created project remained in approval, and its contract did not populate commitment totals as intended. The author therefore uses a separate active demonstration project to explain populated commitments, invoices and forecast figures. That boundary matters: combining the two records into one seamless case study would conceal the operational condition that makes the controls meaningful.
Read the walkthrough as a financial acceptance exercise. What does each number claim to represent? Which underlying records must exist before that claim is reliable? Which approval state permits the expected roll-up? This article uses the lab's documented observations to build a proposed review method. It does not assume that the demonstration approval rules, amounts or organizational hierarchy should be copied into another implementation, and it does not replace the accounting policy that governs your own capital program.
Keep Funding, Budget and Authority Separate
The lab begins with a funding source carrying fiscal-year lines, then reserves money for a program and allocates funding to a project. This is a useful structure because approval of an overall capital envelope does not answer when money is released or which project may draw on it. A project budget and a project allocation are related records, not interchangeable evidence of spending authority.
The author's warning about fiscal-year lines deserves attention. The Amount Approved field is not itself the available allocation: the lines are what count in the demonstrated workflow. A reviewer who checks only the headline field can miss an incomplete release schedule. For implementation acceptance, compare the issued source record with its fiscal-year details and the downstream allocation rather than relying on a name that sounds financially authoritative.
There is also a small inconsistency in the published narrative. Its program section describes a remaining reserve in prose that differs from the available amount shown elsewhere in the same walkthrough. Do not propagate the disputed reserve as a planning fact. Use the actual record and fiscal-year evidence in your own test, and reconcile any disagreement before issuing a management report. A useful lab can still contain an editorial error.
The project-level distinction is clearer. The lab establishes an original budget of 840,000, then issues a budget change of 65,000. It reports current budget of 905,000 while total funding remains 840,000. The author explicitly warns that the change adds budget, not money. A further allocation is required to close the funding gap. Those are the lab's stated figures, not a recommendation for your approval limits.
Turn this into a proposed control: every approved budget increase should trigger a separate review of funding sufficiency and timing. The review should identify the relevant fiscal years, the source of additional allocation and the person authorized to commit it. Whether the workflow technically blocks a mismatch is a configuration question to verify, not a safeguard to assume because both fields appear on the same page.
For a facilities program manager, the practical benefit is a more precise exception list. One project may need scope approval, another a fiscal-year allocation, and another an unresolved reviewer decision. Label those conditions separately. Calling all three a budget issue makes it harder to assign ownership and encourages teams to repair the easiest visible number instead of the missing authority underneath it. Each exception should retain its record reference and responsible reviewer.
Preserve the Baseline and Explain Every Movement
The lab treats the original budget as a separate document. Once issued, the baseline is locked in the demonstrated workflow, while later transfers and changes remain distinct records. That is the important governance pattern: preserve what was originally approved, then explain how the current position came to differ. A current total without its movement history cannot answer the question a sponsor eventually asks.
A transfer and a change answer different questions. The walkthrough moves budget from contingency to another cost code within the same project, leaving the project total unchanged. It then adds budget through a separate change document when the tender exceeds the estimate. The first event reallocates existing permission; the second changes the overall budget. Neither should be disguised as an edit to the original estimate.
Use those events as separate acceptance cases. For an internal transfer, inspect the source and destination cost codes and the issued transfer record. Confirm that the movement has the intended effect on each code without creating an unintended project-level increase. For a change, inspect the new authority and the current total while retaining the original baseline. These are proposed verification steps, not claims about every possible customization.
Keep contingency visible in that history. In the lab, contingency has its own cost code and its use is documented through a transfer. That makes the reason for consuming it available to a later reviewer. Your own cost structure may differ, but hiding contingency inside another package makes it harder to distinguish an estimating adjustment from the deliberate use of a risk allowance.
Avoid treating the demonstration cost codes as an industry mandate. The post uses a construction-style hierarchy in its sample project, including mechanical, electrical and contingency lines. The relevant implementation decision is whether your code structure supports the required financial ownership and reporting. Agree the relationship with finance codes before loading transactions. A familiar label is not enough if the receiving accounting or reporting system interprets it differently.
Finally, test the visibility of the history, not just the calculation. Ask a reviewer who did not enter the documents to explain why current budget differs from original budget. They should be able to identify the issued movements and their business reasons without a developer reconstructing the story. If the explanation depends on private spreadsheets or someone remembering the workshop, the baseline may be technically preserved while the governance evidence remains inaccessible. Repeat that review after promoting the configuration to another environment.
Commitments Reveal Exposure Before Invoices Arrive
The lab defines current commitment as original commitment plus approved change orders. It defines uncommitted cost using current budget less current commitment and pending commitment changes. That model separates money already promised from money already invoiced. A review focused only on actuals misses obligations that have not yet reached the invoice stage, even though those obligations can already constrain the project manager's options.
The walkthrough's approval problem makes this distinction operational. Its new project remained in its approval step when the contract was issued, and the commitment lines stayed at zero. The author warns to activate the project before issuing contracts in this workflow. Do not reinterpret those zeros as proof that the project has no commercial exposure. They show why a summary must be read with the underlying procurement records and project state.
For acceptance, follow one controlled contract from its source record to the project summary. Preserve the project state, contract state, assigned cost codes and resulting commitment figures. If the summary remains unchanged, investigate the prerequisite rather than entering an offsetting adjustment to make the total look right. A compensating entry can conceal a workflow defect and make later reconciliation more difficult.
Pending changes also need their own review. The lab describes open change orders as pending commitment changes and approved ones as moving into change orders. Because the demonstrated uncommitted calculation includes pending changes, a reviewer should not treat unsigned exposure as invisible. Establish how your policy distinguishes an expected scope change, a formally raised change order and an approved contractual amendment, then verify how those stages appear in your configured workflow.
The invoice path is another separate event. The lab builds invoices from the contract's schedule of values and shows retention and the amount due. That is a reminder not to collapse commitment, actual cost and cash payment into one label called spent. Different owners may need each view for different decisions. Finance should confirm the sign conventions and accounting treatment used in your implementation before the figures enter executive reporting.
A useful review question is therefore broader than how much remains. Ask what has been approved, what has been promised, what is pending, what has been invoiced and what has been paid. Require each answer to point to its underlying records. The purpose is not to create a longer meeting. It is to stop a low invoice total from supplying false reassurance when the commercial commitment has already consumed most of the room to maneuver.
Read Forecast Final Before Celebrating a Calm Variance
The walkthrough distinguishes forecast final from the actual-to-budget variance shown on the project. Its forecast final combines current commitment, potential change orders and forecast to complete. Its displayed budget variance compares actual cost with current budget. These answer different questions: one concerns the expected destination, while the other describes expenditure relative to budget so far. Neither should be relabeled to make a dashboard easier to sell.
The active demonstration project makes the difference explicit. The post reports current budget of 308,600, current commitment of 296,655 and forecast final of 378,955. It also reports actuals of 7,100. Those are source-provided demonstration values. The low actual amount does not negate the higher forecast final, because much of the work's financial consequence has not yet become invoiced expenditure.
A proposed management review should therefore place current budget and forecast final together, with the basis of the forecast available underneath. Ask who supplied the remaining estimate, when it was reviewed and which expected changes it includes. A forecast is not reliable merely because it participates in a formula. Its completeness and ownership matter as much as its arithmetic, particularly when the project includes owner-managed costs outside the main contract.
Prevent double counting by distinguishing forecast to complete from amounts already committed. The lab describes forecast lines for costs still to come outside the contract, alongside potential changes. Your implementation must establish how those categories interact and what moves between them as scope becomes contractual. Do not assume every planner uses the same meaning for remaining cost. Document the rule and prove it with a controlled example.
Keep freshness visible as well. The lab notes that the project summary did not refresh while its form remained open; the author closed and reopened it to see the updated figures. Treat that as an observed user-interface behavior, not evidence of a general data-processing delay. In your acceptance exercise, use a repeatable refresh method and retain the underlying issued records so a stale view is not mistaken for a failed financial event.
The review should finish with a decision, not only a color. If the expected final cost is outside the authorized envelope, identify the required scope, budget or procurement action and its owner. A dashboard that correctly signals exposure but leaves no one responsible for responding is an incomplete operating control. The forecast's value is the opportunity to act before the invoice history catches up with the obligation.
Drill Into Cost Codes and Keep the Case Study Honest
The lab's active example shows why the project total is only the opening question. Its Site Construction code carries current budget of 16,200 and forecast final of 95,000, while the larger Mechanical package is below its budget on the displayed forecast. The post uses that contrast to locate the source of the overall problem. These are demonstration records, not evidence that a particular construction package normally overruns.
For facilities teams, the implication is to review both the project envelope and the packages that consume it. A favorable total can conceal an unfavorable package when another package has unused room. Whether that room may be transferred is a governance question, not something a consolidated chart should decide implicitly. Preserve the distinction between a forecast offset and an approved movement of budget.
Build the drill-down into acceptance. Select a project, inspect its cost-code hierarchy and trace a material movement back to its source document. Confirm that the reviewer can distinguish a parent summary from a transaction-bearing detail code. If a reporting export changes the hierarchy, document the transformation and test the resulting totals. A number that reconciles only after undocumented spreadsheet intervention is not yet a controlled portfolio measure.
The lab also explains that MREF is not the general ledger and describes finance integration as a question of which system leads for each type of data. Use that as a design prompt, not a universal ownership rule. Agree which system owns approved funding, contracts, invoices and payments in your estate. Then require common mappings for projects and cost codes so the same event can be reconciled across systems without being counted twice.
For broader portfolio reporting, the author describes an analytics layer that can reshape project data across asset classes or zones. Before building that view, determine which classifications each project must carry and who maintains them. Do not infer that a project-program hierarchy automatically supplies every management hierarchy. Missing classifications become reporting exceptions, and filling them after the fact introduces judgments that should remain visible to reviewers.
Keep the lab's two project populations distinct throughout any demonstration. The new chiller project proves budget-document creation and exposes an approval blockage. The active example illustrates populated commitments and actuals. Neither alone proves an end-to-end implementation in your environment. A defensible case study says exactly which record supports each observation, which steps remain unresolved and what must still be exercised before an operating team can rely on the financial controls.
Practical Implications
For a capital program owner, request a short evidence pack for a representative nonproduction project. It should connect fiscal-year funding, issued baseline, approved movements, contractual commitments, invoices and the current forecast. Require the project state to appear alongside the figures. That prevents an approval blockage from being misread as available budget simply because commitment lines remain empty.
For an MREF implementation lead, build separate acceptance cases for a transfer, a budget change, a funding allocation and a contract event. Exercise the required approvals under the intended roles rather than substituting an administrator's extra review. The lab reports that an additional approved review did not remove an outstanding required review; your configuration needs its own verified evidence.
For finance, agree ownership and reconciliation before connecting systems. Review cost-code mappings, fiscal-year interpretation and the treatment of invoices, retention and payment. Treat the published walkthrough's inconsistent reserve prose as a reminder to reconcile records instead of repeating a plausible narrative.
For reporting teams, label actual-to-budget variance honestly and show forecast final separately. Make the cost-code drill-down available and record when the underlying information was refreshed. These are proposed operating controls, not features assumed to exist in every installation. The deliverable is an explainable decision about exposure, supported by the right records, rather than a visually reassuring total whose meaning changes between meetings.
Bottom Line
A healthy-looking capital summary is not enough. Funding, approved budget, contractual commitment, actual cost and forecast final describe different parts of the same project, and each needs evidence appropriate to its meaning. Combining them into one remaining balance removes precisely the distinctions that help a facilities team intervene early.
The MREF walkthrough is useful because it shows both financial structure and an unfinished workflow. Preserve that honesty when applying it. Do not present the new project's budget documents and the active project's commitments as one completed customer journey. Do not copy a disputed reserve figure when the underlying records need reconciliation.
Use the lab to design your own end-to-end acceptance exercise. Follow funding into an activated project, preserve its baseline, explain later movements and reconcile commitments before reviewing the forecast. Then drill into the package that drives the exposure and assign the next decision. A defensible capital review ends with a traceable explanation of what the project may spend, what it has promised and where it is expected to land.