Statute of Limitations for Securities Fraud (state Blue Sky laws) in Texas

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

Texas “Blue Sky” securities fraud claims rely on a general statute-of-limitations (SOL) framework using the provided Texas criminal-law limitation reference: Texas Code of Criminal Procedure, Chapter 12. In this page, DocketMath’s statute-of-limitations calculator translates the provided SOL period into a practical deadline you can track.

In common usage, “Blue Sky laws” refers to state securities regulation and securities-fraud enforcement. This page is focused on the time limits that apply under the general/default rule you provided for “securities fraud (state Blue Sky laws) in Texas.”

Jurisdiction data used (as provided):

• General SOL Period: 0.0833333333 years
• General Statute: Texas Code of Criminal Procedure, Chapter 12
  Source: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

Important (per your note): No claim-type-specific sub-rule was found. This means the page applies the provided general/default period as the controlling SOL window, rather than a tailored rule for a specific securities-fraud label.

Limitation period

Based on your jurisdiction data, the general/default SOL period is 0.0833333333 years, which is approximately 1 month.

• Conversion (for intuition): 0.0833333333 years × 12 months/year ≈ 1 month
• Practical takeaway: a 1-month window is short. It should trigger early fact collection (including the best-supported “trigger/accrual” date you plan to enter into the calculator) and prompt review of the record.

What “start date” typically means in SOL workflows

While you should consult the underlying statutes and your specific facts, SOL tracking commonly requires choosing a trigger date (for example, the date tied to accrual under the applicable framework). The key operational point is:

• The deadline moves when the trigger date moves.

Using DocketMath (inputs and outputs)

In DocketMath’s /tools/statute-of-limitations workflow, you generally provide:

• Trigger date (your selected start date)
• Jurisdiction: US-TX
• Rule/Period: the provided general/default period (0.0833333333 years)

Expected output:

• Deadline date = trigger date + ~1 month

Because SOL time is calculated from your selected start date, even small changes to the trigger date can shift the deadline by days. DocketMath helps keep the math consistent once the same inputs are used across review.

Quick timeline example (time-boxing)

If your trigger date is January 15, 2026:

• a ~1-month limitation window would land around February 15, 2026 (depending on how your system counts month boundaries for the chosen dates)

Key exceptions

This page is deliberately constrained to the general/default period you provided and explicitly notes that no claim-type-specific sub-rule was found. That said, real-world SOL outcomes can still depend on whether the framework involves an “exception” concept.

In a practical compliance or case-triage checklist, you may want to test issues in these general areas (without treating them as legal advice):

• Accrual vs. discovery-type measuring concepts: Some limitation frameworks measure from occurrence/accrual rather than later discovery.
• Tolling or pauses: Some procedural events can pause or delay the running of the limitation clock.
• Procedural posture effects: The timing outcome may vary depending on what stage the matter is in and how it is framed procedurally.
• Mismatch between your “label” and your governing rule: Even if the matter is described as “securities fraud,” the governing limitation language may depend on how the action is legally characterized.

What to do next in your workflow

To operationalize this safely:

1. Use DocketMath to generate a baseline deadline.
2. Sanity-check internally:

   • What date do you believe is the appropriate trigger/accrual date to enter?
   • Are there any facts suggesting the clock could be paused or treated differently?
   • Does the enforcement/claim framing match the default framework rather than a separate, more specific limitation track?

Statute citation

This page is based on the Texas Code of Criminal Procedure, Chapter 12 limitation framework reference you provided:

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

How the provided jurisdiction data is applied

• General SOL Period: 0.0833333333 years
• General Statute: Texas Code of Criminal Procedure, Chapter 12
• Rule selection: General/default only (no claim-type-specific sub-rule identified in your provided data)

Use the calculator

Run the baseline deadline calculation in DocketMath here: /tools/statute-of-limitations.

How to use it:

• Enter your Texas trigger date (the start date you are tracking).
• Use the provided general/default SOL period (0.0833333333 years).

What you’ll get:

• A deadline date computed by adding approximately 1 month to your trigger date.

Adjustments you can make (and how outputs change)

Re-run the calculator if you change inputs:

• Change the trigger date → the deadline shifts accordingly.
• Change the rule/period → the deadline can change materially.
  In this page, your instruction is to use the general/default period (since no claim-type-specific sub-rule was found).

To keep the audit trail clean, record:

• the exact trigger date used,
• the period used (0.0833333333 years / ~1 month),
• and the resulting deadline date.

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