Culvert Inventory in 2026: Map Drainage Assets and Plan Inspections

One failed culvert on Washington’s SR 503 Spur led to an emergency repair project estimated at $1 million. Heavy rainfall caused the December 5, 2023 failure near Cougar. Both directions closed; one lane reopened on December 7, and both lanes reopened on December 23 after culvert replacement and roadway repairs. WSDOT’s project page reports the estimate and reopening dates.

A county cannot schedule an inspection against an asset that has no dependable location or record. The first task is to know which crossings exist, which department owns the next action, and which upstream changes deserve a closer look. A pin at the middle of the road leaves the inspector with plenty to sort out.

Asset Search by PorchRocket finds visible drainage assets and reconciles them with property records and public datasets. Municipal staff and their engineering primes receive dated evidence and reviewed answers. Drainage contractors can use the same approach to define service territories and prepare field visits. I would start with the maintenance decision, then specify the evidence needed to make it.

What belongs in a county drainage inventory?

Include each crossing with its endpoints, then link the connected drainage features your county must inspect or maintain.

Define the counting unit first. One crossing can contain several barrels. Each barrel has endpoints, and an outlet may also carry a regulatory outfall designation. Counting photographs or endpoints as separate culverts inflates the crossing count and confuses inspection quantities.

I would give the crossing one permanent parent ID with linked records for its barrels and endpoints. Keep the receiving basin or channel in its own layer. An inspector can then work by barrel while the road superintendent budgets by crossing.

Asset or feature	Recommended record	Decision the record should support
Road-crossing culvert	Crossing ID with linked barrels and endpoints	Assign the inspection route and responsible road agency
Driveway or entrance crossing	Separate crossing record with access and responsibility fields	Establish whether it belongs in the public maintenance scope
Culvert inlet and outlet	Endpoint locations linked to the crossing	Direct the crew to the correct side and opening
Catch basin or drop inlet	Structure record with documented connections	Scope surface inspection or cleaning
Roadside ditch or open channel	Segment between defined junctions	Assign the length and limits of a maintenance task
Stormwater discharge point	Physical outlet record plus separate permit classification	Reconcile the MS4 outfall register
Pond or detention basin connection	Link to a separate basin record	Coordinate upstream or downstream work
Upstream obstruction or land change	Dated observation linked to affected candidates	Request a field investigation or engineering review

Use existing plans as evidence, then verify the fields that drive work. FHWA’s culvert management case study describes collecting inventory attributes from design and construction records with field verification, while maintaining condition information separately. The distinction still matters when both datasets live in one GIS.

Agree on exclusions as well. An abandoned pipe, a private entrance outside the contract and a duplicate record should each have a recorded disposition. Record the rejection reason. The next reviewer should not have to investigate the same rejected candidate again.

FHWA culvert inspection rules in 2026

The federal bridge program covers qualifying highway structures, while smaller drainage crossings need inspection schedules drawn from the agency responsible for them.

Under 23 CFR 650.305, the bridge definition includes an opening greater than 20 feet, measured along the roadway centerline, with specified treatment of multiple boxes and closely spaced pipes. Pipe length under an embankment is a different measurement. A long, narrow barrel does not qualify merely because it runs a long distance underground.

For qualifying structures, section 650.311 uses risk-based inspection methods. Method 1 sets a regular interval of no more than 24 months, with provisions for reduced and extended intervals. The National Bridge Inspection Standards text contains the criteria; FHWA’s current program page links the rule and interval guidance. Do not copy that interval onto every small culvert in the county register.

Have the bridge program manager resolve classification. Record the governing program and source document in the working file. Name the person who approves the interval and send missing due dates to that reviewer before dispatch.

A county-wide purchase should also distinguish a location survey from an engineering inspection. Ask bidders to identify who supplies each deliverable and who accepts it. A search team can locate a visible headwall; the inspection team supplies the findings required by the owner’s program.

Carry that separation into progress reports. Count located crossings separately from accepted inspections, and give records reconciliation its own count. Otherwise, a large mapping batch can make an inspection backlog appear smaller even though no condition assessment has been performed. I would also ask for a list of assets awaiting program classification before approving the next fieldwork package.

What does MS4 outfall mapping require?

For regulated small MS4s, federal permit requirements include a storm sewer map locating outfalls and identifying the waters receiving their discharges.

The mapping provision is 40 CFR 122.34(b)(3)(i)(A). It calls for outfall locations and the names and locations of receiving waters of the United States. Read the jurisdiction’s applicable permit for its required attributes and implementation schedule.

The map belongs inside an illicit discharge detection and elimination program, usually shortened to IDDE. EPA describes mapping alongside discharge investigation, prohibition and education. Finding a pipe end supplies a location for that work; it does not settle the discharge classification.

I would keep the observed outlet and the permit designation in different fields. Name the apparent receiving feature and attach the connection evidence. Identify the reviewer who accepted the classification. If the outlet drains into another conveyance, preserve that relationship instead of assigning the nearest named stream automatically.

TxDOT provides an operating example. Its Advanced Outfall Tracking System stores field-collected locations, associated images, inspection information and follow-up investigations. Those linked records let staff revisit a discharge point without starting its history over.

Have the road department and stormwater program agree on shared IDs before delivery. Both teams can use the same location evidence and link future inspections without merging their responsibilities. Add the stormwater pond inventory where basins form part of the network, and keep the impervious-surface inventory for stormwater programs linked by parcel or drainage area. Each dataset answers a different operating question.

What can aerial imagery show around a culvert?

Asset Search can identify visible openings and exposed drainage features, then connect those observations to candidate crossings and dated records.

Start at the road corridor. Look beyond the pavement. Follow the open channel toward the road and examine where it appears on the opposite side. Use exposed openings or headwalls to identify candidate endpoints. Keep the connection provisional until plans or a field check establish it. Record visible access paths too.

The search rules should describe what counts as evidence. An exposed opening may establish an endpoint. A dark patch beneath trees may justify another view. It should not silently become a confirmed pipe mouth because it sits where a pipe would be convenient.

Asset Search cross-references aerial and satellite views with property records and public datasets. The search includes unlisted assets beyond the existing inventory. People review every candidate before delivery. Each disposition explains the result:

• Fits: the visible evidence satisfies the agreed search definition.
• Rejects: the candidate fails that definition, with the reason retained.
• Unresolved: one identified field check is needed to settle the question.

For drainage work, define “fits” around asset identification. Keep engineering condition in the inspection record. “Visible outlet consistent with a crossing” and “barrel acceptable for continued service” answer very different questions.

I would require both the image capture date and review date. A newly reviewed old image remains old evidence. Record which view supports each endpoint, especially when the two ends are visible in different editions.

Use the asset inventory from aerial imagery guide to scope a larger search across several departments. For this job, the acceptance test is narrower: can the receiving team identify the crossing, inspect the evidence and assign the remaining question without repeating the desk research?

Watch upstream changes between inspections

Track newly paved or cleared land alongside channel obstructions using dated views, and attach each change to the downstream assets needing review.

EPA connects developed surfaces with increased runoff volume and velocity. That supports watching development around a crossing. It does not establish how much additional flow reaches a particular pipe; use approved drainage plans or engineering analysis for that answer.

Write the observation in terms the reviewer can verify: a new roof footprint, a paved access road, or an enlarged cleared area between two dated views. Add the parcel and relevant drainage records. The engineer can then decide whether the change belongs in a catchment review or an inspection request.

Beaver activity deserves its own observation category. New York’s environmental agency describes beaver-related flooding and removal of material beside culverts. A visible impoundment or woody obstruction can warrant a field check, but an image of standing water alone does not identify the cause.

Assign a specific question: “Check the obstruction upstream of the west inlet and document the water path.” Give the reviewer the earlier and later views. Avoid sending a crew an instruction that already assumes the diagnosis.

Where removal becomes part of the job, check the local authorization before pricing it. In New York, DEC’s nuisance beaver guidance requires authorization for disturbing beaver dams. Its culvert maintenance permit is available only to certain organizations and covers property they own or maintain a right-of-way on. Identify the eligible applicant and permit responsibility in the work order.

I would review growth corridors quarterly when suitable imagery arrives, then flag observed changes for the program manager. A repeated flooding complaint needs a field response on the agency’s schedule. Keep the imagery refresh date and the response deadline separate.

Field verification that settles the next decision

Give inspectors a location backed by dated evidence and one explicit question to settle, with findings returned against the same asset ID.

A corrected location and photograph can settle an endpoint question. A barrel condition assessment requires an inspection method selected for the structural question. Have the responsible engineer specify that method before mobilization.

MnDOT’s Enhanced Culvert Inspections Best Practices Guidebook compares end-of-pipe observation with enhanced methods such as CCTV. Its access discussion covers submerged outlets and vegetation, along with traffic or private-property constraints. Use those distinctions to scope the visit instead of giving every candidate an identical inspection allowance.

My field handoff would contain these instructions:

• Verify the crossing ID against the road reference and recorded endpoints. Correct the location while retaining the original observation.
• Confirm dimensions and material using the approved field method or supported records. Record the measurement source.
• Photograph the relevant opening and its surroundings so the reviewer can orient the image.
• Document the connection or leave it unresolved with the reason. Do not draw a buried alignment from convenience.
• Return the required inspection findings in the owner’s format and assign any follow-up work.

Include access arrangements in the dispatch file. A parcel record identifies a property; it does not grant entry. Ask the field supervisor to settle traffic control, permissions and the inspection method before the crew arrives. Keep barrel entry outside an ordinary location-check assignment.

When the crew can reach the inlet from a public shoulder but the outlet sits beyond a fenced parcel, dispatch should identify the approved access route and the person arranging entry, so a location-check visit does not end with a photograph taken from the wrong side of the fence.

For acceptance, compare the returned evidence with the original question. A photograph of a ditch does not settle which opening carries the crossing. Send an incomplete answer back against the same record, with the missing observation named.

Give crews a way to add a newly discovered asset during the visit. Preserve its location and field evidence, then put it through the same review. The search should improve the register in both directions: resolving candidates from the desk and accepting findings that only the field visit revealed.

A culvert inventory template crews can use

Use stable IDs to connect each asset with its supporting evidence and assigned work, while maintaining a linked inspection history.

I would test the following field groups on a small batch before expanding county-wide. The acceptance question tells the receiving team why the field earns its place. If nobody uses a requested attribute in a decision, remove it from the first edition.

Field group	Recommended contents	Acceptance question
Identity	Crossing ID, existing agency ID, barrel ID and endpoint ID	Can another department match this record without renumbering it?
Location	Coordinates, coordinate system, road reference and endpoint geometry	Can the crew reach the intended opening?
Asset description	Crossing type, barrel count, dimensions and material	Is the source recorded for each populated attribute?
Evidence	Capture date, review date, view reference and records consulted	Can the reviewer reproduce the finding?
Responsibility	Parcel owner, road owner, maintenance party and supporting document	Who accepts the next action?
Disposition	Fits, rejects or unresolved; reason and field question	Is the decision supported by the attached evidence?
Inspection	Inspection ID, date, method, inspector role and accepted findings	Does the record point to the approved assessment?
Work planning	Assigned task, priority reason, due date and completion reference	Is someone responsible for closing the task?

Use an explicit unknown value when evidence is missing. A zero diameter means something different from an unmeasured diameter. An empty material field should not become a default material during import.

For an illustrative template test, give a crossing two barrel records and a confirmed inlet, but leave the downstream endpoint unresolved until the crew establishes whether the opening behind the fence belongs to that crossing or to the private entrance beside it, retaining both candidates and the evidence for the final decision.

Keep parcel ownership separate from maintenance responsibility. I would ask the county to resolve that assignment from its records and agreements, then record the document used. A nearby owner’s mailing address is a research lead, not a maintenance instruction.

Test the import before acceptance. Use a multi-barrel crossing alongside a rejected duplicate and an unresolved endpoint. Confirm that photographs remain attached to the right records and existing IDs survive the import. For spreadsheet delivery, retain the same relationships in separate sheets with explicit linking fields.

How to prioritize culverts for inspection

Use reported problems and documented service consequences to set priorities, with the responsible engineer approving the inspection action for each crossing.

Start with the decision the county must make this season. A road superintendent may need to group maintenance stops before paving. A stormwater manager may need to resolve discharge classifications. An engineering prime may need survey access for a replacement design. Each should be able to filter the same register without rewriting it.

I would use four work queues:

• Immediate referral for a reported roadway or drainage problem that needs the agency’s response procedure.
• Scheduled inspection for assets already assigned a due date by the governing program.
• Targeted verification for a missing connection, uncertain endpoint or upstream change.
• Records reconciliation for duplicate IDs, responsibility questions and unsupported attributes.

An easy location check can clear several rows quickly. Keep it behind a scheduled inspection unless the program manager changes the priority. Report outstanding inspections separately so closed mapping questions do not conceal overdue assessments.

For routine verification, group nearby assignments after priority is set. Attach the same access arrangements to assets that share an entrance. Mark the correct approach side and road reference so the crew does not cross the corridor twice just to discover which opening the office meant.

Review rejected candidates in the pilot as well as accepted ones. If the search dismisses an obscured opening that the crew later finds, revise the rule for similar candidates across the territory. Checking only the accepted locations cannot reveal assets missing from that set.

I would keep priority reasons in plain language. “Outlet not located; verify before the drainage package is priced” tells the project manager what to do. An unexplained priority score does not establish the next task or its owner.

Where a route includes county crossings and private entrances, the supervisor should be able to separate authorized inspections from access or responsibility questions without deleting either set of records, because the county needs to retain the evidence for a rejected work assignment when the same location appears in a later complaint.

Finding culvert inspection contracts and public work

Search for drainage inventory, hydraulic structure inspection, outfall mapping and storm drain cleaning as separate scopes, then match each opportunity to your crew’s capabilities.

For contractors, I would begin with the owner’s deliverable and work limits. Check whether the contract pays for locating structures, inspecting barrels, cleaning pipes or supplying engineering reports. Quote each authorized task explicitly. A count of crossings alone leaves the estimator without pipe lengths, access needs or the required inspection method.

Read the solicitation for qualifications and acceptance requirements before committing estimating hours. Where an engineering prime holds the program, define your subcontract around the work you can deliver: field location checks, inspection support or authorized maintenance. Ask which party approves the findings and whether the prime supplies the owner’s GIS format.

Separate mobilization from production. Include inspection work and data closeout in the bid worksheet, with allowances for required traffic control or access preparation. Use the question period to settle how uncertain quantities will be measured and paid before committing to a unit rate. Price repeat visits under the solicitation’s terms.

Bid Control by PorchRocket organizes relevant public opportunities with their bid documents and addenda. For drainage firms pursuing county work, Bid Team’s bid preparation service fills the forms, works the estimate with you and tracks the packet. You make the final call on your number, sign and send. Use the public paving contract guide when drainage repairs sit inside a roadwork package.

Before submitting, match the work-item counts to the inventory. One crossing with several barrels should not become several mobilizations unless the scope requires them. Separate the inventory count from field production quantities. Give payment quantities their own column so the estimator can trace a difference back to the scope before the bid is due.

What is one verified drainage asset worth?

In the county model below, a verified destination saves $35.10 in crew operating time per crossing during the first inspection round.

Say a county schedules 286 crossings with a two-person crew. Assume each person costs $47 per paid hour including labor burden, and the truck costs $23 per operating hour. The combined rate is (2 x $47) + $23 = $117 per crew hour.

Assume inspection and travel between assigned assets take 42 minutes per crossing. Poor location records add another 18 minutes spent locating openings and resolving directions. Reviewed locations remove that extra time. The model values one inspection round, assumes all 286 reviewed locations are accepted, and includes no overtime premium or change in inspection scope. The low and high cases change only the avoidable location delay to 9 or 27 minutes.

The arithmetic is 286 x 18 / 60 = 85.8 crew hours released. At $117 per hour, the operating-time value is $10,038.60. Per accepted crossing, 18 / 60 x $117 = $35.10.

Case	Minutes avoided per crossing	Crew hours released across 286 crossings	Value per crossing	Total operating-time value
Low	9	42.9	$17.55	$5,019.30
Base	18	85.8	$35.10	$10,038.60
High	27	128.7	$52.65	$15,057.90

Measure the location time during the pilot. Keep the crew rate and crossing count fixed. Include time spent checking or correcting delivered locations when measuring the net minutes released.

At the base assumptions, a 60-minute assignment falls to 42 minutes. Assume eight productive field hours, with yard travel, breaks and daily closeout outside that allowance. The crew can finish eight crossings before the change and eleven whole crossings after it. That is three more inspections with the same crew and truck. The remaining eighteen minutes do not fund a twelfth stop.

Use the route-density calculator to replace the travel assumptions with your territory’s numbers. Keep time released and cash saved separate: paid staff time becomes capacity for other work unless it reduces an expense. Do not add the value of three extra stops to the saved-time total; they describe the same gain.

For a contractor, compare that released capacity with the work you can sell and deliver. For the county, name the deferred inspections it would cover. Leave avoided failure costs outside this model unless the agency has a separate engineering analysis supporting them.

Cost per accepted asset and the pilot decision

Compare inventory proposals against the same accepted deliverable, then judge the pilot by verified locations and net field time saved.

A drainage inventory quote should identify the search boundary, included asset types, record research and evidence requirements. Specify whether the job reconciles an existing register or searches for missing assets across the territory. Those are different workloads even when they cover the same road mileage.

For Asset Search, I would use per-investigation terms when the county needs every existing candidate resolved, including duplicates and out-of-scope structures. Per-accepted-result terms fit a discovery assignment where the buyer defines an acceptable new find. Ongoing monitoring fits a subscription. Most buyers start with a small paid pilot credited toward the full order.

Make acceptance measurable before comparing quotes. Define a crossing, the evidence needed to accept it and how unresolved endpoints will be handled. Require all dispositions to be returned so the buyer can inspect rejected candidates as well as the delivered finds.

Calculate your own cost per accepted asset by dividing total project cost by accepted assets. Include county review time and any required verification expense in the numerator. Keep newly discovered crossings separate from corrected records so the denominator says what was bought.

If a proposal charges by accepted result, specify whether acceptance means a newly found crossing, a corrected existing location or a resolved endpoint, and state how the buyer will treat multiple barrels at one crossing, so each party can reconcile the invoice against the same register without recounting the territory.

My expansion rule is straightforward. Proceed when the pilot passes the agreed location checks and measured operating benefits exceed the search cost plus county review and verification effort. If corrections consume the gain, fix the definition or delivery before expanding. Compare accepted crossings rather than spreadsheet rows.

How to build a culvert inventory, step by step

Use an eight-step first-month plan to define the territory, test the search and deliver an accepted register with assigned fieldwork.

1. Choose the decision and boundary. In the first week, name the road district, drainage area or maintenance portfolio. State whether the immediate output is an inspection route, an MS4 map update or quantities for a contract. Identify the county staff member who accepts the file.

2. Gather the existing evidence. Assemble current asset IDs, available plans, inspection records and maintenance reports. Preserve the original identifiers. Ask the road and stormwater teams to identify known disagreements, including crossings whose location or maintenance party remains uncertain.

3. Scope the Asset Search pilot. Use the drainage search request to specify visible inlets, outlets, ditches and upstream changes. Set search rules with your technical team, request dated evidence and every disposition, and agree on the GIS-ready or spreadsheet delivery. Start with a paid pilot credited toward the full order.

4. Review a varied set of sites. Include open corridors and obstructed locations, plus known assets and areas where records are thin. Test the definition of a crossing. Check whether reviewers handle multiple barrels consistently and whether an obscured endpoint becomes an explicit field question.

5. Run targeted field checks. Send the crew the evidence and question for each assigned location. Measure time spent locating the asset, correcting the record and performing the task. Review some rejected candidates and independently search a selected area for omissions.

6. Accept the data structure. Import sample records into the receiving system. Confirm coordinate handling, linked photographs and existing IDs. Have the inspection lead approve how field findings attach to the inventory before accepting the larger delivery.

7. Assign the first work package. Separate location verification from required inspections and maintenance. Group nearby routine tasks after setting priorities. For contractor estimates, reconcile crossing counts with the work quantities and payment units in the solicitation.

8. Set the update responsibility. By the end of the first month, name who closes field questions, incorporates repairs and reviews the next imagery edition. Choose a refresh cadence around the decision, and expand only after the pilot’s evidence and time measurements support it.

Keep the pilot small enough that the people who use the file can inspect its details. I would rather have the field supervisor challenge the endpoint convention during that first batch than discover that every exported point sends the crew to the wrong side of the road.

Updating the register after repairs and storms

Update records when accepted fieldwork or construction changes them, and use dated imagery reviews to identify territory changes that deserve another visit.

Tie each repair to its asset ID and supporting completion record. If a crossing is replaced, retain its relationship to the retired structure so earlier complaints and maintenance records remain traceable. A removal needs an effective date and evidence; a missing opening in one image needs further review.

Retain the observation history. Attach the crew’s latest photograph alongside the earlier aerial view, with both dates visible. Link the accepted repair record before changing the asset status. Preserve the earlier evidence.

Asset Search can recheck territories as new imagery arrives. It can also re-answer previously searched sites when the buyer changes the requirement, often using evidence already collected. If the county adds driveway crossings to the scope, review earlier rejects under that new definition before ordering another county-wide search.

For planning, I would start with an annual register reconciliation and quarterly imagery reviews in fast-changing corridors. Those are suggested operating cadences. Preserve the inspection schedule required by the governing program and the agency’s response process for reported storm damage.

Near-real-time monitoring is available where daily satellite coverage exists, but choose it only when that coverage can answer the drainage question. A broad change alert and a small hidden pipe opening call for different evidence. The asset monitoring guide explains how to scope refresh editions and record what changed between observations.

Scoping a drainage inventory with Asset Search

The fastest starting point for a county drainage search is Asset Search, with asset definitions and acceptance rules agreed by the buyer’s technical team. Asset Search combines aerial and satellite imagery with public datasets and property records to find visible drainage assets across a county or the contiguous United States. People review each candidate and return dated evidence, parcel and owner information, plus fits, rejects and unresolved answers. Choose per-investigation terms for record reconciliation, per-accepted-result terms for discovery or a subscription for monitoring. Begin with a small paid pilot credited toward the full order and receive the file in the format your team uses.

For a county drainage order, I would specify six deliverables:

• A crossing register linked to the county’s existing asset IDs.
• Visible inlet and outlet evidence, with capture dates and observed facts.
• Parcel and owner information, with maintenance responsibility tracked as a separate question.
• Every candidate disposition, including rejection reasons and the field check needed for unresolved records.
• A CSV, Excel or GIS-ready delivery tested against the receiving team’s layout.
• An agreed refresh scope for new development, changed drainage features and revised search requirements.

Use the two-minute request to tell us what to find and where. We return a scope and quote, then ship the pilot in your working format. Give the next crew a crossing it can locate and a question it can settle.