Give each phase a reason
Explain why the project is being staged: access, another contractor’s readiness, an owner decision or an occupancy constraint. The reason helps the assessor determine whether the proposed boundaries are meaningful. A phase drawn only to fit a preferred date may conflict with the building or work method.
List what would be removed, retained and accessible at the end of each stage. Include debris handling and temporary arrangements that may need to be repeated. Avoid assuming that one setup can serve several disconnected stages without review.
Identify dependencies between stages
Ask what must be confirmed before the next phase can begin. This could involve a decision about an exposed condition, completion by another provider or a revised access arrangement. Assign a responsible person to each dependency.
Keep the whole intended project visible even if only the first phase is being quoted. An assessor needs to understand future removal that could affect retained items or current protection. Do not use a small first request to conceal a larger known scope.
Agree a phase handoff
Define how each stage will be reviewed and which records pass forward. If a later stage changes, revisit the earlier assumptions before proceeding. Tell YAK the full intended outcome and the reason for staging so the proposed phases can be considered as one coordinated project.
Bring these details
- Explain the reason for each phase
- Define every intermediate endpoint
- Assign dependencies and phase reviews