How to run attorney fee calculations in DocketMath for North Carolina
6 min read
Published April 15, 2026 • By DocketMath Team
Step-by-step
Run this scenario in DocketMath using the Attorney Fee calculator.
Below is a practical walk-through for running attorney fee calculations in DocketMath for North Carolina (US-NC) using the attorney-fee calculator. This is a workflow guide—not legal advice—and fee rules can depend on the claim and procedural posture.
1) Open the attorney-fee calculator
Start at the primary CTA: /tools/attorney-fee.
If you’re already inside DocketMath, navigate directly to the attorney-fee tool and select North Carolina (US-NC) as the jurisdiction.
2) Confirm the inputs you can control
Before entering numbers, gather what you’re trying to calculate—typically fees driven by time and rate. Common inputs include:
- Hourly rate (or blended rate)
- Billable hours (or the hours you intend to treat as compensable)
- Costs (if your workflow includes them)
- Any adjustments you routinely apply (for example, partial reductions tied to time entries)
Then enter those values into the calculator fields.
3) Understand the North Carolina timing assumption (default = 3 years)
For North Carolina attorney fee calculations, DocketMath’s jurisdiction setup uses the default limitations period logic based on the provided jurisdiction data.
Important (default limitation period clarification):
DocketMath’s North Carolina jurisdiction data reflects a general/default limitations period of 3 years. The dataset does not specify a claim-type-specific sub-rule. So, treat 3 years as the default unless your case research identifies a more specific rule that should apply.
4) Run the calculation and review what drives the output
After submitting your inputs, DocketMath will compute totals based on the values you entered and the tool’s internal computation flow.
Use this checklist to interpret the result:
- Check the “hours × rate” base
Does the output match your own quick mental/spreadsheet calculation? - Verify which time is included
If you enter only billable or compensable time, confirm you didn’t accidentally include non-compensable entries. - Review cost treatment (if costs are enabled)
If you entered costs, confirm whether they’re being added on top of fees or handled separately in your intended workflow. - Confirm jurisdiction default assumptions
DocketMath should apply the 3-year general/default period unless you adjust the basis in the tool (or you otherwise align with a specific rule for your matter).
5) Change one input at a time to sanity-check results
A fast way to catch data-entry or field-mapping issues:
- Increase billable hours by 1.0 hour
- Expected impact: output should rise by about rate × 1.0 (plus any cost logic, if enabled).
- Change hourly rate by $25/hr
- Expected impact: output should shift by about hours × $25.
- Add a fixed $100 costs amount (if your setup includes costs)
- Expected impact: total should reflect that addition if costs are configured to be included.
This “single-variable test” helps confirm the calculation is reacting to your inputs the way you expect.
6) Use results for computation and documentation (not legal conclusions)
Treat DocketMath as your calculation engine and a record of assumptions. Keep notes on:
- Where each number came from (timekeeper export, billing ledger, invoice totals)
- Any reductions or adjustments you entered intentionally
- The jurisdiction default used (3-year general/default period)
Note: This guide focuses on how to run the attorney fee calculation in DocketMath. Fee entitlement and recovery can vary by statute and proof—use the output as a computed estimate based on your inputs, not as a final legal determination.
Common pitfalls
Even strong users run into predictable issues. Here are the most common friction points when running attorney fee calculations in DocketMath for US-NC.
- using gross recovery when net applies
- mixing recoverable and non-recoverable time
- skipping statutory prerequisites
- forgetting fee caps or schedules
1) Assuming the default 3-year period is always correct
The jurisdiction data provided here indicates a general/default 3-year limitations period and does not include a claim-type-specific sub-rule.
- If your matter involves a statute with a different limitations/timing rule, the default may not match the correct legal framework.
- DocketMath will still compute using its jurisdiction setup and your entered inputs—so the key risk is pairing correct numbers with an incorrect legal assumption.
2) Mixing billable and non-billable time
If your fee calculation should reflect only compensable time, be careful not to include entries that are:
- non-billable
- reduced or partially compensable
- excluded under your internal standard
When mixed in, results often come out “too high” and become harder to reconcile later.
3) Confusing fees versus costs
Many workflows treat:
- attorney fees separately from costs
- costs as add-ons (or omit them entirely)
If you enter costs, make sure you’re putting them into the calculator’s intended cost section (if available) so the structure of your totals matches your intended approach.
4) Rate mismatch problems (blended vs. per-role)
If your billing records include multiple roles (e.g., associate + paralegal), a blended rate can be reasonable—but only if you apply it consistently.
Common drift scenario:
- you enter hours across multiple roles
- but apply a single rate that only matches one role’s category
5) Skipping a quick output validation
After one run, do a short check:
- +1 hour, verify totals increase by about rate × 1
- +$50/hr, verify totals shift by about hours × $50
If the output doesn’t move as expected, it usually indicates a field mapping or entry problem.
6) Not tracking assumptions for later reruns
DocketMath output is most useful when you preserve:
- the inputs you used
- the jurisdiction default behavior (including the 3-year general/default assumption)
- the scenario you ran
Try it
- Open /tools/attorney-fee
- Select **North Carolina (US-NC)
- Enter your core inputs:
- hourly rate
- billable hours
- (optional) costs, if your workflow includes them
- Confirm the output totals
- Run a quick validation:
- add +1 hour and confirm totals move by ~rate × 1
- If you want to compare scenarios:
- rerun with different rates, hours, or cost amounts and compare the computed outputs
Warning: DocketMath applies the 3-year general/default limitations period from the provided jurisdiction data, and the dataset here does not identify a claim-type-specific sub-rule. If you determine a different limitations period applies in your situation, align your assumptions before relying on computed results.
Also, for context related to victim-support and legal process in North Carolina, the North Carolina Department of Justice provides resources referencing the SAFE Child Act:
https://www.ncdoj.gov/public-protection/supporting-victims-and-survivors-of-sexual-assault/
Related reading
- Worked example: attorney fee calculations in Vermont — Worked example with real statute citations
