Worked example: deadlines in Singapore

Example inputs

Below is a worked example of how DocketMath calculates a deadline in Singapore (SG). This is written to show calculation mechanics—not legal advice. Where exact timing depends on facts (for example, the date you received notice), you should map your real-world dates carefully.

Scenario (single-event deadline)

You received a document on 15 Apr 2026, and you want the “X days from receipt” deadline.

To keep the example concrete, we’ll use an “X calendar days” model:

• Start date (receipt): 15 Apr 2026
• Deadline rule: Add 10 calendar days to the start date
• No business-day adjustments: weekends/public holidays do not change the result in this example (we’ll test that in the sensitivity check)

Inputs as DocketMath would capture them

• Jurisdiction: SG
• Calculator type: deadline
• Unit: calendar days
• Day count: 10
• Start date: 2026-04-15
• Adjust for non-working days: No (for the base run)

Common “gotchas” to confirm before running

Check these items because they affect the start date and therefore the computed deadline:

• ✅ Receipt vs. posting date
• ✅ Whether your task is triggered by service/receipt of a document
• ✅ Whether the deadline is defined as calendar days or business days
• ✅ Whether any extension or excluded period applies (not used in this base example)

Example run

Let’s run the deadline calculation using the base inputs above.

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-by-step date math (calendar days)

We start with:

• Start date: 15 Apr 2026

Add 10 calendar days.

A reliable way to visualize it:

DocketMath output (what you’d expect to see)

When you set:

• SG
• deadline calculator
• Start date = 15 Apr 2026
• 10 calendar days
• No non-working day adjustment

DocketMath should return:

• Computed deadline date: 25 Apr 2026

Interpreting the computed deadline

For this example, the deadline is purely arithmetic: “start date + 10 calendar days.”

• If you submit anything on 25 Apr 2026, it falls within the calculated deadline.
• Submissions on 26 Apr 2026 would be outside the 10-day window under this simplified calendar-day model.

Quick checks you can do in 10 seconds

Before relying on the tool output, run these mental sanity checks:

• Does the result fall roughly X days after the start?
  From 15 Apr, +10 lands on 25 Apr—consistent.
• If the deadline lands on a weekend, is that acceptable for your scenario?
  In the base run we did not adjust for weekends/holidays—so a weekend is allowed by design here.
• Is the start date definitely the “receipt” date?
  If receipt was later than 15 Apr, the deadline moves.

Sensitivity check

Now let’s stress-test the same scenario to show how DocketMath outputs change when you tweak inputs.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity A: start date moves by 1 day

Assume the same rule (10 calendar days), but receipt is actually 16 Apr 2026 instead of 15 Apr.

• Start date: 16 Apr 2026
• Deadline = 16 Apr + 10 calendar days
• Computed deadline: 26 Apr 2026

Result change: deadline moves by +1 day.

Sensitivity B: switch from calendar days to business days

Next, assume the rule is “10 business days,” where weekends are excluded, and (for this example) we do not model public holidays.

Starting again from 15 Apr 2026, count business days:

• 15 Apr 2026 is a Wednesday
• Business days are Mon–Fri

Count 10 business days:

1. Wed 15 Apr
2. Thu 16 Apr
3. Fri 17 Apr
4. Mon 20 Apr
5. Tue 21 Apr
6. Wed 22 Apr
7. Thu 23 Apr
8. Fri 24 Apr
9. Mon 27 Apr
10. Tue 28 Apr

Business-day deadline: 28 Apr 2026

Result change: from 25 Apr (calendar) to 28 Apr (business). That’s +3 days.

Sensitivity C: move to next working day if deadline falls on non-working day

Finally, consider a variation:

• Use the original 10 calendar days
• Add a rule: if the computed deadline lands on a weekend, shift it forward to the next working day.

In our base run:

• Calendar deadline: 25 Apr 2026
• 25 Apr 2026 is a Saturday
• Next working day: Monday, 27 Apr 2026

Adjusted deadline: 27 Apr 2026

Result change: from 25 Apr to 27 Apr (+2 days).

Sensitivity results table

What this means for your workflow

To avoid deadline drift, treat these inputs as “controls”:

Run it yourself in DocketMath

Use DocketMath’s deadline calculator here: **/tools/deadline

If you want to replicate the exact outputs from the table, start by setting:

• Jurisdiction: SG
• Start date: 15 Apr 2026
• Day count: 10
• Day type: toggle between calendar days and business days
• Adjustment: toggle weekend shifting on/off

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