Approving a flooring specification is often treated as the final box to tick before a programme is issued and materials are ordered. In practice, it is the point at which the greatest risk is either accepted or removed. A substrate condition report is the evidence base for that decision, and yet it is frequently skimmed rather than scrutinised. The document describes the floor as it genuinely exists — its moisture, strength, contamination, flatness and defects — not as the drawings assume it to be. Reading it carefully, line by line and reading against the proposed specification, is what separates a floor that performs for years from one that fails within months.
Why the Report Should Shape the Specification, Not Confirm It
There is a common sequence on commercial projects: the specification is drafted first, based on the intended use of the space, and the substrate report is then read to confirm that the chosen system will work. That order is backwards. A substrate report is not a compliance certificate for a decision already made; it is the set of constraints within which any specification must operate. Each result should map directly onto a technical choice — whether a surface damp-proof membrane is needed, whether the slab requires mechanical preparation or repair before coating, whether a levelling screed is required to meet flatness tolerances, and whether the selected resin chemistry is compatible with what is already on the floor.
Facilities managers and property teams are usually reading these reports alongside budget holders, contractors and manufacturers, each with a different interest. The manufacturer will want its own moisture and strength thresholds met. The contractor will want to know what preparation is achievable within the programme. The building owner will want to know what happens if those conditions are not met. The report is the only document that can hold all three to the same set of facts, which is why the specification should reference the report explicitly rather than sit alongside it as a separate assumption.
It is also worth remembering that a substrate report describes a condition at a moment in time. Concrete continues to dry, slabs behave differently across seasons, and a building that was unheated during testing may behave very differently once occupied. A report that gives no sense of when testing took place, under what conditions, and how the building was ventilated at the time is giving an incomplete picture. Readers should look for that context before treating any figure as absolute.
Finally, the report should be read as a risk register. Defects noted in passing — a hairline crack, a patch of old adhesive residue, a localised area of laitance — are not footnotes; they are the specific places where a new coating or screed is most likely to fail. A specification that does not address every observation in the report is a specification with unresolved risk buried inside it.
The Readings That Decide Whether a Specification Will Hold
Most substrate condition reports for commercial and industrial floors contain the same core information, though the labels vary between surveyors. The first is moisture, usually expressed as a percentage by weight or as relative humidity in a sealed test. It is essential to know which method was used, because the two are not interchangeable and the acceptable threshold is dictated by the flooring manufacturer, not by a generic rule of thumb. A reading taken at one depth in one location is a snapshot; several readings across a large warehouse slab tell a far more useful story, particularly near external walls and in older, unheated areas.
The second is strength. Compressive strength of the slab as a whole is only part of the picture; surface tensile strength — how well the top few millimetres will hold onto a coating — is often the more relevant figure. A slab can be perfectly sound in bulk and still have a weak, dusty, laitance-rich surface layer that will delaminate under load. Pull-off test results, where present, should be checked against the requirements of the specified system rather than accepted at face value.
The third is surface condition and profile, which covers existing coatings, adhesive residues, curing compounds, oil and grease contamination, and the texture left by previous preparation. Coatings and screeds rely on a mechanical key, and the report should describe what preparation is likely to be needed to achieve it. Methods such as Concrete grinding, shot blasting and scarifying are commonly specified to remove weak surface layers and open the pore structure, and the report’s description of the substrate should make clear which of these is realistic. Where contamination is present, preparation alone may be insufficient and the report should say so.
Readers should also check flatness, level and pH, and confirm that units are consistent throughout. A profile quoted in micrometres, a level tolerance in millimetres over a set metre, and a pH reading taken from a slurry sample each mean something specific. Mixing them up, or accepting a report that does, is a reliable route to a specification that reads well and performs badly.
Warning Signs, Gaps and Questions Worth Asking Before Sign-Off
Not every report deserves the same weight. A document that lists a single test location for a twenty-thousand-square-metre distribution facility, offers generic conclusions, or copies language between projects should be treated with caution. The same applies to reports that recommend a system without explaining why, or that state a floor is “suitable for epoxy” without any supporting figures. Approvers should look for photographs, a site plan showing test locations, a description of the testing methods and standards used, and a clear statement of the limitations of the survey.
Specific red flags include an absence of any mention of existing coatings or residues, no comment on cracks, joints or patch repairs, and no discussion of how the findings affect preparation and programme. Contradictions between the report and the specification are particularly important: if the report identifies elevated moisture but the specification contains no damp-proofing measure, that discrepancy needs resolving before approval, not after the first delivery arrives on site. Similarly, if the report notes a weak surface layer and the specification assumes only light preparation, the two documents are describing different floors.
Useful questions to put to the author of the report are straightforward. How many test points were taken, and where? Which methods were used, and to which standard? When was testing carried out relative to the building’s heating and ventilation regime? What is the recommended treatment for joints, cracks and localised repairs? What assumptions have been made about what lies beneath the surface? And, critically, which of the findings would change the specification if they turned out to be worse in practice?
Practical scenarios show why this matters. In older UK industrial units, power-floated slabs often carry decades of paint, adhesive and oil contamination that only becomes apparent once preparation begins; a report that flags this allows the specification and programme to include for it. In a new-build warehouse, the risk is more likely to be moisture and curing compounds rather than contamination. In food and beverage facilities, drainage falls, coving details and chemical resistance sit alongside substrate condition. Each of these situations demands a different reading of the same document, and the approver’s job is to ensure the specification answers the report’s specific findings rather than a generic template. Retaining the report alongside the approved specification, and noting in writing how each significant finding was addressed, gives the whole project team a defensible record if questions arise later.
Osaka quantum-physics postdoc now freelancing from Lisbon’s azulejo-lined alleys. Kaito unpacks quantum sensing gadgets, fado lyric meanings, and Japanese streetwear economics. He breakdances at sunrise on Praça do Comércio and road-tests productivity apps without mercy.
