Worked example: attorney fee calculations in California

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

Run this scenario in DocketMath using the Attorney Fee calculator.

Below is a worked example of how attorney fee calculations typically look in California using DocketMath (attorney-fee). This example is illustrative—it shows mechanics, not a guarantee of what a court will award in any particular case. (Use it as a planning aid, not legal advice.)

Scenario

  • Claim type: A civil lawsuit where attorney fees are at issue
  • Jurisdiction: California (US-CA)
  • Fee request timing question: When do attorney-fee-related claims need to be filed?
  • Assumptions for the example: The attorney fee amount is computed based on:
    • a negotiated hourly rate,
    • documented hours,
    • and any fee recovery limits you enter into the calculator.

Inputs you provide to DocketMath

You’d enter the following kinds of inputs in the calculator workflow (with example numbers):

  1. Hourly rate: $450/hour
  2. Hours claimed: 30 hours
  3. Attorney fee multiplier (optional): 1.0 (no multiplier)
  4. Costs included (optional): $600
  5. Pre-judgment interest flag: Off (kept simple for this worked example)

Statute of limitations (timing) inputs used in the example

The calculator can incorporate timing questions based on California’s general/default civil limitations period.

California’s general/default statute of limitations is:

Because no claim-type-specific sub-rule was found in the provided jurisdiction data, this worked example uses only the general/default period. In other words, it applies CCP § 335.1 (2 years) as the default baseline.

Note: This example uses the general/default two-year limitations period under CCP § 335.1 because no claim-type-specific sub-rule was provided. If a different statute or a special timing rule applies to your situation, the outcome can change.

Timing dates (example)

To show how the calculator might treat “how long you have,” we’ll add dates:

  • Accrual / trigger date (example): January 15, 2024
  • Filing date (example): February 1, 2026

These dates are used only to demonstrate how timing impacts whether a filing is treated as “within” the limitations period.

Example run

Now let’s run the example with the inputs above.

Run the Attorney Fee calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Compute base attorney fees

Formula (typical calculator structure):

  • Base fees = (Hourly rate × Hours) × Multiplier

Numbers:

  • Hourly rate = $450
  • Hours = 30
  • Multiplier = 1.0

Base attorney fees:

  • $450 × 30 = $13,500
  • $13,500 × 1.0 = $13,500

Step 2: Add costs (if included)

Costs entered: $600

Total fees + costs (for this example):

  • $13,500 + $600 = $14,100

Step 3: Apply the default statute of limitations window (timing check)

Using the general/default period:

  • CCP § 335.1: 2 years
  • Accrual date: January 15, 2024
  • Two-year deadline: January 15, 2026

Filing date in the example: February 1, 2026

Result (timing):

  • February 1, 2026 is after January 15, 2026
  • Under this default timing assumption, the filing would fall outside the 2-year window.

Warning: A limitations check like this is a mechanical baseline. Accrual, tolling, and legal theory can matter. This worked example is meant to show calculator logic, not to predict litigation outcomes.

Step 4: Summarize the output

Here’s what a DocketMath-style output breakdown might look like for these inputs:

Output componentExample value
Base attorney fees ($450 × 30 × 1.0)$13,500
Costs (optional included)$600
Combined total (fees + costs)$14,100
Default SOL window (CCP § 335.1)2 years
Accrual → deadline (Jan 15, 2024 → Jan 15, 2026)Passed (filed Feb 1, 2026)

If you want to reproduce this workflow in DocketMath, you can start here: /tools/attorney-fee.

Sensitivity check

Next, let’s test how small input changes can shift the result. This is where calculators earn their keep: you can see what drives the number.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity 1: Hours change by ±10%

Keep:

  • hourly rate = $450
  • multiplier = 1.0
  • costs = $600
HoursCalculationFeesFees + costs
27 hours (−10%)$450 × 27$12,150$12,750
30 hours (baseline)$450 × 30$13,500$14,100
33 hours (+10%)$450 × 33$14,850$15,450

Takeaway: With an hourly model, fees move almost linearly with hours.

Sensitivity 2: Rate changes by ±10%

Keep:

  • hours = 30
  • multiplier = 1.0
  • costs = $600
Hourly rateCalculationFeesFees + costs
$405 (−10%)$405 × 30$12,150$12,750
$450 (baseline)$450 × 30$13,500$14,100
$495 (+10%)$495 × 30$14,850$15,450

Takeaway: Rate increases and hour increases have the same effect in this structure because both multiply the same base.

Sensitivity 3: Multiplier applied

Keep:

  • hourly rate = $450
  • hours = 30
  • costs = $600
MultiplierCalculationFeesFees + costs
0.8$13,500 × 0.8$10,800$11,400
1.0$13,500 × 1.0$13,500$14,100
1.2$13,500 × 1.2$16,200$16,800

Takeaway: If your calculator supports multipliers, the multiplier can be a major driver of the final number.

Sensitivity 4: Timing within vs. outside the 2-year default

Now we vary the filing date while keeping:

  • accrual date = January 15, 2024
  • default period = 2 years under CCP § 335.1
Filing dateTiming result vs. Jan 15, 2026 deadline
Dec 20, 2025Within 2 years
Jan 15, 2026At deadline (boundary)
Feb 1, 2026Outside 2 years

Takeaway: A shift of just a few weeks can flip the timing posture when the default two-year window controls.

Pitfall: The “default 2 years” rule from CCP § 335.1 is a baseline. If a different limitations period, tolling, or accrual rule applies to your specific theory, the relevant deadline can be different—even if the fee calculation inputs remain the same.

Related reading