3 miles
Sewer length
2
Prior rejections
48
Manholes logged
First-pass
Result
A utility contractor won a municipal gravity sewer replacement contract covering 3 miles of 8-inch and 12-inch pipe across a suburban service area. The work included 48 manholes, multiple alignment changes, and a mix of shallow and deep installations ranging from 6 to 18 feet of cover. City specifications required as-built documentation showing the invert elevation at each manhole, pipe slope between manholes, and any deviation from design alignment.
Final payment was conditioned on engineer acceptance of the as-built submittals. The contract timeline gave the contractor 30 days post-completion to deliver the complete package.
The first submittal was built from paper field notes. Crews recorded invert elevations in a notebook as each section was completed, and the office compiled them into an AutoCAD-derived table and a written narrative report. The city engineer rejected it within a week: invert elevations for seven manholes were missing, pipe slope calculations for two runs contained arithmetic errors, and the horizontal alignment sketch did not match the GPS coordinates on file.
The contractor corrected the gaps and resubmitted. The second rejection came back with a different set of issues: the corrected invert for MH-22 did not match the field book entry the inspector had photographed during construction inspection. Confidence in the data was gone. The engineer requested a full re-survey of the questioned sections before any further review.
The re-survey took four days and consumed a significant portion of the project margin. By the time the third submittal was in preparation, the contractor had spent more than twice the originally budgeted time on documentation.
The contractor began using Sitemark on the next municipal project and carried the workflow into subsequent work on the same contract for additional sewer extensions.
As each section of pipe was installed and backfill reached the manhole, the field crew logged the invert elevation directly into Sitemark using the invert elevation logger — manhole ID, rim elevation, invert in, invert out, and pipe slope. Sitemark calculated the slope automatically from consecutive invert entries and flagged any run where the slope fell outside the specified design range. The crew could verify and correct while still on that section of pipe, before moving the equipment.
Every data entry was time-stamped and tied to the crew member who logged it. Photographs of the manhole interior could be attached to the record. The project engineer reviewed the running log from the office in real time and noted no gaps or inconsistencies by the time installation was complete.
When the city inspector arrived for the final walkthrough, the contractor pulled up the Sitemark as-built on a tablet and exported the PDF while they were standing at the last manhole. The document showed every manhole, every invert elevation, every calculated pipe slope, and the deviation from design — with the flagged sections already noted and explained.
The inspector reviewed it on site, asked two clarifying questions about alignment at the Highway 14 crossing, and signed off the same day. First-pass acceptance. No re-survey. No revision cycle.
The difference was not the quality of the field work — the crew's installation accuracy was comparable across both projects. The difference was traceability. When every elevation entry has a timestamp, a crew member, and an automatic slope calculation, there is nothing to dispute. The data chain from shot to report has no manual re-entry step where errors or omissions can enter.
Paper field notes create a verification problem: the inspector's photograph of the notebook and the contractor's submitted table are two separate documents that can diverge. A digital system with a single record eliminates that divergence entirely.
For this contractor, eliminating the two-rejection cycle on a future project is worth more than the software cost by an order of magnitude. The re-survey alone on the first project exceeded an entire year of Sitemark subscription.
Quick answer
Why do sewer as-built submittals get rejected by city engineers?
The most common rejection reasons are missing invert elevations, arithmetic errors in pipe slope calculations, and inconsistencies between field notes and submitted documentation. Digital logging with automatic slope calculation — like Sitemark's invert elevation logger — eliminates all three failure modes by generating the as-built directly from field data with no manual re-entry step.
Tired of revisions on your sewer as-built submittals?
Start 14-day free trialNo credit card required.