Assurance and Support Conflict at Calder Rail
Calder Rail Infrastructure has a 22-person P3O. The P3O head reports to the Director of Strategy, but programme directors commission work directly from P3O analysts, who feel unable to refuse. The assurance function sits inside the P3O and also provides hands-on support to the same programmes it assures. A recent gate review of a £48m signalling programme was signed off by the senior adviser who had helped write its business case. Internal Audit has flagged this as a conflict of interest. The benefits analyst post is vacant and benefits are tracked by Finance. Project managers describe the P3O as a reporting factory that does not add value, while the P3O head says demand exceeds capacity and has no authority to set priorities. There is no role description for the P3O head, no career path for analysts, and the last staff survey showed low confidence in P3O leadership.
1. Assess the structural and role-design problems, giving particular attention to the assurance and support conflict.
Read the worked answer
There are three linked failures: mandate, role design and value positioning.
Mandate and authority. The P3O head reports to the Director of Strategy but programme directors commission work directly from analysts. This bypasses prioritisation, destroys capacity planning and leaves analysts exposed. The P3O head has accountability without authority - the classic recipe for an overloaded, low-credibility office.
Assurance versus support. Assurance requires independence in fact and appearance. The same function cannot help write a business case and then sign off the gate review of that programme, and the £48m signalling review demonstrates the self-review threat Internal Audit has identified. Combining assurance and hands-on support in one team is not automatically wrong, but it is wrong when the same individuals do both on the same programme, and it is indefensible when the assurance sign-off is made by the author of the case. Independence must be structural, not a matter of good intentions.
Benefits and capability. The benefits analyst is vacant and benefits sit in Finance. Benefits management is a core P3O capability; leaving it in Finance fragments accountability and weakens the P3O's claim to add value. No role descriptions, no career path and low leadership confidence are capability and succession risks, not HR housekeeping.
Value perception. 'Reporting factory' usually means the P3O produces data but not insight or decisions. Customers see outputs, not outcomes, and the direct commissioning suggests they do not see the P3O as a strategic service at all.
2. Recommend a role architecture and reporting lines, including how to separate assurance from support.
Read the worked answer
Top structure. A P3O sponsor at executive level holds accountability and the mandate. The P3O head is the service owner with authority over demand, capacity, standards and people. The head needs a written role description, delegated authority and a place on the portfolio board.
Functional roles under the head: portfolio analysis; programme and project support; risk and issue; benefits; resource and capacity; reporting and insight; change and configuration; tools; capability and standards. Each needs a role description, competencies and a career path from analyst to senior adviser to lead, with succession cover for critical posts.
Assurance separation. Create a distinct assurance function with its own lead. Administrative reporting can remain to the P3O head, but assurance findings and escalation must run directly to the Audit Committee or an independent assurance board. Staff must not assure work they supported: apply a cooling-off period, rotation and a documented declaration at each review. Where the P3O provides support to a programme, assurance for that programme is delivered by someone outside the support team, or sourced independently. The gate review of the signalling programme should be reopened or re-performed by an independent reviewer.
Commissioning and RACI. All requests go through the service catalogue and the P3O head allocates. Programme directors specify the requirement but do not task analysts directly. Above a defined effort threshold, the portfolio board decides. Make the RACI explicit: who requests, who allocates, who delivers, who assures, who escalates.
Benefits. Recruit or second a benefits analyst and agree the interface with Finance: Finance owns financial data, the P3O owns the benefits realisation plan, owners and tracking. Do not leave benefits orphaned.
3. How should the P3O reposition its value proposition and develop its capability?
Read the worked answer
Repositioning means moving from producing reports to supporting decisions. Concretely: convert reporting into insight with commentary, options and recommendations; provide portfolio-level analysis that helps the board stop, start or re-phase work; make resource and benefits information decision-ready; and use assurance to de-risk programmes rather than to score them.
Segment customers and agree what each needs: the executive board needs portfolio insight; programme directors need delivery support and independent assurance; project managers need standards and practical help. Publish a service catalogue with service levels and measure satisfaction against it, so value is evidenced rather than asserted.
Build capability deliberately: role descriptions and competency frameworks for every P3O role; a career path with development plans; training in benefits, assurance, analysis and stakeholder engagement; a community of practice across the organisation; and mentoring for the P3O head. Address leadership confidence through a clear terms of reference, visible sponsorship and early wins - for example, an independent re-review of the signalling programme and a portfolio decision paper that demonstrates analytical value.
Finally, establish a value narrative with measures: decisions influenced, assurance issues resolved before gates, resource conflicts resolved, benefits tracked to realisation, reporting timeliness, and customer satisfaction. Review quarterly with the sponsor and use the results to justify the next stage of maturity rather than assuming the P3O's value is self-evident.