Worked example: deadlines in United States (Federal)

Example inputs

Run this scenario in DocketMath using the Deadline calculator.

This worked example shows how DocketMath calculates common federal deadlines using a typical “trigger date” plus the rules for business days and weekends/holidays.

Scenario (what we’re calculating)

You need to file a federal submission with a deadline that runs from the date an order is entered (i.e., the court’s docket entry date). In this example, we’ll calculate a deadline that is 14 days after entry, counted using business days (skipping Saturdays, Sundays, and federal holidays).

Inputs you’d provide to DocketMath

Why these inputs matter

The same “14” can produce different results depending on the day-count rule:

• Business days: weekends don’t count, so the deadline moves forward if the period hits a weekend.
• Calendar days: weekends do count, so the deadline moves earlier.
• Holidays: federal holidays can shift the deadline even when the weekend pattern looks predictable.

To keep this example concrete, we’ll walk through the business-day run first and then adjust inputs in the sensitivity check.

Example run

Run the Deadline calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Start from the trigger date

• Trigger date: 2026-04-08 (Wednesday)

Because we’re using business-day counting and the period is measured after the trigger date, we start counting on the next business day.

Step 2: List the counting window (business days)

Counting business days beginning the day after 2026-04-08:

• Wed 2026-04-09 = Day 1
• Thu 2026-04-10 = Day 2
• Fri 2026-04-11 = Day 3
• Mon 2026-04-14 = Day 4
• Tue 2026-04-15 = Day 5
• Wed 2026-04-16 = Day 6
• Thu 2026-04-17 = Day 7
• Fri 2026-04-18 = Day 8
• Mon 2026-04-21 = Day 9
• Tue 2026-04-22 = Day 10
• Wed 2026-04-23 = Day 11
• Thu 2026-04-24 = Day 12
• Fri 2026-04-25 = Day 13
• Mon 2026-04-28 = Day 14

Step 3: Check federal holidays inside the window

For this date range—2026-04-09 through 2026-04-28—the commonly observed federal holidays do not generally land inside it, so no holiday adjustment occurs in this specific run.

If you run the same inputs for a different year or a different trigger/lead time, holidays can matter—DocketMath is designed to reflect that.

Output: the computed deadline date

✅ Computed deadline (14 business days after 2026-04-08): 2026-04-28

Running it through DocketMath

To reproduce the calculation with the tool:

• Use /tools/deadline (DocketMath’s deadline calculator)

DocketMath applies the trigger date, your chosen day-count rule, and the holiday calendar to return the computed due date (and typically the final included day).

A practical sanity check against common mistakes

Before relying on a computed date, double-check these points:

• Did you use the entered date (docket entry date) when the rule keys off entry—rather than the served date (unless the rule keys off service)?
• Are you counting business days or calendar days?
• Did you exclude weekends as required by the business-day rule?
• Did the holiday calendar exclude any relevant federal holidays in the counting window?
• Did you start counting on the correct day relative to the trigger (this is where off-by-one errors often occur)?

DocketMath is helpful here because it makes the relative day-count mechanics explicit: the computed deadline comes from consistent application of the rule “after the trigger” plus your selected business/holiday settings.

Sensitivity check

Now let’s see how the deadline changes when you adjust inputs. This is where DocketMath is especially useful: small changes in the day-count rule or trigger date can move the final date.

We’ll keep the lead time at 14, but change the counting approach.

1) Same trigger date, switch from business days to calendar days

• Trigger date: 2026-04-08
• Lead time: 14
• Day-count rule: calendar days

Counting calendar days after the trigger gives a different result because weekends count.

• Day 1: 2026-04-09
• Day 2: 2026-04-10
• …
• Day 14 lands on 2026-04-22

✅ Calendar-days deadline: 2026-04-22

Delta vs. business-days run:

• Business: 2026-04-28
• Calendar: 2026-04-22
• Difference: 6 days earlier under calendar-day counting

2) Same rule, move the trigger by 1 day

Return to business days and change only the trigger date:

• Trigger date: 2026-04-09 (Thursday)
• Lead time: 14 business days

Counting starts on the next business day (Friday 2026-04-10 as Day 1). Because weekends are skipped, shifting the trigger forward by one business day generally shifts the deadline forward.

✅ Business-days deadline with trigger 2026-04-09: 2026-04-29

Delta: typically +1 business day when the trigger shifts by one business day (though in some configurations, a weekend boundary can affect the pattern).

3) Add a holiday (to see how the tool reacts)

The April 8–April 28 window in this example may not include a major federal holiday. To test holiday behavior, try a lead time/window that overlaps a known federal holiday (for example, a lead time that crosses a late-Monday federal holiday).

When doing so, verify this behavior:

• DocketMath should skip federal holidays when the day-count rule is business days
• The computed due date should land on the next available business day after the holiday

If you want a quick workflow, run a few variations:

• business vs. calendar
• trigger date ±1 day
• windows that do/don’t cross a federal holiday

Compare outputs to build confidence in the mechanics.

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