Header joint next-lane pour record

Direct answer

A header joint next-lane pour record should prove the construction joint location, the bulkhead or header form, the side-form line, the tie bar field, any dowel or tie detail at the transverse header, the condition of the formed edge, visible edge slump, boxouts and fixture openings, opening protection, projecting bar protection, corrections, holds, and the final release status before another lane or continuation pour relies on the work.

The record matters because a header looks temporary while the crew is finishing, but it can control the next placement. If the header board is out of line, the side forms rock, tie bars are bent or buried, a boxout edge breaks down, edge slump is not corrected, or an opening is left with unclear protection, the next crew can inherit a joint that is hard to match and harder to explain. A good photo packet does not approve the pavement by itself. It preserves the facts that the foreman, inspector, engineer, owner, and adjacent-lane crew need before the work disappears or gets covered by the next operation.

This is not a pavement design, tie bar design, dowel design, formwork engineering detail, fall-protection plan, traffic-control plan, opening-to-traffic approval, or authorization to pour an adjacent lane. The plans, specifications, agency standards, approved mix, paving plan, safety plan, traffic-control plan, and responsible engineer control those decisions. The purpose here is narrower: make a traceable field record before the next lane or next placement turns a temporary-looking header into a permanent joint.

What this record covers

Use this record when a concrete pavement placement stops at a construction header, when a lane is being paved beside an earlier lane, when fixed forms define a slab edge, or when a continuation pour will later start from the end of the previous placement. It fits roadways, yards, aprons, shoulders, industrial pavements, curb lanes, heavy slabs, and other exterior pavement work where a formed construction joint needs a clean handoff.

The packet should cover the full chain, not one final photo. Before placement, it records the planned header location, side forms, bulkhead, bars, boxouts, openings, grade, and references. During placement, it records whether the header stayed true, whether bars were disturbed, whether consolidation reached the form face, and whether the edge stayed within the project requirement. After placement, it records form removal, exposed edge condition, curing, protected openings, backfill or edge support, corrections, holds, and release status.

Keep it separate from a dowel basket layout record. Dowel basket records center on hidden load-transfer assemblies and sawcut alignment. This record centers on the formed construction joint and the next lane or continuation pour. The two packets can reference each other, but one should not replace the other.

Define the header handoff boundary

Start the packet by naming exactly what is being handed over. A useful boundary might say northbound outside lane, stations 48+20 to 52+60, transverse construction header at 52+60, longitudinal construction joint along lane line L2, side forms from 48+20 to 52+60, tie bars TB-101 through TB-142, inlet boxout CB-7, utility sleeve opening U-3, and next-lane release limited to the east adjacent lane. That is much stronger than header checked.

The boundary should say which gates are included and which are excluded. A header record may include form line, bar continuity, edge condition, and opening protection, while excluding concrete strength acceptance, traffic opening, smoothness, joint sealing, coring, pullout testing, and owner final acceptance. Exclusions prevent a field photo record from being read as approval for work it did not review.

Name the clock too. Record when the header was set, when concrete reached it, when finishing at the header ended, when the header was reviewed, when forms were removed if applicable, and when the adjacent-lane crew was released or held. A next-lane crew often works from a short window. The record should show which facts were known at release time and which items remained open.

Start with the approved basis

Collect the approved paving plan, joint layout, staging plan, standard details, bar schedule, tie bar submittal, dowel or header detail, side-form requirement, boxout detail, utility adjustment detail, curing plan, rain protection plan, inspection test plan, safety plan, and traffic-control plan before the header is treated as ready. The field record should compare the work to those documents. It should not create a new joint layout from photographs.

FHWA, DOT, and concrete pavement sources agree on the same practical split: construction joints, forms, bars, consolidation, curing, and protection are controlled by the project documents and agency requirements. The article can explain what to record, but it cannot publish one tie bar spacing, edge slump tolerance, form detail, opening cover, or traffic opening rule for every project.

When the approved basis changes, attach the change. If the header moves because trucks are delayed, a boxout shifts, the adjacent lane has a joint mismatch, a form line needs to clear a fixture, or an engineer directs a revised tie-in, the record should show the original basis, the revised basis, who accepted it, and the time. Do not let the photo packet quietly rewrite the plan.

Locate the construction joint

A transverse header should be traceable to a station, panel, grid line, plan joint, or approved field revision. FHWA describes transverse construction joints as end-of-day or staging joints and longitudinal construction joints as joints between lanes placed at different times. Agency examples also treat header location as a controlled item, not a casual stopping point. Your packet should identify the joint type and the reason the placement stopped there.

Photograph the location from both directions. The wide photo should show the paving lane, station marks, edge references, adjacent lane, and nearby fixtures. The medium photo should show the header line, bulkhead, side forms, joint mark, and bar field. The close photo should show the header face, form contact, bar penetrations, wedges, stakes, and any visible gap or movement risk.

If the header cannot land at the planned joint, record the hold before concrete locks in the condition. A header set close to a transverse joint, boxout, inlet, panel corner, or adjacent-lane working joint may need engineer direction. The field record should not make that judgment silently. It should show the conflict, the question asked, the answer received, and the final release limit.

Set the bulkhead form

The bulkhead or header form is the face of the construction joint. Caltrans specifications call for transverse construction joints to be formed with a metal or wooden bulkhead, and FHWA describes formed headers that receive dowels or ties where required by the project. MnDOT describes the header board as shaped to the pavement cross section and calls headers a continuing field challenge. The photo record should treat the bulkhead as a controlled feature, not scrap lumber at the end of a pour.

Record whether the form is straight, vertical where required, cut to the pavement section, tight at the grade, braced, staked, aligned with the intended joint, and able to hold bars in the required position if bars pass through it. Show both sides if the next placement will tie into the face. If holes are drilled through the form for bars, show the pattern and how the bars are held against movement.

A good closeout photo shows the header after finishing as well as before placement. The before photo proves the setup. The after photo proves the joint face and edge were not left with obvious honeycomb, sloughing, displaced bars, damaged corners, or loose material. If the form cannot be removed yet, record the planned follow-up and who owns it.

Record side forms and grade line

Side forms deserve their own sequence because they control edge shape, lane width, finished grade, and the starting condition for the next lane. Caltrans, WSDOT, Iowa SUDAS, MnDOT, and FHWA field references all emphasize form rigidity, bearing, line, grade, cleaning, support, and protection against movement. If the paving equipment rides on the forms, form movement can become pavement shape.

Photograph the side-form run before concrete is placed. Show the top line, pins or stakes, form joints, interlocks, bearing on the subgrade or base, tightness to grade, release agent condition, curve sections, and transitions into the header. If forms are set beyond the header to carry grade or finishing equipment, show that extension. MnDOT specifically notes running forms beyond headers for grade and finishing support.

During placement, record any visible form movement, rocking, lifting, spreading, or settlement. A note that says form line checked before pour is incomplete if the form later moved under equipment. If the form is corrected, photograph the before condition, correction, and after condition before releasing the edge for adjacent-lane work.

Track tie bar continuity

Tie bars at longitudinal construction joints tie adjacent lanes or shoulders together when the project requires that system. FHWA explains that tie bars help prevent lane separation and joint opening at longitudinal joints, while dowels at transverse joints serve a different load-transfer role. Do not blur those functions in the record. Name the longitudinal joint, the tie bar area, and the detail being followed.

The field record should capture the approved tie bar basis, bar type reference, spacing or location reference, embedment basis, coupler or bent-bar detail if used, coating condition if visible, and any restriction near transverse joints. MnDOT, WSDOT, and Caltrans all treat tie bar placement as a plan-controlled item. This article should not publish one bar size or spacing. It should tell the crew to record the project rule and the observed field condition.

Show continuity across the handoff. If tie bars project from the first lane, photograph their line, elevation, spacing reference, protection, damage, bends, and any repairs. If bars will be drilled and bonded later, record that as the planned method and do not imply they already exist. If couplers are used, show the coupler line and the protected ends that the next crew will receive.

Keep transverse bars separate

A transverse header may include dowels, tie bars, sleeves, false dowels, drilled bars, or no bars depending on the project detail and the type of construction joint. FHWA describes formed headers where bars pass through the header board and are cast into the next section, and it also distinguishes tied construction joints from doweled load-transfer joints. The record should use the project terminology instead of calling every projecting bar a dowel.

Photograph the transverse bar field at the header from enough distance to show the joint line and close enough to show the penetrations through the bulkhead. Record the drawing or standard detail, bar condition, visible alignment, end protection, bond-breaker or coating evidence where relevant, and any cap, sleeve, or obstruction that affects the next placement.

Do not certify bar alignment from a photo unless the required measurement or authorized reviewer supports that statement. A photo can show observed position, support, and condition. If the project requires coring, MIT scan, pullout testing, survey, or inspector measurement, attach that record or state where it lives.

Consolidate the header area

Headers and form faces are easy places to leave voids because the paving train changes rhythm, workers hand finish, and concrete must be worked around bars and the bulkhead. FHWA, MnDOT, and WSDOT materials all emphasize consolidation around headers, forms, dowels, and tie bars. The handoff record should show that the crew watched the area where hidden weakness is most likely.

Record the consolidation method used by the project, the timing, and the visible result. Photos can show concrete worked against the header, vibration or hand consolidation near the form, finishing around projecting bars, and the final surface at the joint. If the project uses internal vibrators, form vibrators, or hand spading, record the observed use without writing a substitute procedure.

Do not hide honeycomb, loose paste, segregation, or a weak corner. If the header face or form line shows a void after form removal, the packet should show the condition, the reviewer, the repair requirement or hold, the repair photo, and the release decision. A header with a pretty top surface can still have a weak face if the edge was not consolidated.

Watch edge slump and formed-edge damage

Edge slump is not only a surface blemish when the next lane must tie into the edge. WSDOT and Caltrans specifications include edge slump correction requirements, and MnDOT lists edge slump causes such as concrete consistency, air, gradation, water-cement ratio, edge vibrator position, and paver speed. Those details prove that edge condition is a real inspection item. They do not create one tolerance for every job.

Record edge slump by location, length, side of lane, time observed, and controlling requirement. Take a wide photo showing the edge in context, a medium photo showing the affected run, and a close photo showing the condition against a straightedge or project-approved check if one is used. If the edge is corrected before hardening, show the correction and the recheck.

Also record formed-edge damage after form removal. Spalls, rounded corners, unsupported edges, honeycomb, sloughed shoulders, and paste buildup can affect adjacent-lane fit. If the next lane relies on the edge as a form or reference, the release note should say whether the edge is accepted, repaired, protected, or held.

Record boxouts and fixture openings

Boxouts and fixture openings can break the rhythm of a header record. Iowa SUDAS treats boxouts for fixtures as part of pavement work and calls for construction joints at boxouts where specified. MnDOT includes boxouts and fixture adjustments among fixed-form paving factors. A boxout can affect joint layout, side forms, consolidation, edge protection, and the next paving tie-in.

Photograph each boxout before placement, during placement if practical, and after initial finish. Show the fixture ID, station, boxout dimensions or approved detail reference, form condition, ties or dowels near the opening, clearance to joints, edge condition, and any protection installed after finishing. If the boxout is temporary and will be filled later, record who owns the later fill and what is blocked until then.

Openings are not only concrete details. They can be safety hazards. OSHA rules for holes, covers, guardrails, signs, barricades, and traffic control may apply depending on the work surface, lower level, vehicle exposure, and site conditions. This article does not design those controls. It tells the field team to record the safety-control status and hold the area when protection is unclear.

Protect openings and work areas

Opening protection needs enough evidence that the next crew knows what can and cannot be crossed. OSHA 1926.501 addresses protection from holes and fall hazards. OSHA 1926.502 gives criteria for covers, guardrails, and fall-protection systems. OSHA 1926.200 addresses signs, signals, barricades, traffic control devices, and temporary hazard tags. Those standards belong to the safety program, but the handoff record should not ignore them.

Record whether each opening, boxout, excavation edge, pit, inlet, sleeve, or utility blockout is covered, guarded, barricaded, signed, fenced, or held under the site safety plan. If a cover is installed, photograph its location, marking, securing method, and traffic or equipment restriction as required by the responsible safety authority. If a barricade or sign protects a fresh pavement edge or hole, photograph it in relation to the hazard, not as a close-up of tape.

Do not write safe unless the responsible safety process has made that determination. Better field language is opening U-3 covered and marked per superintendent direction, no equipment crossing permitted, adjacent lane pour held until safety review at 7:00 a.m. That tells the next crew what was observed and what remains controlled by others.

Protect projecting bars

Projecting bars at a header or longitudinal joint need protection because the next operation depends on their position and condition. WSDOT notes that projecting ends from forms should be protected against disturbance that could affect the bond between bars and concrete. FHWA and agency sources also treat bars as part of the joint system, not loose accessories.

Photograph projecting tie bars, dowels, sleeves, couplers, and caps after finishing and after protection is installed. Show whether the bars are straight, supported, clean enough for the next operation, protected from equipment impact, and clear of obvious conflicts. If a bar is bent for staging and later straightened under the project detail, record that sequence and any coating repair or reviewer acceptance required by the project.

Protect people as well as the work. Protruding steel, open holes, wet concrete edges, and night work can create hazards. The photo record should show barricades, caps, exclusion zones, lighting, or other controls only as evidence of the site plan in place, not as a replacement for competent supervision.

Photograph before the pour

Before concrete reaches the header, take a wide, medium, and close photo sequence. The wide photo shows lane, station range, header location, side-form line, adjacent lane, boxouts, openings, and access route. The medium photo shows the bulkhead, bar field, pins, braces, form joints, grade line, and edge references. The close photos show bar penetrations, form bearing, stake or brace condition, release agent, gaps, honeycomb risk points, and any conflict.

Include the approved basis in the photo set. A photo of the plan sheet, marked layout, or inspection checklist placed near the work can help later if file names are stripped by an owner platform. The plan photo does not replace the official document. It connects the field images to the document used at that time.

Photograph exceptions before correction and after correction. If a form rocks, a bar conflicts with a boxout, a bulkhead gap is packed, a side form is reset, an opening cover is replaced, or an edge mark is restored, the packet should show the before condition, the correction, and the release. Final-only photos can make a real correction look like a missing issue.

Record during placement

The header can change during placement. Concrete pressure, workers, vibration, equipment, weather, finishing tools, and delays can move forms or disturb bars. Record the time concrete reached the header, the condition of the bulkhead, the bar field, the side forms, the edge, and any visible movement. A pre-pour form photo is useful, but it does not prove the form held during the pour.

Record truck spacing, delay events, rain, mix consistency concerns, slump or workability test references, paver speed changes, hand finishing at the header, and protection steps only where they affect the handoff. The record should not become a minute-by-minute diary. It should preserve the facts that explain whether the next lane can rely on the joint.

If placement is interrupted, document the decision point. Caltrans specifications, for example, include a construction-joint requirement when placement is interrupted beyond a specified time, and other agencies have their own rules. Do not import that time into another project. Record the project rule, the interruption, the direction received, the header location, and the hold status.

Use holds before the next lane

A hold is useful only if it says what is blocked. Some holds block more concrete placement. Some block adjacent-lane paving. Some block form removal, traffic access, backfill, joint sealing, or final paperwork. Do not write held for review and leave the next crew guessing.

Common header holds include bulkhead out of line, side form movement, unverified tie bar continuity, projecting bars damaged, header face honeycombed, edge slump not corrected, boxout form moved, opening cover missing, adjacent-lane joint mismatch, curing incomplete, edge not protected, or strength/opening data not available. Each hold should name the location, reason, responsible reviewer, required evidence, and release condition.

A release should be just as explicit. Accepted for adjacent-lane layout is not the same as accepted for traffic. Accepted for form removal is not the same as accepted for backfill. Accepted with exceptions should list the exceptions and the blocked follow-up. The next crew should know exactly what it can rely on.

Build a next-lane release map

The next-lane release map is the index for the whole packet. It should show the previous lane, the next lane, the header station, longitudinal construction joint, side-form line, tie bar field, transverse joints, boxouts, openings, protected edges, bars that project into the next work area, and every hold. A simple marked-up plan sheet is often enough if it is dated and controlled.

Use both stationing and field language. The crew may need east side of northbound lane at CB-7, third panel past light pole 12, not only station 52+60. The owner reviewer may need the station and joint number. Put both in the caption where practical.

Do not let the map become fiction. If a tie bar is missing, a header moved, a boxout is held, or an edge repair is pending, show it on the release map. A map that hides open work creates more risk than no map because it invites the next crew to treat uncertain work as ready.

Coordinate adjacent lanes and matched joints

Adjacent-lane work makes header records more sensitive. FHWA notes that transverse joint locations should be matched across adjacent tied lanes unless panels are isolated. WSDOT specifications distinguish lanes paved at the same time from lanes paved separately, with construction joints used when lanes are placed separately. The record should show whether the next lane must match a joint, tie into a longitudinal construction joint, or stay isolated by an approved detail.

Photograph adjacent-lane joint references before the next pour starts. Show existing transverse joints, transferred marks, tie bar line, edge condition, and any mismatch that needs review. If the new lane will start from a header, show the header station and how the continuation joint will be located.

If the adjacent lane is being used by equipment, record protection. Caltrans and WSDOT sources discuss protecting adjacent pavement from equipment and traffic damage. A next-lane release should say whether equipment may run on the previous pavement, what protective material or restriction applies, and who approved it under the project documents.

Record form removal and edge curing

Form removal can reveal conditions that were hidden during finishing. Iowa SUDAS, WSDOT, Caltrans, and MnDOT all address careful form removal and edge curing or protection. If the next lane relies on the exposed edge, the release record should include a form-removal check rather than ending at the finished top surface.

Photograph the edge after forms are removed. Show honeycomb, spalls, chips, sloughed edge, paste buildup, damaged corners, tie bar condition, curing compound on the exposed edge where required, and any repair. If forms remain in place to protect the edge, record the reason, planned removal time, and who will perform the follow-up check.

Do not pry a release out of an unseen edge. If the edge cannot be inspected yet, the next-lane release should say conditional or held, depending on project practice. A buried condition should not become accepted just because the schedule wants to move.

Keep backfill and edge support in the packet

Fresh pavement edges can be vulnerable after forms are removed. Iowa SUDAS calls for backfill or protection adjacent to curbs and pavement edges after form removal and also addresses pavement protection during cold, rain, and traffic conditions. WSDOT requires pavement protection during curing until opening conditions are met. The record should show how the edge is protected until the next operation.

Photograph temporary backfill, edge dams, runoff protection, barricades, cones, fence, equipment exclusion, and any no-crossing condition that protects the edge or subbase. If the next lane will be paved soon, record whether edge support is temporary, final, or intentionally left open for the adjacent placement.

If rain, washout, soft subgrade, or traffic damages the edge before the next lane starts, update the packet. A release from yesterday can become stale after weather or site traffic. The adjacent-lane crew needs the condition at the time it starts work, not only the condition at initial finish.

Separate traffic opening from lane release

Next-lane release is not the same as opening to traffic. Caltrans, WSDOT, and Iowa SUDAS all tie traffic opening or early use to strength, maturity, modulus, curing, testing, agency determination, or other project-specific controls. A header photo packet should not say a pavement is ready for vehicles unless the controlling opening process says that.

Use clear language. Released for adjacent-lane layout means the next crew may use the header and edge references under the project plan. Released for form removal means forms may be removed under the project procedure. Released for traffic means a different gate has been satisfied. The record should not combine those decisions into one accepted stamp.

If equipment must cross fresh pavement to place the adjacent lane, record the approved basis, restrictions, protection, route, and reviewer. Do not let a next-lane handoff become an undocumented early-use decision.

Close corrections

Corrections should be traceable. Use the same chain for every correction: item ID, location, condition, controlling requirement or reviewer direction, responsible party, correction, after photo, reviewer, and release status. If the bulkhead was reset, show it. If tie bars were straightened, show it. If a boxout edge was repaired, show it. If edge slump was corrected, show the recheck.

Do not bury corrections in a general note. A note that says minor corrections complete does not tell the next crew whether the tie bars are usable, the opening is protected, the edge is accepted, or the header face is ready. Each correction should close the specific risk it created.

Keep open items visible. A clean record can still include holds. In many cases, a record that names two open holds is stronger than a record that pretends everything is done. The purpose of the packet is not to make the work look perfect. It is to make the next decision clear.

Inspection table

Use a compact table so the foreman, inspector, adjacent-lane crew, and owner reviewer look at the same handoff evidence.

Paving handoff checklist

Run this checklist before accepting a header joint and next-lane pour packet.

• Lane, station limits, header ID, longitudinal joint, side-form run, tie bar area, openings, and exclusions are named.
• Approved paving plan, joint layout, header detail, bar schedule, boxout detail, curing plan, and safety or traffic-control references are attached or cited.
• Transverse header location is photographed with station, panel, adjacent-lane, and fixture references.
• Bulkhead or header form is shown before placement, including line, grade, bearing, bracing, gaps, and bar penetrations.
• Side forms are shown with stakes, pins, interlocks, bearing, release agent, curve sections, and extension beyond the header if used.
• Tie bar continuity is recorded against the project detail, including projecting bars, couplers, bent bars, protection, and visible damage.
• Transverse header bars are identified separately from longitudinal tie bars.
• Consolidation around the header, forms, bars, and boxouts is observed or assigned under the project inspection plan.
• Edge slump and formed-edge damage are checked by location and recorded against the controlling requirement.
• Boxouts, fixture openings, utility openings, and special forms are photographed before and after placement.
• Opening protection, covers, guardrails, barricades, signs, fencing, or holds are recorded under the site safety process.
• Projecting bars and fresh edges are protected from disturbance, traffic, equipment, and weather where required.
• Form removal and exposed-edge curing or repair are photographed before adjacent-lane release when required.
• Backfill, edge support, runoff protection, or no-crossing restrictions are recorded if they affect the next operation.
• Corrections include before photo, action, after photo, reviewer, and release status.
• Final release states exactly what is allowed: next-lane layout, adjacent-lane pour, form removal, backfill, traffic opening, or final paperwork.

Weak versus strong record

Weak record: Header set. Tie bars ok. Next lane can pour.

That note does not name the lane, station, construction joint, approved detail, bulkhead condition, side-form line, tie bar field, boxouts, openings, edge slump, projecting bar protection, corrections, holds, reviewer, or release limit. It may be true in the moment, but it will not help if the adjacent lane later shows a mismatch, a broken edge, a missing tie bar, or an unsafe opening.

Strong record: Northbound outside lane, stations 48+20 to 52+60, transverse construction header H-52 at station 52+60 and longitudinal construction joint L2 were reviewed for adjacent-lane release on June 9, 2026. Photos NB-001 through NB-006 show approved layout sheet P-21, field markup, station references, inlet CB-7, and side-form run. Photos NB-007 through NB-020 show the bulkhead board set to the planned header, braced, tight to grade, with transverse bar penetrations matching detail J-6. Photos NB-021 through NB-038 show side forms, pins, interlocks, release agent, tie bars TB-101 through TB-142, and projected bars protected from equipment.

The same record says concrete reached the header at 4:18 p.m. and finishing at the header ended at 4:42 p.m. Photos NB-039 through NB-052 show consolidation around the header and boxout CB-7, edge check along L2, corrected slump at stations 51+10 to 51+24, and after photos at 5:05 p.m. Photos NB-053 through NB-060 show opening U-3 covered and marked under the site safety process, edge curing after form removal, and a no-crossing restriction at the fresh edge. The release says adjacent-lane layout may begin, adjacent-lane concrete placement remains held until edge repair R-4 is accepted, and traffic opening is excluded.

The strong record works because another reviewer can locate the joint, understand what was checked, see the open hold, and avoid treating a lane-layout release as a traffic-opening approval. It does not need dramatic language. It needs enough specific evidence for the next crew to make the right decision.

Common mistakes

The first mistake is photographing only the finished top of the header. The top surface does not show whether the bulkhead was straight, braced, tight to grade, or able to hold bars. Keep before, during, and after photos together.

The second mistake is writing tie bars installed without showing continuity. A tie bar record should identify the longitudinal joint, the project detail, the visible bar field, couplers or bent bars, protection, and conflicts. If bars will be drilled later, say that instead of implying they are already complete.

The third mistake is treating edge slump as cosmetic. If the next lane must fit against the edge, the condition belongs in the release record. Record the location, check method, correction, and after photo against the project requirement.

The fourth mistake is treating openings as someone else's paperwork. Boxouts, inlet throats, sleeve openings, holes, and protected work areas can affect both concrete work and safety controls. Put them on the handoff map and state whether they are covered, guarded, barricaded, signed, held, or excluded.

The fifth mistake is mixing release gates. A lane may be ready for layout but not for concrete, ready for form removal but not for backfill, or ready for adjacent-lane work but not for traffic. The final line of the record should use the right release type.

Photo index and file names

The record should survive after photos leave a phone. Use file names or captions that carry the lane, station, header ID, condition, and sequence. A useful pattern is NB-H52-bulkhead-before-001, NB-H52-tiebar-east-edge-002, NB-H52-boxout-CB7-cover-003, NB-H52-edge-slump-corrected-004, and NB-H52-release-map-005. The exact pattern matters less than a pattern that another reviewer can sort and search.

Every caption should answer what, where, when, and why. Example: northbound outside lane, station 52+60, header H-52, bulkhead braced before placement, looking north, June 9, 2026, adjacent-lane pour not released. A caption that says header photo is weak because it does not connect the image to a decision.

Keep wide, medium, and close photos grouped. The wide photo locates the header in the lane. The medium photo shows how the bulkhead, side form, tie bars, and openings relate to each other. The close photo shows a condition that may need review, such as a gap, damaged edge, bent bar, cover, pin, brace, or correction.

If an owner platform renames files, upload a photo schedule with the packet. The schedule should cross-reference platform file name, original file name, header ID, station, joint, bar group, opening, checklist item, correction item, and release status. The point is simple: the evidence should still make sense after the crew leaves and the photos are no longer in the order they were taken.

Weather and delay notes

Weather and delays can change the meaning of a header release. Iowa SUDAS addresses rain protection, pavement protection, cold weather protection, and traffic protection. Caltrans and WSDOT also tie curing, protection, and early use to project-specific conditions. The handoff record should capture weather and delay facts that affect the header, edge, openings, and next-lane work.

Record rain, wind, temperature swings, standing water, soft form support, curing interruptions, night work, late trucks, equipment breakdown, concrete delivery gaps, and delayed form removal when those facts affect the release. If the side-form base softened after rain, photograph the condition and the reset. If a header was finished after dark, record lighting, inspector coverage, and whether the next-lane release was delayed until a daylight check.

Update stale releases. A header accepted at 5:00 p.m. can be damaged by stormwater, jobsite traffic, equipment, or cover movement before the adjacent lane starts the next morning. The packet should show either that the release was rechecked or that the next crew must recheck specific items. A short recheck photo can prevent a clean previous-day record from being mistaken for current conditions.

Questions that come up

Does every header need a full record? Use the level of record that matches risk and contract requirements. A low-risk small slab may need a short note. A pavement lane that controls adjacent-lane tie-in, traffic staging, utility openings, or owner acceptance needs a stronger packet.

Can a photo prove tie bar compliance? A photo can show visible position, protection, damage, and continuity at the time observed. It cannot prove hidden embedment, pullout resistance, coating thickness, or acceptance tolerance unless paired with the required measurement, test, or authorized review.

Should edge slump be measured? Follow the project requirement. Some specifications publish explicit limits, some use inspector judgment, and some route the issue through repair provisions. The article does not set the limit. It says the field record should show the condition, the check used, and the correction or hold.

Can the adjacent lane pour before forms are removed? That depends on the project sequence, strength, edge protection, forms, access, and engineer or agency direction. If the edge cannot be inspected yet, the release should say what is conditional and who owns the follow-up.

Does opening protection mean traffic opening? No. Opening protection here means holes, boxouts, fixture openings, pits, fresh edges, and work areas are protected or held under the safety and traffic-control process. Opening to traffic is a separate pavement acceptance gate.

Does this replace a safety plan? No. OSHA requirements, employer procedures, competent supervision, equipment manuals, traffic-control plans, and site-specific safety controls govern the work. The packet records observed status and holds; it does not design the controls.

Compliance and safety limits

Treat this article as a field documentation structure, not a design or acceptance specification. The adopted agency requirements, owner standards, project specifications, approved plans, engineer direction, quality control plan, quality assurance procedure, safety program, and traffic-control plan control the actual work.

Do not use this checklist to choose tie bar size, dowel size, bar spacing, embedment, couplers, pullout testing, bulkhead engineering, form design, edge slump tolerance, edge repair, curing method, opening cover capacity, barricade layout, fall-protection system, traffic-control device, or opening-to-traffic strength. Those choices belong to qualified personnel using the controlling documents.

Concrete paving around headers can involve fresh concrete, projecting steel, moving equipment, night work, traffic exposure, open holes, boxouts, wet surfaces, sawcut operations, and limited access. OSHA standards, traffic-control plans, equipment manuals, employer safety procedures, and competent supervision control those hazards.

If a condition appears unsafe, outside the approved details, hidden from view, or beyond field authority, record the visible facts and hold the item for the proper reviewer. A good header record does not make uncertain work look certain. It makes the uncertainty visible enough to manage before the next lane starts.

Sources checked

• FHWA Technical Advisory T 5040.30, Concrete Pavement JointsUsed for construction joint types, transverse headers, longitudinal construction joints between lanes, tie bar purpose, adjacent-lane coordination, and consolidation around dowels or ties at headers.
• FHWA, Integrated Materials and Construction Practices for Concrete Pavement: A State-of-the-Practice ManualUsed for construction joint practice, form and header context, paving process controls, mix consistency, consolidation, curing, and field troubleshooting context.
• FHWA, Quality Concrete Pavements Field ReferenceUsed for fixed form setup, header supplies, consolidation at headers, slump and workability checks, edge slump context, and checklist framing.
• Iowa SUDAS Standard Specifications, Section 7010 PCC PavementUsed for forms, boxouts, construction joints at headers and boxouts, longitudinal joint edge controls, pavement protection, rain protection, traffic protection, backfill, and opening-strength boundary.
• Caltrans Construction Manual, Section 4-40 Concrete PavementUsed for preconstruction discussion, tie and dowel bar inspection, side-form inspection, placement monitoring, edge slump, construction joints, curing and saw schedule monitoring, coring context, and repair boundary.
• Caltrans Standard Specifications 2023, Section 40 Concrete PavementUsed for construction joints, bulkheads, side-form construction, tie bar placement methods, interruption header rule, edge slump correction, curing, protecting pavement, early use, and opening to traffic limits.
• WSDOT Construction Manual, Chapter 5Used for inspector checklist, fixed forms, edge slump, night headers, construction joints, projecting bar protection, form removal, curing edges, traffic protection, and adjacent-lane cautions.
• WSDOT Standard Specifications, Division 5, 2026Used for side-form requirements, construction joints, tie bars at longitudinal construction joints, edge slump correction, protection of pavement, construction in adjacent lanes, and opening to traffic.
• MnDOT Concrete Manual, Chapter 6Used for header setup, side forms beyond headers, tie bars, keyways, consolidation around headers, edge tooling, form removal, edge curing, boxouts, and edge slump causes.
• MnDOT Design Scene, Chapter 10 PavingUsed for paving planning context, joint layout and stage coordination, and design-office boundary for field records.
• NRMCA CIP 6, Joints in Concrete Slabs on GradeUsed for general joint purpose, construction joint basics, planned joint layout, raveling, and uncontrolled cracking.
• OSHA, 29 CFR 1926.501 Duty to have fall protectionUsed for safety boundaries around holes, leading edges, unprotected sides and edges, and employer fall-protection duties.
• OSHA, 29 CFR 1926.502 Fall protection systems criteria and practicesUsed for cover, guardrail, hole, and fall-protection system criteria as safety boundaries.
• OSHA, 29 CFR 1926.200 Accident prevention signs and tagsUsed for signs, signals, barricades, traffic control devices, and temporary hazard-warning boundary for protected work areas.

Related guides