Two Deadlines at Once, and Which Governs
Deadlines arrive in layers. A rule provides a default, an order in the matter varies it, a practice direction adds a local requirement, and an agreement between the parties adjusts something else. Reading them together is the whole exercise.
The rule in short
Where more than one instrument sets a date for the same step, the usual order of precedence puts a specific order above a general rule and a statute above both. Where the position is genuinely unclear, the earlier date is the safe one. The real risk is not the conflict but the failure to notice that a second date exists.
A file usually contains more than one instruction about when something is due, and they are rarely in the same place. The rule is in a book, the order is in the file, the practice direction is on a website, and the agreement is in an email.
Where the layers come from
The general rule. The default period for a step, which applies wherever nothing else has been specified.
An order in the matter. Directions frequently set their own timetable, and where they do they are addressing this case rather than cases generally.
A local practice direction. Individual courts and offices publish supplementary requirements, usually adding steps or shortening periods.
A statute behind the rule. Where the period is statutory, no rule or order can lengthen it, which is the point of deadlines that are jurisdictional.
An agreement between the parties. Consent can adjust some periods and not others, per consent extensions between the parties.
A contract that predates the proceeding. Notice clauses in an underlying agreement run alongside procedural deadlines rather than instead of them.
A previous extension. An order granting more time replaces the earlier date and becomes the operative one.
How they usually rank
A statute beats everything. Where a legislative provision fixes a period, nothing below it can extend the date, however sensible that would be.
A specific order beats a general rule. Directions in the matter are addressed to this case and are usually treated as displacing the default.
A practice direction supplements the rule. It rarely contradicts; it usually adds a requirement or an earlier internal date.
An agreement binds the parties, not the forum. Two parties can agree a later date between themselves and still both be late as far as the forum is concerned.
The later instrument usually wins between equals. Where two orders conflict, the more recent one is normally taken to have varied the earlier.
Ambiguity is resolved by asking. Where the position is genuinely unclear, a short application for clarification is cheaper than guessing.
Nothing lets a party ignore the earlier date safely. Until the conflict is resolved, the sooner date is the operative one for planning purposes.
| Source | Typical effect | Can it be varied |
|---|---|---|
| Statute | Fixes an outer limit | No |
| Order in the matter | Displaces the default | By further order |
| General rule | Supplies a default | By order |
| Practice direction | Adds a requirement | Rarely |
| Party agreement | Binds the parties only | By agreement |
What actually goes wrong
The second date is never noticed. Almost every problem in this area is a missed instrument rather than a genuine conflict between two known ones.
A standard rule is assumed. Where an order has varied the default, a party working from the rulebook is working to a date that no longer applies.
An order is read for its outcome only. Directions carry dates in their operative paragraphs, and a reader looking for the decision skips them.
A practice direction is never read at all. Local requirements are published rather than served, and nobody sends a copy.
The parties' agreement is treated as binding on the forum. An extension agreed between the parties does not move a date the forum set unless the forum approved it.
Consequential dates are not recalculated. Varying one date moves everything counted from it, including backward deadlines, per deadlines that run backwards.
Nobody records which instrument produced the date. When the timetable changes, an undocumented calculation cannot be updated because nobody knows what it was based on.
While a conflict is being resolved, the sooner deadline is the operative one. Meeting it costs nothing if the later date turns out to govern, and missing it costs the whole step if the earlier one did. There is no version of this question where waiting is the safe choice.
Resolving a genuine conflict
Identify both instruments precisely. Rule number, order date and paragraph, so the conflict can be described rather than asserted.
Work out whether they really conflict. Frequently one sets a period for filing and the other for service, which are different steps entirely.
Apply the ranking. Statute, then specific order, then general rule, then anything agreed between the parties.
Raise it early and in writing. A short letter or application while both dates are ahead resolves it cheaply.
Comply with the earlier date meanwhile. Nothing is lost by meeting the sooner deadline, and everything can be lost by waiting for an answer.
Ask for the timetable to be varied if needed. Where the earlier date is impossible, the application is an extension request rather than an argument about precedence, per requesting an extension while the period runs.
Record the resolution. The answer, and its reason, belongs in the file so that the next dependent date is calculated correctly.
Keeping track of the layers
Extract dates from every order on arrival. The moment directions are received is the moment to read them for dates rather than for outcome.
Check the local requirements once. Practice directions are stable, and reading them once per forum removes an entire category of surprise.
Record the source of every diarized date. A diary entry naming the instrument can be corrected when that instrument changes.
Re-read the timetable after every variation. One changed date usually moves several, and the ones that move quietly are the backward ones.
Keep the contract's notice clauses in view. Procedural deadlines do not displace contractual ones, and both can be running at once.
Note which dates the parties can move. Knowing in advance which periods are variable by consent saves an application that was never needed.
Review the whole timetable periodically. A file with several layers of dates deserves a single consolidated list that somebody maintains.
Deadlines arrive in layers, and a file usually contains more than one instruction about when the same step is due.
The ranking is stable: a statutory period beats everything, a specific order displaces a general rule, a practice direction supplements rather than contradicts, and an agreement between the parties binds only the parties.
The real problem is almost never a conflict between two known dates. It is a second instrument nobody noticed, which is usually an order that varied the default or a local requirement that was published rather than served.
Where a conflict is genuine, it is resolved by identifying both instruments precisely, raising it in writing while both dates are still ahead, and complying with the earlier one in the meantime.
Keeping track means extracting dates from every order on arrival, recording which instrument produced each diarized date, and re-reading the whole timetable whenever any part of it changes.
Points to carry away
- A specific order usually displaces a general rule.
- A statutory period cannot be extended by a procedural rule.
- Local practice directions add requirements rather than remove them.
- Where it is unclear, the earlier date is safe.
- The common failure is not noticing the second date.
Questions readers ask
If a rule and an order set different dates, which one applies?
Usually the order, because directions in the matter are addressed to this case rather than to cases generally and are normally taken to have varied the default. The exception is a period fixed by statute, which nothing below it can extend. Where the position is genuinely unclear, the practical answer is to comply with whichever date is earlier while raising the question in writing, because meeting the sooner deadline costs nothing if the later one turns out to govern.
Can the parties agree to extend a date the forum set?
Sometimes, and the agreement binds only the parties unless the forum accepts it. Many systems allow parties to extend certain periods between themselves by consent, usually those concerned with steps between the parties rather than with filings or hearing dates, and usually subject to limits on the total extension. Where the date was set by an order, an agreement to vary it generally needs to be approved, and a party relying on an unapproved agreement can be late despite the other side's consent.
What causes most problems in this area?
Not noticing that a second date exists. Almost every difficulty comes from a party working to the general rule when an order has varied it, or from a local practice direction that is published on a website rather than served on anybody. Reading every order for its dates on the day it arrives, checking the local requirements once for each forum, and recording which instrument produced each diarized date removes nearly all of it.
Sources
- Federal Rules of Civil Procedure — Rule 16, Pretrial Conferences and Schedulinglaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 6(b), Extending Timelaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 83, Rules by District Courtslaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 29, Stipulations About Discovery Procedurelaw.cornell.edu
- Administrative Procedure Act — 5 U.S.C. 558, Sanctions and Powerslaw.cornell.edu
- Legal Information Institute — Scheduling Orderlaw.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 Counting the Days
When the Clock Actually Starts Running
Every time limit has a trigger, and the trigger is defined by the rule rather than by common sense. Service, issue, receipt, demand and completion are all different events, and a period counted from the wrong one is wrong by however many days separate them. Finding the trigger in the text is the first step in any deadline question.
What a Month Means in a Deadline
A period expressed in months runs to the same day-number in the later month rather than by adding a fixed number of days. Where the later month is shorter and has no corresponding date, the period generally ends on its last day. Periods expressed in days are counted in days regardless of how many months they span, and mixing the two conventions is a common source of error.
Weekends, Holidays and Closures
Where the last day of a computed period falls on a weekend, a holiday or a day the filing office is inaccessible, the period generally extends to the next day it is open. The extension applies to the end of a period rather than to days inside it, and an office being busy, understaffed or closed to visitors is not the same as being inaccessible.