Abstract background illustration for: Inputs you need for deadlines in Australia

Inputs you need for deadlines in Australia

8 min read

Published April 8, 2025 • Updated February 2, 2026 • By DocketMath Team

Inputs you need for deadlines in Australia

Working out dates under Australian legislation or court rules usually sounds simple: “28 days from service”, “file within 21 days”, “exclude public holidays”. In practice, you need very specific inputs before a calculator can give you a reliable answer.

This post is a practical checklist for using DocketMath’s deadline calculator for matters in Australia (AU). It focuses on what you need to know before you press “calculate”, and how different inputs change the output.

Warning: This is not legal advice. Always confirm which rules apply to your matter (legislation, rules of court, practice notes, or orders) before relying on any calculated date.

Inputs you will need

When you run a deadline in DocketMath for an Australian matter, you’ll typically need the following categories of input:

Use this checklist to gather the core inputs before you run the Deadline tool.

  • trigger event date
  • rule set (civil/criminal or local rule)
  • court level or venue
  • service method
  • holiday/weekend calendar
  • time zone and filing cutoffs

1. Jurisdiction and rule-set

  • Country / jurisdiction: Australia (AU)
  • Specific rule-set (examples):
    • Federal Court Rules (Cth)
    • High Court Rules (Cth)
    • Family Law Rules (Cth)
    • State/Territory court rules (e.g. NSW UCPR, QLD UCPR, VCAT rules)
    • Statutory regime (e.g. Corporations Act, Fair Work Act, Limitation Acts)

Why it matters:
Different rule-sets in Australia can:

  • Count days differently (e.g. include/exclude the first day)
  • Treat weekends and public holidays differently
  • Have their own “business day” definitions
  • Use different time zones or “close of business” assumptions

2. Trigger event

  • Type of triggering event (what starts the clock), such as:
    • Service of a document
    • Filing or lodgment
    • Date of decision or judgment
    • Date of act/omission (for limitation periods)
    • Date of contract, notice, or termination
  • Exact trigger date (and time, if relevant)

Why it matters:

  • Some rules exclude the day of the triggering event; others may include it.
  • Time of day can matter where a rule:
    • Uses “clear days”
    • Ties deadlines to “end of business” or “before 4:00 pm”
    • References “within X hours”

3. Method and place of service (if service starts the period)

If the period runs “after service”, you will need:

  • Method of service:
    • Personal service
    • Post
    • DX
    • Email or electronic service
    • Fax (still appears in some rules)
  • Location details (where relevant):
    • Same State/Territory vs interstate
    • Within Australia vs overseas

Why it matters:

  • Some Australian rules:
    • Deem service on a later date for post or DX (e.g. “on the fourth business day after posting”).
    • Treat electronic service as occurring when the email is sent, received, or first capable of being retrieved.
    • Adjust time when service is outside the jurisdiction.

DocketMath can model both:

  1. The deemed date of service; and
  2. The deadline running from that deemed date.

You’ll get a different result if you enter:

  • The actual date of posting, vs
  • The deemed date of service.

4. Length of the period

  • Number of units (e.g. 7, 14, 21, 28)
  • Unit type:
    • Days
    • Business days
    • Months
    • Years
  • Any modifiers in the wording, such as:
    • “At least X days”
    • “Not less than X days”
    • “Within X days”
    • “No later than X days before [event]”
    • “Not more than X days after [event]”

Why it matters:

  • “Within 21 days after service” and “not less than 21 days before the hearing” may produce different endpoints even with the same number.
  • Months and years can raise issues like:
    • End-of-month alignment (e.g. 31 January + 1 month)
    • Leap years for annual periods

5. Inclusion/exclusion rules

  • First day:
    • Is the day of service/decision included or excluded?
  • Last day:
    • Is the last day included, or must the act be done before that day?
  • Weekends and public holidays:
    • Are they counted?
    • If the last day falls on a Saturday, Sunday, or public holiday, does the period extend to the next business day?

Why it matters:

Australian rules commonly:

  • Exclude the day of the triggering event.
  • Include the last day, but:
    • If it falls on a non-business day, they move it to the next business day.

DocketMath’s AU deadline logic uses rule-based defaults, but you should still know what your rule says so you can confirm the behaviour.

6. Public holiday and business-day assumptions

  • Relevant Australian State/Territory or federal context:
    • National public holidays
    • State/Territory-specific holidays (e.g. Melbourne Cup Day in VIC)
  • Business day definition (if specified):
    • Some rules define “business day” as a day that is not a Saturday, Sunday, or public holiday in the place where the act is to be done.

Why it matters:

  • A “10 business day” period in NSW can produce a different date from “10 business days” in WA if a local public holiday falls in between.
  • For cross-jurisdictional matters, you may need to know which location’s holidays are relevant (place of filing, place of service, governing law, etc.).

DocketMath’s AU configuration uses jurisdiction-aware holiday calendars, but the right jurisdiction still needs to be selected.

7. Time zone and time-of-day sensitivity

  • Time zone:
    • AEST, AEDT, ACST, ACDT, AWST (or simply “local time” in the relevant jurisdiction)
  • Cut-off time (if specified):
    • “Before 4:00 pm”
    • “By close of business”
    • “Before the registry closes”

Why it matters:

  • For electronic filing, many courts treat documents filed after a certain time as filed on the next business day.
  • If a rule says “within 7 days”, whether something is filed at 11:59 pm vs 12:01 am can change whether it is in time.

DocketMath supports time-of-day inputs where the rule-set makes that distinction relevant.

Where to find each input

Here’s a practical map of where you can usually find each piece of information for Australian deadlines.

InputTypical sources in practice
Jurisdiction & rule-setCourt rules, legislation, practice notes, orders, originating process, directions hearing
Trigger event & dateSealed orders, judgments, email from court or registry, service affidavit, file notes
Method & place of serviceAffidavit of service, cover letter, email headers, DX/post records, file correspondence
Length of the periodSpecific rule or section cited in the order or judgment; relevant legislation or rules
Inclusion/exclusion rulesInterpretation or “time” provisions in the rules (e.g. Part/Chapter on computation of time)
Public holiday rulesSame “time” provisions; State/Territory public holiday calendars; court practice notes
Business day definitionDefinitions section of the rules or Act; schedules or interpretation provisions
Time zone / cut-off timeCourt or tribunal practice notes; e-filing protocols; registry information; local rules

Note: When in doubt, start with the computation-of-time provision in the relevant rules (often near the start or in a definitions/interpretation part). That provision usually controls how days are counted, how weekends/public holidays are treated, and how to handle short periods.

Run it

Once you’ve gathered the inputs above, you’re ready to run a deadline calculation using DocketMath’s AU-aware engine.

Enter the inputs in DocketMath and run the Deadline calculation to generate a clean breakdown: Run the calculator.

Step 1: Confirm the rule-set

  1. Open the DocketMath deadline calculator: /tools/deadline.
  2. Select:
    • Jurisdiction: Australia (AU)
    • Relevant rule-set: match the court, tribunal, or statute you’re working under.

Check your source document (order, rule, section) to confirm you’ve picked the right one.

Step 2: Enter the trigger event

  1. Choose the trigger type (e.g. “service”, “decision”, “filing”).
  2. Enter:
    • Date of the trigger event.
    • Time if the rule or practice note makes time-of-day relevant.

If service is involved, DocketMath can either:

  • Calculate the deemed date of service from posting/emailing; or
  • Let you directly enter the deemed service date if you already know it.

Be consistent about which approach you’re using.

Step 3: Specify the period

  1. Enter the length of time:
    • Number + unit (e.g. 21 days, 28 days, 1 month).
  2. Choose whether the rule:
    • Counts calendar days or business days.
    • Is framed as “within X days after” vs “at least X days before”.

Align this with the exact wording of the rule or order.

Step 4: Configure weekends, holidays, and business days

  1. Confirm:
    • Which jurisdiction’s public holidays apply.
    • Whether weekends and public holidays are counted or skipped.
  2. Confirm how the last day is treated:
    • If it falls on a weekend/public holiday, does it move to the next business day?

DocketMath’s defaults for AU rule-sets follow the computation-of-time provisions, but you can still adjust assumptions where the rules or orders in your matter differ.

Related reading

For more detail on how DocketMath handles time computation and jurisdiction-specific rules, see: