Funding Limit Reconciliation

Cost technique · See it on the map

Runnable here

Reshaping planned spending so it never asks for more money than is actually available each period.

When to use it

Whenever the funding organization releases money on a schedule — annual appropriations, quarterly capital releases, tranche-based investor draws — that doesn't automatically match the project's natural spend curve. Check it as soon as a period-by-period funding schedule exists, not after a period's spend has already been planned past its limit.

When to avoid it

Don't reconcile against funding limits that are still provisional or under negotiation — smoothing the schedule against a number that later changes wastes the exercise. And don't treat this as purely a cost problem: reshaping planned spend to fit a funding limit almost always reshapes the schedule too, since the work that generates that spend has to move with it.

Steps

1. Lay the planned spend curve (from the cost baseline) against the funding limits published for each period.
2. Find every period where planned spend exceeds the available funding.
3. Resequence or delay the work driving the excess into a period with headroom, rather than assuming the limit will flex.
4. Re-check the schedule for any downstream effect the resequencing causes — a delayed activity can push dependents past their own dates.
5. Republish the reconciled spend curve as the version the project will actually execute against.

What it produces

• A spend curve where planned cost in every period sits at or below that period's funding limit.
• A documented list of activities moved to fit funding, and the schedule impact each move caused.

Common pitfalls

• Moving work to fit the funding limit without re-checking the schedule network — the delayed activity's dependents slip too, and that schedule impact goes unreported until it surfaces on its own.
• Treating the reconciled curve as a one-time fix instead of rechecking it every time funding limits or the spend forecast change.
• Smoothing spend into future periods so consistently that later periods quietly become overloaded, just moving the mismatch instead of resolving it.

Worked example

A public infrastructure project's total budget is fully approved at $6 million, but the funding authority releases it in three annual tranches of $2 million each. The baseline schedule, driven by construction sequencing, calls for $2.6 million of spend in year one. Reconciliation pushes $600,000 of year-one paving work (which had slack) into year two, bringing year one to $2.0 million exactly — but the paving activity's downstream dependent, landscaping, now can't start until three months later than originally planned, which the team flags and re-baselines the schedule to reflect.

Where it comes from: this technique is named by the PMBOK Guide, 6th edition. No clause number is recorded for it here — a guessed citation would be worse than none.