The Day of the Act, and Whether It Counts
Almost every counting rule begins by throwing away a day. Whether it is the day of the event or the last day of the period, and whether the rule in front of somebody is one of the exceptions, decides which date the deadline actually falls on.
The rule in short
The general rule excludes the day of the triggering act and includes the last day of the period. Some periods count differently, particularly those measured backwards or those fixed by a specific date rather than a length. The convention is easy to state and easy to get wrong, and a single day is enough to make a filing late.
Ten days from Monday is a question with two answers, and the difference is a day. Every procedural system settles it the same way in principle and with enough exceptions that the principle is not enough on its own.
The general rule
Exclude the day of the act. The day the event occurred is day nought, and the first full day afterwards is day one of the period.
Include the last day. The period ends at the close of the final day rather than at its start, which is where the hour question arises.
It applies to most computed periods. Rules of civil procedure, appellate rules and most agency regulations adopt the same convention in substance.
It applies to short and long periods alike. The convention does not change between a five-day window and a two-year one, though the practical effect is larger on the short one.
The rule is usually in one place. Procedural codes carry a single computation provision that governs every period in the instrument unless a rule says otherwise.
Read it once and keep it. The provision is short, and knowing which one applies to a forum removes the question permanently for that forum.
Where the convention changes
Periods counted backwards. A period measured back from a hearing date inverts the exclusion, and the details are in deadlines that run backwards.
Dates fixed by an order. When an order names a date rather than a length, no computation happens and the named day is the deadline.
Statutes with their own provisions. A statute can specify its own counting method, and where it does it overrides the general procedural rule.
Periods measured in months or years. These are counted to a corresponding date rather than by adding days, which is covered in what a month means in a deadline.
Contractual periods. An agreement can adopt any counting convention it likes, and it frequently adopts none explicitly, which is the source of the dispute.
Foreign proceedings. A period running under another country's rules is counted under that country's convention, not the local one.
| Period | Trigger day | Day one | Last day |
|---|---|---|---|
| 10 days from Monday | Monday, excluded | Tuesday | Thursday week |
| 7 days from Friday | Friday, excluded | Saturday | Following Friday |
| 30 days from the 1st | The 1st, excluded | The 2nd | The 31st |
| 3 days before a hearing | Hearing day, excluded | Counted backwards | Third day before |
| Date fixed in an order | Not computed | Not computed | The named date |
Worked examples
Ten days from a Monday. Excluding Monday, day one is Tuesday and day ten is the Thursday of the following week, not the Wednesday.
Thirty days from the first of a month. Day one is the second, and day thirty is the thirty-first in a long month or the first of the next in a short one.
A period ending on a weekend. The last day moves to the next open day, which is dealt with in weekends, holidays and closures.
A period starting on a weekend. The exclusion of the first day applies whether or not that day was a working one; only the ending is adjusted.
Two periods from one document. Each is computed separately from the same trigger, so a seven-day and a fourteen-day period do not share an end date.
A period that has already been extended. An extension usually runs from the original expiry rather than from the date it was granted, and a well-drafted order says which.
A period inside another period. Where a step must happen partway through a longer window, both are computed from their own triggers rather than from each other.
The off-by-one error survives because people count in their heads. Writing the trigger date on a calendar and labelling it explicitly as day nought, then counting visibly, makes the mistake obvious at the moment it would otherwise be made.
Common errors
Counting the trigger day as day one. The commonest error, and it makes every deadline one day earlier than it needs to be, which is at least harmless.
Counting the last day as excluded. The dangerous version of the same mistake: it makes the deadline one day later than it is.
Using a diary that counts differently. Practice management software applies a configured convention, and the configuration is worth checking rather than trusting.
Assuming one forum's rule applies elsewhere. Conventions are close but not identical between courts, agencies and contracts.
Forgetting an added period. Where extra days are added for service by post, they are added after the basic computation, not folded into it.
Filing on the last day by habit. Any error in the counting is invisible until it is fatal, which is an argument for filing earlier rather than counting better.
A practical method
Write the trigger date. Then mark it day nought explicitly rather than starting a mental count from it and hoping the arithmetic holds.
Count on a calendar, not mentally. Marking the days visibly catches the off-by-one error that arithmetic hides.
Check the end for a closure. Once the last day is identified, check whether it is a day the office is open before relying on it.
Note which rule was applied. Recording the computation provision alongside the date makes the calculation checkable, per when the clock actually starts.
Have somebody else verify short periods. On a period of a week or less, a second person checking the arithmetic costs a minute and catches the error that habit hides.
Recheck after any amendment. A corrected order, a re-service or a granted extension replaces the calculation entirely, and the earlier date stops being relevant.
Build in a margin. Treating the deadline as a day earlier than it is absorbs exactly this class of error.
The convention is simple: throw away the day the event happened, keep the last day of the period, and count everything in between.
It holds across most procedural systems and stops holding in identifiable places: periods counted backwards, dates named in an order, statutes with their own provisions, and periods measured in months.
The dangerous error is the one that makes a deadline later than it really is. Counting the trigger day as day one is harmless; treating the last day as excluded is not.
Software counts according to how it was configured, and the configuration is a setting rather than a law. On any short period it is worth checking the arithmetic by hand.
The reliable practice is visible counting on a calendar, a note of which computation rule was applied, and a margin that makes an off-by-one error survivable rather than fatal.
Points to carry away
- The day of the triggering event is normally excluded.
- The last day of the period is normally included.
- Backwards-counted periods invert the convention.
- A date fixed by an order is not a computed period at all.
- Check the counting rule for the forum, not the habit.
Questions readers ask
Does the day of the event count as the first day?
Under the general convention, no. The day the triggering act or event occurred is excluded, and the first day of the period is the day after it. The last day of the period is included, so a ten-day period beginning on a Monday ends on the Thursday of the following week. That convention appears in substantially the same form across civil procedure rules, appellate rules and most agency regulations, though a particular statute or contract can adopt a different one.
What happens when a period is measured in months rather than days?
It is normally counted to the corresponding date in the later month rather than by adding a number of days, so one month from the fifteenth ends on the fifteenth. The complication arises where the later month has no corresponding date, as with the thirty-first or the twenty-ninth of February, and the usual answer is that the period ends on the last day of that month. Because the practice varies, the computation provision for the forum should be checked rather than assumed.
Is it worth filing before the last day?
Yes, and not only for comfort. Every error described here becomes invisible until it is fatal: a miscounted trigger, an off-by-one in the arithmetic, a closure nobody checked, a filing system that rejects a document for a formal defect. Filing a day or two early converts each of those from a missed deadline into a correctable inconvenience. Treating the deadline as one day earlier than it is absorbs the whole class of counting error at no cost.
Sources
- Federal Rules of Civil Procedure — Rule 6, Computing and Extending Timelaw.cornell.edu
- Federal Rules of Appellate Procedure — Rule 26, Computing and Extending Timelaw.cornell.edu
- Federal Rules of Criminal Procedure — Rule 45, Computing and Extending Timelaw.cornell.edu
- 1 U.S.C. 1 — Rules of Constructionlaw.cornell.edu
- Federal Rules of Bankruptcy Procedure — Rule 9006, Timelaw.cornell.edu
- Legal Information Institute — Computation of Timelaw.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.