Denial of Request for Extension of Time Template

In plain language: Identifies the sending and receiving parties by their full legal names and references the original contract, purchase order, or legal proceeding to which the denial relates.

Common mistake: Referencing only a project name without citing the contract date or number — this creates ambiguity about which agreement governs and weakens the denial's legal footing if disputed.

In plain language: Confirms that the Company received the extension request, states the date it was received, and summarizes what was requested — without admitting that the request was justified.

Common mistake: Omitting the date the request was received — this creates a gap in the timeline that a requesting party can exploit to argue the denial was untimely or that silence implied consent.

In plain language: Clearly and unambiguously states that the extension request is denied and that the original deadline remains in full force and effect.

Common mistake: Using hedged language such as 'we are unable to accommodate your request at this time' — courts and arbitrators have read such phrasing as leaving open the possibility of a future extension, undermining the finality of the denial.

In plain language: States the specific reasons why the request is being denied — contractual, factual, or legal — giving the requesting party a clear basis and protecting the denying party if the matter is later disputed.

Common mistake: Providing no grounds at all, or vague grounds like 'business reasons.' A denial without stated reasons is harder to defend in arbitration or court and may be read as arbitrary or bad-faith conduct.

In plain language: Restates the exact original deadline date and the specific obligation due by that date, eliminating any ambiguity about what performance is expected and when.

Common mistake: Failing to restate the deadline explicitly and simply referring to 'the original terms' — if the original contract date is disputed, a vague reaffirmation provides no independent evidence of the agreed deadline.

In plain language: Puts the requesting party on notice of the specific remedies the denying party intends to pursue — liquidated damages, termination, procurement of replacement services — if the deadline is missed.

Common mistake: Threatening remedies that are not actually available under the contract — for example, claiming liquidated damages when the contract specifies only actual damages — which exposes the denying party to a bad-faith claim.

In plain language: Explicitly preserves all of the denying party's legal and contractual rights, preventing the denial letter itself from being construed as a waiver of any remedy.

Common mistake: Omitting the reservation of rights clause — without it, a court may find that the written denial, by specifying certain remedies, implicitly waived others not mentioned.

In plain language: Directs the requesting party on what to do next — proceed with performance, contact a specific representative, or submit documentation — giving them a clear path forward and reducing the risk of further delay.

Common mistake: Leaving the requesting party with no next step — a denial letter that simply says 'no' with no direction can generate follow-up inquiries that further delay resolution.

In plain language: Confirms which jurisdiction's law governs the interpretation of the denial and specifies how disputes arising from it will be resolved.

Common mistake: Omitting this clause from the denial letter when the original contract includes a governing law provision — the absence creates a gap that opposing counsel can use to argue that the denial is governed by a different or more favorable jurisdiction.

In plain language: Provides the denying party's authorized signatory name, title, and date of signing, creating a formal, timestamped record of the decision.

Common mistake: Having an unauthorized person sign the denial — if the signatory lacks actual or apparent authority to bind the company, the denial may be challenged as not representing the company's official position.

A denial of request for extension of time is a formal written document in which one party to a contract or legal proceeding officially rejects another party's request for additional time to perform, deliver, or comply. It creates a documented, timestamped record that the original deadline was not modified, protecting the denying party's right to pursue remedies — such as liquidated damages or termination — if the deadline is subsequently missed.

Deny the request when the original contract contains a time-is-of-the-essence clause, when no qualifying force majeure or excusable delay event has occurred, when the requesting party contributed to its own delay, or when granting an extension would materially prejudice your project timeline or downstream obligations. Always evaluate the commercial relationship and the risk of litigation before issuing a denial — a brief extension may cost less than a protracted dispute.

In most jurisdictions, a verbal denial is legally valid but practically difficult to prove. Most commercial contracts require notices — including modifications and denials — to be in writing and delivered by a specified method such as certified mail or email. Issuing a written denial creates an unambiguous, dated record that eliminates disputes about whether a denial was ever communicated and protects your right to enforce the original deadline.

Yes. The requesting party may respond by submitting additional documentation supporting their request, initiating the dispute resolution process specified in the contract (mediation, arbitration, or litigation), or asserting that a force majeure or excusable delay event applies. Your denial letter should therefore be grounded in specific contractual language and factual reasoning to withstand challenge.

Informal approval of a delay — through conduct, silence, or a casual email — can constitute a waiver of strict deadline rights under the doctrine of estoppel in most common-law jurisdictions. If you then issue a formal denial, the requesting party may argue that you already granted the extension and that the denial is ineffective. To avoid this, issue denials promptly in writing and include a reservation of rights in all correspondence that touches on timelines.

No. A denial holds the original deadline firm, but a breach does not occur until the requesting party actually fails to perform by that deadline. The denial puts the party on notice that time will be enforced and that remedies will follow non-performance — but you must still wait for the deadline to pass before asserting breach and pursuing damages or termination, unless the party has already repudiated the contract.

Generally yes, but the remedy for late performance may be limited to actual proven damages rather than termination or liquidated damages. Without a time-is-of-the-essence clause, courts in many jurisdictions treat deadlines as important but not automatically grounds for termination — meaning a denial letter is still valuable as a notice document but may need to be followed by a formal notice making time of the essence before termination rights arise.

In litigation, denying an opposing party's request for additional time (for example, to respond to a pleading or produce documents) is typically accomplished through an opposition filed with the court rather than a standalone letter. This template is most directly applicable to contractual deadlines between private parties. For court-filed oppositions to motions for extension, consult the applicable procedural rules and consider engaging legal counsel.

This depends on the contract terms and the jurisdiction. Many commercial contracts require a cure period — typically 5 to 30 days — after a notice of default before remedies can be exercised. Even where no cure period is contractually required, providing a short, documented opportunity to perform before exercising termination rights can reduce the risk that a court will characterize your conduct as premature or disproportionate.