Planning preparation
Prepare the inputs for a reviewable construction plan
Define work packages, calendars, dependencies and resource assumptions before reviewing a generated construction schedule.
Original planning workflow. It is not a baseline approval, a delay analysis or a promise that a generated schedule is achievable.
Define what the plan must explain
Begin with a work breakdown that matches the intended decision: estimating a duration, coordinating a package, or preparing a proposed baseline. Keep the objective visible. A sequence intended for early budgeting should not be presented as an approved execution plan.
Record the document revisions, start assumption, work calendar, required milestones and scope boundaries. Name missing information so the reviewer knows which durations or links depend on assumptions.
Prepare a dependency and resource register
A compact register helps reveal why the plan looks the way it does. These are suggested review fields, not a claim that every field is automatically modelled by the product.
| Input | What to make explicit |
|---|---|
| Work package | Included scope, location and completion criterion. |
| Duration basis | Quantity, assumed productivity, crew and working-day basis. |
| Dependency | Predecessor, link type and reason for the sequence. |
| Calendar and constraint | Working days, access windows, procurement and required milestones. |
| Resource assumption | Available crews, shared plant and competing work fronts. |
Review logic before relying on dates
Trace a few complete paths from mobilisation to handover. Look for disconnected activities, circular logic, unexplained lag and milestones imposed without supporting work. Check whether the same crew or plant is assumed to be in two places at once.
Compare the proposed sequencing with actual site access, design release and procurement constraints. Review calendars as well as durations: equal numbers of working days can produce different dates under different calendars.
Record changes and recheck the plan
Keep the starting version, the reviewed version and a short change register. When a duration, calendar or predecessor changes, recheck downstream dates rather than assuming the rest of the plan is unaffected.
A qualified project team must confirm the logic and assumptions before adopting a plan. Generated scheduling material does not prove resource availability, contractual acceptance or delay responsibility.
Choose the correct starting point
The public scheduling page explains the planning service. The public demo is an Excel or CSV BOQ pricing trial; it is not a scheduling execution trial. Use the service page to understand the appropriate workflow before submitting real project information.
Use an invented practice project when learning the review method, and share authorised documents only when their purpose and data handling are clear.