Inputs you need for attorney fee calculations in Texas

6 min read

Published April 15, 2026 • By DocketMath Team

Inputs you will need

Run this scenario in DocketMath using the Attorney Fee calculator.

To run attorney fee calculations in Texas using DocketMath (Calculator: attorney-fee), you’ll want to collect a consistent set of inputs each time. That makes it easier to rerun the calculation when facts change and to document what drove the fee result.

Below is a practical checklist of the inputs that typically affect an attorney-fee computation. Even if your matter is criminal-adjacent or involves a specific procedural posture, the underlying data collection is usually the same.

Checklist: attorney-fee calculation inputs (Texas)

  • Case number (or internal matter ID)
    • Court / proceeding name (helpful for your own audit trail)

    • Confirm you’re running the calculator under Texas:

      • DocketMath jurisdiction: US-TX

      • Hours billed (or compensable hours, as defined by your window)

      • Rate per hour (and whether it changes by task/timekeeper)

    • Start date (the beginning of what you consider compensable for the calculation)

    • End date (your cutoff—commonly a judgment date or internal reporting cutoff)

    • Whether the calculation uses an annualized component (common in time-based setups)

    • Any effective date used for calculation

    • Some attorney-fee workflows require you to convert a statutory period into a “year fraction” (a proportional year value used by the calculator logic).

    • For the Texas default statutory framework, you’ll need the general/default period:

      • General SOL period: 0.0833333333 years (which equals 1 month expressed as a year fraction)

Important (default rule clarification): The Texas statutory time period above comes from the general/default framework in Texas Code of Criminal Procedure, Chapter 12. No claim-type-specific sub-rule was identified for this workflow, so you should use the general/default period as the starting point. Source: Texas CCP Chapter 12 (see link in “Where to find each input”).

Where to find each input

You can make your workflow smoother (and reduce rework) by mapping each input to where it normally lives in your records. This is also the easiest way to avoid “mystery numbers” when you review the output later.

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.

Practical sourcing map

InputWhere to find it in your file
Case / matter identifiersDocket sheet, pleadings cover page, internal intake form
Jurisdiction selectionDocketMath jurisdiction selector (set to US-TX)
Fee basis (hourly vs. flat)Fee agreement, engagement letter, billing guidelines
Hours billedBilling system exports, timekeeper logs, attorney invoices
Rate per hourFee agreement / rate schedule / billing policy; invoice line items
Costs / expenses (if included)Receipts, expense reports, invoice attachments
Payable window start/endBilling instruction email, court deadlines you’re tracking, your internal “cutoff” definition
Statutory time conversion settingDocketMath settings (use 0.0833333333 years for Texas general/default reference in this workflow)

Texas default time conversion reference you’ll need

If DocketMath prompts for a year-fraction-style statutory period, use:

  • 0.0833333333 years — representing the General SOL Period as a month expressed in year fraction form

Use this as the general/default value drawn from:

Warning: Don’t substitute a different time period unless your calculation instructions specifically tell you to. Because no claim-type-specific sub-rule was found for this workflow, the general/default period is the one to use.

Run it

After you collect the inputs, you’re ready to run DocketMath → attorney-fee with the Texas setup.

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

If an assumption is uncertain, document it alongside the calculation so the result can be re-run later.

Step-by-step run sequence (input discipline)

  1. Go to /tools/attorney-fee
  2. Select the attorney-fee calculator.
  3. Set jurisdiction to US-TX (Texas).
  4. Enter your fee model
    • Hourly model: input hours and the applicable rates (including any rate variations by task/timekeeper, if your data tracks that way).
    • Flat model: input the flat amount and any breakdown you’ve chosen internally for tracking/reporting (if your workflow expects it).
  5. Set the payable window
    • Enter the start date and end date that define what time is included.
  6. Apply the Texas default statutory time conversion (if prompted)
    • Use 0.0833333333 years as the general/default period reference.

How outputs will change when inputs change

Use this quick cause-and-effect guide to sanity-check results:

Change you makeExpected effect on output
Increase total billable hoursTypically increases total fee (often proportional to hours, depending on rate structure)
Change hourly rateFee shifts based on the rate difference; mixed-rate cases can change totals in non-linear ways if tasks/rates vary
Shorten the payable windowUsually lowers total fee by excluding time outside the window
Add or include costsIncreases total by the cost inclusion rule used in the workflow
Change the statutory time conversion periodCan materially re-scale time-based components—using the wrong period can significantly distort the result

Sanity check before you finalize

Before exporting or relying on the output:

  • Verify the date range matches your intended payable window (no entries outside the start/end dates).
  • Confirm your rates match your fee basis and billing data (hourly vs. flat).
  • Confirm you used the Texas general/default period (0.0833333333 years) rather than attempting a claim-type-specific alternative (none identified for this workflow).
  • Keep notes on what changed between runs (e.g., different window end date, different timekeeper rates, or newly included costs).

Related reading