The Reasons That Rarely Work
Applications to be excused rely on a surprisingly small set of explanations, and most of those belong to a category that decision-makers have heard several thousand times before and have rejected on very nearly as many occasions.
The rule in short
Certain explanations for missing a deadline fail with great consistency: pressure of work, not knowing about the period, an internal system failure, waiting for instructions, and reliance on somebody else. Recognizing that an application rests on one of them is useful, because it redirects the effort toward the factors that can still be influenced.
Knowing which explanations fail is more useful than knowing which succeed, because it changes what an application concentrates on rather than merely how it is worded.
Pressure of work
It is the most frequent explanation offered. And the one decision-makers have seen most often, which is precisely why it carries so little weight.
It implies a choice. Somebody decided what to prioritize, and this deadline lost, which is an admission rather than an excuse.
It is within the party's control. Resourcing and workload management are matters for the party, not for the forum to absorb.
It could have produced an extension request. Anybody who knew they were overloaded had the option of asking for time before the deadline.
It rarely comes with evidence. Assertions about workload are seldom supported by anything a decision-maker can assess.
It suggests a pattern. If workload caused this failure, the natural question is what else is at risk.
It is worse from a professional. Where an adviser is involved, the explanation reflects on the arrangements rather than on circumstances.
It occasionally works. Where an exceptional, evidenced and short-lived situation is described specifically rather than generally.
It is better omitted than asserted. An application resting on the other factors is stronger than one adding a weak reason to them.
Not knowing about the deadline
Periods are published. Rules and orders are available, and not having read them reflects on diligence rather than excusing anything.
Documents state their deadlines. Most notices identify the period, which makes ignorance difficult to sustain.
Unrepresented parties get some latitude. Though considerably less than they expect, and it decreases as a matter progresses.
Not having received the document is different. That is a non-receipt argument, which is a genuine and separate route, per the notice nobody ever saw.
Miscalculating is different again. An honest arithmetic error is treated better than an admission of never having looked.
It raises the address question. Not knowing frequently traces back to a record nobody updated.
It invites a review of everything else. If one deadline was unknown, the decision-maker wonders about the others.
It does not sit well with representation. A represented party asserting ignorance shifts the question to the adviser.
It has an honest version. Where a deadline genuinely was obscure or newly introduced, saying so specifically is legitimate.
| Explanation | Usual reception | Better framing |
|---|---|---|
| Pressure of work | Poor | Omit; lead with promptness |
| Did not know | Poor | Non-receipt, if true |
| System failure | Poor alone | Pair with the fix |
| Awaiting instructions | Poor | Should have sought time |
| Miscalculation | Moderate | State it plainly |
Internal system and staffing failures
They are within the party's control. Diary systems, staffing and cover arrangements belong to the party rather than to circumstance.
They suggest a systemic risk. A failure caused by a process problem implies other matters are exposed to the same thing.
They are better paired with a fix. An explanation accompanied by what has changed reads far better than one that stops at the cause.
Staff absence is foreseeable. Holiday, illness and turnover are ordinary events that cover arrangements exist to address.
Handovers are a known risk. Which is why they attract little sympathy when they produce a missed date.
Software failures need evidence. Assertions about a system going wrong require records, per system outages on the last day.
They frequently reveal a pattern. Internal explanations tend to surface repeatedly from the same source.
Candor helps. Admitting an internal failure honestly is better received than disguising it as something external.
The fix is the argument. What has changed since is the part of this explanation that carries any weight at all.
Applications are not improved by elaborating an explanation that will not carry weight. One factual paragraph, followed by everything the party can still influence, reads considerably better than three pages about workload.
Other familiar failures
Waiting for instructions. The client's delay is generally attributed to the party, and the answer was to seek an extension.
Waiting for a document from a third party. Which explains why a filing was incomplete, not why nothing was filed.
Assuming an extension had been agreed. Without written confirmation, this is a misunderstanding rather than an agreement.
Relying on the other side to raise it. Opponents have no obligation to remind anybody of anything.
Believing the deadline was different. Miscalculation is treated more kindly than ignorance and is still a failure of diligence.
Assuming a pending application suspended time. It usually does not, per requesting an extension while the period runs.
Postal or courier delay. Where the method was chosen by the party, the delay is usually their risk.
Not appreciating the consequence. Understanding the significance of a deadline is part of complying with it.
A general account of difficulty. Unspecific hardship narratives achieve considerably less than short specific ones do.
Blaming a translation or a language barrier. Where it genuinely prevented understanding it is relevant, and where it is offered generally it reads as an afterthought.
What to do instead
Concentrate on promptness. The factor still within the party's control, and the one that most influences the outcome.
Demonstrate absence of prejudice. With evidence about what the other side did during the period rather than an assertion.
Attach the missed step. Filing it alongside the application ends the default rather than describing it.
Offer costs. Which addresses the practical objection that usually underlies the opposition.
Describe the fix. What has changed so that this does not recur, stated specifically.
Keep the reason short. One factual paragraph, without argument, however weak the underlying explanation.
Do not construct a better story. An account that fails under examination is far worse than a modest true one.
Support it with evidence. A statement from the person who knows what happened, exhibiting the relevant records.
Consider whether to apply at all. Some failures carry no consequence, and an unnecessary application draws attention to one, per what a default actually is.
A small number of explanations account for most applications to be excused, and most of them fail with considerable consistency.
Pressure of work implies a choice about priorities, not knowing about a deadline reflects on diligence, and internal system or staffing failures are within the party's own control.
Waiting for instructions, assuming an unconfirmed extension, relying on the other side to raise a point and treating a pending application as suspending time all belong to the same category.
Recognizing that an application rests on one of these is useful, because it redirects the effort toward promptness, absence of prejudice, the step being taken and the offer of costs.
Where the explanation is weak, it should be short and honest, because an elaborated account that does not survive examination damages everything else in the application.
Points to carry away
- Pressure of work is the commonest and weakest reason.
- Not knowing about a deadline reflects on diligence.
- Internal system failures are within the party's control.
- Waiting for instructions is not an explanation.
- The response is to strengthen the other factors.
Questions readers ask
Why does pressure of work fail as an explanation?
Because it describes a choice rather than an obstacle. Somebody decided what to prioritize and this deadline lost, and workload is a matter the party controls through resourcing and, when necessary, by asking for more time before the period expires. It is also the explanation decision-makers see most often, it is rarely supported by evidence, and it raises the obvious question of what else in the party's caseload is at similar risk.
Is it worth including a weak explanation at all?
Usually in one short factual paragraph, and no more. Omitting the reason entirely looks evasive, but elaborating a weak one draws attention to the weakest part of the application and consumes space better spent on the factors that can still be influenced. What should never happen is constructing a better story: an account that does not survive examination damages the credibility of everything else being said.
What should an application concentrate on instead?
The things still within the party's control: how fast they moved after discovering the failure, evidence that the other side lost nothing by the delay, the missed step filed alongside the application, an offer to meet the costs, and a specific description of what has changed so that it does not recur. Those four elements do more work than any explanation, and they are assessed on material rather than on assertion.
Sources
- Legal Information Institute — Excusable Neglectlaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 6(b), Extending Timelaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 60(b), Relief from a Judgment or Orderlaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 16(f), Sanctionslaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 55(c), Setting Aside a Defaultlaw.cornell.edu
- Legal Information Institute — Diligencelaw.cornell.edu
Urban Justice Docket is a publication, not a law firm. This article states general rules and cites its sources; it is not advice about any particular case, and the law differs by state and changes over time.
More in Missing a Deadline
Filing Late and Asking to Be Heard
A document filed out of time is generally not considered unless permission is given. The application seeking that permission should accompany the document rather than follow it, should explain the delay factually, should demonstrate that nothing was lost by it, and should be made the day the problem is identified rather than the week afterwards.
Prejudice to the Other Party
Prejudice means something the other side has actually lost through the delay: evidence that has degraded, a witness who is unavailable, expenditure incurred in reliance, or an opportunity that has closed. It does not mean the inconvenience of a matter proceeding, or the loss of a windfall that a missed deadline would have produced. Separating the two is what decides most contested applications.
When the Adviser Missed It, Not the Party
A representative's failure is usually treated as the party's own, because the alternative would make timetables unenforceable against anybody who was represented. The principle has limits where the failure was extreme or where the party was effectively abandoned. Meanwhile the practical questions — relief, disclosure, the professional relationship and any claim against the adviser — all run in parallel.