As-Built Schedule

Definition

An as-built schedule is the historical record of what actually happened on a project — the dates work really started and finished, the durations actually consumed, the sequence in which crews and trades actually worked, and the events (good and bad) that shaped that flow. It is not the baseline. It is not a revision of the baseline. It is a separate artifact, built from contemporaneous evidence, that becomes the foundation of delay analysis, time impact analysis, claims, lessons learned databases, and benchmarking.

Why It Matters

On the day a dispute lands on a project director's desk — and on a complex job it is "when" not "if" — the question is rarely "what did you plan?". The question is "what really happened, and why?". A clean as-built schedule answers that question in days. A missing or poorly-built one turns a six-week claim review into a six-month archaeological dig through scattered daily reports, photos, and emails. I have personally seen a contractor lose a legitimate $14M extension-of-time claim because nobody could reconstruct the sequence of events to the standard the contract required.

What Goes Into It

• Actual start and finish dates of every activity, sourced from daily reports, foreman logs, inspection records, photos, drone footage, and signed work tickets.
• Actual durations and crew loadings.
• Out-of-sequence work, with notes on why the sequence changed.
• Suspensions, weather days, RFIs, design changes, late deliveries — each tied to the activities they touched.
• Approved change orders and the activities they introduced or modified.
• The actual logic, which is often not the planned logic.

Real-World Construction Example

On a $620M LRT depot I supported in the Middle East, the as-built schedule turned a hostile commercial negotiation into a structured technical conversation. The original baseline had 1,840 activities; the as-built ended at 2,290 — roughly 450 extra activities introduced by change orders, re-sequencing, and remedial work. Because the field team had captured daily progress in P6 within 48 hours of the event for 36 months, we could overlay the as-built against the baseline and isolate exactly which 71 critical-path activities had been delayed by the employer, which 23 by the contractor, and which 18 were concurrent. The final settlement closed in ten weeks. Without that record it would have been a year-long forensic exercise.

Real-World IT Example

The same principle applies to a long IT programme. On a 22-month core-banking migration, the PMO maintained an as-built equivalent in Jira plus a weekly schedule snapshot. When the bank's risk committee asked, two years in, why the integration phase had slipped by 14 weeks, the team produced a week-by-week causation map: 6 weeks attributable to a vendor SDK regression, 4 to a regulatory change introduced mid-flight, 3 to internal scope additions, 1 to estimating error. That clarity preserved the relationship with the executive sponsor and protected the programme manager's credibility.

Building It Well

• Capture daily, not monthly. Memory decays fast. A 30-day-old "actual start" is already a guess.
• Tie every change to evidence. Each actual date should be traceable to a daily report, inspection, ticket, or photo.
• Preserve the original baseline. Never overwrite it. The as-built only has meaning when contrasted with the plan.
• Record out-of-sequence progress honestly. Hiding it now creates a credibility problem in arbitration later.
• Maintain the calendar. Holidays, shutdowns, weather days — all are part of the historical record.

Practical Lessons Learned

• The single biggest predictor of a fair claim outcome is not contractual position — it is the quality of the as-built record. Lawyers and adjudicators trust evidence, not argument.
• Treat the as-built as a living deliverable owned by the planner, audited monthly, and signed by the project director — not as a year-end exercise.
• Photos with EXIF timestamps and GPS coordinates are extraordinarily persuasive. Modern drone footage is even better.
• Even when no dispute ever materialises, the as-built becomes the raw data for your next bid's productivity assumptions. It pays for itself.

Common Mistakes

• Reconstructing it retrospectively from memory. Courts and adjudicators discount memory-based reconstructions heavily.
• Overwriting the baseline. A baseline that has been "updated to reflect reality" is no longer a baseline.
• Smoothing the truth. If the team worked Saturdays for three months, the schedule must show it.
• Ignoring trade and subcontractor schedules. An as-built that captures only your direct activities misses half the story.
• Hand-stitched in Excel. A schedule of any complexity needs a real CPM tool — Primavera P6, Asta, or MS Project — to preserve logic.
• No narrative. Dates without context are data; dates with a written explanation of why are evidence.

Expert Tips

• Run a monthly "as-built integrity" check: random-sample 20 activities and trace each actual date back to its primary evidence source.
• Tag delay-causing events at the activity level (employer change, design issue, weather, etc.) the day they occur. Coding later is hopelessly error-prone.
• Use the Schedule Health Checker against both the baseline and the latest as-built each month.
• Train the field engineers, not just the planner. The data quality of the as-built is set by the people writing the daily reports.
• For mega-projects, consider a parallel "narrative log" — a short weekly memo describing what happened, written by the project director. Future-you will be grateful.

Key Takeaways

• The as-built schedule is the factual history of the project, not a revised plan.
• Its value is realised in disputes, lessons learned, and future estimating — and it must be built daily, not retroactively.
• Quality of evidence beats sophistication of argument. Photos, daily reports, signed tickets, and timestamped logs are the gold standard.
• Never overwrite the baseline; always preserve it for comparison.
• An as-built that is properly maintained pays for itself many times over the life of a project portfolio.

Related Encyclopedia Entries

• Baseline Schedule
• Delay Analysis
• Time Impact Analysis
• Critical Path Method
• Change Control
• Lessons Learned

Related Research Articles, Case Studies & Tools

• Schedule Health Checker
• Project Controls Academy
• As-Built Schedule Templates
• Learning Tracks: Forensic Scheduling
• LRT depot $14M EOT case study
• As-built data quality in mega-projects