Interfaces, Not Assumptions: A Handover Protocol for Blast-and-Coat Packages

On many UK blast-and-coat projects, the abrasive specification is detailed, the coating data sheet is current and the access arrangements are agreed. The weakness often lies between those certainties: who protects adjacent surfaces, who accepts blast cleanliness, who removes masking and who signs the work forward to the next trade. When those interfaces are left to site convention, rework becomes a matter of timing rather than technique.

A written trade-boundary plan is not an administrative extra. It is the mechanism that turns a blast specification into an operable sequence. It should identify each surface or zone, the trade responsible at each stage, the acceptance criteria and the record that proves acceptance. In practical terms, it is as important as the nozzle size or the abrasive grade.

The mask line is a scope boundary, not a courtesy

Masking is sometimes treated as a minor preliminaries item. In reality, it defines what is excluded from blasting and coating, and therefore what must be protected, inspected and reinstated. Edges, threaded connections, machined faces, datum points, nameplates, glazing, seals and adjacent finishes all depend on a clear mask line.

The boundary should state who supplies the masking material, who applies it, who checks it before blasting, who maintains it during the works and who removes it. It should also define what constitutes acceptable protection. A heavy-duty tape may be suitable for one substrate and inappropriate for another; a temporary shield may protect a window from grit but not from coating overspray. Those distinctions belong in the plan, not in a late conversation after damage is found.

Where responsibilities commonly drift

The most common gaps appear at trade junctions. A scaffolding contractor may provide access but not protection. A masking operative may protect surfaces but not accept blast cleanliness. A blaster may achieve the specified profile but not control the corrosion window before primer. A coating inspector may reject the surface without a shared definition of what was required.

Shift changes compound the problem. Masking applied on a morning shift may be disturbed by afternoon access movements. A blasted area may be left overnight in conditions that affect its readiness for coating. Without a named owner and a recorded handover, each trade can reasonably assume that someone else has checked the condition of the interface.

Build an interface register

A simple register is more useful than a long narrative method statement. For each zone, record the surface or item, the preceding trade, the receiving trade, the hold point, the acceptance criteria and the evidence required. The register should be reviewed at the pre-start meeting and updated when sequence changes.

The language needs to be specific. Terms such as “clean”, “protected” and “ready” are too broad unless they are defined. State the required blast standard, the acceptable level of dust or debris, the masking condition expected at handover and the inspection method. Where a client specification or coating system imposes particular requirements, reference them directly rather than paraphrasing them into ambiguity.

Three hold points that prevent rework

First, a pre-mask inspection. Before protection is applied, confirm the substrate condition, the adjacent finishes, the isolation of services and the compatibility of masking materials. Record existing damage so that later defects are not attributed to the blasting or coating operation.

Second, a post-blast and pre-coat check. This is the point at which blast cleanliness, profile, mask integrity and environmental conditions should be accepted by the appropriate parties. The check should be joint where responsibility is shared, and the result should be recorded before primer is opened. A verbal acceptance is difficult to defend once coating has covered the surface.

Third, a mask removal and reinstatement check. Removing protection can cause adhesive residue, coating damage or disturbance to seals and fittings. The handover should confirm who removes the masking, how residues are dealt with and who accepts the reinstated condition.

Records that settle disputes without blame

Photographs with timestamps, signed checklists and a short non-conformance log are more effective than recollection. They do not need to be elaborate. A dated image of a protected edge, a signed post-blast checklist and a record of environmental readings will usually be enough to establish what was accepted and when.

The purpose is not to build a case against another trade. It is to make the sequence visible. On a busy UK site, where access is shared and weather can interrupt the programme, visible sequence control is a commercial safeguard as much as a quality measure.

The commercial case for clarity

Rework on blast-and-coat packages is rarely limited to the cost of repeating a small area. It can involve renewed access, additional masking, abrasive and coating consumption, inspection time and programme slippage. Where adjacent finishes are damaged, the cost moves beyond the blast package entirely.

A trade-boundary plan reduces that risk by making acceptance explicit. It also improves planning: masking can be sequenced with blasting, coating can follow within the corrosion window and inspection can be scheduled against defined hold points rather than discovered at the end.

Draw the line before mobilisation

The mask line should be agreed before plant arrives and before access is handed over. It should be drawn on drawings, described in the register and understood by the operatives who will work to it. FlowTech Blasting's view is that the blast specification tells a contractor what surface is required; the trade-boundary plan tells everyone who is responsible for delivering it without damaging the next trade's work.