Inputs you need for deadlines in Texas

6 min read

Published April 8, 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 Deadline calculator.

To run a deadline calculation in Texas with DocketMath (deadline tool), you’ll want a clean set of inputs so the tool can apply Texas’s general limitations framework. In Texas, the relevant provisions are in Texas Code of Criminal Procedure, Chapter 12: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

Because your brief indicates no claim-type-specific sub-rule was found, this article uses the “general/default period” as the starting point (i.e., the baseline you should run first).

Texas jurisdiction data used for the baseline run:

General SOL period (default): 0.0833333333 years
Source (general framework): Texas Code of Criminal Procedure, Chapter 12
https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

Note (important): Texas’s Chapter 12 includes multiple limitations concepts and exceptions/extensions may exist depending on the facts. This checklist is meant to help you run baseline deadlines using the general/default period when no claim-type-specific sub-rule is identified.

Use the inputs below as a minimum viable set to get reliable, consistent outputs from DocketMath.

Input checklist (Texas / US-TX)

Even if DocketMath can compute with defaults, explicitly setting these inputs reduces the odds of silent assumptions—especially when records include times or inconsistent date formats.

Where to find each input

Here’s what each input means and how to map it to what you already have in your case file or timeline. Keeping these definitions straight will make your output easier to interpret and easier to validate.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Start date (trigger date)

What to look for: the date that starts the limitations clock, such as:

the date of the alleged offense/event (commonly used in limitations analyses), or
another statutorily defined trigger shown in the document you’re working from.

Why it changes outputs: the start date drives the entire computation—shift it by a day and the deadline typically shifts accordingly (subject to how the tool converts 0.0833333333 years into calendar logic).

2) Clock type (interpretation of the start)

What it is: in practice, “start date” can be recorded differently across sources. DocketMath’s deadline tool needs you to choose the interpretation that matches your workflow, such as:

whether the deadline calculation treats the start date as inclusive/exclusive, and/or
whether the computation treats “after” in a particular way.

Why it changes outputs: two users can use the same calendar date but get different results if the clock-type interpretation differs.

3) Limitations period basis (general/default)

For the baseline run, use the provided general/default period:

0.0833333333 years (general/default)
Authority framework: Texas Code of Criminal Procedure, Chapter 12
https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

Because your brief found no claim-type-specific sub-rule, do not swap in a different period yet. Start with the default so you have a consistent baseline.

Why it changes outputs: this is the “duration” that sets the deadline boundary. Changing it changes the computed end date.

4) Time zone / date handling preference

What to decide: whether your inputs include timestamps and whether you want DocketMath to normalize date/time boundaries (for example, if your source data mixes local time and UTC).

Why it changes outputs: when time components and time zones are involved, normalization can shift the effective “date” used for the calculation.

5) Holidays/weekend handling preference

What it controls: some deadline workflows treat an “end date” as an action deadline that moves when it falls on a weekend or holiday.

Why it changes outputs: the tool may produce:

a raw due date, and/or
an adjusted actionable date (depending on the setting)

Warning: If you compare results that used different weekend/holiday settings, you may think the limitations period changed—when it really was only the adjustment rule.

Run it

For the most consistent results, run the calculation in a repeatable order and document the inputs you used.

Enter the inputs in DocketMath and run the Deadline calculation to generate a clean breakdown: Run the calculator.

Capture the source for each input so another team member can verify the same result quickly.

Step-by-step workflow in DocketMath (deadline)

Open the deadline tool: /tools/deadline
Confirm Jurisdiction: Texas (US-TX).
Enter the required inputs:
- **Start date (trigger date)
- Clock type that matches your “start” interpretation
- Limitations period basis: set to the general/default 0.0833333333 years
- Set time zone/date handling preference (if applicable)
- Set holidays/weekend handling preference (if applicable)
Run the calculation.
Save/capture:
- the computed deadline date
- any intermediate values shown by the tool (if available)
- any assumptions the tool displays based on your selections

What the output should do when you change inputs

Use these quick validation checks:

Change the start date by +1 day:
The output deadline should shift forward by about the same magnitude (noting that conversion from 0.0833333333 years into calendar days/month logic may affect exact day counts).
Change holidays/weekend handling:
You should see an adjusted “action” deadline if the raw deadline lands on a non-business day.
Change clock type:
The computed deadline should shift in a way that matches your inclusive/exclusive or “after” logic.

Pitfall: If changing inputs doesn’t change outputs, double-check that the fields are actually being populated and that the tool isn’t using a hidden default for that category (especially the start date).

Gentle reminder (not legal advice)

Deadlines and limitations outcomes can depend heavily on case facts and exceptions. This tool-based checklist is meant to help you compute a baseline deadline using the general/default period from Texas Code of Criminal Procedure, Chapter 12—not to replace legal judgment.