The programme your planning pack
actually describes.
The system reads your contract, BOQ, and drawings and drafts a programme that carries what manual planning cannot afford to model.
Your planning pack
becomes the first draft.
The system reads the LOI, contract, BOQ, and drawings and proposes activities, dependencies, procurement chains, obligation clocks, and testing sequences — each cited to the document and line it came from.
Progress arrives as diffs. The retyping stops.
Site updates and schedule re-imports flow in as structured changes. You review and approve instead of collecting and retyping each week.
Review queue — proposed revisions as diffs
Each proposed change shown against current state, with its source attached.
2880 × 1800
Walk into the review with the answer cited
The representation audit checks whether the programme actually represents the project. Findings point to the contract clause, the specification section, the drawing — so you defend logic with evidence, not memory.
Representation audit — findings cited to source
Each finding links to the contract page or specification section it came from.
2880 × 1800
Full CPM semantics and keyboard-fast editing
Float, logic, calendars, constraints, driving paths, baselines, resource profiles — the scheduling engine assumes you are an expert.
- Nine constraint types
- Retained logic
- Multi-calendar float
- Driving path
Plan workspace — activity detail and logic editing
Relationship editing, constraint application, and float shown in place.
2880 × 1800