Curb inlet paving tie-in record

Direct answer

A curb inlet paving tie-in record should prove the approved inlet type, throat or curb-opening form, frame and grate relationship, gutter flowline, gutter pan or inlet depression, curb return geometry, tie-in joints, subgrade condition, backfill protection, temporary inlet protection, surrounding traffic and pedestrian protection, correction items, hold points, and the specific release status before adjacent paving or final tie-in work starts.

The record matters because a curb inlet is both concrete work and drainage work. A throat form that moves, a gutter pan that does not drain, a frame set too high, an inlet depression finished wrong, a joint that lands in the wrong place, or backfill left unsupported at the structure can be hidden by the next paving operation. A clean photo packet preserves the field facts while they are still visible.

This is not a hydraulic design, inlet spacing design, ADA design, stormwater pollution plan, trench safety plan, fall-protection plan, traffic-control plan, opening-to-traffic approval, or authorization to pave. The plans, standard details, specifications, agency instructions, safety plan, stormwater documents, traffic-control plan, and responsible engineer control those decisions. This record only helps the team show what was present before the paving tie-in covered it.

What this record covers

Use this record where a concrete curb-and-gutter run meets a storm inlet, catch basin, curb-opening intake, combination inlet, grate inlet, driveway edge, sidewalk return, or asphalt or concrete pavement tie-in. It fits roadway edges, site paving, parking lots, industrial yards, curb returns, and phased paving where the inlet zone will soon become harder to inspect.

The packet should follow the work from reference documents to final handoff. It records the approved basis, stationing, existing grades, throat form, curb opening, gutter pan, frame and grate, joint layout, concrete placement, curing, backfill, inlet protection, and unresolved items. It should also show which later approvals remain outside the packet, such as hydraulic capacity, final drainage acceptance, ADA compliance certification, traffic opening, and final punch completion.

Treat the inlet as a small coordination zone, not as one isolated casting. The useful record includes the concrete crew, drainage crew, grading crew, paving crew, survey crew, inspector, traffic-control contact, and stormwater contact when their work touches the same inlet. If each crew photographs only its own piece, the tie-in can still fail at the boundary.

Define the tie-in boundary

Start by naming the exact work face. A useful boundary might say: Sta 18+42 right, type G curb inlet, curb-and-gutter from 18+20 to 18+68, throat opening and gutter pan at CB-12, concrete pavement tie-in panel P-41, asphalt surface tie-in at lane edge, sidewalk return held outside this release, backfill zone exposed behind structure, and paving release limited to the curb lane.

That boundary prevents the photo packet from growing into a vague acceptance note. If the record covers only form line, flowline, joint layout, backfill condition, inlet protection, and paving handoff, say so. If it does not cover inlet capacity, spread, pipe invert acceptance, ADA slope acceptance, traffic opening, or final drainage test, say that too.

Include the time window. Record when forms were checked, when the inlet throat was placed, when the gutter flowline was verified, when the frame and grate were checked, when concrete was finished, when backfill or edge protection was reviewed, and when the paving crew was released or held. A tie-in decision is often time-sensitive, so the record should show what was known at that time.

Start with the approved basis

Collect the plan sheet, inlet schedule, standard plan, curb-and-gutter detail, gutter depression detail, pavement joint plan, staging plan, survey control, stormwater controls, temporary traffic-control plan, pedestrian access plan, and any field revision before the inlet zone is called ready. The record compares visible work to those documents. It should not design the inlet from memory or from a single photo.

State DOT manuals and specifications point in the same direction: curbs, gutters, drainage inlets, joint locations, forms, subgrade, curing, and protection are project-controlled items. FHWA and Caltrans drainage references also show that inlet performance depends on roadway geometry, longitudinal grade, cross slope, spread, opening, and debris conditions. Those are design inputs, not values a field checklist should invent.

If the approved basis changes, attach the change or cite the direction. A throat may shift to match a drainage structure, a frame may need adjustment to match pavement grade, a gutter depression may be revised, or a joint may need to miss an inlet wall. The packet should show the original basis, the field conflict, the direction received, and the final condition being released.

Identify the inlet type

Name the inlet type before you photograph details. A curb-opening inlet, grate inlet, combination inlet, open-throat curb intake, catch basin gutter pan, and pipe inlet do not create the same field risks. The photo index should use the contract name or standard detail name, not a loose description like drain or box.

Drainage references describe curb-opening inlets as openings parallel to gutter flow, grate inlets as grate openings in the gutter or waterway, and combination inlets as assemblies that use both. That helps the field packet because the throat, grate, opening height, depression, frame, and debris risk are not the same for every inlet. It does not let the crew change inlet type without approval.

Photograph the inlet tag, casting mark if useful, structure number, plan callout, station, flow direction, and surrounding curb run in one wide view. Then take closer photos of the throat, top slab, frame, grate, curb face, gutter pan, and any opening bar or cover. The first page of the packet should make it obvious which inlet was reviewed.

Record the gutter flowline

The gutter flowline is the key visible line that links concrete finish to drainage intent. Record the control points used to establish it: station marks, hubs, string line, laser, grade stakes, existing curb tie-in, frame elevation, gutter pan depression, and downstream continuation. Show whether the flowline was checked before placement, during finishing, and before paving release.

Caltrans construction guidance tells inspectors to verify that gutters will drain and to check existing elevations against planned grades when new curbs join existing facilities. WSDOT construction guidance warns that curb-and-gutter systems should be built so water does not pond on the roadway or run randomly over slopes. Those points support a field record of the flowline, not a field redesign.

Use photos that show water path, not just concrete texture. A wide view should show the approach gutter and the downstream path. A medium view should show the flowline through the inlet. A close view should show the throat lip, gutter pan, depression, frame edge, or grate edge that controls water entry. If there is a hold, mark the exact location and reason.

Capture the throat form

The throat or curb-opening form deserves its own sequence because it can move during placement and can be hard to repair after the curb face is finished. Photograph the form before concrete, after concrete reaches the inlet, after finishing, and after form removal if removal occurs before the paving handoff. Show bracing, stakes, tightness to adjacent forms, opening dimension references, and contact with the structure.

Caltrans Section 73 requires fixed forms to be set to required alignment, grade, and dimensions, rigid enough to resist fresh concrete, clean, and coated with form oil. WSDOT curb-and-gutter specifications require side forms to rest on firm ground, be full depth for straight curb sections, and be cleaned if reused. Those requirements make the throat form a record item, not a background detail.

Record defects without softening the language. If the throat form is bowed, low, high, loose, out of square, gapped at the structure, patched with loose material, or unsupported at the base, the packet should say hold or correction required. A photo that only shows the finished curb face may miss the defect that caused the opening to be wrong.

Show the gutter pan

A gutter pan or inlet depression should be photographed as geometry, not as a pretty finish. Show the pan width, transition, depression, slope toward the inlet, matching pavement edge, frame or grate relationship, and any change from standard gutter to inlet zone. The photo should include enough surrounding pavement or curb to show that the pan ties into the actual path of water.

Standard plan examples show that gutter pans and inlet depressions are detail-specific. WSDOT's catch basin gutter pan plan shows a pan sloping down to the rectangular frame and notes that the drainage structure centerline may differ from the frame and grate centerline. Caltrans standard plans include separate sheets for concrete pavement drainage inlet details and inlet depressions. The field packet should therefore cite the controlling detail.

Do not substitute a universal pan shape or depression depth. If the project has a 0.1-foot depression, a catch basin gutter pan, a local inlet depression, or no depression because the detail says so, record that basis. If the built pan does not match the approved detail, the packet should show a correction path, not a private field tolerance.

Check frame and grate relationship

The frame and grate should be documented before the adjacent paving locks in the surrounding surface. Show whether the frame sits flush with the intended finished surface, whether the grate can be seated, whether the throat or curb opening lines up with the frame, whether the grate conflicts with the gutter pan, and whether temporary covers or sediment devices were removed or reinstalled for the check.

WSDOT construction guidance says catch basin grates and gutter inlets must be placed at proper elevation because low grates can create a traffic hazard and high grates may not intercept water. SUDAS storm structure requirements include visual inspection for damage, slipped forms, reinforcement displacement, voids, seals, embedments, true line, grade, plumb, dimensions, and thicknesses. Those are practical frame-zone checks.

When the frame elevation is disputed, record the reference, not only the opinion. Include the planned rim or grate elevation if available, the nearest control point, the intended pavement grade, the actual field reading, and who reviewed it. A close photo with a level, straightedge, or rod can help, but it does not replace the survey or inspection record required by the contract.

Tie joints to the inlet

Joint layout around an inlet should be traceable to the pavement joint plan, curb joint requirements, boxout detail, and standard plan. Photograph saw marks, planned contraction joints, expansion joints, isolation joints, construction joints, curb return joints, and the relation of each joint to the inlet wall, throat, frame, gutter pan, and pavement edge.

Caltrans Section 73 requires contraction and expansion joints in concrete curbs and sidewalks, including expansion joints at structures and ends of curb returns. WSDOT Section 8-04 places curb or curb-and-gutter expansion joints at drainage structures and cold joints with existing curbs and gutters. SUDAS pavement specifications place construction joints at boxouts and headers and require care in placing, consolidating, and finishing at all joints.

Do not let the next paving operation erase a joint question. If a transverse pavement joint is close to an inlet wall, if a curb joint does not line up with an existing joint where required, if an isolation joint around a drainage inlet is missing, or if a sawcut mark conflicts with the throat, record the hold and get direction. The packet should show the conflict before it is covered.

Include existing tie-ins

Existing curb, gutter, sidewalk, driveway, inlet, pavement, and shoulder edges can control the new tie-in. Photograph the existing condition before demolition or form setting, then again after new forms are set. Include spalls, settled curb, standing water marks, cracked gutter, asphalt overlays, patched edges, existing grates, and any prior repair that affects the new grade.

Caltrans construction guidance warns that existing pavement surfaces and existing edges should not be used directly to establish grade line for curbs. It also tells inspectors to check existing elevations against planned grades when new curbs join existing facilities. That distinction is important: the existing condition is evidence and a coordination point, not automatically the grade authority.

If the new tie-in cannot meet the planned grade, capture the issue early. Show the old elevation, proposed new form line, transition length, location of the inlet, and the practical consequence, such as ponding risk, abrupt edge, pedestrian route conflict, or paving mismatch. The next note should be the direction received from the responsible project authority.

Verify subgrade and foundation

Before concrete, document the foundation under the curb-and-gutter and inlet zone. Show subgrade elevation, moisture condition, compaction status if applicable, soft or disturbed areas, utility cuts, structure excavation limits, pipe trenches, bedding, and any gap under forms. A curb inlet is a common place for multiple excavations to meet, so the support record matters.

Caltrans Section 73 requires removing soft or spongy basement material under curbs, gutter depressions, island paving, driveways, sidewalks, and curb ramps, then backfilling to produce a stable foundation. It also requires water and compaction before placing concrete. WSDOT Section 8-04 requires the foundation for curbs, gutters, and spillways to be thoroughly compacted, with required side forms resting on firm ground.

If the soil under a form softens or a void appears, document the correction before placement continues. SUDAS pavement specifications say forms should be removed, the subgrade reworked, and forms reinstalled when support is inadequate because of rain, standing water, or voids. A photo of a form bridging a soft spot is a hold item, not a ready condition.

Record backfill protection

Backfill around the inlet structure, pipe zone, curb edge, and pavement edge should be documented before the paving tie-in starts. Show whether backfill has been placed uniformly, compacted where required, kept away from fresh concrete when required, protected from contamination, and shaped so water does not undermine the curb, gutter, or pavement edge.

Caltrans structure backfill specifications require uniform layers around structures or drainage facilities, prohibit compaction methods that may damage structures, and restrict backfill until relevant structure parts are authorized. WSDOT drainage specifications require drain pipe to be laid to line and grade, gravel backfill under underdrain pipe where specified, backfill in layers, and care to avoid contamination. These are project-specific controls that need visible evidence.

SUDAS pavement specifications add a practical edge-protection point after slipform paving: backfill or other protection may be needed to prevent water flow and damage by undermining. For a curb inlet tie-in, the record should show whether the inlet edge, curb back, pavement edge, and open trench are protected from storm flow, washout, truck wheels, and paving equipment.

Keep stormwater controls separate

Temporary inlet protection belongs in the record, but it is not the same as final drainage acceptance. Photograph the type of protection, location, fit to curb or grate, upstream sediment barrier, ponding area, maintenance condition, and any relocation needed for concrete placement or paving. Also record when protection was removed, replaced, or modified.

Caltrans temporary drainage inlet protection requirements call for protection around inlets as changing conditions require, clearing obstructions around each inlet, and placing linear sediment barriers upslope and parallel with the curb, dike, or flowline to help keep sediment out of the inlet. WSDOT inlet protection requirements call for devices at each inlet grate as shown in the plans and before clearing, grubbing, or earthwork.

Do not use this record to design the stormwater plan. The SWPPP, WPCP, erosion-control plan, standard specifications, and site stormwater lead control inlet protection type and maintenance. The article's job is to make sure the inlet protection present at the paving handoff is visible, dated, and tied to the approved site controls.

Avoid traffic and ponding conflicts

Inlet protection and backfill protection can create their own hazards if they pond water into traffic, block a pedestrian route, shift under wheels, or hide a drop-off. The tie-in record should show not only that protection exists, but that the responsible traffic, pedestrian, safety, and stormwater controls were considered before release.

Caltrans BMP guidance for temporary drainage inlet protection says ponding should not encroach into highway traffic and that protection should not become an obstacle to oncoming traffic. Caltrans standard specifications also say runoff ponds should be prevented from encroaching onto the traveled way or overtopping curb or dike. These points support a hold when a protection device creates a field conflict.

Use the photo packet to flag conflicts, not to solve them privately. If the curb inlet protection blocks the only temporary pedestrian route, ponds into a live lane, stands proud in a wheel path, or prevents the gutter pan from being checked, record the condition and route it to the responsible plan owner. Do not let a paving release bury an unresolved safety or stormwater conflict.

Document concrete placement

The concrete placement record should show the inlet zone while concrete is still workable. Photograph delivery ticket or load reference if that is part of the project record, placement sequence, form tightness, consolidation at the throat and gutter face, finishing tools, joint filler position, frame protection, curing start, and any rejected or held concrete.

Caltrans construction guidance for curbs and sidewalks tells inspectors to observe concrete placement, verify it is not segregating in the forms, and stop operations if the concrete requires patching with grout or mortar because the placing operation should be corrected. WSDOT construction guidance notes that vibration may be needed around difficult concrete areas and that spades may be needed where a vibrator cannot fill corners and form faces properly.

A curb inlet often has small pockets where concrete can honeycomb: throat corners, back of curb, gutter pan edges, frame blockouts, and the face against existing work. Get close photos before finishing hides the placement condition. If forms are stripped before paving, photograph exposed surfaces and repairs so later spalls are not blamed on the next crew without evidence.

Capture curing and protection

Record the curing method, timing, exposed faces, form removal, edge protection, rain protection, cold or hot weather notes, and traffic protection. Curb-and-gutter edges, back of curb, throat faces, gutter pan surfaces, and tie-in edges are often exposed to wind, sun, water, foot traffic, and equipment before adjacent paving shields them.

Caltrans Section 73 requires exposed faces of concrete curbs and sidewalks to be coated with curing compound. WSDOT Section 8-04 requires curb-and-gutter concrete to be cured for 72 hours by specified pavement curing methods and not exposed to traffic until it reaches the specified strength threshold. SUDAS pavement specifications require curing on pavement edges and back of curbs after forms are removed when forms are used.

The record should not declare the concrete ready for traffic unless the project acceptance path says so. Instead, record the observed curing protection and any supporting test or age data if the project uses it for release. If paving equipment, dump trucks, pedestrian traffic, or public traffic may cross the new work, that is a separate approval gate.

Protect openings and drops

An inlet zone can include open structures, missing grates, throat openings, excavations, exposed pipe, boxouts, and grade breaks. Photograph covers, grates, barricades, fencing, warning devices, and access restrictions that are present at the time of the paving handoff. Also photograph any opening that is not protected, then route the hold immediately.

OSHA fall-protection standards require employees on walking and working surfaces to be protected from falling through holes by covers, guardrail systems, or personal fall arrest systems where the standard applies. OSHA cover criteria include load capacity, securement, and warning markings, with separate notes for roadway cast iron covers and steel grates. OSHA signs and barricade rules also require hazard points in construction areas to be posted and protected.

This article does not design the cover, guardrail, barricade, or traffic-control device. The employer, competent personnel, site safety plan, traffic-control plan, and governing regulations control that work. The field record should simply make the visible condition, responsible hold, and release boundary clear before the paving tie-in changes access around the inlet.

Watch pedestrian interfaces

If the inlet sits near a sidewalk, curb ramp, driveway, crosswalk, island, or temporary pedestrian route, the photo packet needs a separate note. Show the forms, joint layout, detectable-warning panel if present, gutter depression, ramp or landing edges, temporary route, and any area excluded from the paving release. Do not bury pedestrian compliance issues inside a generic curb photo.

Caltrans curb and sidewalk inspection guidance treats pedestrian access, dimensioning, slopes, forms, staking, layout, gutter depressions, curb ramps, driveways, and completed compliance records as controlled items. It also tells inspectors to verify grades will accommodate finished slope requirements and to process changes when layout and grades will not meet requirements. Those are acceptance processes, not casual visual checks.

State the limitation clearly. A curb inlet paving tie-in record may show that the inlet zone was photographed and that pedestrian-related interfaces were flagged, but it is not an ADA compliance certification, slope acceptance report, detectable-warning approval, temporary pedestrian route approval, or final public-access release.

Account for debris and clogging

A tie-in record should show whether debris, slurry, curing compound, sediment, packaging, sawcut residue, loose aggregate, or broken concrete is near the inlet throat or grate before paving starts. The goal is not to predict storm performance. The goal is to prevent the handoff from hiding obvious material that could enter the inlet or block the opening.

FHWA and Caltrans drainage references discuss debris and clogging as factors in inlet performance. WSDOT notes that catch basins and gutter inlets can be susceptible to roadside trash and deciduous debris. Caltrans stormwater materials call for inlet protection maintenance, inspection, and careful handling of sediment filter bags so captured sediment does not spill into the inlet.

Photograph the inlet before cleanup, after cleanup, and after any protection is reinstalled. If sediment or concrete waste enters the structure, document the hold and the cleanup direction. Do not let the paving crew inherit an inlet that looks finished from the surface while debris sits inside the throat or on the grate seat.

Use a photo sequence

A useful packet is built as a sequence, not a gallery. Each photo should answer one question: where is this inlet, what detail controls it, what condition was visible, what was corrected, and what was released. Use wide, medium, and close photos so reviewers can connect the exact defect or release item to the surrounding work.

Take the first wide photo from the traffic approach side, the second from downstream, and the third from the sidewalk or back-of-curb side if available. Then move closer for throat form, gutter pan, flowline, frame, grate, joints, backfill, inlet protection, covers, and edge protection. Retake the same angles after correction so the closeout is easy to compare.

Do not rely on one straight-down photo into the inlet. It rarely shows the curb face, gutter flowline, frame height, traffic exposure, or joint relationship. If a detail matters enough to release paving, it should be visible from an angle that lets another person understand the condition without standing at the site.

Use a release checklist

The checklist should be filled out by the person responsible for the field handoff, then attached to the photos. Keep the wording factual. Mark each item ready, hold, not applicable, or outside this release. A blank item is worse than a hold because it makes the next crew guess whether the item was missed or intentionally excluded.

Do not make the checklist a substitute for project forms. If the agency, owner, or contractor requires an inspection report, daily report, ADA compliance form, survey record, concrete ticket log, stormwater inspection, or traffic-control inspection, attach or reference that record. The checklist below is a field index for the inlet tie-in packet.

• Inlet ID, station, side, lane, and work limits are written on the first page.
• Approved plan, standard detail, inlet schedule, and revision basis are identified.
• Inlet type, throat opening, frame, grate, and gutter pan are photographed.
• Flow direction and gutter flowline are visible in wide and medium photos.
• Existing tie-in elevations and constraints are recorded before release.
• Subgrade, foundation, form support, and void corrections are documented.
• Throat form, curb form, and return form are shown before concrete.
• Joint layout around the inlet is marked and compared with the approved basis.
• Concrete placement, consolidation, finishing, and curing start are recorded.
• Frame and grate relationship to the intended finished surface is checked.
• Backfill, pipe-zone support, curb-back support, and edge protection are shown.
• Temporary inlet protection is shown, including maintenance condition and fit.
• Openings, grates, covers, barricades, and warning devices are photographed.
• Pedestrian, driveway, sidewalk, and curb-ramp interfaces are flagged if present.
• Correction photos match the same angles as defect photos.
• Release wording states what is approved, held, excluded, and routed for direction.

Write the handoff note

A strong handoff note is short and specific. It should say what was reviewed, what evidence is attached, what is being released, what remains held, and which later approvals are still required. It should avoid broad phrases like inlet accepted, curb accepted, or OK to pave everything unless the person signing has that authority.

Example: CB-12 curb inlet tie-in reviewed at 2026-06-09 14:35 for curb-and-gutter throat form, gutter pan, flowline, frame and grate seat, joint layout, backfill edge support, temporary inlet protection, and opening protection. Photos 01 through 24 attached. Release is limited to paving the curb lane tie-in from Sta 18+20 to 18+68 after listed holds are corrected. This note does not approve hydraulic capacity, ADA compliance, traffic opening, or final drainage acceptance.

If there are no holds, say no holds observed for this release scope. If there are holds, list each hold with location, owner, requested direction, and status. Do not bury a hold in a paragraph. The paving crew needs to know whether it can proceed, stop, or proceed only outside a marked area.

Handle corrections

Corrections should be shown as a before-and-after trail. If the throat form moved, show the moved condition, the correction, and the corrected condition with the same reference. If a gutter pan had a flat spot, show the check, the correction method approved by the project, and the final surface. If backfill washed out, show the washout, replacement, compaction or protection record, and release.

Use hold numbers rather than vague comments. Hold H1 might be frame high at northeast corner. H2 might be unprotected opening after grate removal. H3 might be no approved joint direction where saw mark intersects inlet wall. When the issue is corrected, close the same hold number with the photo and the reviewer.

Do not create repair methods in the packet. Concrete repairs, sawcut changes, backfill replacement, frame adjustments, inlet cleaning, and stormwater control changes must follow project documents and responsible direction. The packet should show that a correction happened and who accepted it for the specific release, not invent the technical repair standard.

Separate survey from photos

Photos are strong evidence for presence, sequence, and visible condition. They are weak evidence for exact elevation. When the field issue is flowline grade, frame elevation, rim height, gutter depression, slope, or tie-in transition, attach the survey note, grade check, smart-level record, inspector report, or project form that controls the measurement.

Caltrans curb inspection guidance includes survey staking, form checks, slope and dimensional checks for pedestrian facilities, and documentation of readings where those controls apply. SUDAS pavement specifications include verification of finished slab location and elevation at grade check hubs in critical locations such as intakes and intersections where grades may be flat. These are measurement records, not photo guesses.

A good photo can make the measurement understandable. Show the rod, level, straightedge, string line, hub, stake, or mark in the photo, then write the actual reading in the log. Do not leave a reviewer to infer slope or elevation from camera angle.

Coordinate paving release

Before paving release, identify which crew will cover or lock in each inlet-zone item. Asphalt paving may cover the back of gutter or frame edge. Concrete paving may lock in an isolation joint, pan, or slab tie-in. Sidewalk work may cover a curb return or throat edge. Backfill may cover pipe-zone conditions. The release should match the next operation.

A useful paving release statement names the physical limit and the conditions. For example: release asphalt base tie-in to within 2 feet of CB-12 after H1 frame adjustment and H2 inlet protection reset; hold surface course adjacent to grate until final frame check; do not pave sidewalk return until pedestrian facility inspection is complete. That is much better than release inlet.

If the project requires strength, curing, compaction, proof roll, density, or inspection gates before paving, reference those records. The curb inlet packet can attach them, but it should not claim them unless they are actually complete. The release is only as good as the controlling gates behind it.

Partial release language helps the next crew more than broad approval language. Mark the paving limit on a photo or sketch, note whether the paver can run past the inlet, stop short of the frame, place only base lift, or leave a handwork pocket, and name any condition that must be rechecked after paving. If the release changes during the shift, issue a revised note with the time and reason instead of editing the earlier note silently.

Common mistakes

The most common mistake is photographing the finished inlet after paving and assuming that proves the hidden tie-in. It does not show whether the throat form was braced, whether the gutter pan matched the detail, whether backfill supported the edge, whether the frame was adjusted before paving, or whether inlet protection was in place during the work.

The second mistake is letting design language creep into a field record. A note that says inlet capacity approved, spread acceptable, ADA compliant, or traffic safe may be outside the authority of the person writing it. Replace those phrases with field facts: photos taken, grades checked by survey, protection installed per plan, hold routed, or release limited to a named work area.

The third mistake is losing the sequence. A photo after correction is helpful only if the defect photo, hold note, correction method, and reviewer are linked. Use photo numbers, hold numbers, and timestamps so the packet tells one story rather than twenty disconnected images.

Example field record

A crew is preparing to pave the curb lane beside a newly placed curb-and-gutter inlet. The inlet is a combination curb-opening and grate inlet at a low point near a driveway. The foreman wants release for asphalt paving that will tie into the gutter pan and frame. The inspector asks for the inlet tie-in packet before the paver is called forward.

The packet starts with the plan detail, inlet schedule, station, and work boundary. Photos show the throat form before concrete, the gutter pan during finishing, the frame and grate after form removal, the curb expansion joint at the drainage structure, the backfill behind the curb, and the temporary inlet protection reset after cleanup. One hold is opened because the sediment barrier sits in the wheel path for paving equipment.

The stormwater lead changes the inlet protection method under the project stormwater documents, and the traffic-control lead confirms the protection is outside the live lane. The packet then records the correction and releases only the asphalt tie-in up to the frame edge. It explicitly excludes final drainage acceptance, ADA slope acceptance at the nearby driveway, and opening to traffic.

Questions that come up

Can one photo prove the inlet is ready for paving? Usually no. One photo may show the final surface, but it rarely proves the approved detail, throat form, gutter flowline, joint layout, backfill, inlet protection, and unresolved holds. Use a short sequence and a release note instead.

Should the record include water testing? Only if the project requires or authorizes it. A small water check can sometimes show an obvious reverse slope, but water tests can also conflict with curing, stormwater controls, traffic controls, temperature, or agency procedures. The controlling documents decide whether water testing belongs in the record.

Who signs the release? The person or role named by the contract, inspection plan, agency practice, or contractor quality plan. A foreman can document a condition. An inspector can record observations. An engineer or owner representative may control certain approvals. The packet should not blur those roles.

What if the inlet is existing and only the pavement tie-in is new? Still record it. Existing frame height, grate condition, throat damage, sediment, prior patching, and existing gutter slope can affect the new tie-in. The packet should separate pre-existing conditions from new work.

What not to approve

Do not approve inlet spacing, hydraulic capacity, storm spread, pipe capacity, ponding criteria, or low-point drainage design with this record. FHWA and Caltrans drainage documents show those decisions depend on roadway geometry, rainfall, spread criteria, inlet type, grade, cross slope, clogging, and other design inputs. A photo checklist is not a drainage calculation.

Do not approve ADA compliance, detectable-warning acceptance, curb-ramp slope, landing slope, crosswalk location, temporary pedestrian route compliance, or final public access unless the proper inspection and certification process is complete. A curb inlet may touch those surfaces, but a paving tie-in record is not the same as a pedestrian facility compliance package.

Do not approve traffic opening, worker protection, public traffic control, fall protection, trench safety, confined space, or stormwater plan changes with this record. Those are separate controlled processes. The packet can show visible devices and holds, but it should point back to the approved plans and responsible personnel for final decisions.

File names and index

Use file names that survive email, plan rooms, and claims review. Include date, project, inlet ID, station, view number, and condition. Example: 2026-06-09_ProjectA_CB12_Sta18-42_Ph03_throat-form-before-placement.jpg. Avoid names like IMG_4418 or finaldrain2 because they lose meaning when photos leave the phone.

The index should list photo number, file name, time, photographer, view direction, item shown, hold number if any, and release status. If video is used, add a short written note naming the frames or timestamps that matter. A video walk can help, but it should not replace still photos of the exact hold and correction.

Store the approved basis with the photos. A packet with only images forces the reviewer to hunt for the inlet detail, joint plan, or revision. Add the plan sheet, standard detail title, inlet schedule row, relevant inspection form, stormwater inspection reference, and release note so the record can stand alone.

Preserve the record version that supported the release. If a later photo shows a repaired grate seat, a changed inlet protection setup, or a revised paving stop line, keep the earlier version and add the new one with a revision number. That keeps the handoff defensible because it shows what the paving crew saw at release time and what changed afterward.

Compliance and safety limits

Treat this as a field documentation checklist, not as permission to bypass contract requirements, agency standards, licensed design, safety procedures, traffic-control requirements, stormwater controls, pedestrian-access requirements, or inspection authority. The project documents and responsible personnel control the work.

For OSHA-regulated work, the employer and competent personnel must determine fall protection, covers, guardrails, barricades, excavation protection, traffic-control devices, and worker access. This article only says those visible controls should be recorded when they affect the inlet tie-in handoff.

For drainage and accessibility, the responsible designer, engineer, agency, AHJ, owner, and approved documents control the design and acceptance path. Do not use a photo packet as proof that an inlet has adequate hydraulic capacity, a gutter has acceptable spread, or a pedestrian facility complies with ADA or project requirements.

For paving release, require the same discipline. The packet can show the inlet zone before the next operation. It cannot replace concrete strength data, curing requirements, compaction records, survey records, stormwater inspections, traffic-opening decisions, or final owner acceptance where those gates are required.

Sources checked

• FHWA, Urban Drainage Design Manual, Hydraulic Engineering Circular No. 22, 4th EditionUsed for gutter flow, spread, inlet design factors, curb-opening inlet terminology, depressed inlets, debris and clogging context, and the boundary between drainage design and field documentation.
• FHWA, Introduction to Highway Hydraulics, Hydraulic Design Series No. 4Used for general highway drainage context, surface drainage concepts, and why inlet and flowline conditions are controlled by design documents.
• Iowa SUDAS Standard Specifications, Section 7010, Portland Cement Concrete PavementUsed for subgrade, forms, surface fixture adjustment, boxouts, curb and gutter finishing, construction joints, curing, backfill, protection, and traffic-protection context.
• Iowa SUDAS Standard Specifications, Division 6, Structures for Sanitary and Storm SewerUsed for open-throat curb intake details, structure cleaning and inspection, true line and grade, dimensions, forms, reinforcement, and structure condition checks.
• Iowa SUDAS Design Manual, Section 2C-3, Intake Design and SpacingUsed for intake location and design context and to keep inlet spacing and capacity decisions outside the field photo record.
• Caltrans Construction Manual, Section 4-73, Concrete Curbs and SidewalksUsed for inspection of forms, gutter depressions, staking, grades, drainage, placement, curing, protection, pedestrian interfaces, and documentation.
• Caltrans Highway Design Manual, Topic 836 Curbs and Gutters and Topic 837 Inlet DesignUsed for curb-and-gutter drainage effects, gutter grade and cross slope, inlet types, curb-opening inlet context, inlet location factors, and design limitations.
• Caltrans Standard Specifications 2025, Section 73 and Section 13-6.03CUsed for concrete curb and sidewalk forms, joints, subgrade, curing, surface checks, gutter depressions, structure backfill, and temporary drainage inlet protection requirements.
• Caltrans Standard Plans 2025Used for plan-controlled curb, drainage inlet, inlet depression, frame and grate, and temporary inlet protection details.
• Caltrans Construction Site BMP Manual, March 2024Used for temporary drainage inlet protection purpose, appropriate applications, maintenance, traffic and ponding limitations, and SWPPP or WPCP boundary.
• WSDOT Standard Specifications 2026, Division 8Used for curb-and-gutter construction, line and grade, forms, expansion joints at drainage structures, catch basin gutter pan, curing, traffic exposure, and inlet protection.
• WSDOT Standard Specifications 2026, Division 7Used for drain pipe line and grade, soil-tight joints, backfill layers, compaction, and protection of backfill material from contamination.
• WSDOT Standard Plan F-10.16-00, Cement Concrete Curb and Gutter PanUsed for catch basin gutter pan geometry, frame and grate relationship, face of curb, gutter pan slope to catch basin, and plan-specific detail context.
• WSDOT Construction Manual, Chapter 6, StructuresUsed for form checks, concrete consolidation, curing protection, construction joint alignment, and form-removal caution.
• WSDOT Construction Manual, Chapter 7, Drainage Structures, Storm Sewers, Sanitary Sewers, Water Mains, and ConduitsUsed for roadway surface drainage, curb-and-gutter ponding risk, grate and inlet elevation, flowline grade, pipe backfill, and drainage-structure maintenance context.
• OSHA, 29 CFR 1926.501, Duty to have fall protectionUsed for safety boundary around holes, excavations, wells, pits, shafts, unprotected sides, and fall-protection responsibilities.
• OSHA, 29 CFR 1926.502, Fall protection systems criteria and practicesUsed for cover and guardrail criteria around holes, including capacity, securement, and warning markings.
• OSHA, 29 CFR 1926.200, Accident prevention signs and tagsUsed for construction hazard signs, traffic-control devices, and MUTCD Part 6 boundary for worker protection devices.

Related guides