How to Calculate Contract Deadlines That Never Slip

Every contract deadline you’ll ever calculate comes down to five questions: What’s day zero? Does this contract count calendar days or business days? What happens when a deadline lands on a weekend or holiday? What time of day does it expire? And when an anchor date moves, what moves with it? Answer all five correctly and deadlines don’t slip. Miss one and you’re wrong by a day — which in this business is the same as being wrong entirely.

We’ll take them in order.

Question 1: What’s day zero?

In virtually every standard purchase contract, the effective date is day zero. It doesn’t count. Day one is the next day. A contract effective Monday with a 10-day deadline expires Thursday of the following week, not Wednesday.

Simple — and still the most commonly botched step in the whole process, because “10 days from Monday” reads naturally as “count Monday.” When two sides of a deal count differently, each side’s calendar is internally consistent and one of them is wrong, which is how you get a buyer’s agent confidently terminating on what the listing side has already logged as the day after expiration.

Before you count anything, confirm the effective date itself. It’s the date of final acceptance — filled in by hand, frequently missing, occasionally contradicted by the signature dates around it. An intake that doesn’t verify the effective date is an intake that calculates every other date in the file from a guess.

Question 2: Calendar days or business days?

There is no national answer. The contract form in front of you defines its own day-counting rules, usually in a computation-of-time clause, and the variation between states is bigger than most people working in one state ever realize:

• Texas (TREC): calendar days, all of them, for everything. Weekends and holidays count. A 7-day option period includes its weekend, full stop.
• Florida (FR/BAR): hybrid. Time periods of 5 days or less are computed without Saturdays, Sundays, or national legal holidays. Longer periods count calendar days — but any deadline that lands on a weekend or holiday extends to 5:00 p.m. the next business day.
• Everywhere else: somewhere on that spectrum, defined by the state association or commission form, and occasionally overridden by an addendum. The clause is one paragraph. Read it once per form revision and write down what it says.

The dangerous TC is the multi-state TC running on instinct trained in a single state. Florida instincts make you think a 5-day Texas period is longer than it is. Texas instincts make you panic about a Florida deadline that was never going to land on Sunday in the first place. When we built TC Track we encoded contract date rules for all 50 states precisely because we didn’t trust anyone — including ourselves — to context-switch between these rules from memory on a Thursday afternoon.

Question 3: What happens on weekends and holidays?

Three possible behaviors, and a single contract can contain all three:

1. The deadline stands. Texas option period: day 7 is Saturday, it ends Saturday. No mercy.
2. The deadline rolls forward. Texas earnest money and option fee delivery: due date lands on a weekend or legal holiday, delivery extends to the next day that isn’t. Florida does this for nearly everything.
3. The days were never counted. Florida’s 5-day-or-less periods skip weekends and holidays during the count itself.

So “what happens on weekends?” isn’t a per-contract question — it’s a per-deadline question. The same Texas file contains a deadline that rolls and a deadline that doesn’t, four paragraphs apart.

Holidays add a second layer: which holidays? Most forms mean legal holidays — the eleven federal ones, sometimes state holidays too, and state holidays vary in ways that surprise people. When a federal holiday falls on a Saturday it’s observed the Friday before; on a Sunday, the Monday after. Whether your deadline cares about the actual date or the observed date is — again — a question the form answers and memory doesn’t. We wrote up the messiest version of this in what happens when closing falls on a federal holiday.

Question 4: What time does it expire?

A date without a time is half a deadline. Texas option terminations must be received by 5:00 p.m. local time where the property is located. Florida’s rolled deadlines extend to 5:00 p.m. of the next business day. Wire transfers have institutional cutoffs hours before the bank closes. Recording windows close when the county says they close.

Every deadline in your system should carry a time, and where the form specifies one, it’s the form’s time — not end-of-day, not “sometime Tuesday.” The gap between “due Tuesday” and “received by 5:00 p.m. Tuesday” is exactly nine hours wide, and every one of them has killed a termination notice somewhere.

Question 5: When one date moves, what moves with it?

This is the question that separates deadline calculation from deadline management, because you don’t calculate a file’s dates once. You calculate them every time an anchor moves — and anchors move constantly. The closing date slips a week. An amendment extends the financing contingency. The effective date itself gets corrected.

A typical residential file carries 8-15 dates downstream of the closing date alone: final walkthrough, loan doc delivery, utility transfers, HOA resale packet, funding, possession. Move closing and every one of them needs recalculating — with all four previous questions applied fresh to each one, because the rolled deadline that used to land on Wednesday may now land on Memorial Day.

Done by hand across a 20-file caseload, this is 2-3 hours a week of pure recalculation — and it’s the step where fatigue errors live, because cascade math always arrives attached to a file that’s already having a bad week. It’s the single strongest argument for putting dates in a system where deadlines are defined by their relationships (“10 days after effective date,” “3 days before closing”) instead of stored as values. In TC Track, that’s exactly how due dates work: change the anchor and the dependency graph recalculates the whole chain, weekend and holiday rules included. However you implement it — software, or a spreadsheet with formulas you actually trust — the principle stands: never store a computed date where you should store the rule that computes it.

Putting it together: the intake ritual

The five questions compress into a repeatable intake process that takes about ten minutes per file:

1. Verify the effective date against the signatures. Day zero confirmed.
2. Extract every deadline from the contract and addenda — the contract-to-close checklist is the net that catches the ones people forget.
3. Apply the form’s day rules to each: calendar or business, roll or stand, and the time of day.
4. Attach each date to its rule, not just its value, so the cascade can be re-run when — not if — something moves.
5. Set reminders ahead of the fuse, sized to the deadline: 24 hours for an option period, a week for closing-dependent logistics.

Run that on every file and deadline calculation stops being a skill you exercise under pressure and becomes a system that exercises itself. The five questions still get answered — they just get answered once, in a template, instead of fifty times a month from memory.

Related guides

• Texas option period: calendar days or business days?
• What happens when closing falls on a federal holiday?
• The contract-to-close checklist TCs actually use
• How many transactions can one TC handle at once?
• Running TC work on spreadsheets: what it really costs