Common Plan Set Errors We See

After reviewing civil plan sets across a wide range of project types — commercial grading, residential subdivisions, public infrastructure — patterns emerge. The same categories of errors appear repeatedly, across firms and project sizes. None of them are the result of careless work. Most are the result of the review process being harder than it looks.

Here are the most common error categories we find, and why they keep slipping through.

Pipe invert mismatches between sheets

This is the most common single error we see. The drainage plan shows a pipe invert at one elevation. The profile sheet shows a different number. Both got updated at different points during design revisions, and the update didn't propagate consistently.

The reason this slips through: cross-sheet coordination requires holding two or more sheets in mind at the same time. In a large plan set, the plan and the profile might be 15 sheets apart. By the time a reviewer gets from one to the other, the specific number they were checking has faded. AI doesn't have this problem — it can hold the entire plan set in memory simultaneously.

Slopes that don't meet minimum standards

Parking lot grading at 0.5% when the local drainage standard requires 2%. Pipe slopes below the self-cleaning minimum. Swale grades that look fine on the drawing but calculate out to flat or reverse when checked against the spot elevations.

These errors typically happen at the edges of a design — the areas that were fit to constraints and got a little less attention than the main design elements. They're easy to miss because the drawing looks right at a glance; the problem only becomes visible when you actually run the numbers.

Callouts referencing missing or wrong details

A plan sheet calls out "See Detail 7/C-8." Detail 7 on sheet C-8 doesn't exist — either it was moved, renumbered, or removed during revisions. Or it exists but it's a generic standard detail when a project-specific one was intended.

This category of error is almost entirely a revision artifact. Early in the project, the reference was correct. Then something changed — a sheet was reorganized, a detail was consolidated — and the callout didn't get updated. The original author knew what they meant; a contractor in the field won't.

ADA non-conformances at transitions

Ramp slopes that technically pass when measured in isolation but exceed limits when you account for cross slope. Landings that are too small. Transitions between sidewalk and curb ramp that create a grade change the design didn't intend.

ADA compliance requires checking a combination of conditions — running slope, cross slope, landing dimensions, transition geometry — that interact in ways that aren't always obvious from a single sheet. These findings often appear at the edges of a grading plan where the geometry got complicated.

Drainage study numbers that don't match the plan

The drainage report shows a 100-year peak flow of X cfs through a given inlet. The inlet on the plan is sized for a lower flow. The plan was revised after the drainage study was finalized — or the drainage study was updated and the plan wasn't.

This is one of the harder errors to catch because it requires comparing a plan sheet to a separate document, not just two sheets within the same set. But it's also one of the more consequential — a drainage system sized for the wrong flow rate is a liability.

What the pattern tells us

Almost all of these errors share a root cause: something changed somewhere in the design, and the change didn't propagate consistently to every place it needed to go. That's not negligence. It's the natural consequence of designing a complex document iteratively, under schedule pressure, with multiple people making changes.

The solution isn't a better checklist — it's a systematic process that looks at the entire plan set holistically, every time, before submittal. That's exactly what AI-powered review is built to do.