The Inspection Passed. Why Can’t the Next Trade Start?
An inspection approval confirms one condition, not total workface readiness. The next trade also depends on access, drawings, materials, temporary works, clearances and coordinated handover.
The short answer
An inspection pass confirms that the inspected work met the relevant acceptance requirement at that moment. It does not prove that the area is ready for the next trade. Productive handover also depends on access, current drawings, materials, temporary works, safety conditions, outstanding defects, protection, permits, plant and agreement about what the receiving trade can actually start.
Workface readiness should therefore be treated as a separate operational decision. Inspection is an important input, but the handover is complete only when the receiving activity's prerequisites are satisfied and responsibility for the area is clear.
A project example
A ceiling-services inspection passes on Friday afternoon. The programme expects the ceiling contractor to start Monday morning. When the crew arrives, several access panels are still awaiting final locations, stored materials block part of the floor, one mobile platform is allocated elsewhere, and a late instruction changes a section of the reflected ceiling plan. The previous trade considers its work complete because the inspection passed. The next trade says the workface was never ready.
Both teams are using different definitions of completion. Quality acceptance of the upstream work has been confused with operational readiness for downstream work. The lost shift is then recorded as a site coordination issue rather than a predictable handover failure.
This problem sits inside the broader programme-to-site planning chain. A planned start should be supported by evidence that the receiving workface is executable, not just by the completion status of the previous activity.
Define handover from the receiving trade's perspective
A useful handover criterion asks what the next trade needs in order to work safely and productively. That may include released access, current information, clear work zones, protection of completed work, available materials, temporary lighting or power, lifting access, permits and confirmed interfaces.
The exact criteria vary by package. A concrete pour, MEP first fix, ceiling closure and commissioning activity should not share an identical checklist. Use a small package-specific set of conditions that can genuinely stop the next activity.
This receiving-trade perspective prevents the upstream team from declaring readiness based only on its own scope. Handover becomes a shared decision rather than a unilateral status update.
Separate quality acceptance from workface readiness
Quality inspections and workface handovers answer different questions. The inspection asks whether completed work satisfies the defined requirement. The handover asks whether the next planned activity can begin under controlled conditions.
The two processes should be linked but not merged. An inspection failure normally prevents handover. An inspection pass may still leave other constraints open. Conversely, some preparatory work may proceed before formal completion if the project has defined a safe, controlled partial handover.
Making the distinction explicit improves reporting. “Inspection passed, handover not ready” is far more actionable than a single green completion flag.
Manage outstanding items by consequence
Not every snag or outstanding item should block the next trade. Projects lose time when minor items are treated as absolute barriers, but they also create rework when material issues are waved through. The handover process should distinguish blocking, conditional and non-blocking items.
A blocking item prevents safe or productive start. A conditional item allows start only with a defined control, owner and completion date. A non-blocking item can remain on the snag list without affecting the receiving activity. This classification turns a long defect list into a planning decision.
The receiving trade should understand any conditional items before accepting the area. Hidden conditions become disputes later.
Connect handover to drawings and information
Workface readiness includes information readiness. The receiving team needs the current approved drawings, specifications, coordinated details and instructions relevant to its scope. A passed inspection of previous work does not guarantee that the next trade has the right revision.
For this reason, handover should be connected to the drawing-control process described in did the workface receive the right revision?. Where a recent change affects the area, the handover should identify the revision being used and any unresolved design action.
A project-centric ERP such as Saturn can provide shared project, package and location context so planning, document, procurement and site records refer to the same work. It should support the handover evidence rather than replace package-specific quality and safety procedures.
Include access, temporary works and logistics
Access conditions often make the difference between theoretical and productive readiness. Scaffold may be incomplete, temporary openings unavailable, edge protection may restrict material movement, or the only hoist may be committed elsewhere. These constraints should be reviewed before crews arrive.
Temporary works can be especially important because they sit across design, site and safety responsibilities. If a working platform, support, protection or temporary power arrangement is required, its approved and installed state should be part of readiness where relevant.
Logistics also matter. A clean area without the required material is not a ready workface. Material location, delivery timing and storage access should align with the handover window.
Use a controlled partial handover when it creates value
Large zones do not always need to wait for full-area completion. If interfaces are understood, the project can hand over sub-zones or systems progressively. Partial handover can protect programme logic, but only if boundaries and responsibilities are clear.
Record the exact location, accepted conditions, outstanding interfaces and who owns protection after handover. Avoid vague statements such as “Level 5 released” when only one corridor is genuinely available. Precision prevents later arguments about damage, access and incomplete scope.
Partial handover also allows actual progress to be recorded more realistically. The programme can recognise usable workfaces instead of treating the entire activity as either zero or complete.
Make the handover visible in the short-term plan
A handover should appear before the next activity starts, not as an administrative note after it. Inside the lookahead, identify the planned release date, the receiving trade, the blocking conditions and the person responsible for resolving each exception. That gives procurement, design and site management time to intervene.
Where several areas repeat the same sequence, use the pattern to improve the plan. If the same missing access platform or late drawing delays three consecutive handovers, the issue is no longer an isolated snag. It is a systemic constraint that should change the planning rule, resource strategy or information release process for the remaining areas.
Five practical controls
1. Define readiness criteria for the receiving trade. Do not use inspection status as the only proxy.
2. Classify outstanding items by blocking consequence. Focus attention on what can genuinely stop productive work.
3. Verify current information and access before handover. Include drawings, temporary works and logistics where relevant.
4. Record precise location and responsibility. Especially for partial handovers.
5. Link handover to the planned next activity. A readiness decision should protect a real programme start.
These controls are most useful when reviewed before the handover date. A checklist completed after a crew is already waiting merely documents the failure.
What management should measure
Useful indicators include:
- planned starts delayed after the preceding inspection had already passed;
- workfaces handed over with blocking items still open;
- receiving-trade rejection or conditional acceptance of handovers;
- time between inspection pass and productive next-trade start;
- repeated access, material or information constraints by package;
- areas reported complete without a recorded receiving handover.
The aim is not to maximise handover paperwork. It is to reduce the number of crews arriving at areas that look complete in reports but are not ready to work.
Frequently asked questions
Does an inspection pass ever equal handover?
It can where the project's defined handover criteria are exactly the same as the inspection criteria and no other prerequisites apply, but that is uncommon for complex multi-trade work. The safest approach is to treat quality acceptance and operational readiness as related but distinct decisions.
Who should accept the workface?
The receiving package manager, supervisor or other authorised representative should confirm that the conditions needed for the next activity are present. The exact role depends on the project structure, but acceptance should not be inferred only from the upstream team's completion notice.
Should every snag block the next trade?
No. Classify snags by consequence. Blocking items prevent safe or productive work; conditional items require controls; minor non-blocking items can remain open with ownership and a completion date.
How early should readiness be reviewed?
Start inside the lookahead horizon, when there is still time to resolve drawings, material, temporary works and access. Confirm again close to handover because site conditions can change quickly.