Inputs you need for deadlines in Singapore

5 min read

Published April 8, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Inputs you will need

Run this scenario in DocketMath using the Deadline calculator.

To run a Singapore (SG) deadline calculation in DocketMath, you’ll typically supply a small set of inputs. The goal is consistency: the same start date/time and the same “how to count” rules should produce the same due date every time you rerun the calculation.

Use this checklist before you open /tools/deadline:

Note: Deadlines depend heavily on what the rule counts (days vs months) and which anchor date you use (e.g., actual event date vs a deemed service date). If you pick the wrong anchor, DocketMath will still calculate correctly based on the inputs you provided—so double-check your anchoring before you rely on the output.

Where to find each input

Not every project will need every input above. Here’s how to source the ones you’ll most commonly use when working with deadlines in Singapore.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Jurisdiction (SG)

Where to find it: Your internal matter template, docket setup, or case management notes.
How it changes outputs: Jurisdiction drives which deadline conventions and holiday assumptions you align to in your workflow.

2) Deadline type / scenario

Where to find it: The document that contains the deadline rule you’re applying (e.g., a notice, a procedural step list, or a rule summary in your playbook).
How it changes outputs: Choosing an “X days from event” scenario vs an “X months from event” scenario changes the computation method (day-counting vs month rollover behavior).

3) Start date (event date)

Where to find it:
- From the date stamp on the triggering document
- From your service record (acknowledgment, email log, courier proof)
- From your system’s “event occurred” timestamp converted to a date (using your standard conversion)
How it changes outputs: Even a one-day shift in start date will typically shift the resulting deadline in the same direction—unless your deadline lands on a weekend/holiday boundary and triggers adjustment.

4) Start time (if relevant)

Where to find it: Service logs, delivery confirmations, email headers, or your internal workflow timestamp.
How it changes outputs: If the rule or your workflow is sensitive to time-of-day, using the correct time can prevent off-by-one-day errors around midnight.

5) Duration (number of days/months/years)

Where to find it: The procedural rule text or your internal “deadline rule” table.
How it changes outputs: DocketMath applies the duration exactly as entered—month-based periods can be especially sensitive to how the day-of-month is handled.

6) Business day / holiday handling

Where to find it:
- Your firm’s docketing policy
- Your internal calendar settings
- Matter instructions (e.g., “exclude weekends”, “adjust for public holidays”)
How it changes outputs: If a calculated date lands on a non-working day, the adjustment rules you select can change the final due date.

7) Service method timing (if “deemed service” is involved)

Where to find it: Your service step documentation and the method used for service (as captured in your matter file).
How it changes outputs: Deemed service timing turns the service step into an anchor date; the deadline is then measured from the deemed date rather than the actual send/delivery date.

8) End-of-day convention

Where to find it: Your internal docketing standard (for example, whether deadlines are treated as “by 5:30 pm” vs “by end of day”).
How it changes outputs: If you store times, end-of-day conventions can determine whether an action at 11:59 pm counts on the intended date.

Run it

Once you’ve collected the inputs, run the calculation in DocketMath:

Open the deadline calculator at /tools/deadline.
Select:
- Jurisdiction: SG
- The deadline type / counting method that matches your scenario
Enter the core values:
- Start date (and start time only if your workflow requires it)
- Duration (e.g., 14 days / 3 months)
Set the handling options:
- Weekend exclusion / business day counting
- Public holiday adjustment rules (based on your chosen policy/calendar)
Confirm:
- Time zone (Asia/Singapore)
- End-of-day convention (if applicable in your workflow)
Click to calculate and review:
- The computed deadline date
- Any intermediate results shown by DocketMath (for example, how a date was adjusted due to non-working days)

Before you finalize a due date in your matter:

Double-check the anchor: actual event date vs deemed service date vs filing date (if your rule uses a different anchor).
Verify the unit: days vs months (month-based deadlines are a common source of misunderstandings).
Confirm the calendar assumptions: weekends/holidays and any adjustment behavior.

Gentle disclaimer: This checklist and workflow support calculation consistency, but they don’t replace professional review of the underlying rule and factual inputs. Always verify the underlying deadline rule and the dates/times you’re feeding into the tool.