One date moves and six deadlines move with it
Aug 22, 2026 · 7 min read
The sellers signed on Thursday instead of Tuesday.
You update the contract date, and you are done, because it was a two-day change to one field.
Then the inspection deadline you put in your calendar three weeks ago is wrong. So is the financing deadline, the appraisal date you gave the lender, the walkthrough you penciled in with the buyer, and the reminder you set to chase the homeowners association (HOA) documents.
Every one of them was calculated from the contract date. You changed the contract date.
5–10
business days for the inspection period, in most states
14–21
days for the appraisal contingency
30–60
days for the financing commitment
Common bands, not rules. Yours come from the contract in front of you, and California runs its own convention.
Every one of those is counted from somewhere. Move the somewhere and they all move with it.
Almost no deadline in a contract is a date
When you read a contract the deadlines look like dates, because whoever filled it in computed them and wrote them down. That is not what the contract says. The contract says a number of days from a reference point.
Inspection periods commonly run five to ten business days after acceptance, though convention varies sharply by state; California buyers customarily get 17 days to remove the inspection contingency. Appraisal windows typically fall in 14 to 21 days. Financing runs 30 to 60.
Every one of those is an offset. Change the anchor and they all land somewhere new.
Illustrative day counts. Yours come from the contract in front of you.
Two features of that picture cause most of the damage.
Some deadlines chain off other deadlines. The consideration period runs from the end of the inspection period, not from acceptance. A two-day change to the contract date moves inspection by two days, which moves consideration by two days. It arrives second-hand.
The walkthrough counts backwards. It is anchored to closing. So it is the one date that does not move when the contract date moves, and shifting everything forward by reflex gets it wrong in the other direction.
What a missed one actually costs
This is not a tidiness problem.
Miss a contingency deadline and the contingency can be treated as waived, because you did not exercise the right inside the window. Miss the inspection deadline specifically and the buyer can no longer request repairs or credits, and may be required to purchase as-is or risk the earnest money.
Earnest money typically runs 1–2% of purchase price.
Deposits vary by market and negotiation; 1–2% is the common band.
The stated cause is rarely exotic. One write-up puts it plainly: the agent is focused on other deals and does not track the contingency date, and nobody sends the extension until it is too late.
Where the manual version breaks
The failure is not that someone cannot do arithmetic. It is that the arithmetic gets done once and then copied into places that do not know they are copies.
You compute the dates when the contract arrives. Into your calendar. Into a reminder app. Three of them texted to the buyer, one to the lender, a different one to title.
Six independent copies of a number derived from a field that can still change.
When the contract date moves you have to remember all six. You remember four.
The second failure is quieter and worse: a deadline that never applied. A cash buyer has no financing contingency. If your checklist generated one anyway, you are tracking a deadline that does not exist, and the day it "passes" you either ignore it, which teaches you to ignore the others, or you chase a lender who was never involved.
Waived inspections behave the same way. Waive it and the consideration period that chained off it should disappear, not sit there pointing at a date computed from an event that will never happen.
Business days are not days
One more trap, and it produces off-by-two errors nobody catches until the deadline was yesterday.
Many contracts count contingency windows in business days. Some count calendar days. Some switch between the two inside one document without flagging it.
Ten business days from a Thursday is two weeks and a day later. Ten calendar days from a Thursday is the following Sunday. Four days apart, and one of them lands on a weekend when nobody answers the phone. Federal holidays widen the gap again, and the other side may be counting differently than you are.
If you take one habit from this: when you write a deadline down, write down what it was computed from. "Inspection ends Aug 21" is a fact with no provenance. "Inspection ends Aug 21 — contract Aug 7, 10 business days" is a fact you can re-derive when the anchor moves.
Stop storing answers
The principle is the same one that applies to commission math, and we think it is the single most useful idea in transaction tracking: store the inputs, derive the outputs.
Keep the contract date and the day counts the parties agreed to. Compute the deadlines every time you look. A change to the contract date becomes a change to one field, and everything downstream is correct by construction rather than by memory.
We are not above this. We once published a screenshot to our own homepage with the words "Invalid Date" printed inside it, in the middle of a sentence explaining how a deal had been priced. The date was there; it simply was not in a shape anything could read. It sat there for a week, and what caught it was a person reading the picture rather than any check we had written.
The exception is anything already executed. Once an inspection has happened, the date it happened on is a fact and should be stored as one. Pending deadlines derive. Completed events are recorded.
What this does not solve
Deriving dates correctly does not mean the parties agree on them. The other side's agent is running their own arithmetic, possibly counting business days differently, possibly working from a different contract date if the signature timing was ambiguous. Computed dates are your position, not a consensus. The confirming email is still the job.
And no date engine knows what your state's forms say. Day counts, whether weekends count, what happens when a deadline lands on a holiday. All of it is contract-specific and jurisdiction-specific. None of this is legal advice.
KeyFlow derives the key dates from the contract date and the day counts you enter, chains the dependent ones, and drops the deadlines that do not apply when a buyer is paying cash or an inspection is waived. Change the contract date and the rest follow. We also, now, check that a date is actually a date before we print it.
Sources: HomeLight — buyer contingency periods · Brokerless — how long contingencies last · Skyworks Group — contingency period timelines · US Realty Training — contingencies every buyer should know · HomeKey Title — what happens if you miss a contingency deadline · Top Idaho Real Estate — missed contingency deadline · Freedom RES — what happens when you miss a contract deadline
- contracts
- deadlines
- transactions