Esc

↑↓ move↵ openIndex · Pagefind

Acceleration and disruption: track time recovery and production separately

Distinguish earlier completion efforts from productivity effects and organize the records needed to evaluate changed working methods.

Charley Forey2 min readSchedulingSchedule forensics
On this page
  1. Capture the instruction and the plan
  2. A fictional productivity comparison
  3. Record conditions while they are visible
  4. Review conclusions separately

A team can finish earlier by adding resources and still experience poor productivity. It can also finish on time while absorbing significant inefficiency. Completion dates and production performance answer different questions, so a useful project record tracks both.

In practical planning terms, acceleration involves measures intended to complete work sooner. Disruption concerns interference with the way work is performed and its productivity. Contractual entitlement and legal characterization require project-specific review. The SCL Delay and Disruption Protocol discusses these subjects separately.

Capture the instruction and the plan

Record who requested a changed completion objective or working method, when, and through which communication. Identify the prior forecast, the proposed intervention and its assumptions. Do not assume an informal meeting statement settles responsibility for additional cost.

Measure Schedule evidence Production evidence
Additional crew Revised sequence and milestone forecast Crew hours, installed quantities and work area
Overtime Shift calendar and planned duration Overtime hours, output and rework
Resequencing Changed dependencies and access dates Moves, interruptions and partial work fronts
Expediting Revised procurement commitments Freight, handling and delivery records

A fictional productivity comparison

A crew installs 100 units in 80 labor-hours during one period: 1.25 units per labor-hour. In a later period it installs 100 units in 100 labor-hours: 1.0 unit per labor-hour. Labor-hours per unit rise from 0.8 to 1.0.

Those figures describe observed production, not the cause of the difference. Compare scope, location, crew mix, learning, weather, congestion and rework before attributing the change to an event. A convenient earlier period is not automatically a valid comparison baseline.

Two measures to retain together

Schedule: when did the work and milestone finish?

Production: what quantity was installed, with how many labor-hours, under which conditions?

Record conditions while they are visible

Daily reports should identify locations, activities, crew composition, working hours, quantities, access restrictions and interruptions. Link photographs and instructions to the affected work. Keep quantity definitions consistent so one period is not counting installed units while another counts delivered units.

Record proposed mitigation and the actual response. If a second crew cannot access the area, preserve the access issue and the decision taken. If overtime improves the finish forecast but produces no observed output gain, explain that difference rather than combining both into a single success metric.

Review conclusions separately

A recovery model supports a forecast discussion. Production records support a productivity discussion. A cost analysis and contract review determine what financial conclusions can be supported. Keep their assumptions visible and avoid treating one result as proof of every other issue.

Continue with recovery schedules, extension-of-time preparation and the Schedule Forensics library.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Open file