How It Works
From programme update to governed weekly close-out.
PlanSure turns the latest six-week programme outlook into a controlled weekly process for reviewing readiness, assigning ownership, progressing required actions and preserving the final outcome.
The authoritative master programme remains outside PlanSure and continues to be managed by the planning team.
- Programme input01
- Six-week outlook02
- Governance review03
- Action execution04
- Controlled close-out05
- Permanent record06
- Governance Week stateExecution
- Required actionsOpen
- Weekly PlanLocked
- Weeks 1–2 · Committed
- Weeks 3–4 · Preparing
- Weeks 5–6 · Upcoming
The weekly process
One repeatable governance cycle from input to outcome.
Each Governance Week follows the same controlled sequence. Programme information is reviewed, readiness is challenged, required actions are owned and the cycle remains open until the agreed governance conditions are satisfied.
- 01
Programme input
The planner uploads the latest text-based PDF export of the authoritative master programme.
- 02
Six-week outlook
PlanSure creates an immutable Programme Version and identifies the activities within the current six-week governance horizon.
- 03
Governance review
The project team reviews upcoming activities, tests readiness, examines evidence and agrees the actions required to support delivery.
- 04
Action execution
Named owners progress required and optional actions against defined close-out dates.
- 05
Controlled close-out
Required actions must reach a recorded outcome before the Governance Week becomes Close-Out Eligible.
- 06
Permanent record
The cycle is closed, locked and preserved with its programme version, actions, decisions, evidence and outputs.
01 / 02Programme input and outlook
Begin with the current authoritative programme.
The planner uploads the latest text-based PDF export of the master programme. PlanSure creates a fixed Programme Version for the Governance Week and arranges the extracted activities across the six-week readiness horizon.
- Latest text-based PDF programme export
- Immutable Programme Version created
- Relevant activities extracted and confirmed by the planner
- Master programme remains authoritative
PlanSure does not edit, optimise or replace the master programme.
- SourceText-based PDF
- Uploaded byPlanner
- Programme VersionImmutable
- Governance horizonSix weeks
- Extraction statusAwaiting confirmation / ConfirmedPlanner
Structure only — no schedule editing, cost or contract data.
Six-week readiness horizon
- Weeks 1–2Committed
Immediate delivery activities expected to have required actions closed.
- Weeks 3–4Preparing
Readiness requirements, permits, isolations, RAMS and other constraints are actively being resolved.
- Weeks 5–6Upcoming
Upcoming activities are reviewed early enough to identify long-lead constraints, design approvals, temporary works, surveys and resource requirements.
Immediate commitments are separated from work that still requires preparation or intervention.
03Governance review
Challenge readiness before commitments become delivery problems.
During the Governance Week, the project team reviews upcoming activities, tests assumptions, assesses the evidence supporting each position and decides what must happen next.
Readiness
Is the activity genuinely ready?
Evidence
What supports the current position?
Decision
What action, owner or intervention is required?
- Ductwork installation — Level 2Evidence: access sequence confirmedCommitted
- Riser isolation worksEvidence: permit request referencePreparing
- Facade bracket surveyEvidence: none recordedChallenged
- Temporary works to plant deckEvidence: design review referencePreparing
The team reviews and records the supporting evidence for each position.
04Accountable action
Every required action has an owner and a close-out date.
Required actions are the default. They remain visible until completed or formally force-closed. Optional actions can be recorded for non-gating follow-up without preventing the controlled weekly outputs.
Required actions
- Default action type
- Named owner required
- Close-out date required
- Closure note required
- Must reach an outcome before close-out
- Gates controlled weekly outputs
Optional actions
- Used for non-gating follow-up
- Owner and date may still be recorded
- Tracked without blocking the Weekly Plan
- Preserved within the governance record
| Action | Type | Owner | Close-out date | Status |
|---|---|---|---|---|
| Confirm approved design release — Level 2 ductwork | Required | Design Lead | Set | Open |
| Obtain riser isolation permit | Required | Construction Manager | Set | Open |
| Confirm delivery access and set-down | Required | Planner | Set | Closed |
| Complete facade bracket survey | Required | Package Manager | Set | Open |
| Allocate additional installation resource | Optional | Construction Manager | Recorded | Open |
05Action execution
The cycle stays open while accountable actions are progressed.
Owners progress actions during execution. Open required actions remain visible, close-out dates remain attached and the platform enforces the lifecycle: invalid transitions are rejected, overlapping Governance Weeks are prevented and closed weeks cannot be reopened.
Uploaded
State reachedProgramme received and awaiting confirmation.
Meeting Open
State reachedGovernance review active and actions being created.
Execution
Current stateOwners progress required actions.
Close-Out Eligible
Not yet reachedGovernance conditions satisfied and outputs available.
Closed
Not yet reachedWeek locked, preserved and read-only.
Ownership stays visible
Every required action remains linked to its named owner and close-out date.
Transitions are enforced
State changes are validated by the platform, and cycles cannot overlap.
Outcomes must be recorded
Actions cannot silently disappear when the next meeting begins.
06Controlled close-out
Outputs are released only when governance conditions are satisfied.
The Weekly Plan cannot be generated while required actions remain open. Once all required actions have reached an outcome, the Governance Week can become Close-Out Eligible and its controlled outputs can be released.
- 01
Required actions reach an outcome
Every gating action has reached a recorded outcome through completion or formal force-closure.
- 02
Close-Out Eligible
The platform confirms the governance conditions.
- 03
Weekly Plan and Planner To-Do available
Controlled outputs are released for the week.
- 04
Governance Week closed
The record becomes locked, preserved and read-only.
No draft Weekly Plan exports are available before Close-Out Eligible.
07Outputs
Turn governance into controlled weekly outputs.
Weekly Plan
The Weekly Plan contains only Green activities with zero open required actions, ensuring that immediate commitments have passed the agreed governance conditions.
- Ductwork installation — Level 2Committed
- Riser fixings — Core BCommitted
- Plant deck set-downCommitted
Green activities only · Zero open required actions
Planner To-Do
The Planner To-Do records the actions and programme updates that must be reflected in the authoritative master programme after weekly close-out.
| Activity reference | Programme update | Owner |
|---|---|---|
| Ductwork — Level 2 | Sequence confirmed | Planner |
| Riser isolation | Constraint recorded | Planner |
| Facade survey | Instruction required | Planner |
Spreadsheet-style export structure — illustrative only.
The planner remains responsible for updating the authoritative master programme outside PlanSure.
08Governance record
Every week leaves a permanent governance record.
Programme versions, activities, actions, owners, dates, closure notes, decisions, evidence references and controlled outputs remain linked to the Governance Week in which they were created.
- 01Immutable Programme Version
- 02Append-only audit history
- 03Retained action outcomes
- 04Read-only closed weeks
- 05Evidence references
- 06Controlled outputs
Nothing silently disappears when the next Governance Week begins.
In summary
One governance cycle. Repeated every week, on every project.
PlanSure does not replace the programme, the planner or professional judgement. It provides the structure that keeps the weekly cycle consistent: the same input, the same review, the same accountability and the same permanent record.
- 01
The programme stays authoritative
PlanSure reads it; the planning team continues to own it.
- 02
Readiness is evidenced
Positions are challenged and supported, not assumed.
- 03
Actions are accountable
Required actions carry an owner, a date and a recorded outcome.
- 04
Outputs are controlled
Weekly Plan and Planner To-Do are released only at close-out.
10Responsibilities
Clear responsibility throughout the weekly cycle.
Planner
Uploads the programme, confirms extraction, opens the Governance Week, creates and assigns actions, generates controlled outputs and closes the cycle.
Project leadership
Challenges readiness, reviews evidence, confirms decisions and ensures accountable actions reach an outcome.
Administrator
Manages projects and users, reviews audit history and accesses closed-week records without altering them.
See the complete Governance Week in action.
Explore how PlanSure connects programme information, evidence-based readiness, accountable actions, controlled outputs and permanent governance history.
Governance that lasts longer than the meeting.