Authority concept · Iron Meridian Industrial Services

Repair Before Resurfacing

This resource explains why repair responsibility should be separated from resurfacing/coating responsibility before a system is priced. It complements—but does not duplicate—the Concrete Repair capability page.
Mechanical concrete preparation creating a controlled floor profile.

Decision checklist

  • spalls and section loss
  • broken edges
  • delamination/unsound material
  • cracks/joints requiring defined treatment
  • transition failures
  • repair material cure/compatibility with next system

Why it changes scope

Each input can change preparation, repair quantity, system selection, access, sequence, cure protection, or return-to-service assumptions. Leaving it undefined does not make it disappear; it moves uncertainty downstream.

Contractor boundary

A real project would reconcile the owner/specifier requirements, manufacturer data, field conditions, and any engineering or regulatory responsibilities before execution. This concept does not replace those parties.

Use this before asking one finish layer to solve two problems

Resurfacing can correct profile or create a new wearing surface, but the project still has to decide what happens to unsound concrete, broken edges, delamination, cracks, joints, and failed transitions. Those defects may require a separate repair approach before the next system is ready to perform its own job.

This is why Iron Meridian keeps a Concrete Repair capability page and this decision resource separate: one defines execution; the other helps the buyer recognize the decision.

TruePoint concept · fictional industrial contractor · Built for Aster