Most airport construction QC programs still run on paper binders and spreadsheets. That works — until an FAA inspection. Here is a clear-eyed comparison of every approach, what the FAA actually expects, and what to evaluate when choosing a purpose-built tool.
What software should airport construction contractors use for QC documentation?
Airport contractors need software that captures grade shots at 50-foot station intervals, generates FAA AC 150/5370-10 formatted reports, works offline on remote airfields, and produces QC daily reports accepted by resident engineers. Purpose-built field verification tools outperform paper binders, Excel, and general PM software for FAA compliance.
If you surveyed airport construction QC managers today, the majority would describe some version of the same workflow: a surveyor shoots grade elevations in the field, records them in a paper field book or on a printed grade sheet, and those records are later organized into a binder that gets handed to the FAA inspector. Some contractors have added an Excel layer, where field data is transcribed into a spreadsheet for easier sorting.
This is the most common approach in the industry — and it is also the highest-risk approach. Not because the work is bad, but because paper and spreadsheets create documentation gaps that are invisible until an inspection fails.
Understanding why requires looking at each approach honestly.
Paper grade documentation is deeply embedded in airport construction culture, and for good reason — it requires no technology investment, works without cellular service, and every inspector knows how to read it. On small, simple projects with an experienced QC manager who is meticulous about organization, paper can work adequately.
The problems emerge at scale and under pressure. On a 10,000-foot runway rehabilitation with multiple lifts across multiple work areas, paper binders accumulate fast. Finding the grade shots for a specific station range at inspection time requires sorting through dozens of pages. A missed file, a wet field book, or a night when the transcription didn't get done creates gaps that become inspection failures.
Paper also provides no real-time pass/fail visibility. The crew shoots grade, records numbers, and moves on — with no immediate feedback on whether any shot failed. Deviations are often discovered during office review hours or days after the work is done and equipment has left the area.
Many QC managers have built sophisticated Excel templates for grade documentation — color-coded pass/fail cells, pivot tables for summary reports, station-by-station logs that look organized and professional. When the data is in Excel, it is searchable and sortable, which is a genuine improvement over loose paper.
The core limitation is that Excel has no connection to the field. Data still arrives on paper or via verbal communication from the field crew, and a person has to manually key it into the spreadsheet. That manual entry step is where transcription errors enter the record, and it creates a time gap between when the shot is taken and when it appears in the documentation system.
Excel also has no tamper-evident audit trail. FAA inspectors and contracting officers reviewing AIP-funded project records are increasingly aware that Excel files can be modified without any record of the change. For projects under scrutiny, this creates questions about data integrity that a well-designed digital system avoids entirely.
General construction project management platforms like Procore are excellent tools for what they are designed to do: RFI management, submittal tracking, drawing management, and daily reports. Many airport contractors use them effectively for those functions on the same projects where grade verification is a challenge.
The problem is that these platforms are not designed for grade verification workflows. They do not support importing design elevation data and comparing field shots to design. They do not calculate pass/fail against tolerance automatically. They do not generate the station-by-station elevation logs that FAA contracting officers expect to see. Trying to force a grade verification workflow into a general PM tool typically means building custom forms and workarounds — with the same fundamental limitations as Excel.
Purpose-built grade verification platforms are designed from the ground up for the field workflows that general tools cannot accommodate. When evaluating options, these are the criteria that matter most for FAA-funded airport projects:
The output must match what FAA contracting officers and resident engineers expect to see. Look for station-by-station elevation logs, pass/fail by station, deviation records, and corrective action logs — all in a format aligned with AC 150/5370-10 documentation requirements.
Many airport construction sites have poor or no cellular coverage. The field app must work fully offline, syncing data when connectivity is available. A tool that requires cellular service to record data will fail you at exactly the wrong moment.
The system should allow grade shots to be recorded directly in the field — either by the instrument operator or by a rod person with a tablet. No paper field books, no transcription step, no time gap between measurement and record.
The system should calculate pass/fail against design tolerances (typically ±0.04 ft for runway subgrade) at the moment each shot is recorded. This gives crews immediate feedback and prevents failed areas from being covered before correction.
The Sitemark airport grade verification platform is built to satisfy all four criteria. For a detailed look at what the field workflow looks like and the features that support it, see the airport features page.
For small, simple runway marking or minor grading jobs with minimal AIP funding and an experienced QC team, paper with disciplined organization can be adequate. For anything involving significant earthwork, multiple lifts, FAA resident engineering oversight, or AIP funding that will be reviewed closely, a purpose-built digital system pays for itself by preventing a single failed inspection.
The economics are straightforward. A single failed FAA inspection — stop-work, re-mobilization, crew standby, and re-inspection — costs $20,000–80,000. Purpose-built QC software for airport grade verification costs a fraction of that per project. Survey equipment for airport-tolerance grade verification is available at Express Tools.
Sitemark is designed specifically for FAA-funded airport construction QC — offline-capable, real-time pass/fail, and report formats aligned with AC 150/5370-10 requirements.
Start Free Trial →GPS rovers and total stations capable of FAA-tolerance grade verification. In stock and ready to ship.
Shop Survey Equipment at Express Tools →FAA does not require a specific software product. What FAA contracting officers need is complete, legible, tamper-evident records organized by station, with pass/fail determination against the design. Purpose-built digital systems that produce these records in formats aligned with AC 150/5370-10 are widely accepted.
Excel can organize airport QC records but has significant limitations: no field integration (manual data entry required), no automatic pass/fail logic, and no tamper-evident audit trail. For AIP-funded projects under close scrutiny, Excel spreadsheets are frequently flagged as inadequate because they cannot prove when data was entered or whether it was modified.
Purpose-built grade verification platforms outperform general PM tools on AIP projects. Look for offline field data capture, automatic pass/fail against design tolerances, corrective action tracking, and report formats aligned with FAA documentation requirements. Sitemark is purpose-built for this workflow.