Dowel basket paving handoff record

Direct answer

A dowel basket paving handoff record should prove the path from the approved joint layout to the hidden load-transfer steel and then to the finished sawcut. At minimum, it should name the paving lane or placement area, station limits, joint IDs, basket IDs, dowel type or schedule reference, basket condition, anchorage method, marked sawcut locations, saw crew handoff, placement time, first saw time, sawcut sequence, observed raveling or random cracking, corrections, holds, and final release decision.

The record matters because the most important load-transfer evidence is buried shortly after concrete placement. Once the paver passes, the owner cannot see whether baskets were set at the planned joints, whether they were anchored, whether dowels were parallel, whether the basket moved, whether the saw line was marked over the dowels, or whether the joint was cut inside the proper window. A photo packet and log do not make the pavement acceptable by themselves, but they preserve the facts that an inspector, engineer, agency, or owner needs when a joint later cracks, faults, spalls, or misses its intended sawcut.

This is not a pavement design, agency tolerance table, sawcut depth rule, traffic-opening approval, silica exposure-control plan, or long-term performance warranty. The plans, specifications, agency standards, approved mix, paving plan, sawcut plan, traffic-control plan, safety plan, and responsible engineer control those decisions. The purpose here is narrower: make a traceable field record before the hidden work disappears and before the paving phase is handed to the next crew or reviewer.

Define the paving handoff boundary

Start by naming exactly what is being handed over. A useful boundary might say westbound outside lane, stations 120+00 to 124+50, panel layout J-17 through J-46, transverse dowel baskets DB-17 through DB-46, longitudinal tie bars at the lane line, construction header at 124+50, and sawcut crew release at 7:40 p.m. A weak boundary says dowel baskets checked or joints sawed and leaves the next reviewer to guess which lane, which placement, and which joints were included.

The boundary should cover both the pre-placement and post-placement sides of the work. Before concrete, the record shows basket layout, anchorage, marks, bar condition, and exclusions. During placement, it notes whether baskets stayed put and whether anything in the paving operation disturbed the hardware. After placement, it connects the marked layout to actual sawcut timing, sawcut sequence, raveling, random cracks, slurry removal, and holds. Those three stages make one handoff chain.

State the exclusions in the same place. The record may exclude design verification, coring, MIT scan, pullout testing, ride testing, smoothness, concrete strength acceptance, opening to traffic, sealant installation, or adjacent-lane work. Exclusions are not evasions. They keep a basket and sawcut record from becoming an accidental acceptance of everything in the pavement.

Keep it separate from a general sawcut note

A general sawcut record can be useful for a slab or flatwork area, but a doweled concrete pavement handoff has a different risk. The sawcut is not just a groove. It must relate to the planned joint, the panel geometry, the dowel assembly below, the adjacent lane, and the load-transfer system. The finished surface may look clean while the hidden record is incomplete.

The older kind of note often says joints laid out and cut before cracking. That does not answer whether DB-24 was placed at the planned station, whether its end dowels were within the planned lane edge offset, whether the basket was anchored before the paver reached it, whether the saw crew could find the basket after cover, or whether the first sawcut missed the planned centerline. Those are the questions this record is meant to preserve.

Treat the load-transfer assembly as the center of the packet. The sawcut timing matters, but the article is not only about timing. It is about linking the layout, hardware, placement, saw marks, and finished joint evidence so the hidden steel and visible joint can be reviewed as one system.

Start with the approved basis

Collect the approved paving plan, joint layout, standard details, dowel basket schedule, dowel bar material requirements, basket anchorage requirements, tie bar details, construction joint details, sawcut plan, mix submittal, curing plan, traffic-control plan, inspection test plan, and agency or owner checklist before the crew starts placing baskets. The field record should compare work to the accepted basis. It should not create a new joint design from photographs.

The source set for this article supports that split. FHWA and CP Tech materials explain joint purpose, dowel load transfer, basket assemblies, anchorage, sawcut timing, and joint construction practice. Caltrans, WSDOT, and MnDOT manuals show how agencies frame preconstruction discussion, basket checks, joint location, placement monitoring, and sawcut inspection. NCHRP Appendix A explains misalignment categories and why sawcuts need to be located over the dowel group. None of those sources means one article can publish one tolerance or one sawcut time for every project.

When the project has a stricter rule, record against that rule. When the project has no clear rule, escalate before placement rather than writing a field note that appears to decide the matter. A handoff record is strongest when it says which document controlled each check.

Keep source documents with revision dates. A basket schedule from an early bid set can conflict with the issued-for-construction paving plan, and a sawcut plan can change after a mix or staging review. The photo record should identify the revision actually used in the lane. If a field sketch becomes the working layout for the shift, attach the sketch, name who accepted it, and keep it with the final packet.

Build the joint layout map

The layout map is the index for every photo and log entry. It should show lane, station range, panel numbers, transverse joints, longitudinal joints, construction joints, isolation joints if present, dowel basket IDs, DBI zones if used, tie bar zones, header joints, boxouts, utility conflicts, drainage inlets, edge offsets, and any joints that must line up with existing or adjacent pavement. If the project has an official layout sheet, use it. If field marks are added, identify them as field marks and keep them dated.

Good maps use both stationing and field language. A saw crew at night may need westbound lane, third joint east of inlet, panel between light pole 8 and catch basin CB-12, not only station 122+35. An inspector reviewing photos later may need the station and the joint number. Put both in the caption where practical.

Mark planned changes as changes, not as if they were always in the plan. If a basket is shifted for a boxout, a header joint moves due to a delivery interruption, an adjacent-lane joint must be matched, or a joint is held for engineer direction, the map should show the old planned location, the revised location, who approved the change, and when the change was made. That matters later because a joint that looks odd on the finished surface may be intentional, corrected, or still open.

Keep the map with the final packet. A pile of photos without a layout map becomes hard to use when every dowel basket looks similar. The map lets the owner move from joint J-31 to basket DB-31 to photos DB31-01 through DB31-08 to the sawcut time log.

Identify the load-transfer assembly

Each included load-transfer assembly needs an identity. Record whether the joint uses a full-lane dowel basket, mini-baskets in wheel paths, a dowel bar inserter, drilled and bonded dowels, header dowels, or another project-specific detail. Note the drawing, specification section, approved submittal, basket tag, heat or material certificate reference if used, coating requirement, bond-breaker basis, basket height basis, and location in the lane.

Do not rely on generic wording such as dowels installed. Dowel bars, basket rails, stakes, spacer wires, support wires, coatings, end caps, sleeves, and bond-breaking treatment may all matter to the project. If the field record only says dowel basket, it will not help if the later issue is a missing basket tag, damaged epoxy coating, wrong basket type, unanchored mini-basket, shifted edge dowel, or unlubricated bar.

The record should also distinguish load transfer from restraint. Dowels are used to transfer load across a joint while allowing joint opening and closing when properly configured. Tie bars serve different functions at longitudinal joints and can create problems if they conflict with transverse joints. The field note should not merge dowels and tie bars into one vague reinforcement line.

Photograph baskets before concrete

Before placement, photograph the basket row wide, medium, and close. The wide photo shows the lane, station marks, stringline or edge reference, adjacent joints, grade, and relation to inlets or boxouts. The medium photo shows each basket aligned with the marked joint and lane edges. The close photo shows bar condition, basket tag, rail, support, stake or pin, spacer wire condition, coating damage if visible, and any field correction.

Take the photos before the paver, trucks, labor, and concrete cover the evidence. Once the basket is hidden, an after photo of a clean sawcut cannot prove how the dowels were supported. FHWA and CP Tech sources both frame baskets as devices intended to hold dowels in position during paving, and NCHRP identifies basket placement and fastening as factors in alignment. That is the recordable fact: what was visible before cover.

Show exceptions plainly. If a basket is bent, a rail is loose, a stake missed the base, a basket sits on loose grade, a dowel coating is damaged, a basket conflicts with a utility adjustment, or a joint mark is unclear, photograph it before correction. Then photograph the correction. A final-only photo hides the decision path.

Do not make a photo stand in for a measurement you did not take. If the project requires survey checks, tape checks, coring, MIT scan, or inspector measurements, attach those records. If the record is visual only, say that. A clean photo is useful evidence, but it is not a hidden-bar measurement method.

Anchor and mark baskets

Basket anchorage needs a visible record because unanchored or poorly anchored baskets can move when concrete and paving equipment reach them. FHWA Dowel Basket Anchoring Methods warns that baskets that are not properly secured can slide, tip, pull apart, or be crushed under paving. NCHRP Appendix A similarly ties inadequate anchoring to basket deformation, movement, rotation, or extreme dowel misalignment. Agency manuals also call for checking anchorage and watching for bar movement during paving.

Photograph the anchorage pattern that the project requires. Show pins, clips, stakes, fasteners, rail locations, leave-side or approach-side placement if specified, base type, and any area where anchorage differs because of a stabilized base, thin granular layer, asphalt-treated base, bridge approach, utility patch, or restricted access. If the project requires a certain fastener spacing or number, record the count and the controlling reference rather than publishing a generic rule.

Marking matters just as much as fastening. WSDOT language calls for basket locations to be marked on the grade before the baskets are covered so the transverse sawcut can be located in the middle of the dowel bars. MnDOT says baskets are placed so dowels are parallel to grade and centerline, anchored, and marked for sawing. Those marks should appear in the photo packet before cover and in the saw crew handoff after placement.

Do not let housekeeping erase the evidence before it is transferred. Paint dots, nails, washers, station marks, lath, offsets, and shoulder references may look temporary, but they are often the only visible link between DB-31 before concrete and J-31 after concrete. If a mark must be moved, covered, or removed for paving access, record the replacement mark before the old one disappears.

Record the wire decision

Spacer wires, shipping wires, or tie wires are a project-specific decision. FHWA and CP Tech materials discuss the issue because some specifications require cutting while other guidance says leaving wires intact can help basket stability and does not necessarily hurt joint opening. Caltrans CPD 23-6 Attachment 3 gives a Caltrans-specific instruction to cut and remove temporary spacer wires after anchoring and before placement while demonstrating that bars do not move. MnDOT, in the extracted manual text, requires cutting tie wires before paving. Those examples prove variation, not a universal rule.

The field record should state the controlling requirement and show what happened. If wires remain intact, note the basis and photograph the condition. If wires are cut, photograph the basket before cutting, after cutting, and after any movement check required by the specification. If the inspector or agency representative directs a change, identify the person, time, and affected basket IDs.

Avoid writing wire cut complete without showing whether the basket remained stable afterward. The practical question is not only whether a wire was cut. It is whether the load-transfer assembly still matches the approved location and alignment when paving begins.

Confirm observed alignment

A field handoff record should describe observed alignment without pretending to be a full acceptance test. NCHRP Appendix A identifies five common dowel location or alignment categories: horizontal translation, longitudinal translation, vertical translation, horizontal skew, and vertical tilt. FHWA Concrete Pavement Joints uses similar concepts and explains that dowels are typically placed at mid-depth, parallel to the pavement surface and longitudinal axis, with the joint sawed or formed over the dowel center.

Record what the crew actually checked. Examples include basket set on survey marks, joint mark centered on basket, dowels parallel to centerline by visual check, basket height checked against approved detail, edge offset checked, anchorage complete, and no visible displacement after concrete placement at basket DB-22. If the project requires measured tolerances, include the measurement sheet or inspector log. If it does not, do not invent acceptance numbers in the caption.

Location matters because different misalignment types carry different risks. NCHRP ties longitudinal translation to embedment and load-transfer capacity, vertical translation to cover and potential spalling or loss of load-transfer efficiency, and skew or tilt to joint movement restraint. That does not mean every moderate misalignment creates immediate distress. It means the handoff record should let the responsible reviewer see what was observed before the condition became hidden.

When a hidden-bar scan, coring, or survey is required, keep the photo packet and the measurement record together. A scan without the pre-placement basket photos can miss the reason a problem occurred. Photos without the scan can miss the hidden location. Together they tell a better story.

Track lubricant and bar condition

Load-transfer bars often need a bond-breaker or lubricant treatment so the joint can move as designed. FHWA Concrete Pavement Joints and CP Tech sources discuss dowel lubrication and bond-breaking context, and agency manuals call for checking specified dowel bar lubricant. The field record should not choose the material, rate, or timing unless the project documents say so. It should show that the specified item was checked and what evidence was available.

Photograph damaged coatings, exposed steel, storage damage, mud, concrete splatter, missing end caps, or bars that look inconsistent with the approved submittal. Separate pre-existing delivery damage from damage caused during handling or placement. If coating repair is performed, show before, repair material reference, after, and inspector acceptance if required.

Do not overstate the result. A photo can show visible coating condition and a field-applied bond-breaker at the time of observation. It does not prove coating thickness, corrosion resistance, pullout behavior, or long-term load-transfer performance unless the project has a separate test or acceptance record.

Protect baskets during paving

The handoff record should continue while concrete is placed over the baskets. FHWA anchoring guidance warns that direct dumping onto baskets can tip, deform, or dislodge them unless performed carefully. CP Tech sources note problems from pavers catching baskets near slab edges, and MnDOT calls for extra care when placing concrete over basket assemblies and vibrating that area. WSDOT tells inspectors to watch for anything in the paving operation that moves the bars.

Record truck discharge method, concrete head at the paver, labor walking or pulling concrete around baskets, vibrator use near baskets, and any event that could move hardware. The goal is not to narrate every shovel of concrete. The goal is to preserve notable conditions: basket DB-18 stayed visible until covered, no direct load dumped on DB-18, inspector observed no movement, or DB-21 shifted during truck discharge and was held for correction.

If a basket moves, stop the vague language. Write which basket moved, how it was found, who was notified, what correction was made, whether paving stopped, and what follow-up record proves the correction. Caltrans CPD 23-6, as agency-specific context, includes stop-paving language for noncompliant dowel bar installation. Your project procedure may differ, but the field record should never bury movement inside normal placement notes.

Also record the absence of unusual events when that absence matters. A simple note such as no direct dumping onto DB-14 through DB-21, no visible basket displacement observed at paver pass, and saw marks preserved for handoff can be useful later. It tells the reviewer the crew watched the risk points instead of only taking static photos before placement.

Mark sawcut lines over dowels

After placement, the saw crew needs the same joint logic the basket crew used before cover. NCHRP Appendix A says baskets must be placed on survey marks and joints clearly marked so sawcuts are made at proper locations. FHWA Concrete Pavement Joints says joint locations must be marked accurately before sawing so panel dimensions are as designed and sawed joints are located over the midpoints of dowels and tie bars. WSDOT says basket locations need to be marked before cover to correctly locate the transverse joint sawcut in the middle of the dowel bars.

Record the sawcut marks before the saw starts. Photograph shoulder marks, nails and washers, paint marks, stringline references, station marks, adjacent-lane joint references, existing lane marks, and any magnetic or locating device used to establish the line. If marks are damaged by rain, curing compound, slurry, traffic, foot traffic, or night conditions, note how they were restored.

The sawcut line should be tied to the basket ID. A caption like J-32 saw mark over DB-32, westbound outside lane, looking north, first cut sequence 3, is much stronger than saw mark. Later, if J-32 cracks outside the sawcut or shows spalling, the owner can review the exact evidence.

Record the sawcut timing window

Sawcut timing is a recordable window, not a universal clock. FHWA Early-Entry Sawing says the goal is to saw neither too soon, which can cause raveling, nor too late, which can result in random cracking. CP Tech optimum joint performance describes the same practical window: concrete must be strong enough for sawing without excessive raveling, and the risk of random cracking increases as sawing is delayed. WSDOT says the contractor must determine the most suitable schedule for the job because curing conditions vary.

Your log should include placement start, placement end, finishing completion if used by the project, curing application, ambient temperature, wind or weather note, concrete temperature if recorded, saw equipment type, first saw mobilization, first control cut, joint sequence, delays, second saw or sealant reservoir work if applicable, and visible result. If the project uses maturity, strength checks, scratch checks, trial cuts, or another approved basis, attach that evidence.

Do not write sawed on time without saying what on time means. Better language is saw crew released by foreman at 6:35 p.m. based on approved sawcut plan and field trial cut at J-12; first transverse control cut J-12 at 6:48 p.m.; no visible raveling beyond accepted field sample; random crack check at 8:20 p.m. found none in panels J-10 through J-18. That is a record a reviewer can test against the plan.

Night work deserves special attention. If sawing occurs after dark, note lighting, crew handoff, marked joint visibility, inspector observation, and random-crack checks. WSDOT specifically notes that much sawing may be done at night and that the inspector needs to examine sawcuts and watch for random cracks. The record should make night conditions visible.

Capture depth without designing it

Sawcut depth belongs to the plans and specifications. FHWA Concrete Pavement Joints and FHWA Early-Entry Sawing explain why depth matters, and they discuss common conventional and early-entry concepts. They do not turn one field article into a design table for every pavement. The record should capture the specified depth basis, saw type, blade setting, depth checks if required, and any inspector observation without publishing a universal requirement.

A practical record can show the saw, blade, depth gauge, trial cut, inspector check, slurry removal, and a photo of the cut after cleaning. If the project requires multiple depths because of variable pavement thickness, crown, stabilized base, longitudinal joint, transverse joint, or early-entry method, the log should show which depth rule applied to which joint group.

Also record what was not done. If no depth check was taken by the field team, do not imply one. If depth was checked by another party, identify that record. If the saw crew stopped because of raveling, blade wear, hard aggregate, dust, water supply loss, lighting, equipment failure, or cracking risk, document the hold and the restarted sequence.

Check activation and cracking

The first sawcut is not the end of the record. The handoff should include a follow-up look for joint activation, random cracks, raveling, edge damage, slurry residue, and cuts that do not align with marks. MnDOT warns that if the sawed plane is off center from the dowel assembly, a secondary crack can occur and load transfer can be lost. WSDOT and Caltrans both frame post-saw inspection as part of concrete pavement inspection practice.

Record the time of the follow-up check. A check one hour after cutting is not the same as a check the next morning. If control joints open and intermediate joints remain uncut, note the saw plan basis and who accepted the sequence. If random cracks appear, map them by panel and station instead of writing cracking observed.

Raveling should be photographed with context. A close-up alone can make a small chip look severe or a severe edge look isolated. Take a wide photo showing the joint ID, a medium photo showing the affected length, and a close photo showing the edge condition. Then state whether the condition was accepted, repaired, monitored, or held.

Cleaning belongs in the follow-up record too. Slurry, paste, debris, or standing water left in a fresh cut can hide the condition of the joint and affect later sealing work. If the specification requires immediate removal, record the cleaning step and the post-cleaning photo. If cleaning is assigned to another crew, name that handoff rather than leaving the joint condition ambiguous.

Handle DBI work separately

A dowel bar inserter record is related but not identical to a basket record. DBI work has no pre-placed basket to photograph, so the record should show the approved DBI basis, bar material, bar feed, insertion equipment, spacing and alignment checks, surface correction after insertion, probing or scan requirements, joint marking method, and sawcut location over implanted bars.

FHWA Concrete Pavement Joints states that dowels and tie bars can be pre-placed in baskets or mechanically inserted, and it emphasizes proper positioning and alignment. MnDOT says contractor personnel should perform periodic probing for DBI alignment and depth, agency personnel should spot check, and doweled joints must be carefully marked for sawcutting. WSDOT tells inspectors to check DBI spacing and alignment and ensure consolidation after insertion.

Do not mix DBI evidence into a basket checklist without changing the fields. A DBI record needs equipment checks and post-insertion verification. A basket record needs basket condition and anchorage before cover. If a project uses both methods in different lanes, create separate sections in the packet.

Coordinate adjacent lanes

Concrete pavement joints often need to relate to adjacent lanes, existing joints, shoulders, ramps, inlets, or construction headers. FHWA Concrete Pavement Joints says transverse joint locations should be matched across adjacent lanes unless the panels are isolated. WSDOT says joints should match transverse joints on adjacent concrete pavement. MnDOT says joint layouts at intersections and other special areas should be made available to the saw crew.

The record should show adjacent-lane reference marks before sawing. If the new lane must match working joints in an existing lane, photograph the existing joint marks and the transferred marks. If the joint is intentionally isolated or offset, record the approved detail and exclusion. If tie bars are near transverse dowels, note the approved layout and any hold for interference review.

Construction headers need their own entries. Show header location, dowel or tie detail, end protection, consolidation around bars, and how the next placement will locate the continuation joint. A header can become the place where the handoff fails because it looks temporary even though it controls the next paving operation.

Close corrections and holds

A good handoff record does not hide problems. It turns them into closed items or clear holds. Common correction items include unanchored baskets, unclear saw marks, damaged bar coating, wrong basket ID, basket shifted during placement, missing bond-breaker evidence, raveled trial cut, saw equipment delay, random crack, saw line not matching mark, slurry left in the joint, or adjacent-lane mismatch.

For each correction, use the same chain: item ID, condition, source of requirement, responsible party, correction, after photo, reviewer, and release status. Do not let the correction live only in a text message or crew memory. If DB-19 was re-anchored, show DB-19 before, re-anchored, and accepted. If J-19 sawcut was delayed due to raveling, show the trial cut, delay note, restarted time, and final edge condition.

For each hold, say what is blocked. Some holds block paving, some block sawcut release, some block next-lane work, some block traffic opening, and some only block final paperwork. A hold that says review later is weaker than hold J-33 and DB-33 from next-lane paving until engineer reviews basket shift and sawcut location.

Close the packet with a final decision. Accepted with exceptions is acceptable when the exceptions are explicit. Accepted without naming exceptions is risky when open conditions remain.

Inspection table

Use a compact table so the foreman, inspector, saw crew, engineer, and owner reviewer look at the same paving handoff evidence.

Paving handoff checklist

Run this checklist before accepting a dowel basket and sawcut packet for a concrete paving phase.

• Paving lane, station limits, panel IDs, joint IDs, basket IDs, and exclusions are named.
• Approved joint layout, dowel schedule, basket detail, sawcut plan, and inspection test plan are attached or referenced.
• Each load-transfer assembly is identified by basket, DBI zone, drilled dowel, header dowel, or other approved method.
• Pre-placement photos show the basket row, joint marks, lane references, base condition, edge offsets, and conflicts.
• Close photos show basket tag or ID, dowel condition, coating damage if visible, rail condition, stake or fastener, and wire condition.
• Basket anchorage is photographed and tied to the controlling requirement.
• Spacer wire, shipping wire, or tie wire handling is recorded against the project requirement.
• Dowel lubricant, bond-breaker, coating repair, and delivery damage are recorded where applicable.
• Sawcut marks are photographed before cover or before sawing and tied to basket or joint IDs.
• Paving observations note whether concrete placement, paver head, labor, or vibration moved baskets or bars.
• Sawcut timing log includes placement time, saw crew release, first cut, sequence, delays, and weather or condition notes used by the project.
• Sawcut depth evidence is recorded only against the approved basis and does not invent a generic rule.
• Raveling, random cracking, slurry residue, missed marks, and joint activation are checked and photographed.
• Corrections include before photo, action, responsible party, after photo, and reviewer decision.
• Open holds state what is blocked: paving, sawing, next-lane work, traffic opening, sealing, or final paperwork.
• Final release names the accepted joints, baskets, sawcuts, exceptions, safety limits, and records still controlled by others.

Weak versus strong record

Weak record: Dowel baskets installed. Joints sawed. No issues.

That note does not name the lane, station range, joint IDs, basket IDs, approved basis, anchorage, wire decision, saw marks, placement time, first saw time, raveling, random cracking, corrections, or exclusions. It may be true in the moment, but it will not help when a joint shows distress later or when the next lane crew needs to match the same layout.

Strong record: Westbound outside lane, stations 120+00 to 124+50, panels J-17 through J-46, was reviewed for paving handoff on June 9, 2026. Photos WB-001 through WB-006 show approved layout sheet P-14, field markup, and station references. Photos WB-007 through WB-036 show dowel baskets DB-17 through DB-46 placed at marked transverse joint locations, staked per project detail, with spacer wire handling recorded against specification section 40. Photos WB-037 through WB-044 show coating touch-up at DB-22 and re-anchorage at DB-31 before concrete.

The same record says placement began at 3:10 p.m. and ended at 5:02 p.m. The saw crew accepted marks at 6:20 p.m. after a trial cut. First control cut J-22 was made at 6:38 p.m., followed by every fourth joint until 7:10 p.m., then intermediate joints per the approved sequence. Photos WB-045 through WB-072 show saw marks, first cut, representative depth check by inspector, raveling sample, and random-crack check at 9:05 p.m. DB-31 remained a hold until the engineer accepted the re-anchorage record. Traffic opening was excluded from this packet.

The strong record works because it connects the buried work to the visible joint and the final decision. It does not need dramatic language. It needs enough specific evidence for another reviewer to find the same joint and understand what was accepted.

Common mistakes

The first mistake is taking only after photos of sawcuts. After photos show the surface, not the basket layout. Keep the pre-placement basket photos, marked joint photos, and sawcut photos together so the hidden and visible work stay connected.

The second mistake is using one basket photo for a whole lane. Representative photos may be allowed by some procedures, but a serious handoff should identify each included basket or clearly state the accepted sampling limit. If DB-29 was not photographed, do not let DB-25 stand in for it unless the reviewer accepts that approach.

The third mistake is treating agency examples as universal rules. Caltrans, WSDOT, and MnDOT sources are useful because they show real inspection practices, but they do not control every project. The public record should say project requirement, not internet requirement.

The fourth mistake is recording sawed before cracking without any time context. Sawcut timing depends on concrete strength gain, weather, slab thickness, base friction, saw type, equipment, crew availability, and the approved plan. Record the evidence the crew used, the first cut time, the sequence, and what was seen afterward.

The fifth mistake is hiding movement. If a basket shifts during placement, it is better to document the hold and correction than to leave a blank spot in the packet. A missing record can look worse than a well-managed correction.

Photo index and file names

Photo file names should make the packet searchable. A useful pattern is lane, joint or basket ID, condition, and sequence: WB-J22-DB22-before-cover-001, WB-J22-DB22-anchor-close-002, WB-J22-saw-mark-003, WB-J22-first-cut-004, WB-J22-raveling-check-005, WB-J22-final-release-006. The exact pattern matters less than consistency.

Each caption should answer what, where, when, and why. Example: WB outside lane, station 122+35, DB-22, basket anchored at joint mark before concrete, looking east, June 9, 2026. A caption that says dowel basket is not enough if the lane has thirty nearly identical baskets.

Keep wide, medium, and close photos in order. The wide photo locates the item in the lane. The medium photo shows relation to joint marks, edge of pavement, adjacent lane, or boxout. The close photo shows basket hardware, anchorage, wire condition, coating, sawcut, raveling, or repair. A close-up without context becomes hard to defend.

If the owner platform renames files, upload a photo schedule with the packet. The schedule should cross-reference platform file name, original file name, joint ID, basket ID, station, checklist item, and exception status. The record should survive after the phone, tablet, or messaging thread disappears.

Questions that come up

Does every basket need a photo? If the handoff is meant to prove each included load-transfer assembly, each basket or DBI zone should have identifiable evidence unless the owner, agency, or reviewer accepts a sampling method. If sampling is used, write the sampling limit plainly.

Can a visual record prove dowel alignment? No. It can show observed placement, marks, basket condition, and visible alignment before cover. It cannot prove hidden alignment after paving unless paired with the required measurement, scan, coring, probing, or acceptance test.

Should sawcut timing be recorded by clock time or maturity? Record what the project requires. Clock time alone may not explain changing temperature, wind, mix behavior, curing, or equipment conditions. If maturity, strength, scratch test, trial cut, or inspector judgment is part of the accepted method, include it.

Do tie wires always need to be cut? No universal answer belongs in this article. Some agencies or specifications require cutting, while other guidance discusses leaving wires intact for basket stability. Record the project requirement, what was done, and whether the basket stayed stable.

Does this replace coring or MIT scan? No. It supports those records by showing what was visible before cover and what happened during placement and sawing. If the specification requires hidden-bar verification, attach that verification to the handoff packet.

What not to claim

Do not write that dowel alignment meets tolerance unless the required measurement or authorized reviewer supports that statement. A photo can support the record, but it is not a full alignment acceptance test.

Do not write that the sawcut depth is correct unless the required depth check was performed and recorded by the responsible party. If the article, crew, or inspector did not check depth, write that the cut was visually observed and identify the separate depth record if one exists.

Do not write that the pavement is ready for traffic unless the traffic-opening requirements are satisfied under the controlling documents. Sawcut completion, joint activation, concrete strength, curing, sealing, traffic control, and owner or agency approval may be separate gates.

Do not write that load transfer is assured. Dowel baskets and sawcuts support load-transfer function when designed, placed, and accepted correctly, but field photos do not guarantee long-term performance, bearing stress, aggregate interlock, faulting resistance, or ride quality.

Do not write that silica compliance is satisfied because sawcut photos exist. OSHA 29 CFR 1926.1153 includes specified exposure control methods, competent-person duties, training, and recordkeeping. The employer safety program and site-specific controls decide compliance, not a handoff checklist.

Compliance and safety limits

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

Do not use this checklist to choose dowel size, basket height, joint spacing, sawcut depth, sawcut timing, concrete opening strength, cure method, joint sealant, traffic-control setup, silica controls, or repair method. Those choices belong to qualified personnel using the controlling documents.

Concrete sawing, dowel drilling, working near pavers, working at night, working around traffic, lifting baskets, cutting wires, entering fresh concrete work zones, and cleaning slurry can create safety hazards. OSHA silica requirements, traffic-control plans, equipment manuals, employer safety procedures, and competent supervision control those activities.

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 handoff record does not make uncertain work look certain. It makes the uncertainty visible enough to manage.

Sources checked

• FHWA, Dowel Basket Anchoring Methods: Best Practices for Jointed Concrete PavementsUsed for basket anchoring, sliding, tipping, basket movement during paving, tie or shipping wire discussion, and avoiding damaging concrete discharge onto baskets.
• FHWA Technical Advisory T 5040.30, Concrete Pavement JointsUsed for joint purpose, load transfer, dowel placement, tie bar coordination, sawcut timing and depth context, joint location marking, and construction-phase controls.
• FHWA, Early-Entry Sawing of Portland Cement Concrete PavementsUsed for the sawing window, raveling risk, random-crack risk, early-entry versus conventional saw context, and why timing evidence belongs in the record.
• National Concrete Pavement Technology Center, Guide to Dowel Load Transfer Systems for Jointed Concrete Roadway PavementsUsed for dowel load-transfer purpose, basket assembly function, dowel location variance, alignment, basket height, basket anchoring, and tie wire context.
• National Concrete Pavement Technology Center, Guide for Optimum Joint Performance of Concrete PavementsUsed for joint deterioration, sawcut raveling, sawing window, equipment condition, joint water and debris context, and risk of delayed sawing.
• National Concrete Pavement Technology Center, Dowel Load Transfer Systems for Jointed Concrete Roadway Pavements Tech BriefUsed for dowel basket assemblies, embedment and placement variance, basket height, basket anchoring, stake count context, and tie wire recommendation context.
• NCHRP Report 637 Appendix A, Guidelines for Dowel Alignment in Concrete PavementsUsed for dowel misalignment categories, basket placement, displacement during paving, sawcut location over baskets, and performance effects.
• Caltrans Construction Manual, Section 4-40 Concrete PavementUsed for preconstruction discussion, certificates, basket anchorage spot checks, locating contraction joints and bars, monitoring placement to sawcut schedule, coring context, and inspection levels.
• Caltrans CPD 23-6 Attachment 3, Dowel Bar PlacementUsed as agency-specific context for dowel placement tolerance categories, basket method language, anchoring, spacer wire handling, and noncompliant installation response.
• WSDOT Construction Manual, Chapter 5Used for inspector checklist items, dowel mid-depth basket location, bar movement, DBI checks, sawcut depth, transverse-joint layout, basket marks before cover, and night sawing.
• MnDOT Concrete Manual, Chapter 6Used for basket placement parallel to grade and centerline, anchorage, saw crew layout, dowel load transfer, basket movement, DBI checks, saw directly over dowel centers, and timely sawcut sequence.
• NRMCA CIP 6, Joints in Concrete Slabs on GradeUsed for general joint purpose, planned cracks, contraction and construction joint basics, joint planning, timing, raveling, and uncontrolled cracking.
• OSHA, 29 CFR 1926.1153 Respirable crystalline silicaUsed for safety boundaries around concrete sawing, dowel drilling, wet methods, dust collection, competent-person, training, and exposure record context.

Related guides