In brief
This calculator counts contract deadlines forward from an effective (ratification) date. It treats the effective date as day zero — day 1 is the next day — which matches many form contracts but not all of them. Each deadline can count in calendar days or business days; business-day mode skips Saturdays, Sundays, and U.S. federal holidays on their observed dates. A calendar-day deadline that lands on a weekend or holiday is flagged, not moved, because forms disagree about whether it rolls. The output is a full date table you can print and check against the file. It is educational: your contract’s own definitions control every one of these conventions, so verify each computed date against the document before you act on it.
Hand-counting contract deadlines looks like arithmetic and behaves like a trap. The first snare is day zero: many form contracts start counting the day afterthe effective date, so “ten days from ratification” on a Monday contract is not the following Wednesday night but Thursday — and an agent who counts Monday as day one delivers every notice a day early at best, and builds a mental calendar that is wrong everywhere at worst. The second snare is the word “days” itself, which in a single contract can mean calendar days in one paragraph and business days in another. Three business days and three calendar days are the same number and, over a holiday weekend, five days apart.
The third snare is holidays. A business-day count has to know that the third Monday in February is not a business day, that Juneteenth exists, and that a holiday landing on a Saturday is generally observed the Friday before — details nobody holds in their head on a Friday afternoon with an inspection notice due. This is the counting machinery that decides whether a notice was timely, and we’ve written a full guide to the deadlines that decide a deal — which ones bite, which ones waive themselves silently, and why they slip. This page is the companion tool: the counting, done correctly, with the assumptions in plain sight.
Use it the way a careful coordinator would use scratch paper. Set the effective date, adjust each row to match what your contract actually says, add the deadlines your form has that ours doesn’t, and then — this part is not optional — check every computed date against the contract language itself.
Interactive tool
Contract deadline calculator
How this tool counts: day 1 is the day after the effective date— the effective date itself is day zero. Business-day mode skips Saturdays, Sundays, and U.S. federal holidays (using observed dates when a holiday falls on a weekend). Calendar-day mode counts every day and flags — but does not move — a deadline that lands on a weekend or holiday.
Deadlines
Seeded as 15 calendar days from the effective date, but many forms count title objections from receipt of the title commitment instead — often around 5 business days after it arrives. Check your form’s trigger.
This window often runs from delivery of the resale packet, not from the effective date.
Computed dates
Choose an effective date above and every deadline below will fill in.
Counting conventions vary by form and state — verify every date against your contract. This tool assumes day 1 is the day after the effective date and uses U.S. federal holidays only; your form may define days, triggers, and holidays differently. The governing document controls.
How the math works — and where it stops
A deadline calculator is only as trustworthy as its stated assumptions, so here are ours, plainly.
Day zero is the effective date. Counting starts the day after ratification: a three-day deadline on a contract effective Monday computes to Thursday, not Wednesday. This is the convention many form contracts use, and it is the single assumption most worth verifying against yours, because a form that counts the effective date as day one shifts every date on this page back by a day.
Business days exclude weekends and U.S. federal holidays.The calculator implements the federal holiday calendar for any year — the fixed dates (New Year’s Day, Juneteenth, Independence Day, Veterans Day, Christmas) with their observed shifts when they fall on a weekend, and the floating ones (MLK Day, Washington’s Birthday, Memorial Day, Labor Day, Columbus/Indigenous Peoples’ Day, Thanksgiving) computed by rule. What it does not know: state holidays, court holidays, or a form that defines business days as days a particular office is open. A number of states’ forms use one of those narrower definitions.
Calendar-day landings are flagged, never moved. When a calendar-day deadline computes to a Saturday, Sunday, or federal holiday, the calculator shows the true landing date with a note, because form contracts split here: many roll the deadline to the next business day, others let it stand, and a few roll only certain deadlines. Silently rolling would be wrong for some forms; silently not rolling would be wrong for others. Showing the landing and telling you to check is the only honest option.
Some deadlines don’t start where this tool starts.Everything here counts from the effective date, but real contracts run several clocks from other trigger events: title objection periods commonly run from receipt of the title commitment, HOA or resale-document reviews from delivery of the packet, and cure periods from the date of a notice. The seeded title and HOA rows carry footnotes for exactly this reason. And one deadline near closing follows federal law rather than the contract at all — under the TRID rule, the Closing Disclosure must reach the borrower at least three business days before consummation, counted by that rule’s own definition of a business day. That one has its own guide.
A deadline is a date plus a counting convention. Everyone remembers the number. It’s the convention that gets deals in trouble.
One more limit worth naming: this tool computes dates once, from what you type. A live transaction re-derives its dates constantly — an amendment moves closing, a late title commitment restarts the objection window, an extension re-anchors the financing deadline — and every change ripples through the schedule. If the calculator is your system of record, someone has to remember to come back and re-run it after every signature. That someone is usually the person with the least spare attention in the file, which is how the discipline of preventing closing delays ends up being mostly the discipline of re-counting on time.
That gap — between a correct one-time count and a schedule that stays correct — is the part Ratifylyexists for. It reads the forwarded paperwork and email attachments a transaction generates, extracts the parties, the price, and every date with its counting convention, and builds the timeline from the documents themselves rather than from someone’s re-typing. When an amendment lands, it re-reads the paper and re-flows the schedule; the agent, client, broker, lender, and closing office all watch the same live timeline; and deadlines escalate before they hit, with a human approving every call. The calculator above is the manual version of the first step. The how-it-works page shows the rest.
This calculator and article are educational and general in nature — they are not legal advice, and the computed dates are not a substitute for reading your contract. Counting conventions — day zero, business-day definitions, holiday treatment, and whether a weekend landing rolls forward — vary by state, by form, and by the specific language of your agreement, and several deadlines run from trigger events other than the effective date. The one uniform federal deadline mentioned here, the Closing Disclosure’s three-business-day rule, comes from the CFPB’s TRID rule and uses its own business-day definition. Verify every date against the contract itself, your state association’s form library, your broker or the closing office, and a licensed attorney for any particular transaction.
Questions agents actually ask
Should I count business days or calendar days?
Whichever your contract says — and it may say both, on different deadlines in the same document. Many form contracts define a default (calendar days is a common one) and then carve out specific deadlines that run in business days; others define days one way in the body and another way in an addendum. There is no industry-wide convention you can safely assume. The calculator gives every row its own business/calendar toggle for exactly this reason: read the definition section of your form, set each row to match, and when the form is silent, ask the broker or the closing office rather than guessing.
Does the effective date count as day zero?
In many form contracts, yes — the day of ratification is day zero and counting starts the following day, which is the convention this calculator uses. But it is a convention, not a law. Some forms count from delivery of a document rather than from ratification, some start periods on the day of a triggering event, and a few define the first day differently for different deadlines. A one-day disagreement about day zero is enough to turn an on-time notice into a late one, so check how your specific form words it: phrases like 'within five days after the Effective Date' versus 'within five days of ratification' can be read differently, and the form's own definitions control.
What about holidays — federal, state, or otherwise?
In business-day mode, this calculator skips Saturdays, Sundays, and U.S. federal holidays, using the observed date when a holiday falls on a weekend (Saturday holidays observed Friday, Sunday holidays observed Monday). That matches how many forms treat business days, but not all of them: some states' forms also exclude state holidays, some define business days as days the relevant office is open, and some ignore holidays entirely. In calendar-day mode, the calculator flags a deadline that lands on a weekend or federal holiday rather than silently moving it, because forms split on what happens next — a number of them roll the deadline to the next business day, and others let it land where it lands. Your form's definition wins.
Can I rely on this calculator for my transaction?
No — treat it as an educational worksheet, not a source of truth. It applies one reasonable set of conventions (day zero on the effective date, federal holidays, no automatic rolling) to numbers you type in, and any of those conventions can differ from what your contract actually says. Some deadlines also run from trigger events the calculator cannot see, like receipt of the title commitment or delivery of an HOA resale packet. Compute your dates here, then verify every one against the contract language itself, and confirm anything ambiguous with your broker, the closing office, or an attorney. The governing document controls, always.