Skip to content

Waterproofing

Primer, base, wear and top coat: building a traffic coating and its aggregate

By Review.LivePublished 3 min readHow we write

The university parkade crew has sufficient finish material but discovers that its aggregate allocation is incomplete. The daily sheet records only a combined pail count. The foreman needs to establish which layer and zone are affected before the next stage conceals the problem.

An unoccupied concrete parking deck has painted lane markings and orange barriers beside a metal perimeter railing.
Photo: Tdorante10 on Wikimedia Commons · Pier 40 td (2018-06-09) 17 - Third Floor · CC BY-SA 4.0 · Cropped, resized, colour adjusted and sharpened. Derivative photographs offered under the same CC BY-SA 4.0 licence.

Track each specified layer separately. The cited assembly instructions distinguish its waterproof base, wear layer, aggregate treatment and finish, with different application and timing requirements. Other approved systems can have different arrangements. Use the actual layer schedule rather than a universal primer-base-top recipe or an assumption that every aggregate operation is broadcast to refusal.

Make the layer record follow the zone

  1. Build the actual layer schedule. List the approved components and aggregate treatments for each zone and duty. Identify differences between stalls, aisles, ramps or detail areas where specified. Keep the relevant instruction and revision beside the work sheet so an estimating allowance cannot become an application rule.
  2. Stage identifiable material. Confirm required components, aggregate type, quantities and availability with the applicator. Retain the specified traceability information and storage checks. A full pallet of an unrelated layer does not compensate for missing aggregate or a component required earlier in the sequence.
  3. Record conditions and timing. Provide fields for the actual layer start, finish, required site readings and recoat criteria. Have the trained applicator confirm permitted conditions before proceeding. Keep an interrupted or incomplete stage visible rather than assigning one completion time to the entire zone.
  4. Check the required measure. Record the specified method and result for coverage or thickness as applicable. Keep allocated area, actual used material and losses distinguishable. Dividing total purchases by floor area does not document each layer’s condition or prove that local thin areas do not exist.
  5. Retain aggregate-stage evidence. Identify the actual aggregate regime, treatment extent and required review in the approved assembly. Record interruptions, questionable distribution and technical dispositions. Do not invent extra aggregate, a reduced rate or a later finish adjustment when the required operation cannot be completed.
  6. Close one stage before hiding it. Link the required checks, exceptions and approval to the next layer’s handover. Preserve the original nonconformance and correction history. Make the finishing boundary and remaining work clear so the next crew knows what it can genuinely receive.

Common mistakes

  • Keeping only the combined material count.
  • Treating every zone as the same aggregate duty.
  • Expecting a later finish to erase an unresolved earlier-stage defect.

Checklist

What the next layer needs to receive

  • Actual zone and layer schedule.
  • Component and aggregate identity.
  • Required conditions and timing.
  • Located coverage or thickness evidence.
  • Exceptions and authorized dispositions.
  • Reviewed stage handover.

Check your understanding

The average material use matches an allowance, but one strip missed its specified aggregate stage. Can the zone be recorded as complete?

Show the answer
Keep that strip as an exception and obtain the approved disposition. An average count does not establish local compliance or completion of a required operation. The next-stage handover needs the actual reviewed boundary.

Sources

  1. Vulkem 350/Epoxy WC/346 Application InstructionsTremco · Product-specific details and cure conditions; use current approved assembly requirements · accessed