When the Clock Actually Starts Running

Ask somebody when their deadline runs from and they will name the day the problem arose. Ask the rule and it will name a document, a decision or a demand. The gap between those two answers is where late filings come from.

The common triggers, and how they differ

The date of an act or event. The simplest trigger, used for limitation periods and for steps that follow something happening, and the one people assume applies everywhere.

The date a document was issued. The date printed on a decision, which is fixed by the body that made it and is frequently earlier than anybody outside knew about it.

The date a document was served. When the document was delivered under the rules, which is a separate date again and the one most procedural periods actually use.

The date of receipt. When it actually arrived, which differs from service where a rule deems delivery to have happened at a set interval after posting.

The date of a demand or request. Some periods run only once somebody asks, which means a party can control when their own clock starts.

Completion of a step. Periods that begin when a hearing ends, an inspection finishes or a payment clears, none of which produces a document by itself.

Knowledge. Limitation periods sometimes start when a person knew or should have known something rather than when the event itself occurred.

Why the difference matters so much

The dates are days or weeks apart. A decision issued on the first, posted on the third and received on the eighth gives three candidate start dates for the same period.

Short periods magnify it. On a fourteen-day window, choosing the wrong trigger loses a third of the time available before anybody starts work.

Some triggers are invisible. An issue date is printed on the document; a service date has to be worked out from how the document was sent.

Mailing adds time in some systems. Where a period starts with a posted document, extra days are frequently built in, which is covered in added time for service by mail.

The forum decides, not the parties. An agreement between the parties about when a period started does not bind a decision-maker applying a rule.

A wrong trigger is rarely excusable. Miscounting from an identifiable date is treated as an error rather than a reason, per the reasons that rarely work.

Finding the trigger in the text

Look for the preposition. After, from, following and upon each attach the period to a specific event, and the words around them name it.

Identify the noun. The rule names a thing that happens: service of the order, entry of judgment, receipt of the notice, the date of the decision.

Check whether it says served or issued. These two words appear side by side in procedural rules and mean different dates, and the difference is deliberate.

Watch for whichever is later. Some rules run from the later of two events, which protects a party who was told late and requires both dates to be tracked.

Note any deeming provision. A rule that deems service to occur a set number of days after posting has fixed the trigger regardless of when anything arrived.

Read the definitions section. Terms like decision, order and notice are frequently defined elsewhere in the same instrument, and the definition governs wherever the word appears.

Documents that start several clocks

One decision, three periods. A determination can start an appeal window, a compliance period and a payment deadline at once, each of a different length.

Each period may count differently. One may run in calendar days and another in business days, which is dealt with in calendar days against business days.

Conditions attached to relief. Where a decision grants something subject to a step, the deadline for that step is inside the decision rather than in a rule.

Periods triggered by somebody else's act. A response window opens when the other side files, which means monitoring their filings rather than a calendar.

Deadlines that run backwards. Some obligations are pegged to a future hearing date rather than to a past event, and they are counted in the other direction.

Write all of them down at once. The moment a document arrives is the moment to extract every period it starts, because it will not be reread.

Recording the date properly

Keep the envelope. A postmark evidences dispatch, and the date a document arrived is otherwise unprovable a year later.

Note the day of receipt on the document. A dated stamp or a written note made on arrival is contemporaneous evidence, which nothing produced later can match.

Keep the electronic notification. Where a document arrives by portal or email, the system's timestamp is the record and it should be preserved.

Diarize the trigger and the deadline separately. Recording both makes an error visible; recording only the deadline hides the arithmetic that produced it.

Recalculate when anything changes. An amended decision, a corrected order or a re-service resets the calculation, and the original date stops mattering.

Check the trigger before relying on it. Two minutes with the rule at the start avoids the position described in filing late and asking to be heard.

Every time limit hangs on a trigger, and the trigger is whatever the rule says it is rather than the day the underlying problem arose.

Service, issue, receipt and demand are four different dates that can sit weeks apart, and choosing between them by instinct is how a comfortable period turns into a missed one.

The text answers the question. The preposition attaches the period to an event, the noun names the event, and any deeming provision fixes the date regardless of what actually happened.

One document frequently starts several periods of different lengths, counted in different ways. Extracting all of them on the day it arrives is the only reliable moment to do it.

Recording the trigger alongside the deadline is what makes an error findable. A diary entry showing the calculation can be checked; one showing only a date cannot.