Surface segregation repair and texture match record before final ride

Direct answer

Before final ride acceptance, an asphalt surface segregation repair boundary and texture match photo record should identify the project, route or lot, lane, stationing, offset, suspected segregated area, severity basis, repair boundary, saw-cut or milling limit, removal depth, replacement mix, tack condition, compaction method, texture-match photos, smoothness or ride data, retest result, exceptions, witness, and acceptance boundary.

The record should prove that the visible defect was located, classified, bounded, repaired or accepted by documented exception, and checked again for texture and ride. A final ride report does not by itself explain whether a coarse-textured segregated streak was repaired, whether the repair edge is smooth, or whether the texture mismatch became a new acceptance issue.

Use this field note as documentation guidance only. The contract specifications, agency construction manual, approved mix design, engineer, materials lab, paving inspector, smoothness specification, traffic-control plan, and owner acceptance process control actual segregation classification, repair method, smoothness measurement, payment adjustment, and final acceptance.

Why this record fails at final ride

Segregation and ride acceptance can be reviewed by different people using different evidence. The inspector sees a coarse spot behind the paver, the materials team discusses density or texture, the contractor mills and replaces a small patch, and the final ride data later shows a bump, dip, or rough transition near the same area.

The weak packet says segregation repaired. The strong packet shows where the defect started and ended, how the repair boundary was chosen, what was removed, what mix replaced it, how the repair was compacted, what the repaired surface texture looked like next to the surrounding mat, and how the area related to final smoothness or ride acceptance.

NCHRP Report 441 and Alberta's segregation rating manual both frame segregation as a visible and measurable asphalt pavement condition that can vary by type and severity. That is why the field record needs both location photos and post-repair texture photos before final ride acceptance closes the issue.

Start with the acceptance basis

The first page of the record should name the contract section, asphalt mix type, lift, lot or segment, surface course, segregation specification, repair specification, smoothness specification, final ride method, excluded areas, traffic-control limits, and who has authority to accept, reject, or require more repair.

Do not judge the area from a phone photo alone. The project may use visual classification, density checks, infrared or texture tools, agency distress manuals, ride profiles, or engineer judgment. Record the actual basis used on the job.

Caltrans Section 39, CDOT Division 400, Iowa DOT troubleshooting guidance, and MDOT construction manual material are examples of agency sources that connect asphalt placement quality, segregation, corrective action, testing tools, and acceptance processes. The record should cite the project specification that governs the actual repair.

Locate the segregated area

Record stationing, offset, lane, shoulder, paving pass, paver lane, truck number where relevant, mix ticket range, time placed, weather, mat temperature notes, roller pattern notes, and adjacent reference points. Include wide photos that let the owner relocate the area without the paving crew present.

Map the suspected area before correction. Mark the visible boundary with paint, flags, cones, station marks, or a photo overlay. Include close photos of texture and wide photos showing how the defect relates to the lane, joint, edge, bridge, manhole, inlet, driveway, or smoothness segment.

Saskatchewan's asphalt surface inspection guide and Alberta's segregation manual use photo-based classification context. The local project may not use those manuals, but the practical lesson is stable: a repair record needs repeatable location evidence before the surface changes.

Classify texture before choosing repair

Separate coarse segregation, fine segregation, truck-end segregation, longitudinal streaks, joint-edge defects, screed marks, raveling, flushing, roller pickup, handwork texture, and patch texture. Similar-looking areas can have different causes and different acceptance paths.

Pavement Interactive explains coarse segregation as a shift toward larger aggregate and rougher surface texture, while Asphalt Magazine discusses causes such as loading, hauling, transfer, and paver operations. Those sources support a record that describes the field pattern instead of only writing segregated.

If the agency requires density, texture depth, infrared, coring, or another confirmation method, attach it to the photo record. If the decision is visual, record who made that visual call and what severity language was used.

Set a repair boundary before cutting

The repair boundary should be visible in photos before any saw cutting, milling, or removal starts. Record whether the boundary follows the visible defect, a lane line, a station limit, a smoothness correction segment, a transverse cut, a drainage structure, a joint, or an engineer-directed rectangle.

A fuzzy boundary creates two later arguments: whether all segregated material was removed, and whether the repair itself created an unacceptable texture or ride transition. Use before photos, marked limits, and dimensions so the final reviewer can compare the repaired area to the original defect.

CDOT's specification language is one example of an agency requiring segregated areas behind the paver to be removed and replaced with specification material. The job's own specification controls, but the record should show how the removal limit was chosen and approved.

Document removal and replacement

Photograph the cut line, milled face, cleaned surface, tack condition, replacement mix, truck ticket if needed, lift thickness, compaction equipment, roller pattern, joint treatment, edge confinement, and final surface. Tie every photo to the station and boundary.

If the repair is a surface replacement, document the full depth of removal and whether any underlying lift was exposed. If it is a surface treatment, fog seal, slurry, chip seal, thin overlay, or other accepted correction, record the approved method and why it was allowed for this final acceptance issue.

The article does not prescribe a repair method. It tells the field team what evidence to preserve for the correction method the contract, agency, and engineer allow.

Photograph texture match after correction

Take post-repair photos from the same directions as the pre-repair photos. Include close texture photos at the repair center, repair edge, upstream transition, downstream transition, joint or lane edge, and adjacent original mat. Photograph in consistent light where possible.

Texture match is not only color. Look for aggregate gradation appearance, open texture, tight texture, flushing, rough handwork, roller marks, edge raveling, shadow lines, cold-joint marks, and abrupt transitions. The record should show whether the repair blends with the surrounding surface or remains visibly different.

FHWA's surface texture technical advisory discusses asphalt surface texture as a safety and performance characteristic, while NCHRP 441 includes texture measurement concepts for segregation. The final acceptance record should not let a texture mismatch disappear behind a smoothness spreadsheet.

Tie the repair to ride data

If the project has final ride or smoothness acceptance, identify the profile run, segment, wheel path, station range, excluded areas, localized roughness locations, and whether the repair falls inside a correction area. Save the smoothness report or spreadsheet reference with the photo packet.

Caltrans smoothness guidance and MnDOT smoothness specification material both show that final surface smoothness can be measured and corrected by defined segments and reporting formats. The local specification controls, but the photo record should connect the physical repair to the ride segment being accepted.

Do not call a repair accepted because it looks better in photos if the smoothness correction still fails. Also do not treat a passing ride number as proof that a visibly segregated area was addressed. The record should carry both lines of evidence.

Separate surface appearance from density disputes

A segregation repair record is not the same as a density-core dispute packet. Density results can support an acceptance decision, but this record is centered on visible surface condition, repair limits, texture match, and ride acceptance.

If cores, nuclear density, or lab density results are used to evaluate the area, reference the density record and keep the sample IDs tied to the repair boundary. Do not bury a density exception in a photo-only surface record.

The earlier Anvilfield density-core article covers pay-factor disputes. This article should stay with the final surface condition that inspectors and drivers can see or feel.

Record table

Use a compact table so the paving crew, inspector, materials engineer, smoothness reviewer, and owner can compare the same location evidence.

Before-final-ride checklist

Run this checklist before the final ride acceptance packet is signed off.

• Contract segregation and smoothness acceptance basis is identified.
• Suspected area is mapped by station, offset, lane, and reference photos.
• Pre-repair texture photos show the full defect boundary.
• Repair limits are marked and approved before cutting or milling.
• Removal depth, cleaned face, tack, replacement mix, and compaction are photographed.
• Post-repair texture photos match the pre-repair camera directions.
• Repair edges, transitions, and adjacent mat are photographed close and wide.
• Smoothness segment, ride report, or localized roughness data is linked to the repair.
• Density or materials test records are cross-referenced when used.
• Remaining exceptions and retest requirements are assigned before acceptance.

Weak versus strong record

Weak record: Segregation near Station 42+00 removed and patched. Ride accepted.

Strong record: Northbound Lane 2 segregation from Station 41+86 to 42+31, 3 feet right of centerline, was marked in white paint and photographed before repair. Engineer directed a rectangular milling limit from 41+80 to 42+36. The area was milled 1.5 inches, cleaned, tacked, replaced with the approved surface mix, compacted with two breakdown passes and finish rolling, and photographed at center, upstream edge, downstream edge, and both longitudinal tie-ins. The repair fell in ride segment 0.4 to 0.5 mile and the final profiler report showed no localized roughness in that station range. A slight color difference was accepted by the engineer after texture photos and density reference D-42-2 were attached.

The strong record ties the repair boundary, texture match, ride result, and acceptance exception together instead of leaving each item in a different folder.

Common mistakes

The most common mistake is repairing the visible center of the segregated area but leaving the feathered edges undocumented. Those edges are where texture mismatch and ride bumps often remain.

Another mistake is taking only close photos. A close photo can show texture, but it cannot prove the station, lane, repair boundary, relation to the smoothness segment, or whether the repair edge lines up with the original defect.

Other mistakes include no pre-repair boundary photo, no removal-depth evidence, no tack photo, no adjacent-mat comparison, no ride-segment link, no exception log, and no final photo after traffic has cooled or cleaned loose material from the repair.

When to hold final ride acceptance

Hold final ride acceptance if the suspected segregated area is not mapped, the repair boundary was not approved, the repaired texture still looks open or coarse, repair edges are abrupt, ride data identifies localized roughness in the repair area, or the specification requires additional testing that has not been completed.

Also hold if density or materials records conflict with the surface repair decision, if traffic damaged the repair before acceptance, if weather prevented proper compaction or cooling, if the segment correction spreadsheet excludes the repair without explanation, or if the owner has not accepted a visible texture exception.

A hold should identify the route, lane, station range, repair boundary, missing evidence, responsible party, retest requirement, and whether adjacent ride segments can close.

Owner and payment handoff

The owner handoff should include the final repair map, pre-repair photos, repair photos, texture-match photos, smoothness or ride references, test records used in the decision, exceptions, and the final acceptance note. Payment staff should be able to see why the area was accepted, repaired again, or deducted.

If the project uses incentives, disincentives, or pay adjustments tied to smoothness, surface condition, density, or percent within limits, keep the repair record attached to the payment worksheet. The record should explain whether the repair changed the measured acceptance segment or only closed a visual defect.

Final ride acceptance is a public-facing result. The packet should make it clear that the repaired area was not only smoother on paper, but also visually reviewed for texture and surface continuity.

Questions before closing the segment

Who classified the segregation, and what method or severity language did they use? Who approved the repair boundary? Was the repair limited to the surface course, or did it expose another lift? Does the repaired area fall inside a final ride segment, correction segment, or localized roughness location?

Are texture photos taken before and after repair from comparable viewpoints? Does the repaired surface match the adjacent mat closely enough for owner acceptance? Are density, smoothness, or materials tests still open? Are exceptions accepted in writing?

Answer those questions before the segment closes. Once the paving train moves on and final ride acceptance is signed, the missing evidence becomes a payment or warranty dispute.

Compliance and safety limits

This article does not define a segregation severity threshold, approve a repair method, replace DOT specifications, calculate smoothness incentives, or decide final ride acceptance. It is a field-record structure for preserving segregation boundary, repair, texture, ride, and exception evidence.

The contract documents, agency specifications, materials engineer, resident engineer, smoothness specification, traffic control plan, testing agency, and owner acceptance process control the work. If those documents conflict with this checklist, use the controlling project document and record the decision.

Do not mark, mill, cut, patch, test, or photograph from live traffic without approved traffic control and qualified personnel. Hot mix, rollers, saws, profilers, and night operations belong under the project safety plan.

Sources checked

• NCHRP Report 441, Segregation in Hot-Mix Asphalt PavementsUsed for segregation detection, visual classification, surface texture, and measurement context.
• Alberta Transportation, Paving Guidelines and Segregation Rating ManualUsed for segregation inspection, rating, and photo-reference context.
• Saskatchewan, Asphalt Concrete Surface Inspection GuideUsed for surface inspection and segregation severity identification context.
• Iowa DOT, Problems and SolutionsUsed for segregation troubleshooting context and the connection between varied texture, density, smoothness, and specification requirements.
• CDOT, 2023 Division 400 Construction SpecificationsUsed for agency specification context around removing and replacing segregated areas with specification material.
• Asphalt Magazine, Segregation Causes and CuresUsed for practical causes and patterns of asphalt segregation during loading, hauling, transfer, and placement.
• FHWA, Technical Advisory T 5040.36 Surface Texture for Asphalt and Concrete PavementsUsed for asphalt surface texture context and the importance of adequate surface texture.
• Caltrans, Pavement Smoothness GuidelinesUsed for smoothness correction, final surface compliance, and segment documentation context.
• MnDOT, Pavement Surface Smoothness SpecificationUsed for final bituminous surface smoothness and IRI reporting context.
• Caltrans Construction Manual, Section 39 Asphalt ConcreteUsed for asphalt concrete construction and acceptance-process context.
• MDOT Construction Manual, 501 Plant Produced Hot Mix AsphaltUsed for HMA construction and segregation testing tools context.
• Texas CTR, Segregation of Asphalt MixturesUsed for causes, identification, and field guidance context for asphalt segregation.
• Pavement Interactive, Aggregate SegregationUsed for coarse segregation, rough texture, density, air void, and performance context.

Related guides