Create one portfolio view across programmes, campuses and platform initiatives. Priorities, milestones, dependencies and stop/start decisions are governed in one system, so trade-offs are explicit, delivery stays aligned, and leadership reviews remain decision-led.

Turn scattered programme reporting into one portfolio system with clear owners, decision gates, dependency visibility and a defined stop/start queue.
Used by leaders who need one source of portfolio truth to govern priorities, sequencing, affordability and delivery risk without re-litigating decisions each cycle.
Inputs
We start with what’s needed to establish a usable baseline quickly, then standardise into a consistent portfolio schema.
Your current list of programmes and initiatives, with named accountable owners, to create the first portfolio baseline and remove ambiguity.

Outputs
A standard portfolio structure (owner, objective, milestones, status, risks, dependencies, decision gates) so reporting is consistent across programmes.
Clear criteria that define what “on track” means and what counts as an exception — so reviews focus on decisions, not commentary.
A single view of blockers with owners, ageing and required actions — so constraints are governed early and don’t quietly stall delivery.
A structured queue for prioritisation decisions, with options, minimum evidence and named approvers — so stop/start calls are explicit and auditable.
Repeatable portfolio chapters for ExCo/Board packs — priorities, decisions, exceptions and follow-through in a consistent format.
Configuration
Configured to match your governance model, pack structure and reporting cadence — while sitting above your existing delivery and data tools.
Define categories (programme, platform, estates, compliance, transformation, academic quality initiatives) so the portfolio is coherent and comparable.

Confirm portfolio scope, stakeholders and governance rhythm, and pinpoint where decisions stall (prioritisation, approvals, sequencing, dependencies, resourcing). Agree the first pack chapter to standardise.
Define the portfolio schema, RAG thresholds, decision rights, escalation routes and stop/start governance — so leadership forums become decision-led and comparable cycle to cycle.
Configure portfolio views, dependency/blocker tracking, and stop/start routing in the Bramnor Workspace, then run the agreed cadence (monthly/quarterly) with clear owners and closure discipline.