What ASTM E1155 Actually Measures: FF and FL Defined

ASTM E1155/E1155M-23 is the standard test method for determining Floor Flatness (FF) and Floor Levelness (FL) numbers, using a statistical and graphical methodology to describe a concrete slab’s surface profile. It’s not a visual grade or a pass/fail glance, it’s a data set with defined collection rules and math behind every number reported.

FF describes how “wavy” a floor is at a small scale, the amplitude and frequency of bumps and dips measured in short, one-foot increments. FL describes how well the slab holds a plane or slope over longer runs, typically ten feet. A slab can have a strong FF number and a weak FL number at the same time, which is why the two are always reported together rather than blended into a single score (Archtoolbox, “FF and FL Numbers”).

Both numbers come from the Face Floor Profile Numbering System, developed to give engineers and owners an objective way to compare slabs instead of relying on a superintendent’s eye or a straightedge check in a few spots (IFTI, “ASTM E1155: The Definitive Testing Standard”). E1155 also splits floors into two categories, random-traffic and defined-traffic, because a warehouse aisle that only ever sees forklift wheels in the same six inches of concrete needs a different measurement approach than an open manufacturing floor. That distinction shapes almost every layout decision that follows.

Test Planning: Sectioning the Slab and Setting Survey Requirements

Before anyone walks a profiler across the slab, the tested area gets divided into test sections, and the standard sets a minimum amount of measurement line based on section size. This planning step determines whether the final FF/FL numbers actually represent the floor or just a convenient sample of it.

E1155 requires the minimum total survey length (L, in meters) to be at least the floor area (A) divided by 10. A 10,000 square meter distribution center floor, for example, needs at least 1,000 meters of measurement line spread across it (Face Consultants, “ASTM: E1155 M”). Roughly half of that survey length runs in one direction, the other half at right angles or 45 degrees to the longest boundary of the test section, so the data captures unevenness in both axes rather than just along one grain of the slab.

Two hard limits apply regardless of section size. No individual survey run can be shorter than 3.3 meters (about 10.8 feet), and no part of any run can fall within 0.6 meters (about 2 feet) of a wall, column, penetration, or joint (Face Consultants PDF; Archtoolbox). That 2-foot buffer matters because edges and joints naturally read rougher than the field of the slab, and including them would drag the numbers down in a way that doesn’t reflect actual floor performance in the trafficked area. A test plan that skips this buffer, or that concentrates lines in the easiest-to-reach part of the floor, isn’t testing the floor the owner is actually going to use.

Laying Out Measurement Lines: Random-Traffic vs. Defined-Traffic Floors

Layout pattern depends entirely on how the floor will be used. Random-traffic floors, like open manufacturing space or retail floors, get a serpentine grid pattern that changes direction at section boundaries to keep the survey lines continuous and evenly distributed. Defined-traffic floors, like narrow-aisle warehouse racking or AMR robotics paths, get measurement lines placed along the actual expected wheel tracks, usually 3 to 6 inches off the aisle centerline, because that’s the exact strip of concrete the equipment will roll over thousands of times a year (IFTI, “ASTM E1155: The Definitive Testing Standard”).

A 45-degree layout is often used within a serpentine plan: the longest test boundary gets identified first, and runs are set at 45 degrees to it. Simple corner-to-corner diagonals are avoided unless the section geometry genuinely supports them, since a single diagonal line doesn’t give the coverage density the standard requires (YouTube, “ASTM 1155 Course”).

Getting this wrong has real consequences. Test a random-traffic grid on a narrow rack aisle and you’ll capture flatness data from concrete the forklift wheels never touch, missing the wheel-track dips that actually cause rack leg stress and AMR guidance errors. Test wheel tracks on an open floor and you’ll miss cross-aisle waviness that affects foot traffic and equipment staging. The layout choice isn’t a formality, it’s what determines whether the resulting FF/FL numbers mean anything to the people relying on them.

Instrument Setup and Calibration Before Testing Begins

Every E1155 test starts with equipment calibration, and this step is where a lot of unreliable FF/FL data gets prevented before it’s ever collected. Profilers, digital inclinometers, and laser-based systems all drift with temperature and handling, so the standard’s usefulness depends on disciplined setup, not just the instrument’s spec sheet.

Field technicians acclimatize the device to ambient slab and air temperature before powering on, since a cold instrument brought into a warm building (or the reverse) can produce elevation drift in the first several minutes of use. After power-on and stabilization, the technician establishes a zero reference or benchmark elevation point, then runs a calibration check against a known reference, such as a unipod height check held to a tight tolerance, often around ±1 mm (IFTI, “Floor Flatness Testing Process: Technical Overview”). If that check fails, testing doesn’t proceed until the instrument is re-zeroed or swapped.

Modern E1155 work uses several instrument types, including digital profilers, F-meters, profilographs, and 3D laser scanners, but the standard doesn’t care which tool is used as long as it’s producing elevation data at the required precision and the calibration is traceable to a recognized national reference (IFTI, “Floor Flatness Testing Procedure: Step-by-Step ASTM Standards”). A test report worth trusting will document which instrument was used and confirm the calibration check, not just list a final FF number.

The Data Collection Phase: Reading Elevations in the Field

Data collection is where the instrument physically travels the laid-out lines and records elevation readings at fixed intervals, usually every 12 inches (300 mm). This phase has its own procedural rules, because inconsistent walking technique introduces noise that no amount of downstream math can fully correct.

At the start of each line, the technician stabilizes the instrument for 3 to 5 seconds before recording begins, then walks at a steady 1 to 2 feet per second to keep the reading intervals consistent (IFTI, “Floor Flatness Testing Process: Technical Overview”). The instrument stays perpendicular to the direction of travel throughout, and lifting or tilting it mid-run is one of the most common sources of bad data, since even a brief tilt registers as a false elevation change that the software will later read as a real dip or hump in the slab.

Each test line needs a minimum of 11 elevation readings to support the FF calculation (IFTI, “Floor Flatness Testing Process: Technical Overview”). This isn’t an arbitrary number: E1155’s statistical formulas need enough consecutive readings to characterize the wave pattern along a run, and shorter lines simply don’t generate a data set the math can work with reliably. During this phase, technicians also log slab age, ambient temperature, and humidity, all of which matter because concrete continues to move dimensionally in the days after placement, and testing timing affects how representative the readings are of the floor’s long-term condition.

From Raw Data to F-Numbers: The Statistical Calculation Process

Once elevation readings are collected, the raw data goes through a defined calculation sequence to produce the FF and FL numbers that actually appear on the test report. This is the step most people skip past, but it’s the reason two testers using the same profiler on the same floor should land on the same result.

The process starts by computing elevation differences between adjacent points: dz values at the 1-foot reading spacing (used for FF) and dZ values at 10-foot spacing (used for FL) (IFTI, “Floor Flatness Testing Process: Technical Overview”; ASTM E1155/E1155M-23). Per ACI’s description of the underlying method, floor flatness tracks the elevation difference between two points one foot apart and compares that change against every other one-foot elevation change across the measured run (US Anova, “Dismissing Floor Flatness/Levelness Testing? Don’t Get Tripped!”). The dz and dZ data sets are then run through ASTM’s statistical formulas, calculating means and standard deviations and converting them into the final FF and FL values for each test section.

In practice, this math runs through specialized software built to the exact E1155 algorithms rather than manual spreadsheet calculation (IFTI, “Floor Flatness Testing Procedure: Step-by-Step ASTM Standards”). That software dependency is worth knowing about as a reader evaluating a test report: ask whether the calculation software is documented and whether the raw dz/dZ data set is available for review, not just the final FF/FL summary numbers.

Quality Control: Catching Errors Before They Become Disputes

QC is where field data gets checked against itself before it becomes a report someone relies on for a racking approval or a warranty claim. E1155 testing that skips this step can still produce numbers, they just might not be numbers anyone should trust.

A disciplined QC process re-measures a percentage of the original points as a repeatability check, comparing the second pass against the first to confirm the instrument and technician are producing consistent readings. Outlier review follows, flagging any single reading that deviates sharply from its neighbors, since an outlier is usually a sign of a lifted instrument, a debris chip under the wheel, or a joint that wasn’t properly excluded from the run. Unusual site conditions, cracks, construction joints, standing debris, get documented at the time of testing rather than reconstructed later from memory.

This is also where testing timing becomes relevant. Concrete continues curing and can show measurable dimensional movement in the days following placement, so FF/FL testing performed within 72 hours of placement, a common project requirement, captures the slab close to its as-placed condition rather than after later curling or shrinkage has altered the surface profile (Archtoolbox, “FF and FL Numbers”). A test report that doesn’t note the slab age at time of testing is missing a variable that directly affects how the numbers should be interpreted.

Why the Process Matters: Risk, Spec Compliance, and Next Steps

Every phase above exists because FF/FL numbers get used for decisions with real cost attached: racking system approval, AMR and robotics guidance tolerances, ADA-related trip hazard exposure, and warranty documentation tied to the original spec. Treating E1155 as a black-box number that either “passes” or “fails” misses the point of why the standard is this detailed in the first place.

Skipping or shortcutting FF/FL testing carries downstream risk that’s easy to underestimate during construction: trip hazards for foot traffic, chronic performance issues with lift trucks and racking under uneven loads, and robotics that lose navigation accuracy on floors that don’t hold the tolerance their guidance systems assume (US Anova, “Dismissing Floor Flatness/Levelness Testing? Don’t Get Tripped!”). Early testing functions as a QA tool during construction, catching an out-of-tolerance slab while grinding or patching is still a reasonable fix, rather than after racking, conveyor, or robotics installation makes correction dramatically more expensive.

Understanding the process also gives GCs, engineers, and owners a way to evaluate whether a test was done correctly, before disputing a number or accepting one at face value. Ask what layout pattern was used and whether it matched the floor’s traffic type. Ask what instrument was calibrated and how. Ask whether QC re-measurement was performed and documented. A test report that can answer all of that is a report built on the standard’s actual methodology, not just its final output.

Frequently Asked Questions