Infrastructure
Keep the programme's decisions and evidence together when the team changes
Long programmes lose context across packages and staff changes. Assurance needs the current scope, cost, schedule, risk and decision record drawn directly from current evidence.
The agreement and rules behind the work
Infrastructure assurance, approved governance and package agreements
Illustrative engagement
Three packages in a corridor upgrade
A delivery authority convenes three civil packages in one corridor engagement, where design releases, utility works, possessions and commissioning dates affect one opening commitment.
- Governance
- Programme control group, delegated decisions and independent assurance gates
- Delivery
- Three package agreements represented in one engagement with shared interfaces and opening milestones
- Money
- Approved budget, contingency control, certified work and change decisions
- Handover
- Commissioning, asset data, readiness, defects and benefits evidence
Product example
Nebula workspace
Project
Three packages in a corridor upgrade
Infrastructure assurance, approved governance and package agreements1 assurance gate needs evidence.
ReviewWhere it stands
Corridor delivery is active
2 of 3 packages on planWhat needs you
Your decision1 gate
Utility interface evidenceWho is involved
Delivery position
Current delivery positionDelivery items
Interfaces feeding the opening commitmentDesign release
VerifiedUtility interface
Needs evidenceCommissioning plan
ActiveThe engagement lifecycle
How Nebula carries this work through delivery
01
Form
Turn approvals into a delivery plan
Approved scope, outcomes, budget, delegations, package obligations and assurance gates are recorded with their sources. Each delivery party reviews the obligations attributed to it in the corridor engagement before acceptance.
What stays connected
Approved source, obligation, owner, authority, budget and gateway.
02
Mobilise
Connect package interfaces
Design release, access, utility relocation and possession obligations are linked to the milestones they enable. The programme can see when one package exposes another to delay.
What stays connected
Package dependency, prerequisite, owner, forecast and cascade risk.
03
Deliver
Report from accepted activity
Verified milestones and certified payment data inform the current cost and schedule view. Claimed progress stays distinct from accepted progress, and overdue approvals remain visible beside contractor performance.
What stays connected
Milestone state, certification, earned value indicators, risk and overdue decisions.
04
Change
Govern scope and contingency together
A design standard change affects two packages. Each variation keeps its reason, authority, cost and schedule effect, while the shared corridor engagement shows their combined consequence.
What stays connected
Change cause, approval, contingency effect, revised dates and package interfaces.
05
Assure
Give reviewers the live evidence trail
Governance packs draw on accepted changes, current risks, certified expenditure and unresolved decisions. Reviewers can follow a reported position back to the engagement evidence that supports it.
What stays connected
Current position, supporting evidence, decision history and unresolved exceptions.
06
Close
Carry obligations through handover
Commissioning, operational readiness, asset data, training, defects, benefit measures and lessons stay owned through close-out. The team that inherits the asset reads the same record the programme was run from.
What stays connected
Handover acceptance, defects, residual risk, benefits evidence and lessons.
One connected engagement
What Nebula keeps connected as work changes
Programme
Package dates, interfaces, milestones and downstream consequences.
Commercial
Certified expenditure, accepted budget, contingency, extension and variation responses, and change history.
Governance
Delegations, decisions, risk, defect and suspension notices, evidence and assurance actions.
Continuity
A record with its source wording attached that survives staff and supplier changes.
Delivery trust
Evidence for future programmes
Where package delivery is verified, it stays connected to attributed decisions and can support supplier selection and programme lessons. Project teams can draw on the engagement record, source wording attached, when preparing agency reports and assurance reviews; the agency decides what it approves and lodges.
See how record verification worksUse Nebula to carry this work through close-out
Nebula reads the documents that define the work into a delivery plan, carries approved changes and evidence forward, and prepares reports and handovers. Your people decide what is accepted and what happens next.
Nebula's assistant. Questions about Nebula.