Field Notes
Paving force-account records before extra work is disputed
A useful force-account packet ties the directive, scope, daily labor, equipment, materials, paving location, quantities, photos, signoff, and open exceptions together before the argument starts.
Direct answer
A paving force-account record should prove who directed the extra work, what document or field instruction authorized it, why force-account tracking is being used, exactly where the work happened, what labor and equipment were used, what materials and trucking were supplied, what quantities were accomplished, what photos and tickets support the work, who reviewed the daily record, and what items remained disputed that day.
The record belongs before the dispute because force-account paving work is hard to reconstruct later. Trucks leave, tickets get separated from the area paved, traffic-control setups change, equipment moves to another operation, and a crew that looked obvious at 10 a.m. can become a vague daily report by the end of the week.
Use this field note as documentation guidance only. The contract documents, owner or DOT forms, change-order procedure, engineer or resident engineer direction, project specifications, certified payroll requirements, dispute procedure, claims counsel, and safety plan control the work, payment, time impact, and rights of the parties.
Why the record belongs before the dispute
Force-account work adds a cost-record layer on top of ordinary inspection. The crew still has to perform acceptable paving work, but the project also needs a daily accounting trail that can be compared against later invoices, extra-work bills, pay estimates, or claim narratives.
That trail is strongest when it is written while the work is happening. A same-day record can show the foreperson, inspector, truck count, paver location, roller or loader time, milling limits, base repair area, haul delay, lane closure, photos, and material tickets while those facts are still observable.
Once the parties start arguing, the question often changes from what happened to what can be proved. The useful packet is not a dramatic story. It is a clean chain of directive, scope, resources, quantities, support documents, review, and exceptions.
Daily labor, equipment, materials, and trucking
A useful resource record names the people and equipment enough for someone else to reconcile it. Labor entries should show contractor or subcontractor, name or crew identifier when the project form allows it, classification, task, start time, stop time, break or standby period when relevant, and whether the person was working on the extra work or on a nearby bid item.
Equipment entries should be just as specific. Record the paver, mill, roller, skid steer, loader, broom, saw, compressor, water truck, tack distributor, service truck, traffic-control truck, or other equipment by ID, type, size or model when required, operator, productive time, standby time, and why the equipment was needed for the directed work.
Material and trucking records should tie the force-account sheet to tickets, invoices, haul slips, load counts, disposal tickets, plant tickets, aggregate tickets, tack records, rental invoices, or subcontractor backup. Total dollars are not a field record. The field record should show what was used, where it went, and which support document proves it.
Paving context that cost lines miss
Paving force-account work needs location and production context because the same crew can move through several operations in one shift. Stationing, lane, lift, lot area, driveway, trench patch, shoulder, curb return, or grid square should appear beside the labor and equipment entries, not only in a separate narrative.
Record the paving-specific facts that explain the work: milling depth, sawcut limits, soft spot dimensions, base repair depth, geotextile or aggregate used, tack application, mix type, load ticket numbers, placed tons, handwork, compaction passes when relevant, density test location if the project requires it, rejected or held loads, and final surface condition.
Photos are most useful when they show before, during, and after conditions with scale and location. A close photo of broken pavement is weaker than a photo sequence that shows the directive area, the removal limit, the exposed condition, the material placed, the equipment involved, and the completed patch.
Time, standby, delay, and traffic-control notes
Force-account disputes often turn on time that was not clearly separated. Productive work, standby, mobilization, remobilization, weather delay, plant wait, traffic-control setup, owner-directed wait, utility conflict, inspector hold, and cleanup should not be collapsed into one block of crew hours.
If a roller, paver, mill, or crew is standing by, the note should say why, who was notified, what decision was pending, when the standby started, and when work resumed or the resource was released. If the contract or owner form has a special standby rule, use that form and do not improvise a rate or entitlement in the daily note.
Traffic-control costs need their own clarity. Record the lane, ramp, driveway, flagging, cones, signs, attenuator, police detail, pedestrian route, or night-work setup that was required for the extra work. If the same setup served bid work and extra work, say how the time or resources were separated or that the split remains an open issue.
Daily agreement and exceptions
Use the owner, agency, or contract form first. If the form calls for inspector and contractor signatures, get them while the people who saw the work are still available. The value of a signature is governed by the project documents, but the practical field value is clear: it shows what the parties reviewed that day.
If there is disagreement, do not hide it. Write the exception on the daily record: contractor requests full crew standby from 9:10 to 10:40, inspector agrees one roller and one laborer were used but does not agree paver standby is part of the directed work, or owner review pending on traffic-control split.
A daily exception is better than a silent signature followed by a long email thread two weeks later. It tells the next reviewer which facts are agreed, which facts are disputed, and which documents still need to be attached.
Minimum force-account packet
The project form controls. Use this packet only to check whether the required record is complete enough for later review.
| Record item | Field detail | Why it matters |
|---|---|---|
| Directive | Change order, work order, RFI response, field instruction, owner direction, date, time, and person directing the work | Shows why the crew treated the work as directed extra work |
| Scope and boundary | Station, lane, lot area, lift, patch limits, sketch, drawing reference, what is included, and what is excluded | Prevents bid work and extra work from blending together |
| Labor | Contractor or subcontractor, worker or crew ID, classification, task, start/stop time, productive or standby status | Makes labor hours reviewable against payroll and daily reports |
| Equipment | Equipment ID, type, size or model when required, operator, productive time, standby time, and reason used | Connects equipment charges to actual extra-work activity |
| Materials and trucking | Mix, aggregate, tack, disposal, rental, trucking, load tickets, invoices, haul slips, quantities, and where material went | Lets the cost backup match the pavement placed or material removed |
| Paving production | Milling depth, patch dimensions, base repair, tons placed, area paved, handwork, compaction or test references when required | Turns cost records into a field production record |
| Conditions | Weather, surface condition, traffic-control setup, haul delay, plant wait, utility conflict, owner hold, safety constraint | Explains why resources were used or delayed |
| Review and exceptions | Inspector and contractor review, signature where required, copy distribution, agreed facts, disputed items, pending documents | Keeps disagreement visible before later billing |
Before the crew leaves checklist
Use this checklist at the end of each force-account shift, not at the end of the month.
- Confirm the directive, change order, work order, or field instruction is named on the daily record.
- Mark the exact station, lane, lot area, lift, patch, driveway, shoulder, or drawing location.
- Separate extra work from original bid work and identify any unresolved boundary.
- Record labor by classification, task, and start/stop time under the project form.
- Record equipment by ID, operator, task, productive time, and standby time when relevant.
- Attach or reference material tickets, plant tickets, haul slips, disposal tickets, rental invoices, or subcontractor backup.
- Record quantities accomplished with enough measurements or sketches for a reviewer to reproduce them.
- Take photos before the condition is covered, during the work, and after completion.
- Write delay, standby, traffic-control, weather, plant wait, utility conflict, or owner-hold notes before memory fills the gap.
- Get same-day review and signatures where the project requires them.
- Write exceptions directly on the daily record when an item is not agreed.
- Give copies or upload the record under the project procedure before the next pay cycle.
Weak and strong daily notes
Weak note: extra asphalt work performed at north lot by force account. Crew and equipment on site. Tickets attached.
That note does not identify the directive, station or lot boundary, labor, equipment, productive time, standby time, material ticket numbers, quantities, traffic-control split, photos, signatures, or disputed items.
Stronger note: owner field directive OFD-18 issued at 8:05 a.m. to remove failed base and repave north truck apron outside bid patch limits. Work tracked as force-account pending change order. Limits marked NTA grid B2 to B4, 18 ft by 52 ft, average base removal 8 in. Photos 18-01 through 18-09 show failed condition, excavation, aggregate placement, tack, and completed patch. Crew: foreperson, 2 laborers, skid steer operator, roller operator from 8:30 to 2:40 with 30 minute plant wait noted. Equipment: skid steer SS-14, roller R-8, broom B-2, tack distributor TD-1, traffic-control truck TC-6. Materials: aggregate ticket A-744, mix tickets HMA-331 through HMA-336, tack log TL-09. Inspector agrees labor, equipment, and material quantities except contractor requests paver standby from 9:10 to 10:05; owner review pending on that standby line. Daily record signed with exception noted.
The stronger note is better because it lets a later reviewer follow the work without guessing. It separates the directed scope, the resources actually used, the documents attached, and the open exception.
Common mistakes
The first mistake is starting the record after the work is already covered. A late note cannot show the exposed condition, the patch depth, the equipment actually in use, or the moment the crew was waiting for direction.
The second mistake is mixing original contract quantities with directed extra work. If the crew paved bid-item asphalt and force-account repair work in the same shift, the record should show where one stopped and the other started.
The third mistake is recording crew totals without tasks. Five workers for eight hours is not enough if two were flagging for the bid operation, one was cleaning the extra-work area, and two were waiting while the owner decided whether to expand the patch.
The fourth mistake is treating tickets as self-explanatory. A plant ticket or disposal ticket proves a transaction, not where the material went or why it was tied to extra work.
The fifth mistake is signing a daily record with disagreement left invisible. If the parties disagree about standby, equipment need, traffic-control split, quantity, or scope, write the exception the same day.
Payment, claim, and safety limits
This field note is not legal advice, claim advice, payment approval, rate guidance, scheduling analysis, entitlement review, change-order instruction, engineering direction, or a force-account specification. The adopted contract, owner or DOT procedure, project forms, engineer direction, dispute process, certified payroll rules, documentation-retention rules, and qualified counsel control those issues.
Do not use this checklist to bypass traffic-control requirements, work-zone safety, backing rules, night-work controls, hot-mix handling, burn protection, equipment lockout, utility-clearance rules, silica or dust controls, excavation safety, confined-space rules, or site-specific safety procedures. The record preserves what happened. It does not authorize unsafe work.
Sources checked
- FHWA, Companion Resource for Contractor Force AccountUsed for force-account tracking of labor, equipment, material quantities, worker names, work performed, actual hours, equipment identification, and materials used.
- FHWA, Contract Procedures, 23 CFR 635.120 and 635.123Used for change and extra-work approval context, documented reasons for force account, cost analysis, and pay quantity source-document themes.
- Caltrans Construction Manual, Section 5-3 Change OrdersUsed for change-order scope, payment method, extra-work description, and force-account payment method boundaries.
- Caltrans Construction Manual, Section 3-9 PaymentUsed for daily force-account record content, same-day entries, location, labor, equipment, materials, quantities, off-site work, and disputed-item notation themes.
- Caltrans Construction Manual, Section 5-1 Project Records and ReportsUsed for daily extra-work reporting, extra-work bill forms, and tentative daily extra-work agreement themes.
- WSDOT Construction Manual, Chapter 1 AdministrationUsed for accurate daily time records, Daily Report of Force Account Worked, signatures, copies, timely entry, checked calculations, and conversion-to-agreed-price themes.
- MDOT Construction Manual, Force Account WorkUsed for force-account work plan, monitoring, signed daily records, progress-payment backup, and supporting documentation themes.
- MDOT Construction Manual, Inspector's Daily Work ReportUsed for daily report weather, workforce, equipment, hours, pay item location, material association, calculations, and timely reporting themes.