Before Coating Concrete: What Surface Should the Preparation Crew Leave?
Before approving concrete coating preparation, ask for the required finished substrate condition, not just the name of a machine. The proposal should connect the selected coating system to a surface-profile target, explain how that target will be checked, and identify who releases the prepared area for coating. A line saying grind floor does not answer those questions by itself.
Start with the coating, then define the preparation
A property owner comparing floor-coating bids may see grinding in one proposal and shotblasting in another. That difference deserves an explanation, but it is not enough to decide which bid is better. First ask each bidder to identify the coating system and the preparation requirements that apply to it. Otherwise, you may be comparing different intended results under the same broad project name.
Sika's surface preparation guide distinguishes substrate assessment, removal of contamination, and creation of a surface profile. It also directs readers to product-specific information and technical support. Those distinctions matter: preparing concrete for a coating involves more than making the floor look clean. Use the selected system's current instructions as the project reference rather than treating a general preparation guide as a specification for every floor.
Request a short written pairing: the proposed coating system, its applicable preparation document, and the contractor's intended preparation result. If the product changes after pricing, ask whether the preparation scope changes too. Keep that answer with the revised proposal instead of assuming that all coatings accept the same starting surface.
Understand what a CSP number describes
CSP means concrete surface profile. It describes surface roughness, not the concrete's strength rating or the color of the finished coating. DeFelsko's technical explanation describes ICRI comparator chips as textured references used to compare a prepared surface visually and by touch. It also explains that direct digital depth measurements are a different, quantitative approach to assessing profile.
For an owner, the practical question is how the project will record the specified result. If the proposal calls for a CSP comparison, ask who performs it and where the observations will be recorded. If it calls for measured profile depth, ask which method and units apply. Do not treat a chip designation and a number on an instrument as interchangeable without the project's agreed interpretation.
Avoid choosing a higher CSP number simply because it sounds more thorough. Ask the installer to show how the requested profile fits the actual coating system. Your role is to obtain a clear, consistent acceptance requirement; it is not to select a roughness target from an online photograph.
Separate machine coverage from accepted floor area
Ask the estimator to mark the floor area included in the preparation price. Then walk the perimeter together: door recesses, columns, equipment bases, corners, and transitions to rooms that are staying open. Put any excluded strips on the same drawing. This gives both parties a way to discuss the scope before a large machine arrives and access decisions become immediate.
The useful question is not only whether a machine can enter the room. Ask how the crew intends to prepare areas that require a different approach and whether those areas must meet the same specified result. Request an explanation of any planned exceptions. An edge-work allowance without a marked boundary can leave the owner and installer imagining different amounts of work.
For an occupied Middle Tennessee business, add a separate access note showing what will be moved, by whom, and when. If a storage rack stays in place, state whether the floor beneath it is excluded or scheduled for another phase. Do not leave that decision hidden inside a general instruction to prepare the entire room.
Keep profile approval separate from other checks
A surface-profile result is not a complete coating-readiness report. Sika's guide separately addresses weak concrete, contaminants, moisture assessment, and environmental conditions. Ask the installer which of those items require project-specific checks and who will supply the results. A satisfactory texture observation should not silently become approval of everything underneath or around it.
Keep the owner's questions organized into separate lines: Is the specified profile achieved? Are identified repairs complete? Have the required substrate and application-condition checks been accepted? Are any locations still excluded? This format makes an unresolved item visible without asking the property manager to diagnose concrete or interpret laboratory results independently.
If preparation exposes an unexpected condition, request a location-marked photograph, the proposed next step, and any effect on price or schedule before approving additional work. Keep the affected area identified while the decision is pending. Do not authorize coating over the location merely to avoid changing the reopening announcement.
Agree on the review before the surface is covered
Schedule a preparation review as an explicit project step. Name the person who can accept the contractor's documentation and the technical reviewer who resolves disagreements, if one is needed. Tell the crew how to reach them. An owner who wants a walkthrough should arrange it before mobilization rather than requesting it after the coating materials are already being applied.
Consider agreeing on a representative trial area before full preparation begins. Define what the trial is intended to demonstrate: the proposed preparation result, treatment at an edge, or coordination with an existing doorway. Do not let approval of a convenient open area stand in for agreement about every difficult location elsewhere on the floor.
The review record can remain concise: date, room or phase, specified target, assessment method, reviewer, outstanding areas, and permission to proceed. Photographs are useful supporting records, but ask for the actual assessment result rather than a photograph captioned looks good. Keep any conditional approval precise enough that the next crew knows which boundaries remain on hold.
Close the gap between preparation and application
Before work begins, ask who controls access between the preparation review and coating application. List any planned activity during that interval, including deliveries, equipment moves, or work by another trade. Ask the coating installer what conditions would require another check before proceeding. This is a coordination agreement, not a universal rule about how many hours a prepared floor can wait.
For phased work, keep separate release records for each area instead of using one building-wide approval. Request the preparation record with the final project documents, alongside the selected coating information and any unresolved exclusions. That record makes a later question about a particular doorway or room easier to trace.
Milliken Corporation lists concrete work and indoor and outdoor coatings among its services. When requesting a proposal, provide the floor's use, available product history, access restrictions, and the result you want. Ask the team to confirm the appropriate scope for your property. A useful proposal makes the preparation deliverable understandable before anyone starts removing the existing surface.
Frequently asked questions
Does a grinding line item prove the required profile will be achieved?
No. Ask for the intended surface-profile result and the agreed assessment method. Naming equipment describes an activity, while the acceptance requirement describes what the prepared floor must satisfy.
Can I approve preparation from photos alone?
Use photographs to locate and document the work, but request the specified assessment record as well. Agree in advance who checks the surface and who resolves a result that does not match the project requirement.
Should every concrete coating project use the same CSP target?
Do not assume so. Have the installer identify the preparation requirement for the selected system and explain any proposed exception. Avoid importing a target from an unrelated project or a general illustration.