Floor flatness and levelness exception maps before rack layout release

Direct answer

Before rack layout release, the floor flatness and levelness exception map should identify the building area, slab placement, gridlines, benchmark, survey date, survey method, FF and FL basis where random traffic applies, defined-traffic or automation basis where fixed paths apply, rack layout revision, rack row IDs, aisle centerlines, upright and baseplate zones, anchor zones, construction joints, sawcut joints, curled edges, high spots, low spots, slopes, out-of-tolerance areas, correction plan, retest area, rack designer review, owner acceptance, photo IDs, and release boundary.

The record should make one thing clear: where the floor condition affects rack placement or material-handling travel. A global FF/FL number alone does not tell the rack designer which baseplates need review. A rack layout alone does not prove the floor was surveyed. A red mark on a slab photo does not explain the benchmark, method, tolerance, correction, retest, or whether the layout was released with exceptions.

Do not invent a universal FF value, FL value, Fmin value, TR34 class, straightedge tolerance, rack plumb tolerance, shim thickness, grout detail, grinding limit, acceptance date, or automation requirement. The contract documents, slab specification, adopted code, rack manufacturer, rack engineer, material-handling equipment provider, surveyor, owner standard, insurer, AHJ, and site safety plan control those decisions.

Why this record matters

Rack layout release often happens after the slab is already placed but before the warehouse team has finished every rack, shuttle, conveyor, forklift, or automation decision. If the floor survey sits in a PDF and the rack plan sits in another file, a small elevation problem can become a field conflict at the worst time: when anchors are drilled, uprights are stood, shims are stacked, aisles are painted, or equipment is commissioned.

The purpose of the exception map is to connect concrete evidence to storage-system decisions. It should help the concrete contractor, surveyor, rack designer, rack installer, structural engineer, equipment provider, owner, safety lead, and superintendent see which floor areas are acceptable, which areas need correction, which areas need design review, and which areas are not released for rack layout.

This is different from a general slab placement record. A placement record may prove pour date, mix, finish, curing, and sawcut timing. A rack-layout exception map proves whether the finished floor evidence has been overlaid on the actual rack plan before layout, anchorage, aisle striping, or automation release.

Start with the acceptance basis

Begin by naming the documents that control the floor survey and rack release. Useful references include the slab specification, ACI 117 tolerance section, ACI 302 floor construction guidance, ASTM E1155 or other specified survey method, TR34 or Fmin basis where used, rack design criteria, rack manufacturer requirements, material-handling equipment requirements, approved rack layout, owner warehouse standard, and any AHJ or insurer notes.

ACI 117 is the common concrete tolerance specification reference. ACI 302 explains floor and slab construction considerations, including the need to establish expectations, procedures, and flatness or levelness requirements before work begins. ACI's floor flatness reporting guidance explains why FF and FL reports need interpretation rather than casual straightedge notes.

The exception map should not choose the tolerance after the survey. It should state the acceptance basis already required by the contract, rack design, equipment provider, or owner. If the basis is missing, the release decision should say held for acceptance basis, not acceptable by judgment.

Separate random traffic from fixed paths

Random-traffic floor survey data and defined-path floor requirements answer different questions. ASTM E1155 is associated with FF and FL numbers for randomly trafficked floor surfaces. Its own public summary warns that those results are not the enforcement method for floors primarily intended for fixed-path vehicle systems such as narrow aisle warehouse floors.

That distinction matters before rack layout release. A conventional warehouse floor with random forklift travel may use specified overall and minimum local FF/FL values. A very narrow aisle, shuttle, automated storage, or fixed-path system may need aisle-specific profile criteria, Fmin, TR34, or an equipment-provider standard. The exception map should name which area uses which basis.

Do not let the team treat a passing global FF/FL number as approval for a fixed-path aisle. Also do not let a defined-traffic profile requirement spread to unrelated floor areas unless the contract actually says so. Mark the rack plan with the basis by zone.

Build the exception map

An exception map is more useful than a pass/fail stamp because it locates the problem. Start with the rack layout revision and overlay the survey grid, benchmarks, test lines, sample panels, rack rows, aisle centerlines, column lines, construction joints, sawcuts, door thresholds, pits, trenches, embedded plates, dock areas, and automation corridors.

Show high spots, low spots, slopes, abrupt transitions, curled joint edges, panel edges, control-joint conflicts, and any survey areas that were inaccessible. Give each exception a unique ID. Tie the ID to a station, gridline, rack row, aisle, upright location, baseplate zone, or equipment path that field teams can find without guessing.

A good map distinguishes report data from release decisions. Use one layer for measured evidence, one layer for tolerance comparison, one layer for rack-layout impact, and one layer for corrections and retest status. The point is not a pretty heat map. The point is a release record that installers can trust.

Tie exceptions to rack layout

Rack layout release should not stop at slab-wide values. For each exception, record the affected rack row, bay range, upright line, baseplate group, aisle, anchor zone, pallet position, rack-supported equipment, shuttle rail where used, guide rail where used, and material-handling path.

ICC's 2024 IBC Chapter 22 points steel storage rack design, testing, and utilization to ANSI MH16.1. RMI material explains that rack design and installation depend on building-specific factors, including floor conditions and anchoring. RMI's floor flatness discussion also notes that level floors matter for rack systems and semi-automated pallet handling.

The field packet should therefore tell the rack designer what changed from the ideal floor assumption. If a rack row crosses a known slope, a curled construction joint, or a remediated grind area, the release should identify that condition before anchor layout.

Record survey method and timing

Record who surveyed the floor, when the survey was performed, what method was used, what instrument or profiler was used, what benchmark controlled elevations, what drawing revision was used, what areas were excluded, and whether the slab was loaded, shored, cleaned, cured, or obstructed during the survey.

ACI flatness reporting guidance emphasizes that timing matters because slab behavior can change as curing, curling, loading, and deflection develop. ACI 302 also discusses joints, curling, load transfer, and wheeled traffic concerns that can affect slab performance after placement.

If the rack layout release is happening months after the original FF/FL report, say whether a supplemental survey was performed. A clean 72-hour report may not describe later joint curl, patching, trenching, slab grinding, settlement, loading damage, or floor repairs in the rack area.

Map baseplate and aisle risks

The map should call out baseplate-level risks separately from travel-path risks. Rack baseplates care about local elevation, bearing, shimming or grout requirements, anchor embedment, crack and joint proximity, slab thickness, edge distance, and load path. Aisles care about wheel path, ride, slope, transitions, guide rails, automation path, and clearance.

One exception can affect both. A curled joint under a baseplate can complicate rack leveling and anchorage. A high spot in an aisle can affect lift truck mast movement or shuttle travel. A low area along a row can create shim stacks or grout pads that need rack designer review.

Use the rack layout to classify impact. Mark exceptions as baseplate impact, aisle impact, automation impact, anchor impact, joint impact, housekeeping impact, or no rack impact. That classification helps avoid overcorrecting harmless areas while missing the zones that control release.

Corrections need their own record

Corrections should be recorded with the same precision as the original survey. Common responses include grinding high spots, filling or patching low spots, localized topping, rack baseplate shimming, grout pads, layout adjustment, rack redesign, aisle relocation, or holding an area until the owner and rack engineer decide.

RMI's floor flatness discussion identifies grinding, shimming under rack baseplates, and grout under affected baseplates as possible responses, while tying the choice back to the rack system and floor condition. The article should not turn those examples into universal permission. The correction method still belongs to the design and construction team.

For each correction, record exception ID, method, responsible contractor, approved detail, start and finish dates, photo IDs, dust or debris control where relevant, survey retest limits, and whether anchors, joint fillers, coatings, floor hardeners, embedded systems, or equipment warranties are affected.

Rack designer and owner review

The exception map is not complete until the right people respond. A concrete contractor can mark a high spot, but the rack designer may need to decide whether a baseplate condition, slope, shim stack, grout pad, anchor location, or notional load requires design action.

The owner and operations team may also need to weigh in. A random-storage rack layout has different consequences than a very narrow aisle, robotic shuttle, freezer, high-bay, rack-supported building, or dense automation system. The same elevation condition may be acceptable in a staging area and unacceptable under a shuttle rail.

Record the reviewer, discipline, company, date, layout revision, exceptions reviewed, decision, conditions, and areas held. Avoid vague approval language. Use a release boundary that says exactly what the review covers.

Use an auditable table

Use the surveyor report, rack release form, owner's warehouse standard, or commissioning matrix first. Add a field table where those records do not connect exceptions to rack layout decisions.

Build a photo and survey packet

Photos should make the map verifiable. Capture benchmark, floor survey equipment, slab area, rack layout overlay, exception markings, construction joints, sawcut joints, high spot grind areas, low spot fills, baseplate shims, grout pads, corrected areas, retest marks, and final release labels.

Keep photos tied to exception IDs. A photo named floor issue is weak. A photo named E-07 Row C Bay 12 high spot after grinding is useful because it can be matched to the map, retest, and release decision.

Also keep the raw survey report, processed plan, rack layout revision, correction sketch, reviewer signoffs, and retest report together. The packet should survive turnover without depending on one superintendent's memory.

Retests and failed conditions

Failed attempts should stay in the record. Keep the original survey value or profile note, location, basis, failed condition, correction, retest method, retest date, retest result, and final status.

Common failures include missing acceptance basis, survey performed against the wrong layout revision, rack rows not overlaid on the survey, out-of-tolerance aisle paths, baseplates landing on curled joints, inaccessible areas hidden by stored material, corrections not retested, and rack designer review missing for shim or grout conditions.

Partial release is often the honest answer. Rows A through F may be released for rack layout while Rows G through J remain held for grinding and retest. The map should prevent a broad ready note from releasing a held area by mistake.

Before rack layout release checklist

Run this check before representing a floor flatness and levelness survey as ready for rack layout release.

• Confirm the acceptance basis: slab specification, ACI 117 or project tolerance language, survey method, TR34 or Fmin basis where used, rack criteria, equipment criteria, owner standard, and review authority.
• Confirm the rack layout revision, rack row IDs, bay counts, aisle centerlines, baseplate locations, anchor zones, guide rails, shuttle or automation paths, and areas excluded from scope.
• Overlay survey data on the rack plan with benchmarks, gridlines, test lines, sample areas, construction joints, sawcuts, door transitions, trenches, pits, and slab panel limits.
• Assign exception IDs to high spots, low spots, slopes, curled joints, abrupt transitions, out-of-basis survey areas, inaccessible areas, and areas needing supplemental survey.
• Classify each exception by impact: baseplate, anchor, aisle travel, automation path, rack row, material-handling equipment, housekeeping, or no rack impact.
• Record correction decisions, approved details, responsible contractors, safety controls, photos, and retest requirements for grinding, filling, topping, shimming, grout, redesign, or layout changes.
• Obtain the required review from the surveyor, concrete contractor, rack designer, rack installer, equipment provider, owner, safety lead, engineer, AHJ, or insurer where applicable.
• State the release boundary: released for layout only, released for anchors, released for rack install, released for striping, partial release by row, held for correction, or held for retest.

Weak and strong records

Weak note: Floor flatness report passed. Rack layout can start.

That note does not identify the survey method, acceptance basis, layout revision, rack rows, aisles, baseplates, exceptions, corrections, retests, reviewers, or release boundary.

Stronger note: The slab in Warehouse Area B was reviewed for rack layout release using rack layout R-104 revision 7, survey report FF-AREA-B-02, benchmark BM-3 at grid F/6, and the project floor tolerance schedule in specification section 03 30 00. Survey data were overlaid on rack rows B1 through B12, aisles 1 through 6, and the proposed shuttle corridor. Random-traffic storage aisles were reviewed against the specified FF/FL basis. The shuttle corridor was held for the equipment provider's defined-path review and was not released by the random-traffic FF/FL report.

Exceptions E-01 through E-04 were marked on the plan. E-01 and E-02 were high spots in Aisle 2 outside baseplate zones and were accepted for rack layout after owner review because they do not affect rack rows or equipment paths in the current layout. E-03 crossed Row B7 baseplates at Bays 18 through 21 and was held for grinding and retest. E-04 was a curled construction joint at Aisle 5 and was held for rack engineer review before anchor layout. Rows B1 through B6 are released for rack layout and anchors. Rows B7 through B12 are released for layout marking only and remain held for anchors until E-03 and E-04 are closed.

The stronger note works because it connects survey basis, rack layout, exceptions, corrections, reviewers, held areas, and the limited release.

Common mistakes

The first mistake is treating a global FF/FL number as a rack layout map. Rack installers need locations, not only summary values.

The second mistake is using random-traffic survey results to release defined-traffic aisles or automation paths without the required project-specific review.

The third mistake is surveying against an old rack layout. A changed aisle, bay count, guide rail, or shuttle path can move the risk.

The fourth mistake is hiding inaccessible areas. Stored material, equipment, trench covers, patching, or active work can leave blind spots in the release record.

The fifth mistake is accepting corrections without retest evidence. Grinding, filling, shimming, or grout notes should close with proof and reviewer acceptance.

The sixth mistake is using the exception map as structural approval. The map supports rack layout release only for the scope named in the record.

Questions that come up

Can the rack layout be released if the overall FF/FL values pass? Maybe, but not from that fact alone. The release should also show local exceptions, layout overlay, traffic type, baseplate effects, and any defined-path requirements.

Does every floor exception need grinding? No. Some exceptions may not affect the rack layout or material-handling path. Others may require grinding, filling, shimming, grout, layout changes, or design review. The record should show the decision basis.

Who owns the exception map? Usually the general contractor coordinates it, but the useful record includes the surveyor, concrete contractor, rack designer, rack installer, equipment provider, owner, safety lead, and engineer where their scopes are affected.

Can shims or grout solve every baseplate condition? No. Shim and grout decisions belong to the rack design and installation requirements, slab condition, anchor requirements, and responsible engineer or manufacturer. Record the approved detail and limits.

Should the survey be repeated after rack layout changes? If the change moves rack rows, aisle paths, baseplates, guide rails, or automation routes into unsurveyed or exception areas, a supplemental review is the safer record.

Compliance and safety limits

This field note is not a concrete floor design, slab specification, rack design, rack anchorage design, structural engineering approval, FF/FL test procedure, Fmin test procedure, TR34 interpretation, ACI interpretation, ASTM interpretation, ICC interpretation, OSHA interpretation, equipment-provider acceptance, rack manufacturer instruction, grinding plan, grout detail, shim approval, forklift safety plan, or AHJ approval. The adopted code, project specifications, approved drawings, rack engineer, rack manufacturer, surveyor, material-handling equipment provider, owner, AHJ, insurer, and site safety plan control the work.

Do not use this checklist to bypass barricades, dust controls, silica controls, hot work controls, energized equipment controls, stored material controls, forklift traffic controls, anchor drilling rules, overhead work limits, rack installation instructions, equipment commissioning rules, or qualified-person requirements. OSHA material-handling rules require safe clearances, clear aisles, good repair, marked passageways, and stable storage. The packet preserves floor and rack-layout evidence before release. It does not authorize unsafe work or storage operations.

Sources checked

• ASTM International, ASTM E1155-20 Standard Test Method for Determining FF Floor Flatness and FL Floor Levelness NumbersUsed for official E1155 identity and public context around FF/FL floor profile measurement, random-traffic use, and fixed-path limitation.
• American Concrete Institute, ACI SPEC-117-10 Specification for Tolerances for Concrete Construction and MaterialsUsed for official ACI tolerance specification identity and concrete tolerance basis context.
• American Concrete Institute, ACI 302.1R-15 Chapter 5 Guide to Concrete Floor and Slab ConstructionUsed for floor construction, flatness and levelness expectations, joints, curling, load transfer, racks, and wheeled traffic context.
• American Concrete Institute, The Floor Flatness ReportUsed for FF/FL report interpretation, timing, overall and local value context, and remediation discussion.
• The Concrete Society, TR34 4th Edition Concrete Industrial Ground FloorsUsed for official TR34 publication identity and industrial ground-floor design and construction context.
• International Code Council, 2024 International Building Code Chapter 22 SteelUsed for public code context linking steel storage rack design, testing, and utilization to ANSI MH16.1.
• MHI, Rack Manufacturers InstituteUsed for RMI identity, rack standards context, and industrial steel storage rack industry context.
• Rack Manufacturers Institute, Floor Flatness Critical For Successful Semi-Automated Pallet HandlingUsed for rack floor flatness and levelness context, automation and shuttle path concerns, and correction examples.
• OSHA, 29 CFR 1910.176 Handling Materials - GeneralUsed for material-handling safety boundaries around clear aisles, good repair, marked passageways, and stable storage.

Related guides