Worked example: deadlines in Australia

This walkthrough shows, step by step, how a deadline calculation can work for an Australian court timeline using the DocketMath deadline calculator. It’s a concrete example you can adapt to your own workflows—not legal advice and not a substitute for checking the actual rules or getting legal assistance.

We’ll:

• Set realistic example inputs
• Run them through DocketMath
• See how small changes (dates, service method, weekends, public holidays) move the due date

Example inputs

Assume you’re acting for a defendant in a civil claim in New South Wales, in a court where:

• A defence is due 28 days after service of the statement of claim
• Time is calculated in calendar days
• If the deadline falls on a Saturday, Sunday, or public holiday, the due date rolls to the next business day

We’ll model the deadline for filing and serving the defence using DocketMath’s /tools/deadline calculator.

Matter context (for illustration)

• Jurisdiction: Australia – New South Wales
• Filing type: Defence to statement of claim
• Time limit: 28 days after service
• Service: Ordinary service within NSW (not interstate, not overseas)

Again, this is an illustrative “typical” rule you might see. Your real matter might:

• Use a different number of days (e.g., 14, 21, 28, or 42 days)
• Count from different starting events (e.g., “from the date of order”, “after judgment is entered”, “after notice is given”)
• Use different rules for counting time (e.g., excluding the day of the event, or having special rules for short time periods)

Base example input set

In DocketMath’s deadline calculator, you might plug in:

1. Jurisdiction

   • Australia (AU)
   • Sub‑jurisdiction (if available): New South Wales (NSW)

2. Event that starts the clock

   • Label: Service of statement of claim
   • Date of service: 3 March 2026 (a Tuesday)
   • Time of service: Often irrelevant unless the rules specify a cut‑off (e.g., before 4 pm). We’ll assume no special time rule and leave it at default.

3. Time limit

   • Number: 28
   • Unit: days
   • Time direction: after the service date

4. Counting rules

   • Include the start day? → No (start the count the next day)
   • Count calendar vs business days → Calendar days
   • If deadline falls on a weekend or public holiday → Move to next business day

5. Public holidays

   • Holiday region: New South Wales
   • Auto‑include:

     • National public holidays (e.g., Good Friday, Anzac Day)
     • NSW‑specific holidays (e.g., NSW Bank Holiday, Queen’s/King’s Birthday date for NSW, Labour Day)

6. Output preferences

   • Show:

     • Calculated due date
     • Breakdown of how days were counted
     • Flags for weekends / public holidays

These inputs are all configurable in DocketMath. The value of using a calculator is being able to tweak any of them and immediately see how the due date moves.

Example run

Let’s walk one run from start to finish using those base inputs. The goal here is to make every assumption explicit so you can audit the timeline later and explain each adjustment if someone challenges the date. Keep your rule citation, holiday set, and counting method visible while you work through each step.

Step 1: Define the triggering event

• Trigger: Service of statement of claim
• Service date: 3 March 2026 (Tuesday)

The rules say the defence is due 28 days after service.

DocketMath’s default time‑count logic (for many AU rules) is:

• Exclude the day of the triggering event
• Start counting on the next day

So you count:

• Day 1 = 4 March 2026 (Wednesday)
• …
• Day 28 = ?

Step 2: Count 28 calendar days

We’ll count from 4 March 2026:

1. 4 Mar – Day 1
2. 5 Mar – Day 2
3. 6 Mar – Day 3
4. 7 Mar – Day 4 (Saturday)
5. 8 Mar – Day 5 (Sunday)
6. 9 Mar – Day 6
7. 10 Mar – Day 7
8. 11 Mar – Day 8
9. 12 Mar – Day 9
10. 13 Mar – Day 10
11. 14 Mar – Day 11 (Saturday)
12. 15 Mar – Day 12 (Sunday)
13. 16 Mar – Day 13
14. 17 Mar – Day 14
15. 18 Mar – Day 15
16. 19 Mar – Day 16
17. 20 Mar – Day 17
18. 21 Mar – Day 18 (Saturday)
19. 22 Mar – Day 19 (Sunday)
20. 23 Mar – Day 20
21. 24 Mar – Day 21
22. 25 Mar – Day 22
23. 26 Mar – Day 23
24. 27 Mar – Day 24
25. 28 Mar – Day 25 (Saturday)
26. 29 Mar – Day 26 (Sunday)
27. 30 Mar – Day 27
28. 31 Mar – Day 28

So, before applying any weekend/holiday adjustment, the 28th day falls on:

• Provisional due date: 31 March 2026 (Tuesday)

Step 3: Check weekends and public holidays

Now, DocketMath checks:

• Is 31 March 2026 a Saturday, Sunday, or NSW public holiday?

  • 31 March 2026 is a Tuesday, and not a common Australian public holiday.

Therefore:

• No adjustment is needed
• Final due date remains 31 March 2026

Step 4: Summary of this run

Using the example inputs:

• Trigger date: 3 March 2026 (service)
• Time limit: 28 calendar days after service
• Counting rule: Exclude service day; start from 4 March
• Weekend/holiday rule: Push to next business day if needed
• Result:

  • 28th day = 31 March 2026
  • Not a weekend or holiday
  • Defence due date = 31 March 2026

In DocketMath, that date appears with a short breakdown of the day‑by‑day count and any adjustments.

Sensitivity check

The real power of a calculator is testing “what if” changes. Below are common variations and how they change the outcome.

We’ll run quick sensitivity checks on:

• Start date
• Service method / deemed service
• Time unit (calendar vs business days)
• Weekend and public holiday adjustments

1. Changing the service date

Keep everything else the same (28 days, same rules), but change the service date.

Scenario A: Service the previous Friday

• Service date: 27 February 2026 (Friday)
• Exclude service date → Day 1 = 28 February 2026 (Saturday)

Counting 28 calendar days:

• Day 1 = 28 Feb (Sat)
• Day 2 = 1 Mar (Sun)
• Day 3 = 2 Mar (Mon)
• …
• Day 28 = 27 Mar (Fri)

Check:

• 27 March 2026 is a Friday, not a holiday → due date = 27 March 2026

Result: Just by moving service earlier, the defence is due four days earlier (27 March vs 31 March).

Scenario B: Service on a public holiday

Suppose, instead, service occurs on 7 April 2026 and that day is treated as a recognised public holiday in the relevant jurisdiction.

• Service date: 7 April 2026 (Tuesday, public holiday)
• Many rules still treat that day as the event date; counting usually still excludes it.
• Exclude 7 April → Day 1 = 8 April 2026 (Wednesday)

Count 28 days from 8 April:

• Day 28 = 5 May 2026 (Tuesday), assuming no intervening holidays that push it.

So:

• Provisional due date: 5 May 2026
• Not a weekend or (typically) a public holiday → due date remains 5 May 2026

The fact that service was on a holiday does not necessarily affect the count, as long as the rules don’t say otherwise. DocketMath’s logic is driven by the rules you select.

2. Changing the service method (deemed service)

Many Australian rules have deemed service provisions, e.g.:

• Documents sent by post may be taken to be served several business days after posting
• Certain electronic service after a cut‑off time may be deemed served on the next business day

Imagine:

• Document posted on: 3 March 2026 (Tuesday)
• Deemed service rule: “Service is taken to occur 4 business days after posting”

DocketMath can model this in two steps:

1. Compute the deemed service date (4 business days after 3 March 2026)
2. Then apply the 28‑day rule starting from that deemed date

Step 1: Deemed service = 4 business days after 3 March 2026

Count 4 business days from 3 March:

• Day 1 = 4 Mar (Wed)
• Day 2 = 5 Mar (Thu)
• Day 3 = 6 Mar (Fri)
• Skip weekend
• Day 4 = 9 Mar (Mon)

So:

• Deemed service date = 9 March 2026 (Monday)

Step 2: Apply the 28‑day limit from deemed service

Now treat 9 March as the service date.

• Exclude 9 March → Day 1 = 10 March 2026 (Tuesday)
• Count 28 calendar days from 10 March

Counting forward:

• Day 1 = 10 Mar
• …
• Day 28 = 6 April 2026 (Monday), assuming no intervening public holidays that require adjustment.

So:

• Defence due date = 6 April 2026 (Monday)

Compare this with the original example:

• Original: Actual service on 3 March → due date 31 March
• With deemed service 4 business days later (9 March) → due date 6 April

The combination of deemed service + weekends has pushed the deadline back by nearly a week.

3. Switching to business‑day counting

Now change the time unit itself:

• Time limit: 28 business days after service
• Service date: 3 March 2026 (Tuesday)
• Exclude service date; start on 4 March

We now skip Saturdays, Sundays, and NSW public holidays while counting.

At a high level, 28 business days:

• Roughly equals 5–6 calendar weeks
• Pushes the deadline significantly later than a 28 calendar‑day rule

DocketMath will:

1. Mark each weekday as a business day unless it’s a public holiday
2. Stop at the 28th business day
3. Confirm whether that day is itself a business day (it should be by definition)

Result: You might end up with a due date in mid‑ to late‑April 2026 instead of 31 March 2026. That difference can be critical for scheduling, strategy, and client communication.

4. Changing weekend/holiday roll‑forward behaviour

Not every rule says to “move to the next business day”. Some may:

• Allow filing on the preceding business day
• Require you to meet the original date even if it’s a weekend (e.g., electronic filing systems)

If you change DocketMath’s weekend/holiday handling from:

• Move to next business day → to → Do not adjust; deadline stays on that date

Then in a scenario where Day 28 lands on a Sunday:

• With adjustment: due date = Monday
• Without adjustment: due date remains Sunday (which may be effectively unworkable in practice)

This is why the configuration step is crucial; DocketMath doesn’t guess the rule—it follows whatever setting you specify.

Using DocketMath in practice

For Australian matters, a practical workflow in DocketMath’s /tools/deadline calculator might look like:

• Capture the exact rule citation (e.g., court rule or statute section)
• Note whether the rule uses calendar or business days
• Confirm how the start day is treated (excluded or included)
• Check for deemed service rules if documents weren’t served personally
• Select the correct state/territory public holidays
• Run the calculation and export or save the breakdown to your file

This keeps your reasoning visible to colleagues and auditable if the date is ever questioned.

Related reading

• Browse the blog