How to run deadlines in DocketMath for Texas

Step-by-step

Run this scenario in DocketMath using the Deadline calculator.

This guide walks you through running Texas-related deadlines in DocketMath. I’ll focus on the default deadline logic using Texas Code of Criminal Procedure, Chapter 12 (the general framework), and I’ll show you how to interpret the calculator output.

1) Open the deadline calculator in DocketMath

Start at the primary call to action: /tools/deadline (open the deadline calculator).

When you land on the calculator, you’ll typically see inputs for:

• Start date (the trigger for counting time)
• End condition (how DocketMath should compute the deadline—by date)
• Time period (or a setting that maps to the default Texas general period)

If you don’t see a single “Texas Chapter 12 default” selector, you can still use the calculator by entering the general period in the next step.

2) Use the Texas general/default period (Chapter 12)

For Texas criminal timing under Texas Code of Criminal Procedure, Chapter 12, use the general/default period provided in the brief:

• General SOL Period: 0.0833333333 years

To sanity-check what that means in everyday terms:

• 0.0833333333 years × 365 days/year ≈ 30.4166667 days

In practice, treat it as about 30 days, but let DocketMath produce the final end date, since its day-counting/rounding method may not match the “round number” expectation.

Also, the brief explicitly notes: No claim-type-specific sub-rule was found. The above is the general/default period.
So, treat this as your baseline and don’t assume it automatically applies to every specific situation—always verify whether a different subsection/rule governs your scenario.

3) Choose the start date that matches your trigger

Most deadline workflows only work when the start date matches the actual event that starts the clock.

Examples of common “triggers” you may see in case workflows (illustrative):

• a filing date
• a notice date
• the date an order became effective

Action step:

• Enter the actual event date you’re counting from.
• Use the correct calendar date in your workflow. If your process involves same-day events, double-check whether your system treats them as the same day or different days.

4) Enter the period and run the calculation

In DocketMath, set the Time period to the general/default Texas value:

• Time period: 0.0833333333 years

If the interface asks for days instead of years, use:

• ~30.4166667 days (DocketMath may round—watch the output)

Then click Calculate.

DocketMath should return:

• the computed deadline/end date
• the counted duration (often in days/years)
• potentially a breakdown of the timeline

5) Interpret the output: “clock time” vs. “calendar date”

A common surprise is that “30 days” in everyday language doesn’t always equal the same “30 days” a tool computes—especially with fractions of days.

When you get the end date from DocketMath:

• compare it to your calendar immediately
• if the end date feels off by a day, rerun using the same inputs and check whether the calculator is effectively treating the count as inclusive/exclusive of the start date
• don’t change multiple fields at once—one small change at a time helps you understand what’s happening

Practical tip:

• Write down exactly what you entered: start date + period + any other key settings (so you can reproduce the result).

6) Run quick “what-if” tests to confirm direction and logic

DocketMath is especially helpful when you test your setup.

Recommended pattern:

• Keep the Texas general/default period fixed at 0.0833333333 years
• Change only the start date by ±1–3 days
• Recalculate each time

What you should generally observe:

• Moving the start date later should move the end date later as well (often by about the same amount), with small differences depending on rounding/day-counting.

This helps catch input mistakes like:

• using a “signed” date when your trigger is actually “received/served”
• typing the date in the wrong format
• selecting the wrong jurisdiction workflow (US-TX)

7) Make sure you’re using the right Texas rule set context

Because your jurisdiction is Texas, align your DocketMath workflow to US-TX logic.

In this guide, the timing framework is based on:

• Texas Code of Criminal Procedure, Chapter 12
  Source: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

And again: this guide uses the general/default period from the brief. If you later confirm that a specific subsection applies to your posture, you may need a different period than the baseline.

8) Record the result so it’s easy to reuse

After you compute a deadline, capture these details:

• the start date you entered
• the period used (0.0833333333 years for the Chapter 12 general/default baseline)
• the computed end date
• any notes about why you chose that trigger event date

This prevents “mystery recalculations” later—especially if you need to rerun with a corrected trigger date.

Common pitfalls

Deadline calculations usually go wrong for predictable reasons: mismatched triggers, wrong baseline periods, or rounding surprises.

• Using the wrong clock start date

  • Example workflow error: entering “order signed” when the trigger should be “notice received” (or vice versa).
• Assuming the default applies to every scenario

  • This guide uses the general/default period from Texas Code of Criminal Procedure, Chapter 12: 0.0833333333 years.
  • The brief also states no claim-type-specific sub-rule was found, so your scenario may need a different rule.
• Rounding surprises

  • 0.0833333333 years ≈ 30.4166667 days, so DocketMath may produce an end date that doesn’t match an exact “30-day” expectation.
• Skipping a sanity check

  • If the computed end date is earlier than the start date, or your result is wildly off, stop and re-check:

    • the date format
    • the period input
    • the jurisdiction/workflow setting
• Changing multiple inputs at once

  • For debugging, change only one input at a time (typically the start date). That makes it easier to see why the output moved.

Reminder: Don’t treat a single computed date as definitive until you confirm your selected trigger event matches the start of the relevant timing rule in Texas Code of Criminal Procedure, Chapter 12 (general framework). The calculator is only as accurate as the assumptions you enter.

Try it

Use DocketMath to run a baseline Texas deadline using the general/default period.

Open the Deadline calculator and follow the steps above: Run the calculator.

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

Quick practice checklist

What you should observe

When the start date moves forward by 1 day (with the same period input):

• the deadline end date should generally move forward by about one day or close to it
• any slight differences are often explained by rounding/day-counting behavior

Validate before you act

After your run:

• compare the end date to your calendar
• confirm the start-date trigger is truly the one you intend to count from
• remember this guide uses the general/default period under Texas Code of Criminal Procedure, Chapter 12, and no claim-type-specific sub-rule was identified in the provided brief

Related reading

• Why deadlines results differ in Canada — Troubleshooting when results differ
• Worked example: deadlines in New York — Worked example with real statute citations
• Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations