Drawings, BOQs, specifications, scope and method statements, read as one connected set.
Quantities that inform proposed durations and the resource assumptions behind them.
Propose activities, durations and logic links from the scope and construction method, not generic templates.
Adjust what the model got wrong, then export to Primavera P6 or Microsoft Project, or carry the programme into validation.
Drawings
Structures, zones and levels, read into a work breakdown the programme can be built on.
Bills of Quantities
Quantities that inform proposed durations and the resource assumptions behind them.
Specifications
Materials, standards and testing requirements that add activities a scope list would miss.
Method Statements
The stated construction sequence, read as logic between activities rather than as prose.
Contract Documents
Milestones, sectional completion dates and constraints that bound the programme.
Calendars & Working Patterns
Shifts, seasons and access windows applied to durations rather than added afterwards.
