Straight into the service manual page
WrenchQuarry
More

Florida contractor delays: 2 timing windows to check

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

Florida residential contractors should check the 30-day written-demand window and the 90-day no-work period before delaying a job.

Key takeaways

  • Record when a written demand arrives and when you respond.
  • Check the contract for an agreed work period.
  • Compare payments received with the value of completed work.
  • Document the delay and the owner's notification.

A residential repair job slips for ordinary reasons. A part is backordered, a crew gets pulled to an emergency, or a permit takes longer than anyone planned. Often a slip is only a scheduling problem, and the fix is a new date and a call to the owner. In Florida, though, a long delay can also become a question about whether the contractor kept its obligations to the owner. The contractor statute, Chapter 489, section 126, contains timing rules that matter when a dispatcher is deciding whether a start date can move.

This post covers two timing windows. The first opens when an owner makes a written demand to start work, apply for permits, or refund money. The second covers a period in which a contractor who holds payment above the value of the work performed may not fail or refuse to perform work. The language quoted here comes from the 2025 version of the statute. Statutes change, so check the current text before you rely on it, and talk with a Florida attorney who handles construction disputes once a real disagreement exists.

Window one: the 30-day written demand

The first clock starts when the owner puts a demand in writing. The statute says it may be inferred that a contractor does not have just cause if it fails to apply for the necessary permits, start the work, or refund payments within 30 days of receiving a written demand to do those things from the person who made the payment.

The statute does not say a late start is automatically a violation.

The same section uses a parallel rule for money. It says it may be inferred that a contractor lacks just cause if it fails to perform work, or refund the money received in excess of the value of the work performed, within 30 days after receiving a written demand to do one or the other. So the clock covers two different responses: performing work or returning money that has not been earned.

The practical point is the date. The statute measures the 30 days from receiving the demand, so record the date it arrived and put that date in the job file next to the date you responded. If the demand asks for permit applications, check whether the application has actually been filed, and write down the filing date. A permit that is still sitting on someone's desk does not show that the application was made.

Window two: the 90-day no-work period

The second window is about stopping work. The statute says a contractor who receives money for repair, restoration, addition, improvement, or construction of residential real property in excess of the value of the work performed may not fail or refuse to perform any work for any 90-day period, or for any period that is mutually agreed upon and specified in the contract. The full text is on the same Chapter 489, section 126 page.

Two parts of that sentence set the boundaries. The first is the trigger, which is money above the value of the work performed. A contractor holding a deposit that roughly matches the work finished to date is in a different position from one holding a large upfront payment with little done. The second is the period.

The statute also describes what a failure looks like. It refers to a contractor who failed to perform for the 90-day period, or the period agreed in the contract, without just cause, or who terminated the contract without proper notification to the owner. It describes two separate problems here. One is a gap in work without a good reason. The other is ending the contract without telling the owner properly. A dispatcher who has to push a start date should therefore ask two questions: is there a just-cause reason for the gap, and if the job is being ended rather than paused, has the owner been properly notified?

Do not assume a general reason will establish just cause. "Crew shortage" is a vague reason. A specific, dated reason, such as a permit that has not been issued or a material that was ordered and then confirmed late, gives you something to show. Write down the actual reason when it happens, not a summary written weeks later.

Check the contract for the agreed period

Before you count any days, read the contract. If the contract sets a start date, a completion date, or a schedule with milestones, ask a lawyer whether it specifies the relevant agreed period.

A period remembered from a phone call, or one implied by a text that says "we'll get to it after the holiday," is much harder to stand behind than a date in the signed contract. When a schedule changes, document the change in writing, confirm it with the owner, and attach it to the job file. Keep the original contract and the revision together so the timeline can be rebuilt later.

Look also at how the contract describes the start. If it says work begins on a certain date, the file should show whether that date was kept, moved by agreement, or moved for a reason the owner never accepted. A dispatcher reading the file a month later should be able to answer that without calling anyone.

Some contracts put the schedule in an attachment or an estimate. If that is the case for your job, confirm that the attachment is part of the signed agreement. A schedule that exists only in a side document, and not in the agreement both sides signed, is harder to point to when the timing is questioned.

Compare the deposit with the work done

Owners and dispatchers often watch the calendar and ignore the money. Keep a simple running record for each job with the amount received, the work completed to date, and the difference between the two.

In practice, the pricing in the contract and the completed line items are the starting point. If the difference is large and the job is about to slip, flag it before anyone promises a new date. The person who makes the schedule call should see the money side at the same time as the calendar side.

The statute also gives a refund a role. Ask a lawyer whether returning the unearned difference would help when a job stops without a written demand. That decision belongs with the business owner and, if the amounts are significant, a lawyer, not the dispatcher alone.

Illustrative example: compare payment and work

For illustration, suppose a job has received $1000 and has completed work valued at $0. The difference is $1000. Record both amounts and the work history before moving the start date. This comparison identifies money above the value of completed work; it does not decide whether a delay has just cause.

Pause the job or end it

A pause and an ending can look alike on a calendar, but the statute treats them differently. The stop and restart dates need to be on paper.

Before you tell an owner the job is on hold, decide which one it is. Write the decision in the file with the reason and the date. If it is a pause, record the date work stopped and the planned restart date, and check that the gap fits inside the 90-day period or the agreed period in the contract. If it is an ending, give the owner proper notification, and the record should show when that notice was sent and how it was delivered.

This is a decision for the business and, where money is involved, its lawyer. It should not be settled by a phone call between a dispatcher and an owner who is already unhappy about the schedule.

Sort each delay by cause

Not every delay carries the same weight. A weather day, a supplier who missed a date, a slow permit office, and an owner who has not made a decision are different kinds of delay, and they should be recorded differently. A dispatcher who lumps them all under "delayed" gives the owner nothing to check and gives the business nothing to defend.

Start with the list of open items on the job. For each one, write who controls it, when it was last confirmed, and whether it blocks the start. A permit the business applied for and is waiting on is a different item from a crew scheduling conflict. A material with a confirmed ship date is different from a material that was never ordered.

Then ask which items relate to the two windows. A permit application that has not been filed connects to the written-demand check. A stop in work connects to the no-work check. Items that have nothing to do with either window still need to be tracked, but they do not change the legal picture in the same way.

Decide before the start day arrives

Trouble often starts when a date is promised on the morning it should have started. By then the window may already be running, and the only options left are bad ones. A dispatcher who checks the timeline well before the start date has room to act: order the part, file the permit, or call the owner while there is still time to offer a real alternative.

Build a short check that runs at a fixed point, such as when a job is booked and again whenever a delay appears. Ask three things. Has any written demand come in? Is the work still on track against the contract's schedule? Is the money received still in line with the work performed? Escalate a written demand, an unclear answer, or a mismatch in schedule or payment before promising a new date. Use the dispatch handoff checklist to keep the job record together.

The check does not need to be long. Its job is to make sure the two windows are never discovered by accident. An owner who hears about a slip on the start day has no time to plan around it, and the file will show a thin or missing record of when the business first warned them. A job that slips with a clear reason and a written update is usually manageable. A job that slips with no record, no notice, and a large balance of unearned payment is the kind that ends up in a dispute.

Log every demand and delay

A short log beats memory when a dispute starts. For each job, record the date of every written demand, the date it arrived, the date you responded, the reason for any delay, the notice you sent the owner, and any change to the schedule. Keep the log with the contract and the payment records so the whole history sits in one place.

A workable entry answers four questions in order: when the demand arrived, what it asked for, when the business responded, and what the response said. Each part answers a question someone may ask later, and a reader should be able to follow the sequence without asking you anything.

Use plain words in the log. "Waiting on permit office, application filed on this date" tells a reader more than "delay." Write each entry on the day it happens, and do not rewrite it later. If you have to correct something, add a new line with the correction and the date you made it. A log that changes quietly looks worse than one that shows a correction openly.

Keep the owner's side of the record too. If the owner has not answered a question, has not made a decision, or has held up a payment, note the date and the way the question was sent. That helps show whether a slip came from the job or from the time it took the owner to respond.

Send the new date in a message the owner can answer

When a start date moves, the message to the owner matters as much as the calendar. Give the new date, the reason for the change, and what the owner needs to do, if anything, to keep it. Send it in writing. A phone call is fine as a first contact, but follow it with a short written summary that the owner can answer in writing. The customer arrival update plan can help organize that message.

Avoid vague language like "soon" or "as soon as we can." Give a date range or a condition, such as "once the permit is issued," and say when you will update them next. If the new date depends on an item outside your control, name that item. A written reply that lays out the reason and the next step is also easier to point to later than a message that promises nothing specific.

If the owner pushes back, do not argue the statute in the message. Restate the facts: the reason, the date, and the next update. Legal questions can go to a lawyer if they become real. Reply in the same thread so the record stays together.

Keep the tone plain. Owners who feel informed often accept a slip more easily than owners who learn about it from a missed date. That is general practice, not a legal rule.

When to stop and get advice

Stop and get advice when any of these happen: the owner sends a written demand; the 30 days after a written demand are running out and the work or refund has not happened; the period without work is approaching 90 days or the period specified by the contract; or the money received is well above the value of the work performed. In those cases, talk with a Florida attorney who handles construction contracts before you send the owner a new date.

This post can tell you which clocks exist and where to find them in the statute. It cannot tell you how a court would read the facts of your job, or whether a particular delay has just cause. Those calls depend on the contract, the timeline, and the records. A lawyer who has the full file can make them with more confidence than any general summary.

What to do today

Choose a delayed job and put its contract, payment record, written demands and latest owner update together. Identify who will decide the next action.

Questions about delayed work

Is a late start automatically a violation?

No, a late start alone does not establish a violation. Review the demand, payment, work history and contract before drawing a conclusion.

What should a dispatcher take to a lawyer?

Take the contract, payment records, demand messages, work history and owner notifications. Include the dates and the actual reason for the delay.

Sources

More field guides