Financial Tailoring: Not Every Project Needs the Same Controls
Financial controls tend to arrive as a package. An organisation designs them for its largest and most exposed projects, quite properly, and then applies them to everything, because the template exists and nobody has been given permission to use less of it. The result is small projects carrying machinery built for programmes forty times their size, and it consumes management effort that the project cannot spare.
Section 2.4.3 of the PMBOK® Guide Eighth Edition covers tailoring considerations for the finance work, and proportion is the whole of the idea: the controls should match what is actually at stake.
What sets the level
Size and exposure. Not only the budget, but what a failure would cost: a small project that can stop a production line matters more financially than a larger one that cannot. Judging exposure rather than headline value is what stops a portfolio applying its controls by budget band alone.
Uncertainty. Well-understood work with firm prices needs little monitoring; first-of-a-kind work with cost-reimbursable elements needs a great deal, because that is where the money can move without anybody intending it. Control effort should follow where the variance can actually come from.
Contract type. A fixed-price package needs verification that the work was delivered and very little else. A time-and-materials arrangement needs somebody checking hours and rates every month, and an organisation that chose that contract type without resourcing that check has bought an exposure it is not watching.
Funding source and audit regime. Public money, grant funding, regulated capital and partner investment bring requirements that are not negotiable, and they set a floor under everything else. Knowing that floor early prevents both under-control and the more common failure of over-applying it to work that never needed it.
What can be dialled down
Frequency. Monthly cost reporting on a project that spends in three lumps is producing nine reports that say nothing. Reporting aligned to when money actually moves is both cheaper and more informative.
Granularity. A cost breakdown structure with sixty lines on a project with four suppliers describes precision the project does not have. Fewer, meaningful lines that somebody can actually check beat a detailed structure that gets filled in by estimate.
The machinery. Full earned value on a small project costs more in setup and maintenance than the insight is worth. A simple comparison of committed cost against delivered work, done honestly, answers the same question at a fraction of the effort.
A sensor and three ring binders
A pharmaceutical site replaced a temperature sensor on a process skid: a small piece of work, about forty thousand pounds including the validation, taking six weeks.
It ran under the site's capital project controls, because it was capital. That meant a full cost breakdown structure, monthly cost reporting with variance commentary, a change control board for anything above two thousand pounds, and a stage gate pack at each of three gates.
The validation office desk told the story plainly enough. The sensor sat sealed in its labelled bag in the middle of the desk, and beside it stood a lever-arch file too full to close, propped open with tabbed dividers, with two more binders stacked behind it.
Somebody measured the effort afterwards. About eleven days of project management and engineering time went on financial control and gate documentation, against roughly nineteen days of actual work. The controls found nothing, which was the correct outcome for a project with one supplier, one fixed price and no uncertainty worth the name.
The site introduced a small-project route: fixed-price work under a stated value, with a named approver, one gate, cost reported at completion, and the same audit trail requirements as everything else. The controls that mattered were kept and the machinery around them was not. Three similar projects the following year averaged two days of control effort each.
What never gets tailored away
The audit trail. Who approved what, when, and on what basis. This is cheap to maintain, it is what regulators and auditors ask for, and it is the thing organisations most regret losing. It survives every level of tailoring.
Authority limits. What a project manager may commit without asking. Tailoring can raise or lower the threshold for a particular project; it cannot remove the need for one, and a project operating without a stated limit is operating on assumption.
For a PMP® candidate, the point to hold is that control effort should be proportionate to exposure and uncertainty, so a scenario about heavy process on a small project is asking what the controls are actually protecting against. A response that applies the standard framework has not made a tailoring decision at all. Situations where the controls are correct for a larger project and wrong for this one are a recurring theme in a structured PMP exam preparation course.
Add up the hours your own project spends each month on financial reporting and control, and set that against the money genuinely at risk of moving. If the first number is large and the second is small, there is a conversation worth having with whoever owns the framework, and it usually goes better than people expect.
Interested in going further?
Controls designed for the largest projects get applied to the smallest because nobody has the standing to use less of them. Omega's PMP® Exam Preparation works through proportionate control as a deliberate decision.
Tailoring considerations for project finance are set out in the PMBOK® Guide Eighth Edition.
Ad · Amazon affiliate link.
References
A077: Tailoring in Project Management: What It Actually Means
A165: Tailoring Risk Management to the Project
A141: Tailoring Stakeholder Engagement for Different Contexts
A122: Tailoring Schedule Management for Adaptive Delivery
A151: Tailoring Resource Management for Agile and Hybrid Teams
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
