Attorney Fees Guide for Washington

What this calculator does

DocketMath’s Attorney Fee calculator for Washington (US-WA) helps you estimate potential attorney-fee exposure or recovery using a structured, math-first approach.

Instead of trying to predict a judge’s discretion, the calculator focuses on the inputs that typically drive fee calculations:

• Fee basis you enter (for example, hourly rate × hours, or a negotiated/estimated fee number)
• Enhancements or modifiers you choose to include (if your internal model uses them)
• Arbitration or litigation structure assumptions you encode in your inputs (e.g., phase assumptions you reflect via different hours/categories)
• Total requested fees vs. fees you expect to be awarded (you choose how to model reductions)

What it does not do

• It does not determine whether Washington law allows fees in your specific case.
• It does not decide whether a court will reduce fees for reasons like duplication, inefficiency, or excessive hours.

If you’re starting from scratch, you can run the estimate here: DocketMath Attorney Fee Tool.

When to use it

Use DocketMath when you need a quick, auditable estimate during a real workflow such as:

• Early case assessment: Compare settlement value vs. likely fee magnitude.
• Demand or response planning: Roughly size the “fees and costs” component so numbers aren’t pulled from thin air.
• Budgeting for litigation: Translate expected work into a fee range you can manage.
• Post-motion review: Sanity-check fee submissions after hours are recorded and billed.

Timing: connect the calculation to deadlines

Even a great fee estimate can miss the practical window if the claim is time-barred. For Washington, your general/default statute of limitations (SOL) is 5 years.

• General SOL period: 5 years
• General statute: RCW 9A.04.080

Because the brief you provided indicates no claim-type-specific sub-rule was found, treat the calculator and this guide as using the general/default period.

Step-by-step example

Below is a concrete example showing how you can use DocketMath to model attorney fees in Washington. (This is an estimate workflow, not legal advice.)

Scenario

You expect two phases of work:

1. Pre-filing / early motion work
2. Main litigation period

You have two attorneys (or billing categories).

Inputs to consider (what you enter)

• Hourly rates (or blended rates)
• Hours per billing category
• Total hours
• Optional multipliers/modifiers (if your internal model uses them)
• Optional reduction factor to model expected award trimming (if you want to estimate “likely recovery,” not just billed totals)

Example inputs

Assume the following:

• Attorney A: $300/hour, 20 hours
• Attorney B: $200/hour, 35 hours
• Estimated costs (optional, if your model includes them): $1,250
• Reduction factor (optional): 0.85 to model you expect the final award to be less than the billed amount

Compute the fee totals

1. Attorney A billed amount

   • $300 × 20 = $6,000
2. Attorney B billed amount

   • $200 × 35 = $7,000
3. Total billed fees (before reduction)

   • $6,000 + $7,000 = $13,000
4. Apply the reduction factor

   • $13,000 × 0.85 = $11,050
5. Add costs (if included in your modeled output)

   • $11,050 + $1,250 = $12,300

How this changes the output

• If you set the reduction factor to 1.00, the output becomes $13,000 (+ $1,250 if included).
• If you reduce to 0.70, the modeled fee becomes $9,100 (+ costs).
• Changes come from two places only:

  • Your hour/rate inputs
  • Your reduction factor or expected award percentage

Quick table of the example

Common scenarios

Attorney fee estimation becomes much easier when you separate scenarios by how the numbers typically flow. Here are practical, Washington-focused modeling scenarios you can plug into DocketMath.

1) Hourly billing with no reduction factor

Use this when you want a high-end “billed” number (for budgeting or initial negotiation ranges).

Checklist:

Outcome:

• Output tracks billed fees, not expected court outcomes.

2) Modeling expected reductions (award percentage)

Use this when you anticipate trimming, such as:

• duplication across filings
• time spent on tasks that may not fully survive scrutiny
• inefficiencies or excessive time blocks

Checklist:

Outcome:

• Output becomes a more realistic “most likely” modeled range.

3) Blended rate modeling (when you don’t have granular data)

If you only know a blended rate:

Outcome:

• Faster estimates, less precision.

4) Multi-phase litigation (pre-filing + litigation + post-judgment)

Many teams estimate fees phase-by-phase so updates can be inserted without rewriting everything.

Checklist:

Outcome:

• Your estimate becomes easier to keep current.

5) Deadline-driven budgeting using Washington’s general SOL reference

If your planning depends on whether you can pursue claims (including those that might lead to fee recovery), you can anchor planning to Washington’s general/default SOL.

• General SOL period: 5 years
• General statute: RCW 9A.04.080

Practical use:

Tips for accuracy

Estimates get meaning when your inputs are consistent. These tips improve reliability of your DocketMath results in Washington.

Work from a clean time summary

If your raw timekeeping includes misc entries, normalize first:

• Group time by who (Attorney A vs. Attorney B)
• Group time by what (e.g., drafting, discovery, hearings)
• Keep rates and hours aligned to the same time window

Don’t mix billing currencies or time units

Common accuracy errors:

• minutes treated as hours
• rate per hour entered as rate per 30 minutes
• copying hours from one time period into another

Keep the reduction factor methodology explicit

When you apply expected award percentage, write down what it represents in plain language:

• “We expect 85% of hours to be credited in the final submission.”
• “This reflects expected trimming of time entries and efficiencies.”

That way, your future revisions update the model knowingly, not randomly.

Use a range, not a single number (when you’re negotiating)

If you’re deciding whether to send a demand or respond with an offer, model at least two outcomes:

• Base case: reduction factor 0.85
• Conservative case: reduction factor 0.70

Then compare each modeled total to settlement proposals.

Connect the model to your timeline (SOL reference)

Even though attorney-fee entitlement depends on the case structure, the schedule planning often matters. Washington’s general/default SOL reference point is:

• 5 years, under RCW 9A.04.080

Use this to keep your internal project calendar from drifting.

Sources and references

Start with the primary authority for Washington and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Wash. Rev. Code § 60.44.010

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