How to run deadlines in DocketMath for Canada

Step-by-step

Running deadlines in DocketMath for Canada is straightforward once you map your date inputs to the type of deadline you’re calculating. This guide walks through the typical workflow so you can generate a due date (and, when relevant, supporting dates like notice timelines) using the Deadline calculator.

1) Start at the Deadline calculator

1. Open DocketMath’s deadline calculator:

   • Primary CTA: Run a deadline calculation

2. Select the Canada jurisdiction (CA), if your interface prompts you.

   • Your jurisdiction selection ensures the calculator uses the Canadian-centric approach built into the tool.

2) Choose the deadline pattern

Most deadline calculators ask you to define:

• Start date (the “clock starts” date)
• Deadline length (e.g., 5, 10, 30 days)
• Counting method (calendar days vs. business days, and whether weekends/holidays are skipped)

In DocketMath, you’ll typically complete fields in this order:

• Start date: when the triggering event occurs
• Number of days: how long until the deadline
• Day type: whether to count calendar days or business days

If you’re unsure which to use, pick the most defensible operational assumption for your document workflow:

• Use business-day counting when the rule says “business days” or when filings are expected to occur only on business days.
• Use calendar-day counting when the document or rule uses “days” without excluding weekends.

3) Enter the triggering event date

Add the date that should start the countdown. Common “clock starts” anchors include:

• Date of service (mailing/email/service date)
• Date of receipt
• Date a document is issued
• A contract “notice given” date

How the output changes:

• If you move the start date by 1 day, the computed deadline will usually move by 1 day as well.
• With business-day counting, moving the start date across a weekend/holiday can shift the result by more than 1 day because non-business days may be skipped.

4) Confirm how the calculator counts days

DocketMath’s deadline tool generally supports options for how days are calculated (for example: calendar days vs. business days). Set it to match the deadline logic you’re trying to run.

Practical tip:
If your deadline is tied to “filing” or “responding,” business-day counting is often a safer baseline for internal scheduling—because staff and service providers generally operate on business days.

If the rule explicitly references “calendar days,” switch to calendar days to avoid under-counting.

5) Add any extra time or offsets (if your workflow uses them)

Some deadline setups include additional offsets beyond the base deadline length (for example, a notice period plus a response time).

If DocketMath provides fields for offsets (or lets you model it by running separate calculations), do one of these:

• Single run: enter the total day count if the rule is expressed as one combined period.
• Two-step run: calculate the end of the notice window, then use that computed date as the start date for the next stage.

Output behavior guidance:

• Two-step calculations can reduce mistakes because each step has a clear “clock start.”
• Single runs are faster but require you to be precise about the combined day count.

6) Review the results and export what you need

After you run the calculation, DocketMath displays:

• The computed deadline date
• Often a breakdown of how the counting worked (depending on the tool’s UI)

Use the result to populate your workflow, such as:

• Calendar entry date
• Internal task due date
• “Last day to act” reminder date
• A second reminder date (e.g., 2–3 business days earlier) so you’re not relying on the final day

Common pitfalls

Deadlines are easy to mis-run when day counting and trigger dates aren’t aligned with how the underlying rule is structured. Here are the most frequent issues when people use DocketMath for Canada.

• counting from the wrong triggering event
• ignoring court-closed days or holiday rules
• mixing calendar days with court days
• missing time-of-day cutoffs for filing

1) Mixing up calendar days and business days

• Symptom: Your deadline lands on a weekend/holiday even though you selected business-day logic—or vice versa.
• Fix: Verify the day-counting mode before running the calculation.
• Quick check: After computing, look at the day-of-week. If it contradicts your selected counting method, redo with the correct setting.

2) Using the wrong “start date”

• Symptom: Off-by-one or off-by-more-than-one errors.
• Common causes:

  • Using the date you generated a document instead of the date it was served/received
  • Using an inbox timestamp instead of the actual service date your process records
• Fix: Identify the triggering event date used by your internal recordkeeping, and enter that exact date as the start date.

3) Forgetting that skipping non-business days changes the interval

When business-day counting is enabled:

• A “10-day” interval might span more than 10 calendar days.
• Moving the start date across a weekend can change the computed deadline more than you expect.

Checklist:

4) Trying to “stack” deadlines without recalculating

Some users try to handle sequential components (e.g., notice period then response period) in a single run with a total day count. This can go wrong if:

• the second stage’s “start” is not the same as the first stage’s “start,” or
• the stages use different day-counting rules.

Safer approach:

5) Not planning for reminder buffers

Even if the computed deadline date is correct, execution risk remains:

• documents may require signatures,
• service workflows can take time,
• internal review cycles don’t happen instantly.

Operational scheduling:

Try it

If you want to validate your workflow right now, run a test calculation in DocketMath and compare the output with your expectations.

Open the Deadline calculator and follow the steps above: Run the calculator.

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

A simple test run (practice)

1. Go to the deadline calculator: **Run a deadline calculation
2. Choose Canada (CA).
3. Enter:

   • Start date: pick a known weekday (for example, a Monday)
   • Day type: start with calendar days for an easy sanity check
   • Number of days: try a small value like 10
4. Run the calculation and confirm:

   • Your deadline falls exactly 10 days after the start date (for calendar-day counting).

Then switch to business-day counting with the same values and confirm the deadline is not shorter than the calendar-day version.

Use DocketMath to schedule a two-stage workflow

If your process has:

• a notice window, then
• a response period,

do this:

Related reading

• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations
• Common deadlines mistakes in Australia — Common errors and how to avoid them