Design delegated authority and conflicts controls
6 min read
Lesson objectives
- Identify decision authority when financial or nonfinancial conditions are breached and treat conflicts of interest.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A portfolio board can approve a project's funding while its manager still lacks authority to sign the contract or change how personal data are used. These approvals concern different objects. Authority to prioritise investment does not automatically include authority to enter a commercial commitment or accept exposure beyond organisational risk appetite. Start a delegation matrix by naming the decision, the person or body entitled to make it, the conditions for a valid decision and the evidence it requires. APM's public explanation links governance to delegated limits and escalation. Section 4.1 of the UK government's GovS 002 similarly addresses authority, autonomy and reporting. Here those ideas inform a fictional organisation. Actual authority must be traced to the organisation's own valid arrangements and applicable requirements.
Separate five choices often compressed into an approval box: admitting an initiative to the portfolio, authorising a particular stage, committing expenditure, accepting risk exposure and receiving a benefit into operations. One board may own some of these while others belong elsewhere. For each choice use a precise verb: recommend, review, authorise, execute or verify. A responsibility matrix identifying the person doing the work, the accountable person, advisers and recipients of information supports coordination. It does not demonstrate that any of them holds financial delegation. A PMO manager does not acquire investment authority by assembling recommendations or writing the minutes. Trace the delegation to its source, check its validity period, and establish whether the holder may delegate it again.
A single money limit is rarely sufficient. A delegation may permit a small cost change only when service scope, a critical date and approved benefits remain within specified conditions. Read those conditions together. Breaching any one of them escalates the choice even when the financial amount is below the cap. For successive changes, the arrangements should state whether limits apply to each change or to the total since the baseline. Breaking one commitment into smaller requests to circumvent the limit defeats the control. An operational rule might say: the sponsor may approve cumulative increases up to 0.5 million from baseline, provided forecast benefit falls by no more than five percent and the service commitment does not change. These are fictional teaching thresholds, not universal professional limits.
A valid decision combines proper authority with relevant expertise. A security specialist's opinion does not replace the investment owner's approval, and investment approval does not remove the need for technical advice. Specify the package that reaches the decision maker: options, effects on capacity, benefits and exposure, specialist advice, and unresolved points. Where finance and operations disagree, do not ask the PMO to average their views into an apparently agreed recommendation. Show the precise disagreement, each side's evidence and the implication for the choice. Escalation should end with the body that actually owns that class of decision, rather than merely the most senior familiar person. A response deadline and a legitimate interim action can allow unaffected work to continue while the disputed change awaits a decision.
A conflict of interest is not limited to a direct financial reward. Someone may be reviewing the success of a design they created, or their performance reward may depend on the initiative being approved. Disclosure starts the response. Depending on the relationship, separate evidence provision from judgement, exclude the person from voting, or arrange a separate review of a material assumption. Exclusion from every conversation is not always necessary: a committee may need the person's information before deliberating without them. Its rules should explain how quorum remains valid after recusal and who chairs if the chair is conflicted. Losing quorum cannot be cured by a later signature pretending the original decision was valid. The record should identify the relationship, treatment and alternative authority, rather than only saying that disclosure occurred.
Emergency response may be necessary before a scheduled board meeting. Its delegation should identify the triggering event, permitted action, amount, duration and notification route. For example, an operations director might be authorised to spend a bounded sum restoring a service without acquiring authority for permanent expansion. Emergency delegation does not create a missing legal right or let every team declare its own emergency. Afterwards, review events, commitments and lessons, returning permanent choices to the normal route. This review examines what was authorised and what happened; it does not erase an earlier overreach. The ability to resume safe work is part of the design. A dispute about one change should not automatically freeze every unrelated activity in the project.
Lesson summary
Delegation conditions operate together; investment approval does not replace contracting or risk acceptance authority.