Inputs you need for Statute Of Limitations in Philippines

5 min read

Published April 15, 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 Statute Of Limitations calculator.

To run a Philippines Statute of Limitations check in DocketMath (PH), gather the inputs below so the statute-of-limitations calculator can apply the right, jurisdiction-aware rule set. Use this checklist to build a timeline and avoid “garbage in, garbage out.”

Examples: written contract, oral contract, quasi-delict, injury/assault with specific labels, collection of sum of money, foreclosure-related claims, etc.

Limitation rules differ sharply between civil claims and criminal prosecutions, so this is one of the most important toggles.

Civil: the event that starts the prescriptive period (commonly a contract breach date).
Criminal: the date the offense was committed (or the last relevant act for continuing offenses).

Examples (depending on your facts): written extrajudicial demands and certain filings that may interrupt prescription. Only enter these if you have dates and proof.

If you already filed, the filing date matters for timing—and for how interruption may be modeled (depending on what you input).

Examples: whether a special law might apply instead of general rules, or whether the subject matter is regulated (which can change the prescriptive period).

This helps confirm which operative date is relevant in your setup (accrual/commission vs. who is “bringing” the action).

Not always required for limitation calculations, but helpful for matching the correct claim category in your case summary.

Keep a quick list: contract, demand letter, incident report, complaint/case number, police blotter, judgment, or pleadings.

Note (not legal advice): DocketMath can only calculate what you tell it. If you select the wrong case type (for example, treating a quasi-delict claim as a contractual claim), your computed deadline can be off by a lot.

If you’re working from documents, aim to extract exact dates from:

signed agreements,
timestamps on demand letters,
incident reports,
affidavits,
court docket entries,
and pleadings.

Where to find each input

Use this quick “source map” to avoid hunting through files at the last minute.

Input	Where to find it in your documents	How precise it must be
Case type / cause of action	Complaint/position paper, demand letter, legal theory section of your pleading	High—choose the label that matches your factual theory
Civil vs. criminal	Caption and body of the filing; whether it references the Revised Penal Code / special penal laws	High
Date of accrual or commission	Contract breach date; incident date; “on or about” date in affidavits; police blotter; complaint allegations	Very high—use the day/month/year
Interruption/tolling evidence	Copies of demand letters, proof of receipt, filed motions/complaints	High—need dates and proof
Complaint filed and when	E-filing confirmation, court stamp, docket entry	High—need the actual filing date
Special-law vs. general rule indicators	Statute mentioned in demand or complaint; regulatory context	Medium to high—depends on your case facts
Parties and roles	Caption page; verification; criminal complaint details	Medium—helps map “who is seeking what”
Claim amount/currency	Demand letter amount; Statement of Account; receipts	Low to medium—usually not a limitation input, but helpful

Practical extraction checklist (fast)

If you’re unsure which category fits, start by writing one sentence:
“The claim is for ___ because ___ happened on ___.”
That sentence usually reveals the correct DocketMath pathway.

Run it

Follow this workflow in DocketMath: start with the tool, confirm PH jurisdiction, then enter the operative date(s) you verified.

Open the calculator: **/tools/statute-of-limitations
Choose Jurisdiction PH (Philippines).
Enter:
- Civil or criminal
- Case type / cause of action
- Relevant date (accrual or commission)
- Any interruption events you have dates for (e.g., demand, filing) only if supported by documents
Review the output for:
- Computed prescriptive period
- Deadline date (based on the rule and the relevant date)
- Effect of interruptions (if your inputs support that concept)

What changes the output most

These inputs usually drive the largest differences:

Can completely change the limitation framework. A one-month difference can shift the computed deadline by about the same magnitude, and may affect whether something looks timely. Contract vs. quasi-delict vs. other categories can differ materially. The deadline can move because the calculator uses your interruption date(s).

Suggested data entry order (to reduce errors)

Warning (practical): If you don’t have the receipt date of a demand letter (or similar proof), you may be missing the most date-sensitive interruption input. That can skew results even if the theory is correct.

Quick self-check before finalizing

Before relying on the computed deadline, confirm:

If your timeline includes multiple events (e.g., series of breaches), list each date in a short note—even if the calculator ultimately needs only one. That helps you adjust your inputs if the first run produces an implausible deadline.