A single programme control layer for capex, renovations and openings, built around milestones, dependencies, constraints and spend pressure. Exceptions are trigger-led with clear decision points, so sequencing, scope and approvals are governed before drift becomes cost.
One governed programme view that feeds packs, decision queues and escalation routes. Capex stays controlled and does not drift between decks, spreadsheets and contractor updates.
Designed for leadership teams who need portfolio-level control while still managing asset-level delivery reality.
Inputs
We start with what you already run, then standardise fields, thresholds and decision routes.
A list of active and planned renovations/openings/repositionings, with named owners and governance forums.
Outputs
A consistent structure for every programme—so reporting is comparable across assets, regions and categories.
Milestones and stage gates with clear exception logic—so slippage becomes a decision point, not a status update.
A live register of blockers (permits, access, vendors, IT, trading windows) with owners and ageing—so issues cannot disappear between meetings.
A structured queue of decisions with options, trade-offs and the minimum evidence required to land the call.
Visibility on scope shifts, variations and claims signals—supporting disciplined approvals and early intervention.
Repeatable pack sections that draw from the same operating data—so capex reporting stops being rebuilt every cycle.
Configuration
Configured during implementation to match your governance model, pack format and reporting cadence.
Triggers for slippage, affordability pressure, readiness risk, contractor confidence, and variations/claims signals—seasonality-aware where required.
Confirm programme scope, trading constraints, current reporting reality and where decisions stall (sequencing, approvals, contractor constraints, brand sign-offs).
Define the minimum operating architecture: programme taxonomy, milestone gates, exception triggers, decision rights and escalation routes—plus the capex pack structure.
Configure programme views, registers and decision queues, then run the cadence (monthly review plus exception forums) with defined thresholds and closure rules.
