Plan Financial Management: Decide the Rules Before the Numbers
Two people can agree entirely on what a piece of work will cost and still be in a serious dispute about it. The disagreement is about whose money it is: whether the analyst's time is a project cost or an operational one, whether the licence bought in year one belongs to the project or to the service that inherits it, whether the ward staff covering during a decant are being paid for by the refurbishment. Arithmetic has nothing to do with it.
Those questions have answers, and the answers are much easier to obtain before any numbers exist. Section 2.4.2 of the PMBOK® Guide Eighth Edition treats the planning of financial management as work that precedes estimating, and the reason is visible in any project that skipped it: once a figure is on the table, every classification question becomes a question about who absorbs a shortfall.
What counts as the project's money
The boundary is the first thing to settle, and it is usually less obvious than people expect.
Internal effort is the standard argument. Some organisations charge project time at a rate and some treat their own staff as free because the salary is paid anyway. Both are defensible positions and they produce completely different business cases. What causes damage is the project that assumes one convention while its finance function applies the other, which surfaces at the first month-end and is never comfortable afterwards.
Capital and revenue sit in different pots with different rules, and in the public sector and healthcare they often cannot be moved between. Equipment, software licensed perpetually and physical works tend to be capital. Backfill, training delivery, temporary staff and support subscriptions tend to be revenue. A project that spans both is running two budgets with two approval routes, and it needs to know that on day one.
The end of the project's responsibility needs a date. Hypercare, the first renewal, the defect period, the cost of running two systems in parallel: each of these belongs to somebody, and the receiving service will have a view about which. Settle it while the question is theoretical.
How money moves and who may commit it
Commitment and spend are not the same event, and the plan should say which one is being tracked. A signed order commits the money; the invoice arrives two months later. Projects that report only invoiced spend look comfortably underspent right up to the moment they are not, because everything ordered is still invisible in the figures.
Approval thresholds belong in writing, with names against them. What the project manager can authorise, what needs the sponsor, what needs a board and what needs the finance director. Vagueness here does not prevent spending; it moves spending into informal channels where nobody records the decision.
Contingency needs an owner and a release rule. Money held for identified risks and money held for the unknown behave differently, and a project that cannot say who releases either will find that its contingency has been consumed by ordinary overruns before the risks it was held against have even occurred.
The funding profile is a constraint in its own right. Money that arrives in quarterly tranches, or is withheld until a gate is passed, or expires at the end of a financial year, changes what the plan can do. A spend curve that ignores when the money is actually available is an estimate, and not a usable one.
The decant nobody had funded
A hospital trust refurbished a ward in two halves so the service could keep running. The capital programme funded the works, the equipment and the professional fees, all of it properly estimated and approved.
Moving the patients was not in it. The decant needed agency nursing for eleven nights, portering out of hours and a temporary equipment hire, all of which were revenue costs. The project team had assumed they sat with the ward, because the ward was continuing to deliver care. The ward manager had assumed they sat with the refurbishment, because none of it would have happened without the works. Neither had raised it, because each was confident.
The first half completed. The second half stopped at a line of tape across the corridor while the revenue funding was found, which took most of a month and had to be taken from a budget that had other plans for it. Nothing about this was a costing error. Every figure in the estimate was sound, and the project still stalled, because one category of cost had never been allocated to a holder of money. Recognising which of these boundaries a particular project actually has to nail down, before it becomes a negotiation, is financial planning that Omega's PMP® Exam Preparation works through in detail.
What gets reported, and when it escalates
Agree the basis of the forecast before the first one is produced. A forecast built from commitments to date plus the remaining plan behaves differently from one built by extrapolating the burn rate, and both are legitimate. What is not legitimate is switching between them when one produces a more comfortable number, which is difficult to detect afterwards and destroys trust when it is.
Set the point at which a variance becomes somebody else's decision. A named percentage or a named amount, agreed with the sponsor, so escalation is a rule the project follows and not a judgement call made under pressure by the person the news reflects on.
For a PMP® candidate, the distinction worth carrying is between the cost of the work and the funding of the work. A scenario describing an approved budget, a competent estimate and a project that still cannot proceed is normally describing a funding constraint or an unallocated category of cost, and the response that helps is a conversation with the sponsor about money that exists, not a re-estimate.
The practical step is a single page agreed with your finance contact before estimating begins: what is in, what is out, who approves what, how the money arrives, and what triggers a conversation. It takes an hour, and it is the difference between a cost report people argue with and one they act on.
Interested in going further?
Holding a clear line between what a project's money covers and what it does not, while a sponsor and a service owner both have views, is a practical skill worth building deliberately. Omega's PMP® Exam Preparation covers financial planning, budgeting and cost control as one connected set of decisions.
The PMBOK® Guide Eighth Edition is where the relationship between financial planning, the budget and cost control is set out as one structure.
Ad · Amazon affiliate link.
References
A123: The PMBOK 8 Finance Performance Domain: What It Really Covers
A124: Cost Is Not the Same as Value
A125: Budget vs Cost Baseline vs Funding
A126: Contingency Reserve vs Management Reserve
A127: CPI and SPI Explained Without Formula Memorisation
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
