Temporary trench patch traffic-switch photo record

Direct answer

Before a traffic switch, a temporary trench patch photo record should identify the work zone, lane, station or address range, trench limits, patch type, traffic-switch stage, accepted traffic-control plan, sawcut edge condition, existing pavement condition, backfill and base release reference, tack coat evidence, asphalt mix reference, lift thickness, placement time, compaction method, roller or plate pass evidence, surface profile, lane-line or temporary marker status, cooling or opening basis, cleanup, open exceptions, reviewer, date, and release decision.

The record should also say what it does not prove. A photo of a flush trench patch does not prove permanent restoration acceptance, final density, long-term settlement performance, utility backfill compliance, traffic-control plan approval, asphalt mix acceptance, tack coat rate, compaction temperature, or owner warranty release. It proves the observed temporary patch condition and the attached records at one point before traffic is moved.

Use this as documentation guidance only. The roadway owner, agency permit, approved traffic-control plan, project specification, asphalt mix design, paving inspector, engineer, trench safety plan, utility permit, and site safety lead control the actual patch requirements, traffic switch, lane reopening, density acceptance, and permanent restoration.

What this record covers

This record covers a temporary asphalt trench patch that will carry traffic during a phase change, detour change, lane shift, temporary alignment, business access change, public reopening, or utility cut holdover before final restoration. It is useful for water, sewer, gas, electric, telecom, storm, signal, and civil utility trench work in paved public or private roads.

The record is not limited to public streets. It also fits campuses, hospitals, logistics yards, airports, industrial drives, data center service roads, and private developments where a temporary trench patch will carry construction traffic, deliveries, emergency access, or owner operations before the final pavement section is placed.

The core question is narrow: can this temporary patch safely and clearly carry the traffic assigned to it under the approved traffic switch? The answer needs more than a finish photo. It needs location, boundary, edge, tack, lift, compaction, marking, cooling, traffic-control, and exception evidence.

Keep the scope narrow

Do not turn this photo record into a paving specification or traffic-control plan. Sawcut offsets, backfill density, base thickness, asphalt mix type, tack coat product, tack coat rate, lift thickness, roller pattern, compaction acceptance, cooling temperature, plate use, lane closure, flagging, and temporary markings must come from the accepted documents and qualified field direction.

The narrow scope is observed release evidence. The record should say what the crew saw, what the approved basis required, what supporting records were attached, what was held, and what traffic condition was released. It should not invent a universal trench patch section or tell a crew how to compact asphalt.

This boundary matters because temporary patches vary widely. A four-hour utility crossing in a low-speed access drive, an arterial night patch, a bus-route lane shift, and a long-term temporary restoration before final milling can all require different controls. The photo packet preserves the decision for this patch and this traffic switch.

Start with the approved basis

The first page should list the permit, traffic-control plan, utility cut detail, trench restoration detail, pavement section, mix requirement, tack coat requirement, compaction requirement, density or proof requirement, temporary pavement marker requirement, inspector hold point, and agency or owner release authority. If the project has an RFI or field change, include it.

FHWA's HMA asphalt patching checklist starts with document review, including project specifications, construction manual, traffic control plan, agency requirements, safety data sheets, OSHA safety requirements, and the contractor quality control plan. That source supports building the photo record around the accepted project basis before field observations.

If the patch detail, permit, and traffic switch plan disagree, hold the release. A lane can look passable while the record is still wrong. The field packet should name the conflict and assign the responsible reviewer before traffic is moved onto a patch that no one can later explain.

Identify location and traffic switch boundary

Record the road name, station range, lane, travel direction, offset, nearby intersection, driveway, access point, utility crossing, trench ID, and traffic-switch stage. Include wide photos that show the patch in relation to the approach, downstream taper, lane line, temporary barrier, cones, signs, drainage path, and pedestrian or bicycle route where present.

A temporary patch release should say what traffic is being allowed. Examples include construction traffic only, local access only, single-lane flagger control, right lane open, two-way traffic shifted west, emergency access released, or public traffic reopened after night work. These phrases are different, and the record should not blur them.

The boundary should also say what remains excluded. A patch may be released for one lane while the adjacent lane remains closed, or released for low-speed access while heavy haul traffic stays on a separate route. Write that limit before the first vehicle uses the switch.

Temporary patch versus permanent restoration

Separate temporary patch release from permanent restoration. Temporary patch means the surface is being accepted for a limited traffic condition, phase duration, or maintenance period. Permanent restoration means the final pavement repair or overlay requirements have been accepted by the owner or agency. A temporary release should not quietly become final acceptance.

NYC's Street Works Manual separates permanent restoration from temporary restoration and states that unfinished street opening work must receive temporary repairs under the highway rules. Tampa's restoration standard includes temporary restoration language and a trench restoration detail set. Those municipal sources show why the record should preserve the temporary status.

Use labels such as temporary patch, temporary wearing course, temporary restoration, interim traffic surface, or permanent restoration only when the project documents use them. If the patch is temporary, the final decision should say what permanent work remains.

Sawcut edge evidence

The sawcut edge evidence should show the patch outline, edge straightness, vertical face, loose or raveled edge, undermined edge, broken corner, edge overcut, base exposure, adjacent pavement cracking, and whether the cut aligns with the approved trench restoration limit. Include a tape, station mark, or lane reference when the limit is disputed.

FHWA's HMA patching checklist says the patch outline should be made using a pavement saw, milling machine, or pneumatic hammer and that the patch should be square or rectangular with edges aligned parallel or at right angles to the pavement centerline. WSDOT maintenance guidance also discusses cutting patch edges vertically and in straight lines.

The photo record should not approve every edge condition. If an edge is broken or unsupported, write it as a hold or limited release. A patch can be smooth in the middle and still fail at the edge if the joint is unsupported or the traffic wheel path crosses a weak seam.

Existing pavement condition

Document the pavement that the temporary patch ties into. Photos should show adjacent cracking, rutting, shove, delamination, soft edge, previous patches, utility covers, milled areas, exposed base, standing water, and lane-line conflicts. A rough existing road does not excuse a poor patch, but it explains the baseline.

FHWA's tack coat guidance ties bonding and distress risk to pavement layers and existing surface preparation. WSDOT's patching chapter discusses patching within a broader pavement maintenance context. The temporary patch record should therefore show the surface the patch is being bonded and compacted against.

If the adjacent pavement is already distressed, state whether the release is for the temporary patch only or also includes a broader lane repair. Do not let an existing rut become a claimed trench-patch defect later if it was outside the patch boundary and documented before the traffic switch.

Backfill and base release boundary

The paving photo record should reference backfill and base release, but it should not replace those records. Include the compaction test number, proof-roll note, inspector signoff, base lift record, density test, flowable fill record, or utility trench acceptance that allowed asphalt placement to proceed.

FHWA's HMA patching checklist addresses subgrade excavation, backfill lift thickness, and density requirements before asphalt patch construction. Tampa's restoration standard also includes compaction and testing language for trench backfill and base materials. Those sources support a record that attaches the base release instead of guessing from asphalt photos.

If the backfill or base record is missing, hold the traffic switch or issue a written limited release if the owner accepts that risk. A neat top lift does not prove that the trench below it was compacted or tested as required.

Tack coat evidence

Tack coat evidence should show the cleaned vertical edges, bottom or horizontal surface where required, tack product or ticket if required, application method, coverage, missed spots, puddles, tracking, contamination, and whether the tack was placed wider than the patch where the accepted plan requires overlap. Record both before and after tack when the surface condition matters.

FHWA's tack coat best practices brief explains that tack coat helps bond asphalt layers and that poor bonding can contribute to slippage, shoving, delamination, fatigue cracking, and potholes. FHWA's HMA patching checklist also calls for tack coat on vertical asphalt faces along the patch perimeter.

The photo record should not set a universal tack rate. It should say tack coat evidence photographed and reference the project specification, inspector direction, or agency requirement. If the tack coat is streaked, tracked off, contaminated, or missing at the edge, hold the patch or document the correction before asphalt covers it.

Tack break, set, and tracking boundary

For emulsion tack, the record should preserve whether the surface looked brown, broken, set, wet, tracked, picked up, dusty, rained on, or contaminated before the asphalt lift was placed. When the project requires a time, color, or acceptance check, include the inspector note and timestamp.

FHWA's tack coat checklist says damp pavement may slow break and cure time, includes surface preparation and equipment checks, and lists tracking controls such as requiring tack to break or set before haul trucks are allowed on it. FHWA's best practices brief also defines tack break and set.

Use careful wording. A photo can show observed condition and timing, not laboratory confirmation of residual rate or bond strength. Write tack set observed by inspector at 21:35 or tack tracked by haul truck at east wheel path and corrected before placement, not tack perfect.

Mix ticket and temperature evidence

Temporary patch records should connect the surface to the asphalt delivery. Include mix type or job mix reference, ticket number, truck number, delivery time, placement time, measured temperature where required, rejected load status, handwork area, and whether the patch used hot mix, warm mix, cold mix, or an approved temporary material.

FHWA's HMA patching checklist calls for verifying that materials such as asphalt binder, aggregates, tack coat, and sealant are from approved sources and that the mix is produced by an approved plant and meets the job mix formula. Caltrans Section 39 gives agency inspection context for asphalt concrete work.

Do not make a temperature or material acceptance claim from a finish photo. If the material record is missing, state that the surface photo does not prove mix acceptance. If a load was held, rejected, or placed under a limited approval, keep that note with the patch record.

Lift thickness evidence

Lift thickness evidence should show the planned lift count, depth marks, grade pins, loose-lift reference where allowed, compacted-lift reference where tested, existing pavement thickness, and any area where hand placement created a variable depth. Include a close photo only when it is tied to the whole patch location.

FHWA's HMA patching checklist states that air and pavement surface temperatures, humidity, wind, and lift thickness affect how quickly mix cools and the time available for compaction. The same checklist says asphalt should be compacted in lifts no greater than 3 inches for patching. WSDOT gives similar patch lift guidance in its maintenance chapter.

Do not turn those source numbers into a universal project rule. The project specification controls. The article's point is that the temporary patch record should preserve the lift requirement and the evidence used to release each lift before traffic is switched.

Compaction method evidence

Compaction evidence should identify the equipment used: steel drum roller, vibratory roller, pneumatic roller, trench roller, plate compactor, hand tamper, truck wheel only where allowed, or another approved method. Photograph the equipment in the patch area and tie it to the lift being compacted.

FHWA's HMA patching checklist says small patches can be compacted with a vibrating plate compactor while large patches should use a steel drum roller, and it calls for vibratory plates or hand tampers where rollers cannot reach. WSDOT discusses matching patching production to the roller train and avoiding rolling mix that is too cold.

The photo record should not claim final density unless the accepted test or proof method is attached. It should preserve what equipment was used, when, where, and under whose release. If density testing is required, attach the test result or hold the lane switch.

Roller pass record

A roller pass record should identify the lift, roller or plate, pass direction, start and finish time, edge pass, wheel-path pass, confined-area pass, and any area where equipment could not reach. The record does not need a theatrical photo of every pass, but it should prove the compaction sequence was observed.

Caltrans' patching and edge repair guidance notes that deeper repairs may require multiple lifts and describes final lift material enough that several roller passes are needed to roll a patch flush with old pavement. FHWA's patching checklist also says patch edges should be compacted first for the surface lift.

If the roller bridged the trench, if a plate could not reach the edge, or if traffic had to be released before the intended rolling was complete, write the exception. The issue is not the number alone. It is whether the record explains the compaction actually performed before traffic moved.

Edge compaction and joint confinement

Temporary trench patches are often narrow, which makes edge compaction important. Photograph the wheel path, both sawcut edges, unsupported corners, utility casting edges, transverse ends, and any area where the compactor bridged the trench rather than compacting the asphalt inside it.

FHWA's HMA patching checklist says asphalt should be placed against patch edges first and that surface-lift patch edges should be compacted first. Caltrans warns that compaction equipment that bridges the repair area is less likely to achieve adequate compaction of the HMA material.

The release note should identify edge holds separately from surface holds. A patch can look smooth across the center while the edge joint is open, low, cracked, or loose. That edge may matter most during the first traffic switch when tires are forced onto a new path.

Surface profile and flushness

Surface profile evidence should show whether the patch is flush, crowned, low, high, rutted, shoved, segregated, torn, scuffed, open textured, ponding, or rough at the wheel path. Use a straightedge, level, ruler, stringline, or inspector note where the project requires a profile check.

FHWA's HMA patching checklist says the finished asphalt surface should be flush with surrounding pavement or slightly above it to account for further traffic compaction. WSDOT also discusses a surface lift compacted even and flush with surrounding pavement while allowing for additional traffic compaction.

Do not hide a low spot under the phrase temporary patch. If the patch is intentionally left slightly high or crowned under the accepted detail, say so and reference the basis. If the patch is low at a wheel path before traffic switch, hold it or document owner acceptance of the limit.

Lane line and marker evidence

If the patch crosses lane lines, crosswalks, stop bars, bike lane markings, edge lines, channelizing lines, arrows, or temporary alignment markings, the record should show how the lane will be delineated after the traffic switch. Include temporary pavement markers, temporary tape, cones, drums, channelizers, signs, and covered or removed old markings where required.

FHWA's HMA patching checklist says that if a patch extended into pavement lane lines, temporary pavement markers should be placed on lane lines for delineation before opening the pavement to normal traffic. The current MUTCD page identifies the official current MUTCD edition, and MUTCD Part 6 frames temporary traffic control requirements.

The patch release should not approve the traffic-control plan. It should document whether the visible devices and markings match the accepted plan at the moment of release. If markings are missing, old markings conflict, or devices are not in place, hold the traffic switch.

Cooling and opening to traffic

Opening evidence should show placement time, final rolling time, cooling or temperature check where required, edge sealant or tack pickup status where relevant, cleanup, traffic-control change, and the responsible person who released the lane. The record should say what temperature or time basis was used if the project requires one.

FHWA's HMA patching checklist says pavement can be opened after the mix has been compacted and the mat has cooled to 140 degrees F or the agency's required temperature. WSDOT says finished patches should be cool enough before traffic is allowed so traffic does not leave marks in the surface.

Do not state open to traffic because the surface looks black and smooth. The release should point to the accepted opening rule, the inspector's decision, or the agency's field direction. If heavy trucks, buses, or emergency vehicles are expected, call out that expected loading in the release.

Traffic control status

Traffic-control evidence should show signs, cones, drums, barriers, flaggers, arrow boards, lane closure status, work vehicle position, pedestrian channelization, bicycle detour, driveway access, and whether old devices were removed or covered when no longer needed. Photograph the approach view from the road user's perspective where it is safe to do so.

FHWA's HMA patching checklist calls for verifying that traffic control conforms to plans and specifications and complies with the MUTCD. It also calls for trained and qualified traffic-control personnel as required by contract documents and agency requirements, and for signs to be removed or covered when no longer needed.

The patch photo record should not redesign the traffic switch. It should tie the patch release to the traffic-control status that existed at release. If the patch is ready but the signs and channelizers are not, the final decision should say paving released, traffic switch held.

Pedestrian, bicycle, and access context

A traffic switch can affect more than vehicles. Record pedestrian access routes, curb ramps, temporary walkways, driveway openings, loading zones, bus stops, business access, emergency access, bicycles, scooters, and accessible route changes where the traffic-control plan includes them. A lane patch can create a trip edge or block a crossing even when vehicle travel is clear.

The MUTCD current edition page identifies the current official manual, and Part 6 covers temporary traffic control for road users. The article does not interpret every pedestrian or bicycle requirement. It asks the field record to show the accepted route condition before traffic is changed.

If a temporary trench patch crosses a pedestrian route, show the walking surface, edge transition, barricades, signs, and detour status. If pedestrians are excluded by the traffic-control plan, show the exclusion devices and alternate route rather than assuming the patch has no pedestrian impact.

Weather and moisture evidence

Weather evidence should include rain, wet surface, damp patch hole, standing water, temperature, wind, night cooling, shade, humidity when relevant, and any delay that affected tack or compaction. A temporary patch placed in marginal weather needs a clearer record, not a shorter one.

FHWA's tack coat checklist says existing pavement should be dry and notes that damp pavement may slow break and cure time. FHWA's HMA patching checklist says paving should not begin if rain is imminent and that weather and lift thickness affect cooling and compaction time.

Do not use this article to set weather limits. Use it to document whether the field condition matched the accepted requirements. If rain started before tack, if water remained in the patch, or if the mix cooled during a lane closure delay, write the hold or exception.

Drainage and ponding

Temporary trench patches can create small dams across lanes, shoulders, gutters, curb returns, trench crossings, and driveways. Photograph the gutter line, low side, crown, shoulder edge, inlet approach, curb opening, and any water path affected by the patch before traffic is switched.

Caltrans' patching guidance discusses crown or surface shape to help avoid water ponding, and FHWA's patching checklist includes flush or slightly high finished surface language. Tampa's details also tie trench restoration to lane and pavement-edge geometry. These sources support documenting drainage effects without making a drainage design ruling.

If water ponds against a patch edge, list it as a hold or limited release. A traffic switch can make drainage worse by moving tires and splash toward a new path, and the record should show whether the patch creates an avoidable hazard.

Temporary maintenance period

Temporary patches need an owner for maintenance. Record who will monitor the patch, how often, what defects trigger repair, how settlement or rutting will be reported, who controls after-hours response, and when permanent restoration is expected. Attach the permit or owner note if it assigns maintenance responsibility.

NYC's Street Works Manual and Tampa's restoration standard both show that temporary restoration is a regulated condition rather than a casual field convenience. The record should therefore include the maintenance period or next inspection point when the patch will carry traffic beyond one shift.

If no maintenance owner is named, hold the release or escalate to the agency or owner representative. A temporary patch can fail after the traffic switch, and the record should make response responsibility clear before public traffic uses it.

Photo sequence

Take wide photos first: road name or station, approach, trench limits, traffic-control setup, pedestrian or bicycle route, and adjacent access. These photos prove where the patch is and what traffic condition is being considered.

Take mid-range photos next: sawcut limits, trench boundary, adjacent pavement, backfill or base evidence, tack coat, lift placement, compaction equipment, edge passes, surface profile, lane markings, cleanup, and traffic-control devices.

Finish with close photos and records: edge condition, tack coverage, lift depth reference, ticket, temperature check, roller or plate pass note, straightedge or profile check, temporary marker, cooling or opening decision, exception tags, and final release or hold note.

Minimum traffic-switch packet

Use the owner's required field form first. Add this packet when the existing form does not connect trench patch condition to the traffic-switch release.

Before traffic switch checklist

Use this checklist after the accepted patch details and traffic-control plan are already in place.

• Road name, lane, station or address range, trench ID, utility, reviewer, date, and traffic-switch stage recorded.
• Permit, traffic-control plan, trench restoration detail, mix requirement, tack requirement, and inspection hold point attached or referenced.
• Wide photos show approach, patch limits, adjacent lane, traffic-control setup, pedestrian or bicycle context, and access points.
• Backfill, base, or proof record is attached or the patch release is held for missing support evidence.
• Sawcut edges are photographed for straightness, vertical face, raveling, undermining, broken corners, and edge support.
• Existing pavement condition at the tie-in is recorded before tack or asphalt hides the edge.
• Tack coat evidence shows clean surface, edge coverage, break or set status where required, tracking, and corrections.
• Mix ticket, mix type, placement time, and temperature record where required are tied to the patch.
• Lift thickness evidence is recorded by accepted measurement, mark, test, or inspector note.
• Compaction equipment and pass evidence identify roller, plate, hand compaction, edge pass, and inaccessible areas.
• Surface profile shows flush, slightly high, low, crowned, rutted, shoved, torn, segregated, or held condition.
• Temporary lane markings, markers, signs, cones, drums, or barriers match the accepted traffic switch.
• Cooling or opening basis is recorded before vehicles are released onto the patch.
• Cleanup is complete and debris, loose aggregate, tack tracking, tools, and unneeded signs are removed or held.
• Open exceptions assign responsible party, correction, evidence required, and release limit.
• Final decision states released, held, limited release, repair required, traffic-control correction required, or owner review required.

Normal condition wording

A useful release note might say: TP-7 at Main Street eastbound lane station 14+20 to 14+68 photographed before Phase 2 traffic switch. Basis: permit UT-44, traffic-control plan TCP-2B, trench restoration detail P-6, and inspector release IR-31. Sawcut edges visible, tack coat placed at vertical faces, HMA ticket 288 attached, two lifts recorded, steel drum roller and plate compactor used at edge, surface checked flush to adjacent pavement, temporary lane markers installed, cleanup complete. Released for eastbound traffic switch at 22:40. Permanent restoration remains open.

That wording gives the road owner, inspector, and contractor a clear record without claiming final density, permanent restoration acceptance, or long-term settlement performance. It also ties the release to a time, phase, and traffic condition.

Avoid vague wording such as patch okay, lane ready, or paved and open. Those notes do not identify the patch, traffic switch, evidence, or release limit.

Exception wording

If the patch is not ready, write it plainly. Example: Traffic switch held. TP-4 at northbound lane station 8+10 has raveled west sawcut edge, missing tack at south transverse face, low wheel path at centerline side, and no temporary lane markers over removed centerline. Paving crew to repair edge, retack, add mix and compact, install markers, and provide updated photos before release.

If the owner accepts limited use, say exactly what is allowed. Example: Released for emergency access only until 07:00. Public traffic switch remains held pending surface profile correction and traffic-control inspection.

Exception wording should not sound like a debate. It should identify the condition, location, responsible party, next evidence, and traffic status so field crews do not argue from memory during the switch window.

Hold criteria

Hold the traffic switch when the backfill or base release is missing, the sawcut edge is unsupported, tack coat is missing or contaminated, lift thickness is not documented where required, compaction is incomplete, the surface is low in the wheel path, the patch is still deforming, temporary markings are missing, traffic-control devices are not in place, or release authority is unclear.

Also hold when the patch photo contradicts the traffic-control plan. If the plan shifts traffic across one lane and the patch crosses both lane lines without temporary delineation, the paving surface may be ready but the traffic switch is not.

A hold is not a permanent rejection. It means the record is not clear enough to move traffic without creating avoidable safety, maintenance, or dispute risk.

Night and phased traffic switches

Night switches need extra timing evidence. Record lighting, placement time, final rolling time, cooling time, inspector release, temporary marker installation, sign changes, cone removal, flagger release, and whether traffic was switched before or after the next phase started.

In phased work, a patch can be accepted for one night and replaced or overlaid the next day. The release should name the duration and next work step. If the temporary patch is expected to remain through weather or peak traffic, state the monitoring plan.

When photos are taken at night, include enough wide context to identify the lane and approach. A black patch under a work light is not useful later unless it is tied to a station, sign, cone line, or recognizable location.

Multiple trench patches

If several trench patches are released in one switch, give each patch a separate ID and decision. TP-1 released, TP-2 held for marker correction, and TP-3 limited to construction traffic is much clearer than northbound patches ready.

For a corridor with repeated utility cuts, record the order of release and the lane they affect. A traffic switch may route vehicles across multiple patches in sequence. One weak patch can control the whole switch even if the others are acceptable.

Keep photos grouped by patch ID. The most common documentation failure is a folder full of close-ups with no route order, station, or lane reference.

Safety boundary for photos

The photo task should not put anyone in live traffic, inside an unprotected trench, under suspended loads, near hot mix without PPE, in front of backing equipment, inside the roller path, or into a traffic-control zone without authorization. Use safe vantage points and the designated traffic-control setup.

OSHA 1926.651 includes requirements for excavation egress and high-visibility garments for employees exposed to public vehicular traffic. OSHA Subpart P covers excavation requirements and protective systems. Those sources support keeping the record outside trench entry and live-traffic exposure.

If the needed evidence cannot be photographed safely, record the limitation and attach the qualified inspection or test record. A missing photo is easier to fix than an unsafe photo attempt.

What not to claim

Do not claim permanent restoration acceptance, density compliance, asphalt mix compliance, backfill compliance, utility trench acceptance, traffic-control plan approval, lane-opening authority, ADA compliance, pavement smoothness acceptance, or warranty release unless the responsible record says so.

Do not claim tack coat rate, residual asphalt rate, or bond strength from a photo. FHWA sources support documenting tack condition and rate language, but actual acceptance depends on the project requirement and test or inspection method.

Do not claim that traffic can use the patch just because the roller left. Opening depends on compaction, cooling, traffic control, surface condition, markers, cleanup, and the release authority.

Source-specific limitations

The sources used here support documentation concepts: patch outline, sawcut edge, tack coat, surface preparation, lift thickness, compaction method, roller or plate evidence, surface profile, cooling, temporary traffic control, trench safety, and temporary restoration boundaries.

They do not create one universal trench patch section. Agency specifications vary by road classification, utility permit, pavement age, pavement type, traffic load, climate, inspection authority, and temporary duration. The article intentionally avoids universal thicknesses, rates, temperatures, densities, and roller patterns.

For a real project, the controlling sources are the approved permit, traffic-control plan, trench restoration detail, agency standard, asphalt mix submittal, tack submittal, contractor quality plan, inspector direction, OSHA requirements, and owner release decision.

Reviewer questions

Ask whether another person can find the patch, lane, and traffic-switch stage from the record. If not, add wide photos, station references, lane labels, or drawing mark-ups.

Ask whether the record separates patch surface readiness from traffic-control readiness. A patch can be paved and still not released for traffic if markers, signs, barriers, pedestrian routing, or authority are missing.

Ask whether the packet could be mistaken for permanent restoration acceptance. If it could, add the limitation: temporary traffic-switch release only, permanent restoration and final acceptance remain by owner or agency.

Final decision record

The final decision should name the patch, evidence reviewed, traffic condition, open exceptions, and next action. Good decisions are released for traffic switch, held for sawcut repair, held for tack correction, held for compaction proof, held for surface profile correction, held for markers, released for construction traffic only, released for emergency access only, or owner review required.

Keep the final note short but specific. The owner does not need every photo repeated. They need to know which trench patch was documented, what traffic is allowed, which records support the patch, what remains temporary, and what conditions still need permanent restoration.

A clean temporary trench patch record protects the traffic switch. It ties the sawcut edge, tack coat, lift thickness, compaction evidence, roller or plate passes, lane-opening details, traffic-control status, and release decision into one field packet before vehicles use the new path.

Sources checked

• FHWA, HMA Asphalt Patching Checklist FHWA-HIF-19-041Used for patch document review, traffic-control plan context, saw or milling patch outline, tack coat on vertical faces, lift thickness, compaction, surface flushness, lane-line markers, and opening to traffic.
• FHWA, Tack Coat Best Practices FHWA-HIF-16-017Used for tack coat bonding purpose, poor-bond distress context, residual-rate language, surface preparation, uniformity, break, set, tracking, and distributor context.
• FHWA, Asphalt Emulsion-Based Tack Coat Checklist FHWA-HIF-19-039Used for tack coat document review, surface condition, dry pavement, break and cure context, tracking controls, traffic control, and residual-rate checks.
• FHWA, Thin Hot Mix Asphalt Overlay Checklist FHWA-HIF-19-030Used for weather, lift thickness, cooling, compaction timing, traffic control, and paving inspection context.
• City of Tampa, Pavement and Right-of-Way Restoration StandardUsed as a municipal trench-restoration example for temporary restoration limits, mechanical compaction, sawcut and bench geometry, lane restoration details, and right-of-way restoration boundaries.
• WSDOT, Maintenance Manual Chapter 3 Pavement Patching and RepairUsed for patch edge, tack coat, lift thickness, compacting hot mix patches, roller timing, cooling before traffic, and patching operation context.
• Caltrans, Construction Manual Section 4-39 Asphalt ConcreteUsed for agency inspection context around hot mix asphalt, materials, paving, compaction, and traffic release boundaries.
• Caltrans, Tack Coat GuidelinesUsed for tack coat terminology, type and grade selection context, quantity estimation, surface condition, tracking, and inspection boundaries.
• Caltrans, MTAG Chapter 5 Patching and Edge RepairUsed for patching and edge repair context, temporary versus semi-permanent patching, square patch boundaries, tack on repair edges, compaction equipment, roller passes, crown, and edge sealing.
• FHWA MUTCD, 11th Edition with Revision 1 Current EditionUsed to identify the current official MUTCD edition and to keep traffic-control references tied to the current FHWA publication.
• FHWA MUTCD, Part 6 Temporary Traffic ControlUsed for temporary traffic control context, road user needs, TTC plans, and device responsibilities, with current-edition confirmation checked separately.
• OSHA, 29 CFR 1926.651 Specific Excavation RequirementsUsed for excavation safety boundaries, trench egress, and public vehicular traffic high-visibility garment context.
• OSHA, 29 CFR 1926 Subpart P ExcavationsUsed for excavation scope, protective systems context, and the safety boundary between documentation and trench work.
• NYC DOT, Street Works Manual Section 4.3 Street Restoration RequirementsUsed for temporary restoration context, unfinished street opening repairs, temporary asphalt pavement thickness after compaction, and flush-with-adjacent-surface language as a municipal example.

Related guides