Deemed Receipt, Explained Plainly

Almost every deadline in a matter is counted from receipt, and almost nobody knows when receipt actually happened. Deemed receipt is how systems resolve that, and it is a rule rather than a finding.

What the rule does

It fixes a day. The document is treated as received on a stated day, and every following period is counted from it.

It applies whatever happened. Earlier reading, later collection and complete ignorance make no difference to the calculation.

It varies by method. Post, personal delivery, email and portal each attract their own provision in most systems.

It usually counts business days. Weekends and closures are commonly excluded, per weekends, holidays and closures.

It frequently has a cut-off hour. Documents delivered after a stated time are treated as received the following day.

It is not a finding of fact. The rule does not assert that receipt occurred; it decides how time will be counted.

It creates certainty for both sides. Sender and recipient can calculate the same dates from the same information.

It is displaceable, sometimes. Many systems permit evidence that the document was not received at all, or was received considerably later.

It applies to both sides. The same provision governs when a document served by a party is treated as received by their opponent, which means the calculation matters equally to whoever is counting.

How it differs by method

Personal delivery. Usually receipt on the day, subject to any cut-off hour applying to late delivery.

Ordinary post. Commonly a stated number of business days after posting, which is the most familiar version.

Tracked or certified mail. Sometimes the delivery date, sometimes the same deemed period as ordinary post.

Email. Frequently the day of sending, subject to a cut-off, per service by email and by portal.

Portal. Often the day the document becomes available rather than the day the alert is sent.

Courier. May or may not be treated as post, and the applicable provision needs checking.

Service abroad. Different and usually longer, tied to the certificate from the receiving authority.

Under a contract. Notice clauses set their own deemed receipt provisions, which override the general default position as between the parties to that agreement.

Under a specific statutory regime. Particular subject areas frequently carry their own timing provisions that displace the general procedural rule entirely, and those are easy to overlook when the general rule is familiar.

Why it exists

Timetables need fixed points. A system counting from actual receipt could not schedule anything reliably.

Senders cannot control delivery. Once a document is properly dispatched, what happens next is outside their influence.

It removes an evidential inquiry. Otherwise every deadline would require proof of when somebody opened something.

It discourages avoidance. A recipient cannot delay a period by declining to collect mail.

It matches the obligation to maintain records. Recipients are expected to monitor their nominated address or channel.

It allows both parties to calculate. Which prevents disputes about dates that have nothing to do with the merits.

It is balanced by additional time. Methods with delivery delay frequently attract extra days for the recipient.

And by displacement provisions. Genuine non-receipt is dealt with separately, per rebutting the presumption of receipt.

It reflects an allocation of risk. Delivery failures fall on the party better placed to prevent them, which is usually the recipient who chose and maintains the address or account.

Working with it

Identify the method first. Everything else follows from which provision applies.

Read the provision rather than recalling it. Deemed receipt rules differ between systems more than almost anything else.

Note the cut-off hour. Late delivery frequently moves the deemed date by a day, which moves everything after it.

Apply the business-day adjustment. A deemed date landing on a closure usually rolls forward.

Calculate the following deadline immediately. The deemed date is an input, not an output, and its value is the diary entry it produces.

Record how it was calculated. So that somebody else can check the arithmetic without redoing it.

Check whether extra time applies. Some methods add days for the recipient and others expressly do not.

Do not rely on actual receipt. A document opened early starts nothing early, and one opened late delays nothing either.

Diarize the underlying dispatch date too. Where a deemed date is later challenged, the dispatch record is what supports it, and keeping both together makes the calculation reproducible months afterwards.

Common errors

Counting from dispatch. Where the rule counts from a deemed date several days later, or the reverse.

Ignoring the cut-off. An item delivered at six in the evening may count as the next day.

Using the wrong method's rule. Courier treated as post, or portal treated as email.

Missing the business-day adjustment. Which produces a date one or two days out and can be decisive.

Double-counting additional time. Applying both a deemed receipt period and an extra-days provision where only one applies.

Assuming the contract follows the rules. Notice clauses frequently say something different, and they govern between the parties.

Forgetting time zones. For electronic service across zones, per time zones and a national deadline.

Never writing it down. A calculation that nobody recorded is a calculation that nobody else can check.

Recalculating from a moved date. Where a hearing or a step is relisted, every deemed date counted from it changes as well, and refreshing one entry while leaving the others is how a diary quietly goes wrong.

Deemed receipt is a rule fixing the day a document is treated as reaching its recipient, adopted because a system counting from actual receipt could not schedule anything.

It varies by method, commonly counts business days, frequently carries a cut-off hour, and is displaced only by evidence meeting a defined standard rather than by assertion.

It exists to give both sides the same calculable dates, and it is balanced by provisions adding time for slower methods and by mechanisms addressing genuine non-receipt.

Working with it means identifying the method, reading the provision rather than recalling it, applying the cut-off and the business-day adjustment, and converting the result into a diary entry immediately.

The recurring errors are counting from the wrong event, ignoring the cut-off, applying another method's rule, double-counting additional time, and assuming a contract follows the default position when it does not.