← Back to Blog

Catch Basin and Inlet Inventory Planning: What Public Works Teams Should Verify Before Field Surveys

Catch Basin and Inlet Inventory Planning: What Public Works Teams Should Verify Before Field Surveys

A catch basin inventory gives public works teams a shared field record for drainage inspections, maintenance, and future stormwater decisions.


Who This Affects

This issue affects municipalities, counties, transportation departments, utilities, developers, civil engineers, survey crews, and contractors who work around curb inlets, yard inlets, manholes, culverts, channels, and private connections. It also affects staff responsible for asset management, public complaints, capital planning, inspections, and emergency response. A field survey is more useful when everyone understands what the inventory is meant to support.

Some agencies have a map but not a dependable asset list. Others have inspection forms that collect detailed observations without a consistent identifier. A planning effort can connect those pieces by defining the asset, the location, the condition fields, the photographs, and the process for updating information after maintenance or construction.

The inventory should not be presented as a permit, approval, or guarantee of compliance. It supports compliance planning and helps a team organize evidence. Local requirements, permit conditions, engineering standards, and ownership questions still need to be reviewed by the responsible authority.


The Stormwater Planning Issue

Catch basins and inlets are small visible parts of a larger drainage system. They connect streets, parking areas, pipes, channels, ponds, outfalls, and receiving waters. A blocked grate can create a localized flooding complaint, but the solution may involve a downstream pipe, private connection, erosion problem, or maintenance responsibility. An inventory helps staff ask that system-level question before assigning a project.

The first planning decision is the unit of record. One agency may track the grate, structure, pipe connection, and inspection as separate records. Another may use one asset record with related components. Either approach can work if identifiers are stable and the relationships are clear. Changing the structure midway through a survey creates duplicate records and makes later comparisons difficult.

The second decision is the level of accuracy needed. A screening inventory may use GPS and street references to locate assets for maintenance. A design or capital project may require surveyed elevations, pipe sizes, inverts, structures, easements, and hydraulic connections. The team should state the intended use so a lower-cost screening effort is not mistaken for design-grade information.

The third decision is the condition vocabulary. Terms such as clogged, damaged, inaccessible, submerged, eroded, or unknown should have a shared meaning. A simple rating scale is useful only when inspectors apply it consistently. Photos should show the asset, the surrounding drainage path, and the problem that supports the rating.


What to Review Before Moving Forward

Start with existing information. Review GIS layers, as-built drawings, maintenance work orders, complaint logs, inspection reports, drainage studies, easements, and recent capital projects. Look for conflicting identifiers and missing areas. A short reconciliation exercise can prevent a field crew from spending time locating an asset that was already replaced or from missing a private connection that affects the public system.

Define the survey boundary. It may be a watershed, a road corridor, a maintenance district, a project area, or a set of complaint locations. State whether the inventory includes private inlets, school or campus facilities, construction entrances, detention facilities, and outfalls. The boundary should match the planning question and the available budget.

Create a field dictionary before the first visit. Useful fields can include asset identifier, date, inspector, coordinates, inlet type, grate condition, frame condition, sediment depth, standing water, visible flow, pipe direction, obstruction, vegetation, safety concern, photo references, ownership, maintenance priority, and follow-up action. Not every field is needed for every use, but every required field should have clear instructions.

Plan for safety. Crews may work beside traffic, in heat, near water, or around unstable covers and contaminated material. The survey plan should identify traffic control, personal protective equipment, confined-space restrictions, and when a structure must not be entered. A map project should never encourage an employee to open or enter a structure without the appropriate evaluation and controls.

Use a consistent photo method. A location photo can show the inlet's relationship to the road and drainage path. A close photo can show the grate, sediment, vegetation, or damage. A downstream photo can show the direction of flow or a potential obstruction. The naming convention should connect each image to the asset identifier and survey date so it remains useful after staff changes.

Plan quality control. A supervisor can review a sample of records for missing coordinates, inconsistent ratings, duplicate identifiers, and unclear photos. A second visit may be appropriate for high-priority or inaccessible assets. The team should also record uncertainty rather than forcing an inspector to choose a confident answer when the grate is buried, the pipe is not visible, or private ownership is unclear.


Planning, Permitting, or Compliance Support That Fits

For public works maintenance, the inventory can support route planning and work-order prioritization. The team can group assets by complaint frequency, condition, sediment, flooding history, or proximity to sensitive areas. This does not guarantee a reduction in flooding or pollutant loading, but it can make the next maintenance discussion more organized and evidence-based.

For MS4 program work, the inventory can support documentation for outfall screening, illicit discharge detection and elimination, construction site runoff control, and good housekeeping. EPA describes these as parts of municipal stormwater management programs. The local permit and state requirements determine what must be documented, how often work occurs, and what follow-up is required.

For a development or redevelopment review, the inventory can help an engineer compare existing drainage assets with proposed connections and flows. It can reveal missing inlets, mismatched elevations, downstream constraints, or maintenance responsibilities that should be clarified during design. It does not promise approval or shorten every review, but early information can reduce avoidable questions and help prepare a clearer submittal.

For capital planning, the inventory can connect condition, consequence, and project opportunity. A damaged inlet near a school, a recurring complaint in a low area, and a failing downstream pipe may belong to one project or to different work packages. The map helps staff explain the relationship, while engineering analysis and local decision-making determine the preferred solution.


Common Mistakes to Avoid

Do not start field collection before deciding what an asset record means. Do not use street address alone when several inlets share a block. Do not erase old identifiers without keeping a crosswalk. Do not treat a map point as proof of ownership, legal access, or hydraulic capacity.

Avoid collecting more attributes than the agency can maintain. A large form with unused fields creates inconsistent data and slows field work. Start with the information required for the decision, then add fields when a real planning need is identified. A smaller reliable inventory is more useful than a large incomplete one.

Avoid using a condition score without a maintenance response. If a score of three means something different to every crew, it cannot support prioritization. Pair ratings with a recommended action, inspection interval, or review flag, and document who can change that recommendation.

Do not assume a visible inlet is the entire drainage story. Trace the available information downstream, compare records with complaints, and note uncertainty. Do not enter a structure simply to complete a field. When a survey reveals a safety or water-quality concern, route it through the agency's established response process.


Next Step

Choose one manageable survey area and write a one-page inventory protocol. Define the boundary, asset identifier, required fields, photo method, safety limits, quality-control sample, and update process. Test the protocol on a small set of inlets, review the records with maintenance and engineering staff, and revise the form before expanding the survey.

The first pilot should include different conditions rather than only easy curb inlets. Include one asset with a complaint history, one with uncertain ownership, one with limited access, and one connected to a known downstream feature. The pilot will show whether the form captures the decisions staff actually make and whether the map can support a conversation between field crews, engineers, and managers.

After the pilot, establish a maintenance loop. When an inlet is cleaned, repaired, reconstructed, or abandoned, the work order should update the inventory and preserve the prior condition. When a public complaint is resolved, the complaint reference can remain connected to the asset. That relationship helps the agency distinguish a one-time obstruction from a recurring drainage problem and can reduce repeated field searches.

The pilot should end with a short review meeting. Ask field staff which questions were difficult to answer, ask engineers whether the records support design or review decisions, and ask managers whether the proposed priority field is understandable. Revise the protocol while the lessons are fresh. That step can reduce later rework, clarify responsibilities, and help prepare documentation that is easier for a reviewer or public works director to follow.

Sources

U.S. Environmental Protection Agency, NPDES Stormwater Program https://www.epa.gov/npdes/npdes-stormwater-program

U.S. Environmental Protection Agency, Developing an MS4 Program https://www.epa.gov/npdes/stormwater-discharges-municipal-sources-developing-ms4-program

U.S. Environmental Protection Agency, National Menu of Best Management Practices for Stormwater Construction https://www.epa.gov/npdes/national-menu-best-management-practices-bmps-stormwater-construction