Common attorney fee calculations mistakes in North Carolina

The top mistakes

Run this scenario in DocketMath using the Attorney Fee calculator.

Running attorney-fee calculations in North Carolina is where small input errors can create big downstream problems—especially when fee shifting is part of the analysis. Below are common mistakes people make when using DocketMath’s attorney-fee calculator (US-NC).

1) Using the wrong statute of limitations (SOL) for fee timing

A frequent error is applying an incorrect limitations period to fee-related timing.

• North Carolina’s general/default SOL period is 3 years.
• Your provided materials reference the SAFE Child Act as a general statutory theme (victim/support framework), but no claim-type-specific sub-rule was found for this purpose.

Baseline for calculations: If your governing law does not clearly supply a different rule, use the general/default 3-year period.

How this affects DocketMath outputs If your workflow includes a “recoverable period” (e.g., you limit time entries by date), the SOL choice can change:

• which dates are included,
• the eligible “billable-to-include” window,
• and therefore the total hours used in the fee calculation.

2) Mixing billed hours with collectible (recoverable) hours

People often enter hours billed when the question is really hours that may be collectible/recoverable.

This happens when:

• time includes tasks that aren’t necessary for the claim at issue,
• time includes internal revisions, clerical work, or non-case communications that may not map cleanly to recoverable litigation work,
• time categories aren’t separated (e.g., drafting vs. appearance vs. uncertain/duplicative work).

Calculator impact DocketMath computes from what you enter: (hours × rate) (plus any other inputs you use). If your “hours” bucket includes non-recoverable time, the resulting fee estimate can be inflated even if rates and other numbers are correct.

3) Misstating hourly rate inputs

Another high-impact error is entering the wrong rate for the correct person and time period.

Examples:

• using a single blended rate when your rates vary by attorney or year,
• entering a “pre-discount” rate when your effective rate is different under the billing agreement,
• confusing “total billed amount” with an hourly “rate” (which can lead to double-counting).

Calculator impact Because fee math scales with rate, even a modest mismatch can change the output substantially (for example, a 10% rate difference scales the hours portion by 10%).

4) Double-counting costs (entering the same expense twice)

Costs can be counted twice in a few common ways:

• entering expenses in the costs section and again embedding them in time-based entries,
• adding the same itemized cost line multiple times.

Calculator impact DocketMath may be internally consistent, but double-counted inputs will produce an overstated fee/cost demand relative to your real underlying damages/fee request.

5) Running fee math without confirming fee-shifting eligibility

Not every scenario supports a fee award automatically. A practical error is running “attorney-fee math” without first confirming there is a pathway to fees (statutory or contractual).

Calculator impact Even if the arithmetic is correct, the output may be unusable if the governing authority doesn’t permit fee shifting in your situation.

6) Letting date/format issues skew eligibility windows

Date-based inputs drive inclusion/exclusion logic. Common data problems include:

• start and end dates swapped,
• including a date that falls just outside the limitations window,
• using the wrong date field (for example, invoice date vs. work-performed date).

Calculator impact A boundary error can change which time entries are included, producing “why is my number so different?” confusion that’s really caused by input mapping, not legal substance.

How to avoid them

Use this checklist to sanity-check your DocketMath attorney-fee inputs before you rely on the output.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step 1: Set (and document) the default SOL window

Because the brief indicates no claim-type-specific sub-rule was found, treat 3 years as the default assumption for fee-related timing unless your governing law clearly indicates otherwise.

If your DocketMath workflow includes an inclusion window:

• define the start date (trigger),
• define the end date (trigger + 3 years).

Checklist

Step 2: Separate recoverable work from other time before entering hours

Before entering hours, break your source data into buckets, such as:

• recoverable litigation work (claim-relevant drafting/research/motion work),
• hearing/appearance time (if applicable),
• non-recoverable/uncertain time (clerical, duplicative, or non-claim work).

Then enter only what you intend to treat as recoverable (based on your review).

Checklist

Step 3: Match rate inputs to the right attorney/role and time period

Confirm rate inputs align to who did the work and when it was performed.

Checklist

Step 4: Enter costs once, using one consistent approach

Pick one approach and stick to it:

• Enter itemized expenses only in the costs section, and keep time entries free of reimbursable expense duplication; or
• If time entries reflect reimbursable expenses, ensure you do not also add the same expenses as separate cost lines.

Checklist

Step 5: Confirm fee-shifting eligibility before trusting the estimate

Before relying on a fee number, confirm the scenario supports fee recovery under a valid basis (statute/contract) and that your framing is consistent with reasonableness/timing expectations.

Checklist

Step 6: Run a sensitivity check on the biggest drivers

Fee totals usually move most with:

• included hours,
• hourly rates,
• and any multiplier/adjustment inputs.

Try quick tests in DocketMath:

• reduce included hours by ~10% and confirm the output decreases in a proportional way,
• adjust one rate category and confirm the output responds accordingly.

Checklist

Related reading

• Worked example: attorney fee calculations in Vermont — Worked example with real statute citations
• Attorney Fees Guide for Alaska
• Attorney Fees Guide for American Samoa