Common statute of limitations mistakes in Singapore
9 min read
Published September 6, 2025 • Updated February 2, 2026 • By DocketMath Team
Singapore’s limitation rules can look deceptively simple: “6 years from the cause of action” or “3 years from the date of knowledge.” In practice, that simplicity is where many calculation mistakes start.
Below are the most common traps we see when people try to run statute of limitations calculations in Singapore—whether in spreadsheets, practice management systems, or by hand—and how to avoid them with a more systematic approach (and tools like DocketMath’s statute of limitations calculator).
The top mistakes
- using the wrong cause-of-action period
- skipping tolling or suspension windows
- treating discovery as accrual without support
- missing choice-of-law constraints
If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.
1. Treating “6 years” as a universal default
A frequent error is assuming:
“If it’s a civil claim in Singapore, the limitation period is 6 years.”
That’s only partially true. Under the Limitation Act 1959 (SG), 6 years is common for:
- Simple contract claims
- Most tort claims (e.g., negligence causing property damage)
But different periods apply in other contexts, for example:
- Personal injury: 3 years from the date of injury or date of knowledge
- Contribution claims between wrongdoers: 2 years from the date of judgment or settlement
- Land-related actions: often 12 years
- Enforcement of judgments: 12 years (with nuances)
If your “calculator” only has a single “6 years from event date” formula, it will silently miscalculate many claims.
Inputs that are often missing:
- Type of claim (contract, tort, personal injury, land, judgment enforcement, etc.)
- Whether the claim is against the Government (which may involve separate regimes)
- Whether the claim is about contribution between defendants
2. Using the wrong “start date” for the clock
Another common error is picking the wrong date as the “accrual” or “start” date. Common missteps:
- Using the date of contract instead of the date of breach
- Using the date of discovery for non-personal-injury torts, when time may run from the date damage first occurred
- Using the date of invoice instead of the date payment became due
- For instalment contracts, treating all sums as accruing on a single date, instead of each instalment having its own accrual date
For personal injury, people also confuse:
- Date of accident or injury
- Date the claimant first realised they had an injury
- Date they realised it was attributable to the defendant’s act/omission
Each of these can shift the limitation end date by months or years.
Typical input error:
Only one “event date” field is captured, without clarifying what legal event it represents (breach, damage, discovery, judgment, etc.).
3. Ignoring “date of knowledge” rules for personal injury
Singapore’s limitation regime recognises that some injuries are latent. For personal injury, the 3‑year period may run from the later of:
- The date of the injury; or
- The date the claimant had the requisite “knowledge” (e.g., that the injury was significant and attributable to the defendant).
Common errors include:
- Always calculating 3 years from the accident date; or
- Always calculating 3 years from the diagnosis date, even when the claimant knew or should have known earlier.
Because “knowledge” is a fact-sensitive concept, a rigid spreadsheet formula often oversimplifies this.
4. Failing to factor in disability, minority, or death
Limitation periods can be affected by:
- The claimant being a minor
- The claimant lacking mental capacity
- The claimant’s death before expiry of the limitation period
A typical error is to:
- Run the limitation as if the claimant were an adult with full capacity from day one
- Ignore the impact of the claimant’s death on when the estate’s cause of action can be brought
Practical impact:
If your inputs capture only the date of the incident and not:
- Claimant’s date of birth
- Periods of mental incapacity
- Date of death
your calculation may be incomplete.
5. Misunderstanding contribution and indemnity deadlines
In multi-defendant or third-party situations, contribution claims are often misunderstood.
Common issues:
- Assuming the contribution claim shares the same limitation period as the underlying claim
- Calculating from the original accident date, instead of from:
- The date of judgment; or
- The date of a settlement or compromise
Because these are often secondary or “follow-on” claims, they get diarised late or not at all.
6. Overlooking contractual limitation clauses
Many commercial contracts shorten (or sometimes extend) the time to bring a claim, for example:
- “Any claim must be commenced within 12 months of delivery.”
- “No action may be brought more than 2 years after termination of this Agreement.”
Common errors:
- Assuming statutory limitation periods always apply, regardless of contract
- Calculating from the statutory accrual date instead of the contractual trigger (e.g., “delivery,” “termination,” “completion”)
- Forgetting that multiple limitation regimes can overlap (statutory + contractual + insurance policy limits)
Warning: Contractual limitation clauses can sometimes be unenforceable or interpreted narrowly. Whether a clause actually binds the parties is a legal question; a calculator can’t resolve that. It can only model “if this clause applies, then the latest date is X.”
7. Treating limitation dates as inclusive of the anniversary
Another subtle error: misinterpreting how to count the final day.
People often:
- Treat “6 years from 1 Jan 2020” as “you can file up to and including 1 Jan 2026”
- Or they mix up whether the calculation is “before the 6th anniversary” vs “on the 6th anniversary”
This becomes especially messy when:
- The incident date is 29 February
- The court filing deadline falls on a weekend or public holiday
- E‑filing cut‑off times are involved
A one‑day miscalculation can be fatal to a claim.
8. Not updating calculations when facts change
Limitation dates are often calculated once and then treated as final. But they can change when new information surfaces, such as:
- Discovery of earlier damage (bringing accrual forward)
- Evidence that the claimant knew of the injury much earlier
- Recharacterisation of the claim (e.g., from contract to tort, or adding a personal injury component)
- Identification of a new defendant or cause of action
If your system:
- Stores only a single “limitation date” without the underlying assumptions; and
- Never re-runs the calculation when facts change
you risk relying on stale, inaccurate deadlines.
Pitfall: A bare date in a case management system (“Limitation: 14/08/2026”) without stored inputs and logic is almost impossible to audit later. You may not remember which assumptions produced that date.
How to avoid them
Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.
If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.
1. Start with the claim type and legal trigger
When using a tool like DocketMath, treat the claim type and trigger event as non‑optional inputs:
- ✅ Select: contract, tort (non‑personal injury), personal injury, land, contribution, judgment enforcement, etc.
- ✅ Identify the legal trigger:
- Date of breach
- Date damage first occurred
- Date of knowledge (for personal injury)
- Date of judgment or settlement (for contribution)
- Contractual trigger (e.g., delivery, termination)
This forces you to think about why the clock starts when it does, instead of defaulting to “incident date + 6 years.”
2. Capture all relevant dates, not just one
Design your workflow so that your limitation calculation can consider multiple dates:
- Incident / accident date
- Date of breach
- Date damage was first suffered
- Date claimant first consulted a doctor or expert
- Date claimant first knew (or is alleged to have known) the injury was significant and attributable
- Date of birth (for minors)
- Periods of mental incapacity
- Date of death
- Date of judgment or settlement (for contribution)
In DocketMath’s statute of limitations calculator, this translates into filling more than just the “event date” field. If you’re unsure which dates matter, treat them as scenario inputs and compare outcomes.
3. Model personal injury “date of knowledge” scenarios
Because “date of knowledge” is fact-sensitive, it helps to run multiple scenarios:
- Scenario A: knowledge on the accident date
- Scenario B: knowledge on first medical consultation
- Scenario C: knowledge on diagnosis of a serious condition
Then compare the limitation outputs for each scenario and record:
- Which date you used
- Why you chose it (e.g., based on current evidence)
This doesn’t replace legal advice, but it gives you a transparent, auditable calculation history.
4. Add claimant status fields (minor, capacity, death)
In your intake or case setup, add checkboxes and date fields such as:
Each checked box should prompt for:
- Date of birth
- Start and end of incapacity (if known)
- Date of death
Feed these into your calculator so you can see how they shift the limitation end date. If the law is unclear on how a specific status affects time, note that in your file and avoid treating any single output as definitive.
5. Separate primary claims from contribution/indemnity claims
For multi-party cases, maintain a simple table:
| Claim type | Trigger event | Limitation input date |
|---|---|---|
| Primary claim vs Defendant A | Date of breach / damage | e.g., 10 Mar 2021 |
| Contribution claim vs Defendant B | Date of judgment/settlement | e.g., 15 Aug 2024 |
| Indemnity under contract | Contractual trigger | e.g., date of termination |
Run each row as its own calculation rather than assuming all claims share the same deadline.
6. Always check for contractual limitation clauses
Make it routine to:
- Search your key contracts for terms like “limitation
