How to run statute of limitations in DocketMath for Singapore

Step-by-step

This guide walks you through running a statute of limitations calculation in DocketMath for Singapore (SG) using the Statute of Limitations calculator. The goal is to help you turn relevant dates into a clear timeline quickly—without digging through spreadsheets.

1) Open the right tool

1. Go to the primary calculator: **/tools/statute-of-limitations
2. Confirm the jurisdiction is set to SG (Singapore).

If you’re starting from elsewhere in DocketMath, go directly to the Statute of Limitations calculator to avoid accidentally using the wrong jurisdiction settings.

2) Identify the cause type you’re calculating

In Singapore, limitation outcomes depend on the type of claim (and often the statutory category). Before entering dates, decide what you’re modeling. Common categories you may see in calculators include:

• Contract / debt-type claims (commonly time-limited under the Limitation Act framework)
• Tort / personal injury-type claims
• Actions for damages linked to negligence or other civil wrongs
• Recovery actions that may include specific limitation structures

If your situation involves more than one category, run separate calculations for each category and compare the resulting “last day” outcomes.

3) Enter the key date(s)

Most limitation workflows require a starting reference point and a duration. In DocketMath, you’ll typically enter dates like:

• Start date: the date the clock begins (for example, date of breach, date of damage, date of act/omission, or a discovery-related date—depending on the claim type you select).
• Claim date / event date (if prompted): sometimes the tool asks you to specify the relevant triggering event in a separate field (for example, date of injury or date of wrongdoing).
• Filing / action date (optional but recommended): the date you plan to file (or the date you want to evaluate against).

How outputs change based on inputs

Use these rules of thumb while entering data:

• Move the start date later → the computed deadline generally moves later by the same offset (when the period is fixed in the selected scenario).
• Move the filing date later → the “within time / past due” evaluation becomes more likely to flip from “within” to “out of time.”
• Change the claim type selection → the duration and/or the clock-start logic may change, which can significantly alter the “deadline” result.

4) Review the computed “last permissible date”

After you submit (or after the calculator auto-updates), DocketMath should show items such as:

• The calculated limitation period (e.g., a specified number of years or another window, depending on the selected category)
• The deadline date (the last day to start the action as modeled)
• Often an indicator of whether a chosen filing date falls before or after that deadline

Treat the “last permissible date” as the tool’s modeled endpoint for the inputs you entered. If you later refine the dates or the claim type, rerun the calculation.

5) Validate with a quick timeline check

Before relying on a deadline date, sanity-check it against your timeline.

Use this checklist:

If something feels off, re-check:

• the claim type selection, and
• which date field you used for the clock-start logic (start vs event vs discovery, where applicable).

6) Run scenario comparisons (recommended)

Many limitation questions reduce to: “What if the relevant starting date is different?” DocketMath is easiest to use when you run a small set of scenarios.

Try 2–3 scenarios such as:

• **Scenario A (earliest plausible start date)
• **Scenario B (best-estimate start date)
• **Scenario C (latest plausible start date)

Then compare:

• the three computed deadline dates, and
• whether your intended filing date is within time in any scenario.

This is especially helpful when dates are uncertain (for example, when evidence supports a range rather than a single day).

7) Export or copy results for case notes

Once you get outputs you can rely on for your current assumptions, capture:

• the chosen claim type
• the start date used
• the computed deadline
• the filing date you evaluated (if you included one)

Keeping these notes makes it easier to rerun the calculation quickly after you confirm details from documents or timelines.

For related workflow support, you may also find it useful to review DocketMath’s other timeline and date-handling tools under /tools so your case calendar stays consistent across calculations.

Common pitfalls

Even when a limitation-period calculation is correct, results can be misleading if the inputs don’t match the claim category or the clock-start logic. Common issues include:

• Using the wrong date in the wrong field

  • Example: entering a “knowledge/discovery” date into a field intended for an “event/act” date (or the reverse), depending on how the calculator models the clock for that claim type.
• Selecting an incorrect claim category

  • Contract-style and tort-style models typically produce different deadlines, even if you reuse the same date.
• Mixing multiple claims into one run

  • Different causes of action can have different limitation regimes. Combining them can produce a deadline that’s wrong for one component.
• Assuming day-count details won’t matter

  • DocketMath uses actual calendar dates. A shift of even a day (e.g., 1 May vs 2 May) can shift the computed deadline accordingly.
• Confusing “planned” dates with “actual filed” dates

  • If the tool compares against a filing date, be sure you’re consistent about whether you entered the date you intend to file or the date you actually filed.

Try it

Use this quick practice run to get comfortable with the calculator workflow:

1. Open /tools/statute-of-limitations.
2. Choose SG as the jurisdiction (if not already set).
3. Select one claim type (start with the category closest to your situation).
4. Enter:

   • a start date you can justify from your timeline, and
   • a tentative filing date to see whether you fall before or after the computed deadline.
5. Note the computed deadline date.
6. Change only one input at a time (e.g., move the start date by +30 days) and observe how the deadline shifts.

To make comparisons meaningful, test this while you practice:

You can also copy this mini comparison structure for your own scenarios:

Once you can interpret how a single date change moves the deadline, you’ll be ready to run scenario sets tied to your real document dates.

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator
• Statute of limitations in United States (Federal): how to estimate the deadline — Full how-to guide with jurisdiction-specific rules