Manhole inspection contracts: requirements for US sewer buyers
Require a defined asset inventory, explicit inspection methods, coded findings linked to photographs, and a structured handover tested against the municipality’s asset register. Make the following checklist contractual rather than relying on an inspection-level label or a PDF report.[2][3]

- Required in the proposed base scope: asset identifiers, inspection and exception records, selected component coverage and measurements, condition codes, supporting media, structured data and acceptance checks.
- Optional unless expressly selected: additional capture products such as sidewall imagery, point clouds and models, which ITpipes describes as possible additions.[3]
These are proposed procurement conditions, not a statement of nationwide inspection obligations.
Define the inspection population and access
Issue a controlled starting inventory and name the municipal role authorized to approve changes to asset records. Treat field corrections as proposals, not permission to overwrite the GIS.
The Manhole Condition Assessment specification requires locating structures from the city GIS map, collecting sub-meter-grade GPS coordinates at manhole or lamphole covers, and documenting structures not found, not at grade or absent from GIS plans. These are requirements in that specification, not a nationwide acceptance standard.[2]
Use a buyer-defined outcome list separating access exceptions from condition findings:
- Inspected: Link the completed inspection to the assigned asset ID.
- Not found: Record the attempted location and evidence; do not treat absence as confirmed removal.
- Not at grade: Document the situation and recommended access work.
- Inaccessible: Record why inspection could not proceed without assigning an unsupported condition rating.
- Newly discovered/GIS-missing: Assign a provisional discovery ID pending municipal matching or creation of an authoritative record.
For each exception, require the source or provisional ID, attempted location, observation date, reason, evidence, revisit recommendation and reconciliation status. Preserve original IDs alongside proposed corrections until the municipality resolves the match.
Specify the coordinate reference system, accuracy-validation method, provisional-ID convention and GIS-edit approval workflow. Assign responsibility for locating structures, access, traffic management, cleaning, revisits and authorization of additional work.
Proposed completeness rule: Every assigned asset must have an inspection record or documented exception; newly discovered structures must remain traceable while awaiting an authoritative ID.
Replace level labels with explicit methods and evidence
The Manhole Condition Assessment specification associates Level 1 with full-access manholes and Level 2 with small-diameter maintenance access or cleanouts. ITpipes instead describes Level 1 as fast visual screening taking 10 to 15 minutes per structure, with 40+ structures per day, and Level 2 as a full diagnostic inspection taking 25+ minutes per structure, with 10 to 14 per day and measurements for every component.[3] Those labels are not interchangeable.[2][3]
Write the selected assessment terminology, version and complete level definitions into the contract. For each method, specify the decision supported, component coverage, measurements, evidence and limitations.[2][3][4]
- Screening: Support triage using surface observation or a zoom camera. Identify components that must be visible, record obscured areas, specify dimensions separately, and require photographs, observations and video where selected. ITpipes-sponsored guidance describes surface inspection as visual notes without measurable defects and zoom inspection as video with limited measurement.[3][4]
- Detailed remote assessment: Support rehabilitation or replacement planning using a defined camera or scanning system. List component measurements and require coded observations, defect photographs, video and structured records. The sponsored guidance describes measurable detail from 360-degree capture and point-cloud outputs from scanning; specify system-specific measurement acceptance criteria rather than assuming accuracy from the method name.[3][4]
- Specialist-defined entry: Address questions requiring tactile examination. Have a specialist define suitability, coverage and measurements, and specify photographs and recorded findings. The sponsored guidance distinguishes tactile inspection from remote capture and identifies confined-space entry as part of this method.[4]
Require specialist review of whether the selected method can answer the intended condition question. State the contractual boundary: visual observations are not to be accepted as proof of structural integrity.
Keep entry safety separate from the data checklist. OSHA’s account of a fatal manhole incident in 2004 describes a worker found unconscious after being assigned grouting work.[1] If entry is proposed, require a qualified specialist to define applicable confined-space controls before work proceeds; the incident account is not a project-specific safety program.
Specify an escalation route for access or visibility limitations: record the missing observations and obtain municipal direction before additional investigation.
Specify identifiers, condition codes and photographs
Put the record relationships in a data dictionary. ITpipes describes structured Header, Component Observation and Component Details record groups; require an agreed exchange format and schema version rather than leaving the database structure to the contractor.[3]
Use this proposed contractual minimum, with local field names, identifier formats and null-value conventions:
- Asset identity: Municipal asset ID and corresponding inspection-record identifier.
- Inspection event: Unique event ID, asset ID, date, method and completion status.
- Component observation: Observation ID, parent inspection ID, component, location, condition and applicable measurements.
- Coded defect: Defect ID, linked observation, code, grade and coding-system version.
- Evidence reference: Media ID, linked event and observation, filename or path, and applicable timestamp or frame reference.
Specify coverage of cover and frame, chimney, cone, wall, bench and channel, and pipe connections—the six component groups described by ITpipes. For connections, require material, shape, diameter, direction, condition and seal integrity where included in the selected scope.[3]
Define the media package by method. ITpipes identifies area, cover-and-frame and open-cover top-down photographs, plus photographs linked to each coded defect for its comprehensive inspection description. Its described package also includes full-HD descent or ascent video.[3]
Specify naming and folder conventions, stable media references and explanations for missing evidence. Require applicable video to link to inspections and observations through timestamps or frame references. Keep point clouds, models and additional imagery outside the base scope unless expressly selected.[3]
Keep ratings traceable to observations
Retain individual coded observations and evidence alongside summary ratings. ITpipes describes separate structural and operations-and-maintenance defect grading on a 1–5 scale; this is the vendor’s description, not independent verification of the underlying standard.[3]
ITpipes recommends overall-rating measures for rehabilitation ranking and separate structural filtering for capital needs. It describes OMR as the sum of each defect grade multiplied by its occurrence count, and MRI as OMR divided by total defects. Specify the measures to deliver while keeping municipal intervention thresholds and capital-ranking policy separate from those calculations.[3]
Define summary fields explicitly: ITpipes uses “Quick Rating” or “QR,” while the ITpipes-sponsored article labels its worked example “QSR.” Require a definition and calculation rule rather than assuming the labels are interchangeable.[3][4]
Add a proposed action field separating maintenance follow-up, engineering review and further investigation, with a rationale linked to observations. This should complement the evidence, not create an unsupported repair trigger.
Test a sample handover before production acceptance
Have asset management, engineering and GIS staff review the same sample package. The Manhole Condition Assessment specification references two completed sample inspection forms; a pilot-import gate is an additional proposed procurement control, not a process established by that specification.[2]
Select a sample exercising an ordinary inspected asset, multiple coded observations and an inventory exception. Require:
- The written report and structured inspection database.
- Photographs and applicable inspection video.
- Code definitions and a field-mapping document showing how delivered fields map into the asset register.
ITpipes describes report, photograph, video and structured-database outputs, identifying the database deliverable as a NASSCO Exchange Database file; the code definitions and mapping document are additional proposed handover requirements.[3]
Run a trace-through test: Start with the source GIS asset ID, follow it into the inspection header, then through a component observation and defect code to its photograph or video reference. Locate that finding in the imported asset-history record, not just the contractor’s viewing software.
Use these proposed sample pass conditions:
- Records join to the intended asset without unexplained duplicates.
- Asset, inspection and observation relationships survive import.
- Media links open the correct evidence.
- Exceptions remain distinguishable from completed inspections.
- The report agrees with the structured data.
Require correction and a successful repeat import before accepting routine production submissions.
Write measurable acceptance and correction conditions
Make final acceptance depend on usable records, not report delivery. The inventory exceptions and structured data-and-media outputs provide a basis for these proposed checks.[2][3]
The cited assessment specification and ITpipes guidance do not prescribe municipal validation tolerances, review percentages, correction deadlines or final sign-off rules.[2][3] Define them in the contract, name the reviewer and acceptance authority, and specify how errors will be returned and corrected.
- Reconcile the assignment: Account for each assigned asset through a completed inspection or documented exception. Resolve unmatched records and duplicates without silently deleting findings.
- Validate the dataset: Check asset matches, required fields, permitted codes, coordinate reference system, accuracy metadata, unique inspection IDs and observation-to-media links.
- Review evidence manually: Set the sample and tolerances for checking coding against imagery, component coverage and report accuracy.
- Separate limitations from omissions: Distinguish municipality-accepted access or visibility limitations from missing deliverables requiring correction.
- Test corrected files: Repeat the agreed validation and import checks, including media links. Treat ITpipes’ integration statements as vendor claims, not assurance of compatibility with a particular asset register.[3]
The acceptance condition should be explicit: each assigned asset is accounted for, and each finding remains traceable from the asset record to its supporting evidence under the agreed schema.
References
- Confined Spaces in Construction – Manhole Slides | Occupational Safety and Health Administration (osha.gov, 2004)
- MANHOLE CONDITION ASSESSMENT (speakcdn.com)
- Manhole Inspection Best Practices for Municipal Sewer Systems – ITpipes (itpipes.com)
- Manhole Inspection Best Practices for Municipal Sewers (mswmag.com, 2026)