Inputs you need for statute of limitations in Rhode Island
5 min read
Published April 8, 2026 • By DocketMath Team
Inputs you will need
To run a statute of limitations (SOL) calculation in Rhode Island using DocketMath, you’ll want the case facts that determine when the clock starts and whether any timing exceptions apply. Rhode Island’s general rule is the baseline you start from in DocketMath:
- General SOL period (default): 1 years
- General statute: General Laws § 12-12-17 (Rhode Island)
Important: The provided jurisdiction data did not identify a claim-type-specific sub-rule. That means you should treat the 1-year period as the default starting point in DocketMath unless your scenario clearly involves timing exceptions that the tool can reflect via its tolling/exception inputs.
Before you click Run, gather these inputs (use the exact dates from your case file whenever possible):
- **1) Date of the triggering event (the “start date”)
- Example categories: the date an act occurred, the date a violation happened, or another event your workflow treats as accrual/trigger.
- 2) Filing date
- The date the matter was commenced (or the filing milestone your workflow uses).
- 3) Case type / cause of action label you want to evaluate
- DocketMath may use this to decide whether it applies the general 1-year rule under § 12-12-17 versus any additional logic available in the tool. With the current jurisdiction data, the safe baseline is the default 1-year rule.
- 4) Jurisdiction confirmation
- Confirm you’re using Rhode Island (US-RI).
- **5) Any known tolling or exception facts (if applicable)
- Even when your starting point is 1 year, certain facts can change the timing. If you already know them, capture the relevant date ranges (for example, the period(s) you believe toll the SOL) so DocketMath can model the result.
Gentle reminder: DocketMath can only calculate based on the inputs you enter. If you omit a date tied to a tolling/exception you believe applies, the output may show a deadline that looks “expired” even if an exception could extend it.
Where to find each input
Use the checklist below as a practical guide to where each input typically lives in your records. Prefer official dates (docket stamps, filed documents, court entries, and authenticated records) over summaries or memory.
| Input | What you’re extracting | Typical place to find it |
|---|---|---|
| Triggering event date | The date you treat as accrual/trigger (the event that starts the SOL clock) | Complaint narrative, incident report, contract/communications log, event memo |
| Filing date | The date the case was filed/commenced | Electronic filing confirmation, clerk’s stamp, docket entry, notice of filing |
| Case type label | The legal category you’re evaluating (helps align the tool’s logic with your scenario) | Pleading caption, case management summary, internal issue tracker |
| Jurisdiction confirmation | Evidence you’re in Rhode Island for the SOL analysis | Complaint caption, court assignment, docket header |
| Tolling/exception facts | Facts that may pause/extend the SOL, including any relevant date ranges | Motion practice, discovery timeline, correspondence, prior orders |
To keep your baseline aligned with Rhode Island law while you input data, keep General Laws § 12-12-17 in mind during entry and use US-RI with the default 1-year period—unless your workflow identifies an exception scenario and DocketMath provides corresponding fields for it.
Run it
Open DocketMath’s SOL calculator:
Confirm jurisdiction:
- Set it to US-RI (Rhode Island).
Select or confirm the SOL logic:
- Use the general/default period of 1 year tied to General Laws § 12-12-17.
- Because the jurisdiction data did not surface a claim-type-specific sub-rule, don’t switch away from the default 1-year rule unless your workflow includes additional exception logic you’ve identified and can support with facts.
Enter the key dates:
- Triggering event date (start date)
- Filing date
Add tolling/exception inputs (if available in the tool and if you have them):
- Enter the relevant dates/ranges based on what’s in the record—not estimates.
Review DocketMath output:
- Identify the computed deadline (the “latest filing date” under the entered assumptions).
- Compare that deadline to the filing date you entered to see whether the result indicates:
- within time, or
- time-barred, under the entered facts.
Warning: SOL deadlines can hinge on single-day details. If your triggering event date is off (for example, using the incident date instead of the accrual/trigger date your case treats as controlling), a 1-year deadline can shift materially.
How the output typically changes when you adjust inputs:
- Changing the triggering event date: shifts the SOL deadline forward/backward.
- Changing the filing date: can move the case from “within time” to “time-barred” (or vice versa) relative to the computed deadline.
- Adding tolling/exception facts: can effectively extend or alter the deadline if the tool supports those inputs and the facts are properly entered.
- Switching case-type logic: may change which SOL rule the tool applies. With the current jurisdiction data, the safest baseline is still the default 1-year rule under § 12-12-17.
After you review the result, consider saving it along with the exact inputs used so you can rerun the calculation if you later obtain clearer dates from discovery, corrected docket entries, or amended filings.
Related reading
- Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
- Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
- Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator