How to Review a Time-of-the-Essence Delivery Deadline

Remy, Ops at a 33-person UK health-tech, is about to treat “time is of the essence” as a motivational stamp because sales said it keeps everyone honest. How to review a time of the essence delivery deadline is a 25-minute hunt: mark which dates are of the essence, decide whether one miss is for-cause or a cure plus delay credit, clock the inputs you control, then demand writing — not Slack.

September 2026. Finance has said yes on a vendor implementation packet — the MSA, SOW and Schedule 2 Remy will actually kick off. The MSA — master services agreement, the vendor frame this PAS hangs on — is not the fight. Clause 8: “Time shall be of the essence regarding any date for delivery by the Supplier of any good or service specified in this Agreement and the SOW, and regarding all dates and times specified herein.”

Schedule 2, an exhibit — the attached date list — puts Go-Live on 15 October 2026, weekly Friday status reports, and invoice dates Net 14 in the same grid. Access, data and approvals: “promptly.” No clock. No day-for-day. Termination for cause on any missed date. Last week’s two-day UAT slip: the AE Slacked “fine.” Kick-off is Monday.

Typical mistake: treating essence as a stamp. In England and Wales, LPA 1925 s.41 still points to equity’s default: time is not of the essence. Remy’s Clause 8 is the different intention. Topalsson (2023): any delay, however small, went to the root. Whitburn (30 July 2026): “strictly no later than” was enough. Sprintlaw: a blanket clause invites termination over a late weekly update. Remy’s Clause 8 copies Topalsson, then adds “all dates and times specified herein.”

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

Which dates are of the essence — not every calendar line?

There is no general rule that time is of the essence for the contract as a whole. Essence attaches to named obligations, or to every date if the sentence says so. Write two lines: the essence sentence, then named / any / all dates. Circle weekly status and invoices.

Do: hunt “must,” “strictly,” and “condition,” not only the phrase. Don’t: treat every calendar line as motivational. For example, Trethowans: essence is an obligation, not the whole paper. SGA 1979 s.10: payment is not of the essence unless a different intention appears — Remy’s “all dates” is that intention. SGSA 1982 s.14: if time is not fixed, implied term is a reasonable time. Schedule 2 does fix dates. If the fight is deliverables, acceptance, or change orders, that is a different hunt — the SOW review checklist. Write “weekly status inside essence?”

What does one miss buy — for-cause, or a cure and a delay credit?

A time-of-the-essence date is usually a condition. One miss can be a for-cause exit, even if the delay looks trivial. That is a different, easier door than terminate-for-substantial-breach. Mark “for-cause on any miss” or “cure / delay credit / neither.”

Topalsson: any delay goes to the root, no matter how small. One milestone was 11 days late. Union Eagle: ten minutes was enough. In practice, Sprintlaw prefers a 3–5 Business Day cure. If the paper names a pre-agreed daily sum for delay, that is liquidated damages — a different hunt. Do: pair essence with a short cure. Don’t: assume you will “just chase them.” SCL: IT milestones without express status are often innominate. Remy has express status.

Why does a “promptly” customer input still keep 15 October live?

If Go-Live is of the essence and your access, data and approvals are only “promptly,” the vendor can still hold 15 October. Clock each input you control. Write access / data / approvals — clocked Y/N — day-for-day Y/N.

Trethowans: essence is often also on the customer’s data or documents. Sprintlaw: delay in Data Room Access extends the Completion Date day-for-day. SCL: if you caused the slip, a date can become reasonable time — unless the paper keeps 15 October. Remy’s “promptly” with no clock is a fail. The hidden risk is a for-cause notice after Remy’s own team delayed the data room. Do: day-for-day. Don’t: leave customer inputs as wallpaper.

How do you keep force majeure and customer delay as one-line fences?

If essence is silent on force majeure and customer delay, the hair trigger stays live when the world, or you, caused the slip. Write “FM carve-out Y/N — customer-delay carve-out Y/N.” Then stop. Name the fences; do not hunt the FM list here.

EM Law: force majeure may excuse delay; an extension of time can weaken essence. If the fight is the FM event list, notice clock, and longstop, that is how to read a force majeure clause — one sentence, then leave. Remy’s Clause 8 has no customer-delay carve-out. Slack is not a carve-out. Do: name both fences. Don’t: assume “they’ll understand we delayed them.”

When to treat a Slack “fine” as not an extension

An informal yes can waive essence, or it can leave the old date live. Neither is a variation unless the paper’s writing path is used. Write “written EoT / named signatory / Slack only.”

LegalVision (18 May 2026): change the date in writing if both parties agree. Sprintlaw: notify within 3 Business Days; essence stays on the new date. Slack “yes” can be waiver. Topalsson: the first terminate notice failed on superseded December Plan dates after a March Plan extension. If the paper has a no-oral-modification clause, a Slack “fine” is not the path. Do: use the variation mechanics. Don’t: file the screenshot as the extension. Under Monday pressure that is a costly error.

How do you decide: narrow dates, drop essence, or walk?

Narrow if Go-Live stays of the essence and weekly status, invoices, and “promptly” come out. Drop essence if dates should be targets plus a credit, not for-cause. Walk if Clause 8 covers any date and all dates, weekly status is of the essence, there is no customer-delay carve-out, and the only extension is Slack.

Success bar: a one-page log plus one sentence that would pause Monday. Remy already has three: weekly status inside essence; no customer-delay carve-out; Slack only. Workflow: which dates are of the essence → one miss = for-cause or cure + delay credit → access / data / approvals clocked → FM and customer-delay carve-outs → writing not Slack “fine” → narrow / drop / walk. Do: spend counsel — a solicitor for England and Wales — on those three misses. Don’t: mark this paper a green light before you sign. Optional: upload the same PDF to document analysis for a first-pass — a machine extract before a human reads every page. A human still opens Clause 8 and verifies every High flag — a high-severity extract a person must still open.