Worked example: statute of limitations in Texas
5 min read
Published April 8, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Statute Of Limitations calculator.
This worked example shows what a statute of limitations (SOL) calculation can look like in Texas (US‑TX) using DocketMath – statute-of-limitations.
Here is a simple illustration for Texas. These values are for demonstration only and should be replaced with your actual inputs.
- Principal or amount: contract claim
- Rate or cap: N/A
- Start date: undefined
- End/as-of date: N/A
Assumptions for this example
To keep the math concrete, we’ll use one set of dates and the general/default SOL rule:
- Jurisdiction: Texas
- Statutory basis: Texas Code of Criminal Procedure, Chapter 12
Source: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm - SOL rule used: General/default
- No claim-type-specific sub-rule was found in the provided jurisdiction data.
- So this example uses the general SOL period rather than a specialized rule for a particular offense type.
General SOL period value used by the calculator: 0.0833333333 years
That equals 1 month, because 1 / 12 = 0.0833333333.
Gentle note: This is a worked example of the calculator’s mechanics, not legal advice. Texas’s Chapter 12 includes nuances, and offense-specific timing rules may apply in real cases.
Example scenario (dates)
Assume the following facts:
- Date of the alleged conduct (event/conduct date): 2025-01-15
- Case filed (charging) date: 2025-02-20
- Date precision convention: treat dates as calendar dates (no “hours” precision)
- SOL computation method (as modeled by the DocketMath tool in this example):
- Compute a deadline by adding the general SOL period to the conduct date
- Compare the filing/charging date to that deadline
Inputs you’d enter in DocketMath
Use these as a baseline set in DocketMath – statute-of-limitations:
- Conduct date: 2025-01-15
- Filing/charging date: 2025-02-20
- Jurisdiction: US‑TX
- SOL rule selection: General/default
- General SOL period: 0.0833333333 years (= 1 month)
If you want to reproduce it, use: /tools/statute-of-limitations.
Example run
Now let’s run the calculation step-by-step using the inputs above.
Run the Statute Of Limitations calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Convert the SOL period
The provided general SOL period is:
- 0.0833333333 years
Convert years to months:
- 1 year = 12 months
- 0.0833333333 years × 12 = 1.0 month
So, the calculator’s SOL length here is effectively 1 month.
Step 2: Compute the deadline
Add one calendar month to January 15, 2025:
- Deadline = 2025-01-15 + 1 month = 2025-02-15
Step 3: Compare filing date to deadline
Now compare:
- Filing/charging date: 2025-02-20
- Deadline: 2025-02-15
Because 2025-02-20 is after 2025-02-15, the general/default model flags the filing as:
- Outcome (general/default SOL): likely time-barred (based on this simplified general-period model)
Quick results table
| Item | Date |
|---|---|
| Alleged conduct date | 2025-01-15 |
| SOL length used | 0.0833333333 years (= 1 month) |
| Calculated SOL deadline | 2025-02-15 |
| Filing date | 2025-02-20 |
| Comparison | 2025-02-20 > 2025-02-15 |
What this example is (and isn’t)
- What it is: a demonstration of how a general/default period turns into a deadline and how the filing date comparison works in the DocketMath tool.
- What it isn’t: a comprehensive legal conclusion. Even within Texas Code of Criminal Procedure, Chapter 12, real-world outcomes can depend on case-specific details and which limitations rule applies.
Sensitivity check
Small date changes can flip the result. Below are three “what-if” variations using the same conduct date (2025-01-15) and the same general/default SOL period (1 month).
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Variation A: File 5 days earlier
- Filing date: 2025-02-10
- Deadline: 2025-02-15
Result: Not time-barred under this general/default model (because 2025-02-10 ≤ 2025-02-15).
✅ Passes the deadline check.
Variation B: File exactly on the deadline
- Filing date: 2025-02-15
- Deadline: 2025-02-15
Result: On time under this illustration’s boundary convention (filing on the deadline date meets the condition).
✅ Passes the deadline check.
Variation C: File 1 day later
- Filing date: 2025-02-16
- Deadline: 2025-02-15
Result: Likely time-barred under this model.
⚠️ Fails the deadline check.
Sensitivity table
| Scenario | Filing date | Deadline | Model comparison | Result |
|---|---|---|---|---|
| A | 2025-02-10 | 2025-02-15 | ≤ | Not time-barred |
| B | 2025-02-15 | 2025-02-15 | = | On time |
| C | 2025-02-16 | 2025-02-15 | > | Likely time-barred |
Key takeaway
With a 1-month SOL period (derived from 0.0833333333 years), the deadline is highly sensitive to month boundary effects and even single-day shifts. In practice, you’ll want to ensure the dates you enter match what the tool expects (e.g., the event date and the specific filing/charging date used for comparison).
Checkbox checklist for cleaner inputs
Use this checklist to keep your runs consistent:
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
