Charter Section Deep-Dive

Project Charter Budget Section: Capital, Operating, and Contingency

The budget section is where most charters skip or fudge: base estimate without contingency, contingency without drawdown rules, total without capex / opex split. The seven components below, drawn from AACE International recommended practice, are the minimum for a charter that survives the first overrun.

Seven Components of a Charter Budget

1. Direct labour (loaded)

Team cost at fully loaded rate (salary plus benefits plus overhead). Most projects under-budget here by 20-30% by using gross salary only.

2. Vendor and contractor

External services with named vendor or contract envelope. Should sum the contracted minimum, not the full envelope, with a separate variance line.

3. Equipment and capital

One-time hardware, software licences, and capital purchases. Often the cleanest line because it ties to specific quotes or POs.

4. Operating costs (post-launch)

Cloud hosting, SaaS subscriptions, ongoing licences. Should be costed for at least 3 years post-launch with a named owner for the operating budget.

5. Training and change management

Most under-funded line in most charters. Training, change management, communications, and adoption support typically need 5-10% of the project budget.

6. Contingency reserve

10-15% of base estimate, controlled by PM, drawn down for known unknowns (risks that materialise). AACE Recommended Practice 40R-08 gives the methodology.

7. Management reserve

5-10% of base estimate, controlled by sponsor / steering committee, drawn down for unknown unknowns (scope or risk not anticipated at charter time). Separate from contingency.

Filled Budget Tables (3 Project Sizes)

Three worked examples scaled from small (USD 100K) to enterprise (USD 22M). Note how contingency and management reserve scale with both size and complexity.

Small project (under USD 100K, 6-week effort)

Direct labour (3 FTE for 6 weeks, loaded)USD 56,000
Vendor (UX research firm)USD 18,000
Tooling and licences (one-time)USD 4,500
Training and changeUSD 6,000
Base estimateUSD 84,500
Contingency (10%)USD 8,500
Management reserve (skipped, project size below threshold)USD 0
Total approved envelopeUSD 93,000

Management reserve typically not used below USD 250K. Contingency at the lower end of the band (10%) because scope is small and well-understood.

Medium project (USD 500K to USD 2M, 6-12 months)

Direct labour (8 FTE for 9 months, loaded)USD 980,000
SI vendor (statement of work)USD 320,000
Cloud infrastructure (3-year commitment, NPV)USD 180,000
Software licences (year 1)USD 65,000
Training and change managementUSD 80,000
Independent assurance / IV&VUSD 40,000
Base estimateUSD 1,665,000
Contingency (12%)USD 200,000
Management reserve (7%)USD 115,000
Total approved envelopeUSD 1,980,000

Contingency at 12% (mid-band) reflects moderate uncertainty. Management reserve introduced because project size and duration justify it. PM controls contingency; sponsor controls management reserve.

Enterprise project (USD 10M+, 18+ months)

Direct labour (40 FTE for 18 months, loaded)USD 8,200,000
Systems integrator (SOW + change envelope)USD 4,800,000
Hardware and capitalUSD 1,200,000
Cloud and licences (3-year commitment)USD 1,800,000
Change management and trainingUSD 980,000
Independent assurance / IV&VUSD 320,000
Legal, procurement, complianceUSD 240,000
Base estimateUSD 17,540,000
Contingency (15%)USD 2,631,000
Management reserve (10%)USD 1,754,000
Total approved envelopeUSD 21,925,000

Contingency at 15% (top of band) reflects complexity and integration risk. Management reserve at 10% reflects substantial scope ambiguity typical of large transformations. Per AACE Class 3 estimate (definitive), this would correspond to early-stage detailed design.

Contingency and Reserve Drawdown Rules

The most-skipped part of the budget section is the drawdown rules. Without them, the PM either becomes overly conservative (never drawing contingency, leaving budget unspent while the project struggles) or overly liberal (drawing without governance and discovering the reserve is gone at month 6).

Draw amountAuthorityGovernance
Contingency draw under 25% of reservePM, with notification to sponsorLogged in monthly status report
Contingency draw 25-75% of reservePM with sponsor approvalApproved in steering, documented in minutes
Contingency draw above 75%Sponsor + steering committeeTriggers re-baseline conversation; consider whether to extend project or descope
Management reserve draw (any amount)Sponsor + finance partnerTreated as scope change; updated charter and revised baseline required

Frequently Asked Questions

What is the difference between contingency and management reserve?
Contingency covers known unknowns: identified risks that may or may not materialise (vendor delays, integration complexity, regulatory changes). The PM controls contingency within a published threshold. Management reserve covers unknown unknowns: scope changes or risks not anticipated at charter time. The sponsor controls management reserve. Both should appear in the charter; treating them as one number gives the PM authority over too much budget and reduces sponsor visibility into emerging scope.
What is the right contingency percentage?
10-15% for most projects, per the AACE International Recommended Practice 40R-08 on contingency estimating. Below 10% the project lacks resilience to identified risks; above 15% the budget likely contains hidden scope. The percentage should be a function of project class (AACE Class 1 to 5, where Class 1 is execution-ready and Class 5 is concept) and the explicit risk register. Larger or more complex projects benefit from Monte Carlo simulation to set contingency by confidence level rather than a flat percentage.
Who approves the project budget?
The sponsor, with input from the finance partner. For projects above a corporate threshold (often USD 1M to USD 5M depending on company size), CFO co-sign or board approval is typically required. For nonprofit and government projects, board / appropriating-body approval is mandatory above bylaw or statutory thresholds. The charter should name the specific governance step (e.g. 'CFO approval per Finance Policy Section 4.2' or 'Appropriated under California Budget Act, Item 2740-001-0001').
Should the budget be in the charter or in a separate document?
Summary in the charter (totals, contingency, drawdown rules), detailed line items in a separate budget document. The charter is approved once and revised through formal change control; the budget detail is reforecast monthly. Embedding monthly-reforecast detail in the charter creates an artefact that becomes stale immediately. The charter version should be the envelope and drawdown rules; the project plan owns the detailed forecast and actuals.
How are capex and opex handled in the charter?
Separately. Capex is one-time capital investment (equipment, system buildout, licences purchased outright); opex is ongoing operating cost (cloud subscriptions, licences leased, ongoing support). Many CFOs and tax practices require explicit capex / opex split for accounting and tax-treatment reasons; some grants and appropriations restrict use to one category. The charter should show both lines and the methodology used to allocate (e.g. cloud spend is opex per FASB ASC 350-40 cloud computing guidance).
What happens if the project exceeds the approved budget envelope?
PRINCE2 calls this an Exception Report; PMBOK calls it a change request requiring re-approval. Either way, the PM should not silently absorb overruns by drawing management reserve without sponsor approval. The charter's drawdown rules section should make the escalation path explicit. Sponsors who discover overruns through year-end variance reports rather than active escalation become substantially more cautious on future project approvals.
Does an agile project need a budget section?
Yes, but denominated differently. Agile budgets are typically expressed as 'N Sprints of team capacity at the team's loaded cost' rather than line-item project costs. The charter should still show the loaded cost per Sprint, the number of Sprints in the envelope, and the criteria for extending the envelope. Atlassian's Agile project management guidance recommends framing this as 'fixed-time, fixed-cost, variable scope' for finance partners accustomed to traditional budgets.

Related on this site

Charter objectives sectionCharter milestones sectionRisk matrix (basis for contingency)Enterprise charter (deeper budget detail)PMBOK charter formatNonprofit charter (restricted funding)

Updated 2 May 2026