Deadlines reference snapshot for Australia

Rule or statute summary

Run this scenario in DocketMath using the Deadline calculator.

This is a practical “deadline snapshot” for Australia, designed for quick orientation. It focuses on common procedural deadlines that arise in many civil and administrative matters—especially where an external event starts the clock (for example, service, notification, or a decision being made). Because Australian practice can differ by forum (federal vs state/territory; court vs tribunal) and by matter type, treat this as a reference guide rather than legal advice.

1) When does the clock start?

Many deadlines in Australia are keyed to one of these events:

• Service of documents (e.g., originating process, court orders, requests)
• Notification of a decision (e.g., reasons, reviewable decisions)
• Publication or giving notice (varies by statute and instrument)
• Filing/receipt by an official registry (for some applications)

For deadline planning, you typically need:

• the trigger date (what happened, and when), and
• the end-date rule (how days are counted, including whether weekends/public holidays are included).

2) How days are usually counted

Australian legislation and rules often rely on general conventions such as:

• “working day” concepts for some time periods, and
• rules about excluding the day of service/notification and counting forward to the next relevant day.

That said, the exact counting method depends on the specific instrument (e.g., Federal Court Rules, Federal Circuit and Family Court Rules, court-specific Practice Directions, or particular statute sections). This is why the “Citations” section matters: it’s where you confirm the authoritative time-computation approach for your forum and document category.

Gentle reminder: deadline counting can change the outcome by several days. If your trigger is unclear (for example, whether a document was received versus merely sent), build margin and re-check the exact rule for your situation.

3) Appeals/reviews: common pattern

In many contexts, review/appeal deadlines follow a pattern like:

• a primary time limit (often measured from when a person is notified of the decision), and
• an extension mechanism (commonly requiring reasons and prompt action).

However, the review body matters. A court pathway and a tribunal pathway usually draw their deadlines from different rules and statutes. Your deadline source must match the review pathway set out in the statute or in the decision notice.

4) Document-related deadlines (filing, responding, and extensions)

In litigation and related proceedings, common deadline categories include:

• filing and serving pleadings
• responding to applications
• steps after orders (e.g., compliance dates, further submissions)

These are usually governed by:

• court rules (civil procedure), and
• practice directions (operational details).

In federal matters, many time periods appear in the Federal Court and Federal Circuit and Family Court procedural rules (as applicable), plus any relevant case management orders.

Citations

Because Australian deadline rules are highly forum- and statute-specific, this snapshot highlights commonly used “citation anchors.” Use these as starting points for your document set—then verify the exact provision that applies to your category of document and trigger event.

Sources and references

• TODO: Add the exact time-computation sections from the relevant federal court rules once you confirm the forum (e.g., Federal Court vs Federal Circuit and Family Court) and the case type (civil vs family vs migration vs general administrative).
• TODO: Add the exact service/notification provisions that define when time starts for your document category.

Start with the primary authority for Australia and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Federal Court Rules 2011; state Supreme Court Rules; Limitation Acts (state)

Use the calculator

Use DocketMath to translate a triggering date into a calculated deadline date. This is especially helpful when:

• your document is governed by a days-based rule (e.g., 14 days, 28 days), and
• you need to account for weekends and public holidays under the relevant counting rule.

Open the tool here: /tools/deadline

Step 1: Choose the trigger date

Common trigger dates include:

• Date of service (e.g., when the claim was served)
• Date you were notified of a decision (e.g., date of decision letter)
• Date of receipt (if the statute/rules use receipt rather than sending)

Step 2: Choose the time period

Select the rule’s time window, such as:

• N calendar days (commonly includes weekends), or
• N working days (commonly excludes weekends/public holidays, depending on configuration).

Step 3: Select the counting method

If the rule says:

• “working days”, weekends/public holidays are usually excluded
• “days” (without “working”), you may be dealing with calendar-day counting, subject to interpretive provisions in the relevant instrument

Step 4: Generate the result and sanity-check it

After calculating, compare:

• the output date against your calendar,
• whether the trigger day is excluded or included by the governing rule, and
• whether there are multiple steps (e.g., service → response → hearing).

Practical checklist before you rely on the output

Example planning scenarios (how inputs can change outputs)

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations