Curb ramp punch-walk photo record

Direct answer

A curb ramp punch-walk photo record should prove the approved basis, exact ramp location, ramp type, crosswalk or pedestrian route served, existing tie-ins, form layout, landing slopes, ramp run, gutter transition, grade breaks, detectable warning panel, joint layout, sawcut edges, concrete placement, curing, temporary protection, open corrections, and the limited release status before the accessibility punch walk or pedestrian reopening decision.

The record matters because a curb ramp can look finished while the evidence needed for review is already gone. Forms may be removed, saw marks may be covered, the detectable warning panel may be dirty or hidden by barricades, and the gutter transition may be paved before the field team records how the landing, ramp, street, and sidewalk connect.

This article is documentation guidance. It is not ADA design, PROWAG legal interpretation, survey acceptance, detectable warning product approval, temporary pedestrian access route approval, traffic-control approval, sawcut repair method, trip-hazard abatement plan, final accessibility certification, or permission to open a pedestrian route. Approved drawings, specifications, agency standards, owner requirements, safety plans, traffic-control plans, inspectors, engineers, and responsible officials control those decisions.

The practical output is a dated answer packet. It should let a superintendent, inspector, accessibility consultant, owner representative, or repair crew see what was present before the punch walk without relying on memory, text messages, or a later photo taken after protection and markings changed.

What this record covers

Use this record for a concrete sidewalk curb ramp, landing, blended transition, island passageway, driveway crossing, shared-use path connection, pedestrian refuge island, or site sidewalk tie-in where the work will be reviewed before an accessibility punch walk. It fits new work, alteration work, phased replacement, utility restoration, and curb-return repair when a photo packet needs to preserve the field condition.

The packet should track what is visible and measurable in the field: station or address, ramp type, sidewalk or crosswalk served, tie-in surfaces, ramp run, landing, flare or returned side, gutter or street transition, detectable warning panel, joints, edges, covers, obstructions, curing, protection, and holds. It should also show what is excluded from the release.

Do not let the packet become a private accessibility verdict. The field record helps the team compare the visible work with the approved basis and preserve evidence for the person authorized to accept or reject the facility. That is different from deciding design compliance from a few photos.

A good packet also keeps concrete issues separate from adjacent discipline issues. The ramp may need signal work, striping, sign relocation, drainage review, asphalt patching, landscape restoration, or a temporary-route adjustment. The concrete photo record should name those interfaces without pretending to own them.

Define the punch-walk boundary

Start with a boundary that another person can find without calling the crew. A strong boundary might say: northwest corner of Market Street and 4th Avenue, curb ramp CR-4N, single-direction ramp serving the east crosswalk, landing against existing sidewalk panel S-18, detectable warning panel DWS-4N, sawcut tie-in along existing walk joint, and release limited to concrete photo record before punch walk.

State whether the record includes the landing only, the ramp and gutter transition, the full curb return, the island passageway, the driveway crossing, or the temporary pedestrian route around the work. If the crosswalk striping, pedestrian signal, sign, drainage inlet, pavement patch, or landscape restoration remains outside the release, name that exclusion.

A precise boundary keeps the team from arguing later over what was reviewed. It also prevents one ready-looking photo from being used as a pass for adjacent work that was not measured, photographed, or released.

The boundary should include time as well as location. Record whether the photos were taken before placement, after finishing, after curing protection was installed, after corrections, or immediately before the punch walk. A ramp can change quickly when barricades move, mud tracks cross the panel, or an adjacent pavement patch is placed.

Start with approved basis

Attach or cite the plan sheet, curb ramp detail, standard plan, site civil detail, crosswalk plan, accessible route plan, survey staking, field revision, product submittal, inspection form, and agency instruction that control the work. The record should show the basis before it shows the finished concrete.

PROWAG, ADA Standards, state DOT plans, and state DOT specifications all separate geometry, surfaces, detectable warnings, and pedestrian access from casual field preference. A photo packet should respect that hierarchy. It can say which detail was used and what was observed. It should not invent a ramp type, slope target, panel location, or exception from memory.

If the approved basis changed, record the change. Existing sidewalk may not meet proposed grades, a utility cover may conflict with a landing, a drainage inlet may affect the gutter transition, or a crosswalk line may be shifted. The packet should show the conflict, the direction received, and the condition being presented for punch-walk review.

Do not rely on a generic standard detail if the project has a revised sheet, local detail, or site-specific clarification. Put the controlling reference in the record title or first page so later reviewers do not have to guess which rule set the crew thought it was building.

Identify ramp type

Name the curb ramp type in the same language used by the project documents. Perpendicular curb ramp, parallel curb ramp, single-direction ramp, combination ramp, blended transition, driveway crossing, raised crossing, and island cut-through do not create the same photo needs. The packet should not just say ramp.

PROWAG defines a curb ramp as a sloped connection cut through or built up to a curb, and it separates perpendicular and parallel curb ramps from blended transitions. WSDOT and Caltrans standard plans also show ramp types and details that depend on crossing direction, landing position, gutter transition, curb return, and detectable warning location.

Photograph a wide view showing the crossing direction and pedestrian path before closeups begin. The photo set should make it obvious whether the ramp serves one crosswalk, two crosswalks, a driveway, a refuge island, a shared-use path, or a site sidewalk connection.

Ramp type also controls the language of the hold. A missing top landing on a perpendicular ramp, a bottom landing concern on a parallel ramp, a blended transition question, or an island cut-through issue should not all be described as ramp slope problem. Specific terms lead to cleaner corrections.

Record existing tie-ins

Existing sidewalk panels, curb faces, gutter pans, asphalt edges, concrete pavement, driveway aprons, utility covers, retaining curbs, landscaping, building entrances, and signal equipment can control the final tie-in. Photograph the existing conditions before demolition or sawcutting, then again when forms are set against them.

Caltrans construction guidance tells inspectors to compare contract details with field conditions, check existing elevations against planned grades when new curbs or sidewalks join existing facilities, and avoid using existing pavement surfaces directly as the grade line for new curb work. That is a useful distinction for this packet: existing work is evidence, not automatic authority.

When an existing tie-in creates a slope, width, ponding, trip-lip, or cover conflict, the photo record should show the problem before it is hidden by fresh concrete. The next note should be the direction received from the person authorized to handle the change.

Existing work should be photographed with enough context to show whether it is inside or outside the release. If a cracked sidewalk panel is adjacent but not part of the ramp replacement, label it excluded. If the ramp must match it, label it as a tie-in constraint.

Capture layout before concrete

Before concrete, record the layout marks that define the curb ramp. Include stationing, control points, grade stakes, stringline, paint marks, sawcut limits, form line, landing outline, ramp centerline, crosswalk edge if known, detectable warning panel outline, and any utility cover or drainage structure that affects the work.

Caltrans guidance calls for checking layout as staked, including gutter depressions, curb ramps, and driveways, and verifying that grades will support the finished slope requirements. WSDOT standard plans show ramp geometry tied to sidewalk width, crosswalk containment, grade breaks, and adjacent curb or gutter details. Those points make layout a punch-walk record item.

A layout photo should include a reference scale or known feature. Paint marks on concrete are easy to misread later unless the image also shows the curb face, back of walk, crosswalk direction, adjacent panel, or plan sheet reference.

Include the rejected layout when a layout was changed. If the first line would have put the panel outside the crossing, run the landing into an existing cover, or create an awkward gutter transition, the correction story is stronger when the original condition and revised layout are both visible.

Check forms and subgrade

Forms and subgrade are often the last visible proof that the ramp was set up to hit the intended lines and slopes. Photograph form material, bracing, stakes, top edge, side alignment, form depth, subgrade elevation, soft spots, wetting, compaction condition, voids under forms, and any correction before placement starts.

Caltrans Section 73 requires forms to be set to required alignment, grade, and dimensions, to be smooth and rigid, and to have enough stakes, clamps, spreaders, and braces to resist fresh concrete. WSDOT Section 8-14 requires sidewalk forms to extend full depth, stay in horizontal and vertical alignment, and rest on a shaped, compacted foundation.

Do not use a finished-ramp photo to replace the form record. A landing that is slightly off, a flare that wanders, or a panel that is crowded by a utility cover may start as a form layout problem. The packet should preserve the condition before concrete makes correction harder.

The form photo should also show access for finishing and panel placement. A form that blocks proper tool work, leaves no room to set the detectable warning panel, or requires workers to stand on a protected pedestrian route can create quality and safety problems even if the final edge looks straight.

Document landing geometry

The landing deserves its own photo and measurement sequence. Record the landing location, dimensions, approach route, direction of travel, adjacent sidewalk tie-in, slope readings, grade breaks, returned curb or flare relationship, and whether the landing serves one ramp or multiple ramps.

PROWAG requires a landing in specific curb ramp conditions and gives slope, width, length, and direction criteria for curb ramp landings. WSDOT similarly requires landings at the top of perpendicular curb ramps and the bottom of parallel curb ramps, with a 4-foot minimum length and width in its design manual. The project documents decide which rule set applies.

For the photo packet, the important point is not to certify the landing from memory. Show the landing plane, the measuring orientation, and the surfaces that connect to it. If the landing is being held because an existing walk, pole base, cover, or curb return affects slope or clear space, mark the hold.

Landings are also easy to confuse with nearby sidewalk panels. Label the actual landing limits on the photo or sketch so the reviewer can see which area was measured. If the landing overlaps a sidewalk panel or shared path, show that overlap in the wide view.

Record ramp run and grade breaks

Record the ramp run separately from the landing. Show running-slope direction, cross-slope direction, top grade break, bottom grade break, side flare or returned side, curb face, gutter transition, and path of travel. A single photo from above rarely proves how the ramp connects to the street.

PROWAG requires grade breaks at the top and bottom of curb ramp runs to be perpendicular to the direction of the ramp run and flush where surface slopes meet. WSDOT uses similar language and calls for planar vertical alignment within curb ramp runs, landings, and gutter areas inside the pedestrian access route.

Photograph a straightedge, level, or measurement tool only if it adds clarity. The tool should be shown in the direction being checked. A level turned diagonally across a ramp does not prove the same thing as a level placed along the travel direction or across the run.

Keep the grade-break photo low and wide enough to show both planes. Closeups of a line in concrete may hide whether the two slopes are flush, whether the break is perpendicular to travel, and whether a detectable warning panel or gutter transition crowds the break.

Keep gutter transition visible

The curb ramp does not stop at the back of curb. The record should show the gutter, street, pavement edge, curb depression, drainage path, and bottom transition because those surfaces can affect usability, ponding, and punch-list findings. Take wide photos before vehicles, cones, or paving equipment block the view.

ADA Standards address counter slope at adjoining gutters and road surfaces immediately adjacent to curb ramps. PROWAG addresses changes of grade at gutters and streets adjacent to curb ramps and blended transitions. WSDOT warns that surface runoff can flood the lower end of a curb ramp and says drainage structures should not be located in the pedestrian access route.

The field packet should not redesign drainage. It should show whether the street transition, gutter pan, inlet, pavement patch, or ponding concern was visible and whether a hold was routed to the responsible design or inspection authority.

Photograph after rain or wash water only when that condition is available and safe to observe. Standing water can help document a concern, but the absence of water during a dry check should not be turned into proof that drainage is accepted.

Verify panel basis

Detectable warning panels need source evidence before closeup photos. Record the approved product or material basis, submittal status if available, panel type, color or contrast basis, cast-in-place or surface-applied condition, manufacturer instructions, and whether the installation is permanent or temporary work-zone use.

Caltrans specifications require detectable warning surfaces to be on the Authorized Material List and to match the specified yellow color. Caltrans also requires a 5-year manufacturer replacement warranty for prefabricated detectable warning surfaces. WSDOT specifications require detectable warning surfaces to be located as shown in the plans and installed by the applicable method.

The photo packet should not approve a product that the project has not approved. A useful note says the panel shown is the product submitted for this location, or it says product approval not verified and held for inspector or owner review.

If the panel is cut, the record should show the cut edges and the reason for the cut. A cut panel at a return, island, or constrained sidewalk may be correct under the approved detail, but it can also reveal a layout conflict. The photo should not hide that choice.

Photograph panel location

For the detectable warning panel, show more than domes. Take a wide view showing the crossing, curb, ramp, landing, and back of curb. Then take medium views showing panel width, offset from the curb or pavement edge, relation to the grade break, relation to the ramp run, and relation to any island or driveway condition.

PROWAG calls for detectable warning surfaces at curb ramps and blended transitions where required, describes dome geometry and contrast, and places the surface according to ramp type and grade break conditions. WSDOT Standard Plan F-45.10 gives plan-specific placement examples, including full-width coverage and alignment of dome rows with direction of travel.

Do not crop the photo so tightly that no one can tell where the panel sits. Closeups of truncated domes help show damage, cuts, gaps, and dirt, but they do not prove the panel is at the right location or tied to the correct crossing.

Panel orientation is worth a separate image when the dome rows are directional or the plan calls for alignment with direction of travel. Include the travel arrow, curb face, or crossing direction in the frame so the orientation can be checked later.

Record joints and sawcuts

Joint layout and sawcut edges should be visible before the punch walk. Photograph expansion joints, contraction joints, construction joints, sawcut tie-ins, panel boundaries, joint filler, curb-return joints, adjacent sidewalk joints, and any sawcut that separates the ramp work from existing concrete.

Caltrans Section 73 requires contraction and expansion joints in concrete curbs and sidewalks, and Section 73-10 addresses sawcutting true lines before removing portions of existing curbs, sidewalks, curb ramps, driveways, or gutter depressions. WSDOT Section 8-14 requires sidewalk expansion and contraction joints as shown in the plans and aligns sidewalk expansion joints with adjacent curb spacing where applicable.

The packet should show whether sawcut edges are clean, spalled, undermined, held for repair, or excluded from the ramp release. Do not let a later patch or sealant hide a questionable edge before it is recorded.

Joint photos should distinguish planned joints from damage. A neat contraction joint, an expansion joint with filler, a construction joint, and a cracked tie-in edge have different meanings. Label the joint type so a punch-list reviewer does not treat every line as the same condition.

Coordinate covers and appurtenances

Utility covers, junction boxes, signal pole bases, pull boxes, drainage inlets, valve boxes, sign posts, bollards, and landscaping edges can turn an otherwise clean ramp into a hold. Photograph them in relation to the ramp run, landing, gutter transition, and pedestrian access route.

WSDOT design guidance says gratings, access covers, utility objects, and other appurtenances should not be located on curb ramps, landings, or gutters within the pedestrian access route. WSDOT Standard Plan F-40.16 also says not to place gratings, junction boxes, access covers, or similar appurtenances on any part of the curb ramp or landing or in the depressed curb and gutter where the landing connects to the roadway.

If a cover or pole base is already there, the photo packet should not pretend it is harmless. Record the condition, identify the responsible discipline, and mark whether the ramp is held, partially released, or released only for concrete documentation pending accessibility review.

Show both the object and its offset from the walking path. A closeup of a cover lid does not show whether it is on the ramp run, in the landing, in the gutter transition, or outside the pedestrian route. The wide view is what makes the conflict understandable.

Document concrete placement

During placement, photograph the concrete source record if required, placement sequence, form stability, subgrade condition, consolidation, strikeoff, detectable warning panel installation timing, joint filler position, finishing tools, and any rejected or held concrete. Small curb ramp placements can still create large punch-list disputes.

Caltrans construction guidance tells inspectors to observe placement, record rejected concrete, verify the concrete is not segregating, and stop operations if patching with grout or mortar is needed because the placement operation should be corrected. WSDOT Section 8-14 requires concrete in sidewalks and curb ramps to be placed in forms and struck off with an approved straightedge.

The useful photo is not only the finished broom texture. Show what happened while the work was still workable, especially at the bottom grade break, panel edges, return curb, landing tie-in, and sawcut boundary.

If placement pauses, record the pause condition. Cold edges, delayed finishing, rain covers, rejected loads, or a panel that had to be reset can become important later. The photo record should show the field event before everyone remembers it differently.

Capture finish and surface checks

After finishing, record broom direction, surface texture, trowel marks, water addition, straightedge checks where used, panel edges, ramp face, landing face, gutter interface, and any repair. For pedestrian surfaces, the finished plane can be more important than the surface appearance.

Caltrans Section 73 requires broom finish on sidewalks, gutter depressions, curb ramps, and driveways, with broom finish perpendicular to the path of travel on pedestrian surfaces. It also says the finished surface must not vary more than 0.02 foot from a 10-foot straightedge except at grade changes. WSDOT Section 8-14 also calls for brushed walking surfaces with strokes perpendicular to travel direction.

If the surface is rough, slick, uneven, chipped, contaminated, or visibly ponded, record the condition without burying it in a pass note. A punch walk needs the defect location, not a general claim that concrete finish was acceptable.

Surface checks should include edges where the ramp meets older work. The center of the ramp may look clean while the sawcut tie-in, back-of-curb edge, panel perimeter, or gutter joint creates the complaint.

Record curing and protection

Curing and protection evidence should cover timing, method, exposed surfaces, barricades, weather protection, foot traffic controls, vehicle protection, and whether adjacent work will disturb the ramp. Photograph the protection at the time the work is left for the day and again before punch-walk review.

Caltrans Section 73 requires exposed concrete faces to be completely coated with curing compound. WSDOT Section 8-14 requires concrete sidewalks to be cured for at least 72 hours by approved methods and excludes pedestrian and vehicle traffic during the curing period, with vehicle exclusion extended as directed by the engineer.

A curb ramp may be small enough that crews walk across it without thinking. The record should show whether the route was blocked, whether alternative access was provided under the controlling plan, and whether early traffic or damage created a hold.

Curing photos also help separate construction damage from later damage. If the ramp was barricaded, protected, and clean at handoff, the record gives the team a starting point for any later footprint, chip, stain, or edge damage investigation.

Separate temporary pedestrian access

Temporary pedestrian access belongs in the photo record because it may affect whether the area can be approached safely during punch work. It should not be treated as the same approval as the finished ramp. Photograph barricades, channelizing devices, temporary signs, temporary ramps, accessible detour surfaces, decision points, and any gaps or obstructions.

PROWAG addresses alternate pedestrian access routes when a pedestrian circulation path is temporarily closed by construction or similar conditions. Caltrans construction guidance points inspectors to temporary pedestrian facility requirements and temporary traffic control guidance. Those are plan and agency controls, not decisions to be improvised in a ramp photo note.

Write the separation plainly: permanent curb ramp photo record complete, temporary pedestrian route remains under traffic-control or site-safety review. That prevents a concrete closeout from being misread as an approval of every temporary pedestrian condition around the work.

If the temporary route changed during the concrete work, record the version that was present at the time of the ramp release. A detour that was acceptable in the morning may be different after forms are stripped, equipment moves, or a sidewalk panel is reopened.

Protect openings and hazards

Curb ramp work can leave holes, missing covers, open utility boxes, exposed sawcuts, uneven temporary edges, excavations, loose forms, protruding stakes, and abrupt drops. Photograph covers, barricades, fencing, warning devices, temporary fill, and any unsafe condition that is held before public or worker access changes.

OSHA standards require protection from falling through holes where the standard applies, including covers or guardrails, and require cover criteria such as capacity, securement, and warning markings. OSHA signs and barricade rules also require points of hazard in construction areas to be posted with legible traffic-control signs and protected by traffic-control devices.

This article does not design the cover, barricade, warning device, or traffic-control setup. The field record should make the hazard, responsible hold, and release boundary visible before the crew removes forms or opens access.

Hazard photos should be routed quickly, not saved only for the final packet. If a hole, cover, edge, or traffic exposure needs immediate attention, the photo label should identify it as a live hold and the responsible person should receive it through the project communication channel.

Use measurement discipline

Slope and dimensional readings should be recorded as measurements, not as impressions. Identify the measuring tool, calibration or verification basis if required, measuring direction, surface condition, reading locations, and whether readings were used for the project inspection report or only for the contractor photo packet.

Caltrans guidance gives a detailed pedestrian-facility measurement process: smart levels with minimum sensor accuracy, calibration before readings, 4-foot and 2-foot level guidance by location, clean surfaces, three readings dispersed across the surface, no averaging, and recording slope measurements to the nearest 0.1 percent. It also gives tape-measure guidance for dimensions and says to record checks on applicable compliance inspection reports.

If a measurement is outside the allowed range or cannot be taken because the surface is dirty, blocked, wet, curved, or still protected, record hold. Do not average away a bad reading or convert a field photo into a final compliance report unless the project procedure allows that.

Write measurement units consistently. Percent, ratio, inches, feet, and decimal feet can all appear in source documents and project forms. The punch-walk packet should not mix them casually in a way that makes later review harder.

Record corrections and holds

Punch-walk records are most useful when they show corrections clearly. For each hold, write the location, issue, responsible trade, required direction, target correction, retest or remeasure step, and whether the ramp remains closed, partially released, or excluded from the current walk.

Caltrans guidance says noncompliant pedestrian-facility dimensions or slopes should be corrected or removed and replaced, with the project engineer involved in determining whether ADA compliance has been achieved. That is a strong boundary for this article: the packet reports the condition and the hold. It does not privately decide compliance.

Photograph the same angle before and after correction. If the sawcut edge was chipped, show the chipped edge and the repair. If a panel was misaligned, show the original position and the corrected position. If a slope reading was disputed, show the measurement setup used for the retest.

A hold should not disappear from the record when it is fixed. Keep the original hold and add the closeout evidence. That history helps explain why the final condition was rechecked and prevents a repaired defect from looking like it was never found.

Use a photo sequence

Build the photo record as a sequence that another reviewer can follow. Start wide, then move to layout, forms, subgrade, concrete placement, landing, ramp run, gutter transition, detectable warning panel, joints, sawcut edges, surface checks, curing, protection, and final holds.

Give each photo a short label. The label should say what the photo proves, not just what it shows. A useful label is landing L-4 slope check facing north before punch walk, not IMG-4091. If a photo supports a hold, put hold in the label and carry that same number into the punch list.

The table below is an example structure for the packet. It does not replace the owner, DOT, contractor, or inspector form. It helps field teams avoid a pile of disconnected photos.

Keep the sequence stable even when a photo does not apply. If there is no island, mark island not applicable. If there is no surface-applied panel, mark surface-applied panel not applicable. This is clearer than renumbering the packet differently at every location.

Use a release checklist

The checklist should be completed by the person making the field handoff, then attached to the photos. Mark each item ready, hold, not applicable, or outside this release. Blank items create ambiguity and should be avoided.

Use the required project forms first. If the owner, DOT, municipality, accessibility consultant, or contractor requires a compliance inspection report, survey, daily report, material submittal, temporary pedestrian route inspection, or punch-list form, attach or cite that record. The checklist below is a field index for the photo packet.

The checklist is most useful when it is completed before the crew leaves the location. Missing photos can often be taken the same day. Missing evidence discovered after paving, striping, landscaping, or opening to pedestrians may be much harder to reconstruct.

• Ramp ID, location, crossing served, and work boundary are written on the first page.
• Approved plan, standard detail, revision, product basis, and inspection form are identified.
• Ramp type, landing, ramp run, gutter transition, and sidewalk tie-ins are photographed.
• Existing conditions and sawcut limits are recorded before demolition or placement.
• Layout marks, control points, forms, and subgrade condition are visible before concrete.
• Landing dimensions and slope-reading directions are recorded with tool context.
• Ramp run, cross slope, grade breaks, and clear area are photographed before release.
• Gutter or street transition and drainage concern are shown in wide and close views.
• Detectable warning panel type, location, width, orientation, contrast, and cuts are recorded.
• Joint layout, expansion joints, contraction joints, sawcut edges, and filler are visible.
• Utility covers, drainage structures, pole bases, signs, and obstructions are checked.
• Concrete placement, finish, broom direction, curing, and protection are documented.
• Temporary pedestrian access and traffic-control conditions are separated from ramp acceptance.
• Open holes, covers, barricades, edge drops, and worker or public hazards are flagged.
• Corrections, retests, remeasurements, and unresolved holds are tied to photo numbers.
• Final status says released for punch walk, partial release, held, or outside this release.

Write the handoff note

A good handoff note is short enough to read in the field and specific enough to defend later. It should identify the ramp, the work inspected, the documents used, the photos attached, the measurements recorded, the holds remaining, and the release limit.

Example: CR-4N at northwest corner of Market and 4th photographed on 2026-06-09 before accessibility punch walk. Basis: Sheet C5.4 revision 3, city curb ramp detail CR-2, detectable warning submittal DWS-07, and field clarification FC-12. Packet includes existing tie-ins, sawcut limits, forms, subgrade, landing, ramp run, gutter transition, detectable warning panel, joint layout, curing, and protection. Released for accessibility punch-walk review only. Held items: chipped sawcut at west tie-in photo 21, utility-cover conflict outside ramp run photo 24 pending inspector direction, and temporary pedestrian route maintained under separate traffic-control record.

The note works because it does not say ADA passed or open to public. It says what was documented and which decisions remain with the project process.

Handoff notes should avoid vague words like okay, acceptable, and done unless the project form defines them. Use status words that point to action: ready for punch-walk review, held for correction, corrected and rechecked, excluded from this release, or pending authorized acceptance.

Weak and strong records

Weak note: curb ramp done, detectable warning installed, ready for ADA walk. That note does not identify the ramp, the crossing, the plan basis, the measurement setup, the landing condition, the gutter transition, the sawcut edge, the temporary protection, or the open exceptions.

Strong note: CR-2B south driveway crossing was checked against approved detail A88A-style project sheet C-412 and owner revision OR-6. Photos 01 through 08 show existing sidewalk tie-ins and sawcut limits. Photos 09 through 14 show forms, landing outline, ramp run, gutter transition, and detectable warning panel outline before placement. Photos 15 through 26 show finished landing readings in both directions, ramp run readings, bottom grade break, gutter tie-in, panel width, panel position, dome orientation, joints, and sawcut edge. Ramp is released for punch-walk review only. Crosswalk striping, temporary pedestrian route, and final accessibility certification remain outside this release.

The strong note is better because it gives a reviewer the path from approved basis to field evidence. It also avoids turning the photo packet into a legal conclusion.

The weak note also fails a maintenance test. Months later, no one can tell whether a chip, panel edge, cover, or slope complaint was present at handoff. The strong note gives the team a dated baseline for later questions.

Common mistakes

The first mistake is photographing only the detectable warning panel. The panel is important, but a curb ramp punch walk also depends on landing, ramp run, gutter transition, grade breaks, tie-ins, joints, sawcut edges, obstructions, and protection.

The second mistake is recording slope without direction. Running slope, cross slope, landing slope parallel to the ramp run, landing slope perpendicular to the ramp run, and gutter counter slope are not interchangeable. A reading without direction can be nearly useless during review.

The third mistake is calling the ramp complete while excluding the condition that caused the punch item. If the sawcut edge, utility cover, asphalt patch, crosswalk layout, or temporary route is not ready, the handoff should say partial release or held.

The fourth mistake is overwriting the record after correction. Do not delete the first failed photo or replace the original reading with only the passing retest. The point of a punch record is to preserve the path from issue to closeout.

Use careful release language

Release wording should match authority. Released for punch-walk review means the packet is ready for review. Released for concrete closeout means the concrete scope has the required documentation under the project process. Open to pedestrians, ADA compliant, accepted, and certified mean more and should only be used by the person or process authorized to use them.

Caltrans guidance places compliance inspection reports, latitude and longitude records, post-construction survey checks where required, and Form DOT CEM-5773 in the project record process. The Caltrans ADA construction resource page also lists specific CEM-5773 inspection report forms for curb ramp cases, sidewalks, driveways, passageways, and parking. That is more formal than a contractor photo note.

When in doubt, use narrow wording: photo record complete for CR-4N concrete punch-walk review; final accessibility acceptance, temporary pedestrian route approval, crosswalk striping, and public opening remain by others under approved project procedures.

Narrow wording protects the reviewer too. It allows an inspector to use the photo record as evidence without accepting responsibility for work that was not in the packet, not visible, not measured, or not within that person's authority.

Close the punch list

Closeout should pair each punch item with the original photo, correction photo, and reviewer response. If an item was held for engineer direction, include that direction. If an item was repaired, include the repair method only if the project record requires it and the method came from approved documents or qualified direction.

For measurement-related holds, show the retest setup. A photo of a corrected surface without the measuring direction can reopen the same argument. If the original issue was a high panel edge, show the panel edge after correction. If the issue was a sawcut spall, show the repaired edge in context with the landing and pedestrian path.

Final closeout should still name exclusions. A curb ramp may be ready for concrete punch closeout while striping, signals, drainage, landscaping, temporary route removal, or final opening remain pending. The record should keep those limits clear.

Closeout should also preserve the date of each step. Original placement, first punch walk, correction, retest, and final response may happen on different days. Combining them into one undated pass note weakens the record.

Do not decide design

This packet should not choose curb ramp type, alter crosswalk location, set slope targets, move detectable warnings, approve product substitutions, decide technical infeasibility, accept a nonconforming landing, or approve a temporary pedestrian route. Those decisions belong to the approved project process and the people with authority over it.

ADA Standards, PROWAG, state DOT design manuals, standard plans, local standards, owner criteria, and agency policies can differ by setting, funding, adoption status, and project type. A field article cannot turn those into one universal rule. It can help the crew collect the facts that the responsible reviewer needs.

The safest use of this record is factual: what was planned, what was built, what was measured, what was photographed, what was corrected, what remains held, and what release status was actually granted.

That factual lane still has real value. It reduces repeat site visits, gives reviewers the context they need, helps crews correct the right item, and makes it harder for a later dispute to depend on an unsupported memory of the ramp.

Source notes

The source set supports a documentation article. PROWAG and ADA materials supply the vocabulary and surface, landing, grade break, gutter transition, and detectable warning concepts. Caltrans sources support inspection workflow, form checks, measurement discipline, detectable warning material controls, curing, jointing, and formal compliance record boundaries.

WSDOT sources support plan-based ramp types, landing and curb ramp criteria, detectable warning placement examples, sidewalk forms, joints, curing, and appurtenance conflicts. OSHA standards support the safety boundary around holes, covers, barricades, and construction hazard points.

The sources are not used here to publish a design standard or legal opinion. They are used to explain why a narrow, dated, photo-backed field record is better than a vague note before accessibility punch-walk review.

Release questions

Before the packet is sent, ask four questions. Can a reviewer locate the exact ramp without help? Can they see the approved basis? Can they follow the sequence from existing tie-in to final protection? Can they tell what remains held or outside the release?

If any answer is no, add the missing photo or note before the punch walk. The best time to capture the landing, panel, sawcut edge, joint layout, and gutter transition is while the crew is still there and the work is still visible.

A useful curb ramp punch-walk record does not try to win an argument with adjectives. It gives dated facts, measured context, photos from the right angles, and release wording that matches the authority of the person signing the handoff.

If the record can answer those questions without a site visit, it has done its job. If it cannot, the missing information should become a hold before the route is represented as ready for the next review step.

Sources checked

• U.S. Access Board, Public Right-of-Way Accessibility Guidelines, complete textUsed for pedestrian access route, curb ramp, blended transition, landing, grade break, gutter transition, and detectable warning concepts.
• U.S. Access Board, Chapter 4: Ramps and Curb RampsUsed for ADA curb ramp and ramp guidance, top landing context, side flare context, and detectable warning discussion.
• U.S. Department of Justice, 2010 ADA Standards for Accessible DesignUsed for curb ramp, counter slope, landing, location, and accessible route context.
• Caltrans Construction Manual, Section 4-73, Concrete Curbs and SidewalksUsed for curb ramp inspection workflow, layout checks, forms, grades, placement, slope measurements, documentation, and compliance record boundaries.
• Caltrans ADA Construction ResourcesUsed for examples of ADA compliance inspection report forms tied to curb ramps, sidewalks, driveways, passageways, and parking.
• Caltrans Standard Specifications 2025, Section 73Used for concrete curb and sidewalk subgrade, forms, joints, curing, detectable warning surfaces, broom finish, straightedge checks, existing curb ramp work, and warranties.
• Caltrans Standard Plans 2025Used for plan-controlled curb ramp, curb ramp and island passageway, temporary pedestrian access route, and detectable warning context.
• WSDOT Design Manual, Chapter 1510 Pedestrian FacilitiesUsed for curb ramp type, landing, running slope, cross slope, counter slope, detectable warning, appurtenance, grade break, clear area, and drainage context.
• WSDOT Standard Specifications 2026, Division 8Used for curb and gutter forms, sidewalk and curb ramp forms, placing, broom finish, joints, curing, traffic exclusion, and detectable warning installation.
• WSDOT Standard Plan F-40.16-03, Single Direction Curb RampUsed for single-direction curb ramp plan context, crosswalk containment, grade break flushness, appurtenance restrictions, broom finish, and contraction joint examples.
• WSDOT Standard Plan F-45.10-05, Detectable Warning SurfaceUsed for detectable warning panel placement, width, concrete pad, back-of-curb relationship, dome orientation, and temporary surface-applied panel boundary.
• WSDOT Construction Manual, Chapter 6, StructuresUsed for form review, concrete placement, consolidation, curing protection, and construction-joint caution around concrete work.
• OSHA, 29 CFR 1926.501, Duty to have fall protectionUsed for safety boundaries around holes, walking and working surfaces, excavations, pits, wells, and fall-protection responsibilities.
• OSHA, 29 CFR 1926.502, Fall protection systems criteria and practicesUsed for guardrail and cover criteria around holes, including support, securement, and warning markings.
• OSHA, 29 CFR 1926.200, Accident prevention signs and tagsUsed for signs, barricades, points of hazard, and MUTCD Part 6 boundary for construction worker traffic-control devices.

Related guides