Project Running Late? How to Document a New Deadline

Contractor documentation, plain and practical · Article 7 of 12 · September 6, 2026

The countertop fabricator calls: templating pushed a week, fabrication pushed two. The inspector's next opening is nine days out. The prior job ran long, or the customer took three extra weeks choosing tile, and the start date everyone remembers is no longer real.

Schedules slip. That is construction. Jobs are lost not by the slip itself but by the silence around it: the customer watching a date pass with no explanation, then filling the silence with the worst available theory.

Wisconsin has something specific to say about this moment, and the practical habit it points to is one most good contractors already believe in: say it early, say why, propose new dates, and get agreement in writing.

What Wisconsin expects on covered projects

Under Wis. Admin. Code section ATCP 110.027, a contractor on a covered home-improvement contract must give the customer timely notice of any impending delay if performance will be delayed beyond a deadline specified in the contract. The notice must state the reasons for the delay and propose new deadlines for beginning and completing the work. And when a written contract is required under ATCP 110.05 or the customer signs a written contract, a change in performance deadlines is not effective unless the customer agrees to it in writing. Wisconsin law recognizes that an electronic record can satisfy a writing requirement.

Notice the word impending. The rule contemplates notice before the deadline passes, when the delay is coming into view, not a retrospective explanation after the date is already gone.

The rule also recognizes that not every delay is the contractor's responsibility, including delays caused by the customer's own actions or inactions. And Wisconsin's home-improvement rules address customer remedies in some situations where required delay notice is not given or a new deadline is not agreed, which is a good question to put to your attorney about your own contract terms.

Two boundaries to keep in mind. First, ATCP 110 is not universal contractor law: its definition of "home improvement" excludes construction of a new residence and major renovation of an existing structure, so confirm what applies to the particular project. Second, remember why the dates exist at all: when ATCP 110.05's written-contract conditions apply, start and completion dates or time periods are required material terms of the contract, which this series covered in the article on which document a job needs. A deadline that was a required term going in deserves a documented change going out.

The four parts of a useful delay notice

A delay notice is short. It contains:

The affected deadline. Name the date or time period in the contract that will be missed.
The reason. Plain and factual: supplier delay, inspection scheduling, added work from an approved change order, weather, a prior discovery.
The new proposed dates. A new start date, a new completion date, or both. Propose real dates you can stand behind, not optimistic ones that set up the next notice.
The request for written agreement. Ask the customer to approve the new dates in writing, and make that easy to do.

The contract anticipates substantial completion by November 21. The countertop fabricator has delayed templating and fabrication by two weeks due to a material backorder, which affects the countertop installation and the plumbing trim that follows it. We propose a revised substantial completion date of December 5. All other contract terms remain unchanged. Please confirm your written approval of the revised date.

That is the whole document. It took longer to dread than it would take to write.

Connect the delay to its cause in writing

When the delay flows from something already documented, say so and reference it:

An approved change order added work. The best practice is to state the schedule effect inside the change order itself, as this series has said from the first article. If a change order was approved without a schedule effect and one emerges, the delay notice should reference that change order by number.
A concealed condition added repair work. Reference the discovery record and its approval.
The customer's own timeline moved. Late selections, restricted access, and late owner-supplied products are legitimate reasons, and they belong in the notice as plainly and respectfully as a supplier delay would: "The tile selection anticipated by October 15 was finalized on November 3, which shifts the tile installation and the work that follows it."

Documenting customer-caused delay is not an accusation. It is the same factual record-keeping applied evenly. It is also considerably easier when the scope of work assigned selection deadlines and responsibilities in the first place.

Chained delays: renumber, recompute, restate

Real schedules slip more than once. The discipline that keeps a slipping schedule honest is the same discipline that keeps change-order math honest:

Each notice states the current agreed completion date, not the original one, as its starting point.
Each notice proposes a specific new date, so there is never a period where the job has no operative completion date, only a vague "we're running behind."
Vague extensions do not accumulate. "A couple extra weeks" said three times is not a schedule. Three written notices moving November 21 to December 5 to December 12 is.

If a date genuinely cannot be known because it depends on an event outside your control, propose the most realistic date you can and say what it depends on. How far event-based language can carry weight on a covered project is a question for your attorney; the rule asks for proposed new deadlines, and a specific date is always the cleaner answer.

What to say without sounding like excuses

The delay conversation goes better when the notice reads like management, not apology.

When a supplier slips

I want to get ahead of a schedule change. The window package moved two weeks at the factory. Here is what that affects, here is the revised completion date I can stand behind, and here is what we are doing in the meantime so the crew stays productive. I am sending the revised date for your written approval today.

When the customer caused it

Thanks for finalizing the tile selection. Since the selection came in after the October 15 date we planned around, the tile work and everything downstream shifts. I am sending a revised completion date for your approval so the schedule on paper matches the real one.

When you caused it

Our prior project ran past its date, and that pushes your start by four working days. That is on us. Here is the new start and completion date in writing for your approval, and I will confirm the crew's arrival the day before.

Customers can absorb almost any honest date. What they cannot absorb is discovering that the date they were counting on was quietly abandoned.

What not to do

Let the deadline pass and treat the customer's phone call as the notice.
Give the reason without new dates, leaving the job with no operative schedule.
Propose new dates verbally on a covered written contract and treat a nod as agreement.
Blame a supplier in writing for a delay that was actually sequencing on your side. The reason in the notice should be true.
Stack vague extensions instead of restating one clear, current completion date.
Forget that an approved change order was the right place for the schedule effect, and try to introduce it weeks later as if it were new information.

The habit, compressed

When a deadline is going to move: notify promptly while the delay is impending, state the true reason, propose specific new start and completion dates, request written agreement, and file the approval with the contract and its change orders. On a covered written contract in Wisconsin, that written agreement is what makes the new deadline effective. On any contract anywhere, it is what keeps the customer inside the project instead of outside it, guessing.

Where ScopeAccord fits

ScopeAccord keeps the schedule story attached to the documents that caused it.

Describe the delay by voice or text: what moved, why, and the new dates. The interaction is conversationally AI-native, organizing the notice while the legal document structure stays deliberately deterministic, using counsel-reviewed Wisconsin templates, and keeping change orders, discoveries, and schedule changes connected to the same contract record with verified running totals.

You review and approve every date and every word before anything is final. ScopeAccord does not replace your judgment, your scheduling, or your attorney. It makes the notice easier to send today than to explain next month.

Try ScopeAccord →

Learn more about ScopeAccord.