Who Can Say Yes? How Financial Authority Shapes Project Outcomes

Accountability is weak governance when the person answerable for the result cannot control the decisions and resources that produce it.

A project manager is told to deliver within budget. A functional manager owns the people. A finance manager controls expenditure approvals. A steering committee holds contingency. A business executive owns the benefit. Procurement controls the commercial process. Each role can be individually reasonable, yet the combined decision system can make accountability difficult to locate and delivery unnecessarily slow.

The supplied organisational-finance study notes frame financial authorisation through responsibility accounting and budgeting. Cost, revenue, profit and investment centres create different forms of accountability. Financial delegation is shaped by organisational structure, while delegated authority does not necessarily remove accountability from the delegator.

For executives, the important issue is not accounting terminology. It is whether the organisation's decision rights match the outcomes for which people are held responsible.

The Strategic Context

Budgets are more than financial forecasts. They are part of the management-control system. They define where resources can be committed, who has authority to commit them and how performance will later be judged.

Projects cross those boundaries. A project may be funded from a capital budget while changing the future operating budget. It may sit within one responsibility centre while creating benefits in another. It may require functional resources that are financially accountable to a different manager.

This makes financial governance an organisational design issue.

If decision rights are too centralised, routine changes queue for executive approval and delivery slows. If authority is too dispersed, aggregate exposure can grow without sufficient control. If the project can spend but the benefit owner is passive, output may be delivered without value. If a business owner is accountable for benefits but cannot influence design, the project may optimise the wrong outcomes.

What Leaders Commonly Misread

The first misreading is to equate a delegation schedule with effective governance. A document showing monetary approval limits does not resolve who can change scope, accept risk, reallocate contingency or trade cost for schedule.

The second is to assume that more approvals create more control. Additional approval layers can reduce risk where independent challenge is genuinely required. They can also diffuse accountability because no one feels fully responsible for the decision.

The third is to measure project performance only against its own budget. A project can be under budget while increasing future operating cost, delaying revenue or transferring expenditure to another business unit. Enterprise economics matter more than local budget compliance.

The fourth is to separate benefits from funding. When the person requesting capital is not clearly accountable for the promised outcome, optimistic business cases can survive without a strong post-investment consequence.

Reframing the Issue

Financial authority should be designed around decision accountability, not simply hierarchy.

For each major investment, leadership should be able to answer five questions: who owns the business outcome, who controls the investment envelope, who can change scope, who can accept material risk, and who decides whether the project continues when assumptions deteriorate?

These roles may be held by different people, but the interfaces must be explicit.

A useful principle is that authority should sit as close as practical to the information required for the decision, while safeguards should become stronger as consequences become larger, more irreversible or more difficult to detect.

Strategic Analysis: Responsibility Centres and Project Behaviour

The supplied notes distinguish cost, revenue, profit and investment centres. Each creates a different managerial lens.

A cost-centre manager is primarily accountable for costs. A revenue-centre manager focuses on revenue. A profit-centre manager is accountable for revenue and expense. An investment-centre manager is also accountable for the capital employed to generate returns.

Projects intersect these lenses. A maintenance project may look unattractive to a cost centre because it increases current expenditure, while protecting enterprise reliability. A sales initiative may increase revenue while creating fulfilment cost elsewhere. A capital project may improve one division's profit while consuming corporate capital that has higher-value alternatives.

The governance system should therefore recognise that local financial incentives can produce rational behaviour that is not enterprise-optimal.

Capital versus operating budgets

The study material also distinguishes operating and capital budgets. This matters because project approval can move expenditure between periods and categories without changing the underlying economic burden. Leaders should examine total lifecycle cash and economic impact, not use accounting category as a substitute for value analysis.

Contingency and change authority

Contingency should not be treated as an unowned pool of money. Define what uncertainty it is intended to absorb, who can release it, under what evidence and when escalation is mandatory.

Benefit ownership

The strongest governance link is between the capital decision and the benefit owner. Someone in the permanent organisation should be accountable for whether the expected value actually emerges after project delivery.

Decision Framework

A practical financial-governance map can be built around six decision rights.

Then establish tolerances rather than requiring approval for every deviation. The project team should be able to operate within approved cost, schedule, scope and risk boundaries. Escalation occurs when a tolerance is forecast to be exceeded, not after it has already failed.

Financial thresholds should also be complemented by consequence thresholds. A safety, regulatory, cyber or architectural decision may require higher authority even when the immediate cost is low.

Related article: Organisational Structure Is a Project Risk

From Strategy to Execution

Immediately, require major projects to publish a one-page decision-rights map alongside the governance structure. It should show who can decide, who must be consulted and which thresholds trigger escalation.

In the medium term, align portfolio and budget cycles. A portfolio decision to accelerate an initiative should have a mechanism to move capital and resources rather than waiting for the next annual budget round.

Strengthen post-investment accountability by reviewing benefits with the operational owner, not only project cost and schedule with the project manager. This changes the definition of success from delivering the approved output to realising the intended enterprise outcome.

Longer term, analyse approval data. If routine expenditure repeatedly waits at senior levels, delegations may be too narrow. If projects repeatedly exceed authority before escalation, thresholds may be unclear or incentives may discourage early disclosure.

Signals to Monitor

Look for budget owners who cannot influence scope; project managers who spend large amounts of time obtaining routine approvals; contingency released without reference to specific risks; benefits that have no named operational owner; repeated transfer of cost between capital and operating budgets to preserve local targets; and governance forums that review variances but rarely make explicit continuation or termination decisions.

A further warning sign is when accountability becomes retrospective. If responsibility is only clarified after something goes wrong, the governance design was incomplete before the decision was made.

Questions for the Leadership Team

1. Who is accountable for the economic outcome of each major investment after the project closes?
2. Which decisions are being escalated because delegations are too narrow rather than because risk is genuinely high?
3. Where can one business unit approve expenditure that creates significant cost or risk for another?
4. Who can stop an initiative when its original investment assumptions no longer hold?
5. Does contingency have a defined purpose, owner and release logic?
6. Are we measuring managers against local budgets in ways that encourage enterprise-wide value destruction?

Closing Perspective

Financial governance is not a back-office control layered onto project delivery. It is part of the operating system through which strategy becomes expenditure, commitments and results.

The central design challenge is to align information, authority and accountability. When those three elements sit too far apart, decisions become slow, responsibility becomes negotiable and project economics become harder to protect. Strong governance makes it clear who can say yes, who can say no, and who remains answerable for what happens next.

Source Foundations

• MPM416 Internal Uncertainties and Organisational Financial Decision Making (supplied course material).