The Schedule Is a Contract Document: Baselines, Updates, and How Delay Gets Proven

Most contractors treat the schedule as a chart they submit once and argue about later. That is expensive. On a public project the schedule is a contract deliverable, and it is almost always the document that decides who pays for lost time.

The pattern is familiar. A baseline gets submitted late and approved loosely. Updates stop going out around the third month. Then something goes wrong — a late approval, a utility conflict, an owner-directed change — and the contractor is asked to prove impact using a schedule that no longer resembles the job. At that point the argument is not really about entitlement. It is about evidence, and there isn't any.

The schedule is a deliverable, not a courtesy

Read what your contract actually requires before you build anything. Most specifications state the required scheduling method, the software, the level of detail, activity coding, submission dates, update frequency, and what has to accompany each submission — narrative, look-ahead, manpower, cash-flow curve. Those requirements are enforceable, and they are frequently the first thing an owner cites when a time claim arrives.

Treat the baseline like any other submittal: log it, transmit it formally, and track the review to a documented disposition. A schedule that was emailed to one project manager and never formally accepted is weak evidence. The same discipline that governs a submittal log applies here.

If the specified requirements conflict with the way the work can actually be built — an unrealistic milestone, a required sequence that does not sequence, a phasing plan that assumes access you will not have — raise it in writing during the baseline review, not after the fact.

What a baseline has to show

A credible baseline shows how the work will be built, not just when it ends. At minimum it should reflect the full contract scope, the contractual start and completion dates, every milestone and phasing constraint named in the contract, procurement and approval durations for long-lead items, and the access or possession assumptions you are relying on.

Procurement is where most baselines quietly fail. Submittal preparation, review, resubmittal, fabrication, and delivery are real durations, and on public work they often exceed the field durations they feed. If those activities are not in the schedule, an approval delay has nowhere to show up.

Write the assumptions down. Working hours and days, weather allowances, inspection availability, other contractors on site, owner-furnished items and dates. Assumptions that live only in the estimator's head cannot support a position later.

Logic, not decoration

A bar chart with no relationships is a picture. A critical path method schedule is an argument: every activity is tied to its predecessors and successors with defined relationship types and any lags, so the calculation shows which chain actually controls completion.

Keep the logic honest. Sequences driven by crew availability or a preferred means and method are legitimate, but they should be modeled as what they are rather than disguised as physical constraints. Over-constrained schedules — hard dates applied to activities that should float — hide the critical path and destroy the schedule's usefulness as evidence.

Durations should trace back to the estimate: quantity, crew, production rate. A duration nobody can explain is a duration nobody will defend.

Float is a project asset until your contract says otherwise

Float is the amount of time an activity can slip without pushing the completion date. Who is entitled to consume it — the contractor, the owner, or whoever reaches it first — is a contract question, and the answer varies. Some contracts address float ownership explicitly; many do not.

Read the clause before you plan around float, and do not assume that spare time in your schedule protects you from an owner-caused delay. Where the contract is silent, the safer practice is to identify float plainly in the narrative rather than burying it, so the record shows what the schedule contemplated and when.

The monthly update is the record

Updates are not a formality. They are the contemporaneous record of how the job actually went. Each update should carry actual start and finish dates, remaining durations for work in progress, any logic or duration revisions with a stated reason, and a narrative that identifies the current critical path and explains any change to it.

Two habits separate useful updates from useless ones. First, take actual dates from field records — daily reports, inspection records, delivery tickets — not from memory at the end of the month. Second, explain revisions as you make them. A logic change with no explanation looks, months later, exactly like a schedule rewritten to fit a claim.

Issue every update formally and keep the transmittal. An update that was never sent is not a record.

How delay actually gets proven

Entitlement to more time is generally established by showing that a specific event affected the controlling path of the work, that the contractor was not responsible for it, and that the required notice was given. The schedule is how the first element gets demonstrated.

That is why the update history matters more than any narrative written afterward. A delay analysis performed on a schedule that was maintained throughout the job is an explanation. The same analysis performed on a baseline that was never updated is a reconstruction, and reconstructions invite the argument that the contractor's own performance caused the slip.

Document the event when it happens: what occurred, on what date, which activities were affected, what work could not proceed, and what you did to mitigate. Tie it to the RFI, change order, or correspondence that created it. Asking the question in writing at the time is frequently what makes the schedule impact provable later.

Whether an extension of time also carries compensation for extended overhead or general conditions is a separate question governed by your contract. Do not assume the two travel together.

Notice is the clause that quietly decides the outcome

Most contracts require written notice of a delay, or of a condition that may cause delay, within a defined period and often in a defined form and to a named recipient. Missing that requirement can defeat an otherwise sound position regardless of the merits.

The notice periods, the recipients, and the form are set by your contract documents and applicable law, and they differ between agencies and between contracts with the same agency. Find them at award, put them on a one-page reference, and give that reference to whoever is running the field.

Notice is cheap. Give it early, give it in writing, and give it even when you expect the issue to resolve itself. A notice that turns out to be unnecessary costs nothing. A notice you did not send can cost the entire position.

Concurrency and acceleration

When two delays overlap — one owner-caused, one contractor-caused — the analysis becomes materially harder, and the outcome depends on the contract, the jurisdiction, and the quality of the records. The practical defense is the same as everywhere else in contract administration: a clean, contemporaneous record showing what was driving the job week by week.

Acceleration deserves the same care. If you add crews, shifts, or overtime to recover time, document the direction you were given, the reason for it, and the additional cost as it is incurred. Recovery costs absorbed quietly and priced months later are difficult to recover — the change order process exists precisely for this.

Habits that make the schedule worth having

Build the baseline before mobilization and submit it on time. Update it every period, whether or not anyone asks. Reconcile the schedule against the pay application so that progress billed and progress scheduled tell the same story. Keep the narrative short and factual. Never revise logic silently.

One person should own the schedule, and that person should walk the site. A schedule maintained entirely from an office is a forecast. A schedule maintained by someone who has seen the work is a record.

The bottom line

Time is the most expensive thing on a construction project and the hardest thing to reconstruct after the fact. A baseline that reflects how the work will really be built, updated honestly every period and paired with timely written notice, is what turns the schedule from a compliance chore into the strongest document you own. It also tends to make closeout a matter of weeks rather than quarters.

MODRN Inc. is a New York construction management, contract administration, and estimating firm. This article is general guidance on construction scheduling and delay documentation practice and is not legal or contractual advice; scheduling method and submission requirements, float ownership, notice periods and form, time-extension procedures, and entitlement to delay compensation are set by your contract documents and applicable law, which you should always confirm for your specific project.