How Fast to Move Once It Is Noticed
Everything about a missed deadline is fixed by the time somebody notices it, except one thing. What happens over the following days is the only part still capable of improving the outcome, and it is examined more closely than anything else.
The rule in short
Once a deadline has been missed, the length of the overrun, the reason and the compliance history are all settled. The interval between discovery and action is not, and it is the factor decision-makers comment on most consistently. Moving the same day, taking the missed step alongside any application, and recording the sequence are what convert an ordinary failure into a recoverable one.
Applications about missed deadlines are decided largely on a period that had not yet begun when the deadline passed. That period starts at discovery and it is entirely within somebody's control.
Why promptness dominates
Everything else is already fixed. The overrun, the cause and the history cannot be changed by anybody, which leaves one variable in play.
It demonstrates seriousness. A party who acted within hours is treated differently from one who took three weeks to decide what to do.
It limits the prejudice. The shorter the total delay, the less the other side can point to as having been lost.
It is easy to assess. Dates are objective, unlike explanations, so decision-makers rely on them.
It reflects on the underlying failure. Slow correction suggests the problem that caused the failure has not been addressed.
It is the same test everywhere. Whatever the formal standard, promptness after discovery appears in every version of it.
It carries into later applications. A party who moved quickly once has a record supporting them the next time.
It costs nothing. Unlike almost every other factor, improving it requires no resource beyond a decision.
It is frequently the ratio. Refusals commonly turn on the interval rather than on anything about the original failure.
It shapes the tone of everything. An application opening with a same-day response reads quite differently from one that has to account for a fortnight of inactivity first.
What the first day looks like
Establish exactly what was missed. The deadline, its source and its consequence, confirmed against the rule or order rather than assumed.
Establish what has already happened. Whether a default has been entered, a decision made, or nothing at all, since that changes the route.
Take the step if it can still be taken. Filing the missed document immediately ends the continuing default rather than describing it.
Record the discovery. The date, the time and how it came to light, written down before anything else is done.
Preserve the evidence. System logs, delivery records and correspondence, before retention policies remove them.
Tell whoever needs to know internally. Escalation on the first day is what produces resource; escalation in week three produces recrimination.
Tell the client. Promptly and factually, because the decision about what to do next is frequently theirs.
Contact the other side if useful. Consent to an extension or to setting aside is more available immediately than later.
Start the application. Even a short one filed today outperforms a comprehensive one filed next week.
| Interval | Usual reception | Effect |
|---|---|---|
| Same day | Strong | Failure looks isolated |
| Two to three days | Good | Explained easily |
| One to two weeks | Weak | Requires justification |
| A month or more | Poor | Frequently decisive |
| Only after being challenged | Very poor | Suggests a position |
What delay after discovery costs
It is the first thing examined. The interval appears in every judgment on these applications, usually early.
It compounds the original failure. One missed deadline is an accident; a slow response to it is a decision.
It increases the prejudice. Every additional week gives the other side more to point at.
It undermines the explanation. A party genuinely surprised by a failure acts on it, and a party who did not act invites the inference that they knew.
It removes options. Consent, cure and correction all become less available as time passes.
It affects credibility generally. Delay at this stage colors how the rest of the account is read.
It can convert curable into fatal. Some routes close on defined periods running from discovery, per the notice nobody ever saw.
It is difficult to explain. Explanations for post-discovery delay are weaker than explanations for the failure itself.
It is entirely avoidable. Which is precisely why it is treated so unforgivingly.
Waiting to understand a situation fully before responding to it is the single most common cause of post-discovery delay. A protective step taken on partial information can be refined afterwards; the days spent gathering it cannot be recovered.
The usual causes of delay after discovery
Waiting for complete information. The commonest cause, and the most avoidable, since a protective application can be made on partial facts.
Waiting for advice. Advice takes days, and a holding step filed meanwhile costs almost nothing.
Waiting for a decision from the client. Which should be sought urgently rather than added to a routine update.
Hoping it will not be noticed. It will be, and the delay will be noticed with it.
Drafting something comprehensive. Perfectionism at this stage is a luxury the timetable does not support.
Internal reluctance to escalate. Where the failure is somebody's fault, the instinct to resolve it quietly costs days.
Absence. The person who discovers a failure being away is a foreseeable event that cover arrangements should address.
Confusion about who owns it. Where responsibility is unclear, nobody acts and everybody assumes somebody has.
Underestimating the consequence. A failure treated as minor generates a slow response, and the assessment is frequently wrong.
Building the record of promptness
Note the discovery precisely. Date, time, and what prompted it, recorded contemporaneously rather than reconstructed.
Keep a log of the steps taken. Each action with its timestamp, which becomes the chronology in the application.
Keep the correspondence. Messages to the client, the other side and the forum all evidence the response.
File the step with a timestamp. The filing record shows precisely when the default ended, per proving that a document was filed.
Lead the application with the timeline. Because it answers the question the decision-maker will ask first, per excusable neglect, explained.
Explain any unavoidable gap. Where something genuinely took days, say why, in a sentence.
Do not compress the account. Overstating speed is easily checked against the records and damages everything.
Keep it proportionate. A chronology, not a narrative, since the dates carry the argument.
Preserve it afterwards. The same record supports any future application in the same matter.
By the time a missed deadline is discovered, the overrun, the cause and the compliance history are all settled, and only the response remains capable of improving the outcome.
That response is examined closely and assessed objectively, because dates are easier to evaluate than explanations, and it appears in every version of the applicable standard.
The first day should establish what was missed and what has already followed, take the step if it can still be taken, record the discovery and begin the application.
Delay after discovery compounds the original failure, increases the prejudice, undermines the explanation and closes routes that were available immediately, and it is uniquely difficult to justify.
Its usual causes are waiting for complete information, waiting for advice, drafting something comprehensive and internal reluctance to escalate, all of which are addressed by acting on partial facts.
Points to carry away
- Discovery is the moment the clock that matters starts.
- Days are treated very differently from weeks.
- Taking the step immediately ends the default.
- The sequence should be recorded contemporaneously.
- Waiting for complete information is the usual mistake.
Questions readers ask
How quickly should a missed deadline be acted on?
The same day it is discovered, wherever that is possible. The interval between discovery and action is the only factor still within anybody's control once a deadline has passed, and it appears in every version of the standard applied to these applications. A response measured in hours makes the original failure look isolated; one measured in weeks makes it look like a position that was adopted rather than an accident that occurred.
Is it better to wait until the full position is understood?
Almost never. Waiting to understand a situation completely before responding is the commonest cause of post-discovery delay, and the days consumed cannot be recovered. A protective step or a short holding application made on partial information can be refined once more is known, and the record then shows a party who acted immediately rather than one who investigated for a fortnight before doing anything.
What should be recorded while responding?
The moment of discovery with its date and time and what prompted it, then each step taken with its own timestamp, along with the correspondence to the client, the other side and the forum. That log becomes the chronology in any application, and it answers the question decision-makers ask first. It should be accurate rather than flattering, because an overstated account of speed is easily checked against the underlying records.
Sources
- Legal Information Institute — Excusable Neglectlaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 6(b)(1)(B), Extending Time After Expirationlaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 55(c), Setting Aside a Defaultlaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 60(c), Timing of a Motionlaw.cornell.edu
- Federal Rules of Appellate Procedure — Rule 4(a)(5), Motion for Extension of Timelaw.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.
The Reasons That Rarely Work
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.
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.