How to calculate attorney fee in Washington

Quick takeaways

• Washington attorney fees must be reasonable under Wash. R.P.C. 1.5 (“A lawyer shall not make an agreement for, charge, or collect an unreasonable fee.”).
• DocketMath’s attorney-fee calculator helps you quantify your fee request by turning your case details (time, rates, expenses) into a structured, audit-ready estimate you can compare against Washington’s reasonableness framework.
• Washington’s reasonableness standard here is treated as general/default, not a single claim-type-specific formula. This is because no claim-type-specific sub-rule was found for this guide.
• Your output will change most when you adjust:

  • billable hours
  • hourly rate(s)
  • whether you include/omit modeled adjustments
  • included expenses (if you’re estimating total requested amount)

Inputs you need

Before you run DocketMath’s attorney-fee calculator for Washington (US-WA), gather the inputs below. Washington reasonableness analysis starts with the fee being reasonable in relation to the work performed—so your inputs should be defensible and clearly tied to case activity.

Core inputs (commonly used)

• Billable time (hours)

  • Total hours worked (or hours by attorney/role)
  • If you have multiple timekeepers: split time by person
• Hourly rate(s)

  • Current billing rate(s) for each timekeeper (e.g., partner, associate)
• Fee structure choice

  • “Time & materials” (hours × rate)
  • “Blended rate” (single effective hourly rate)
  • “Other arrangement” (if applicable—use DocketMath’s available fields)
• Expenses to include (estimate)

  • Filings, transcripts, copying, expert costs, delivery, travel, etc.
  • Decide whether your calculation is for a requested fee only or fee + expenses estimate

Washington reasonableness documentation inputs

Wash. R.P.C. 1.5 is the controlling general standard for “unreasonable fee,” but you’ll usually support reasonableness by capturing (and later summarizing):

• Nature of the work performed (briefly categorize time)
• Complexity of the matter (simple / moderate / complex scale is fine for estimating)
• Outcome / results obtained (if known)
• Time constraints (e.g., expedited schedule)
• Experience level of the lawyer(s) doing the work

While Wash. R.P.C. 1.5 is not a “mechanical” calculator rule, these facts are what you’ll map to the reasonableness narrative behind your numbers.

DocketMath tool setup inputs (typical)

Use DocketMath to enter:

• Jurisdiction: Washington (US-WA)
• Calculator: attorney-fee
• Your time × rate inputs (plus any adjustments you’re modeling)
• Expense inclusion choice

How the calculation works

DocketMath’s attorney-fee calculator performs a structured fee math workflow. With Washington, the key is that the output is an estimate of a reasonable fee request, grounded in Wash. R.P.C. 1.5’s prohibition on unreasonable fees.

Step 1: Compute base fees from time and rates

Use this relationship as your baseline:

• Base attorney fees = Σ (hours worked by timekeeper × that timekeeper’s hourly rate)

If you split time across multiple attorneys:

• Enter each timekeeper’s hours and rate, then DocketMath sums the products.

Example structure (illustrative only)

Step 2: Apply any modeled adjustments (if you choose to use them)

If your DocketMath workflow allows adjustments, treat them as an analytical overlay rather than changing the meaning of your underlying time records.

Common adjustment types you might model (depending on DocketMath’s fields):

• Multipliers (e.g., premium modeling for risk/complexity)
• Reducing hours (if you track non-billable/inefficient time)
• Task-based weighting (if your entries support it)

In Washington, even if you model an adjustment, the final fee must still be reasonable under Wash. R.P.C. 1.5.

Step 3: Add expenses (optional, depending on your calculation goal)

If you’re estimating a total fee request including costs:

• Estimated total = base attorney fees (± adjustments) + included expenses

To keep the estimate credible:

• separate “fee” and “expenses”
• list expense categories internally so you can explain them quickly if questioned later

Step 4: Connect the numbers to Washington’s reasonableness standard

Washington’s rule is not claim-type-specific for this guide. Your calculator result becomes more useful when you match it to facts explaining why the fee is reasonable under Wash. R.P.C. 1.5, such as:

• how the work’s nature and difficulty relates to time and rates
• whether the matter required specialized experience
• whether the matter demanded substantial time under tight deadlines
• whether the results achieved justify the work performed

Clarifying the “default/general” scope

Per your brief: No claim-type-specific sub-rule was found. That means this guide treats Washington reasonableness as a general/default approach—rather than applying a specialized time/fee pattern tied to a particular claim type.

Step 5: Interpret DocketMath outputs as “audit-ready estimates”

When you review DocketMath’s output:

• compare base fees vs. any adjusted fees
• run sensitivity checks:

  • increase/decrease billable hours by 10–20% and observe changes
  • switch rate tiers (e.g., $275 vs. $350) and see how quickly totals move
• make sure each major number ties back to time records, roles, and categories

Common pitfalls

These issues commonly cause attorney-fee calculations to drift away from Washington’s reasonableness expectations under Wash. R.P.C. 1.5.

• Over-relying on a single “average” rate

  • If your case had distinct roles (intake vs. motion practice vs. trial prep), a blended rate can obscure whether time was matched to experience level.
• Including too many expenses without categorization

  • Expenses may be legitimate, but “misc.” buckets are harder to justify. Group into understandable categories.
• Modeling adjustments that don’t match case facts

  • If an adjustment assumes complexity, but your time categories show mostly administrative work, the adjustment is harder to defend.
• Assuming Washington has a fixed fee schedule

  • Wash. R.P.C. 1.5 does not set a mechanical “rate table.” It sets a reasonableness boundary for what a lawyer may charge.
• Forgetting the “default/general” scope

  • Because no claim-type-specific sub-rule was found here, avoid applying claim-specific heuristics unless you have separate, sourced Washington authority for that claim category.

Sources and references

• Wash. R.P.C. 1.5 (General rule on fees; unreasonable fee prohibited)
  https://www.courts.wa.gov/court_rules/?fa=court_rules.display&group=ga&set=RPC&ruleid=garpc1.05
  Statute text (excerpt): “A lawyer shall not make an agreement for, charge, or collect an unreasonable fee”

Next steps

1. Open DocketMath attorney-fee (Washington): /tools/attorney-fee
2. Enter:

   • time totals (or time by timekeeper)
   • the rate(s)
   • whether you’re estimating fees only or fees + expenses
3. Review the results for:

   • base fees vs. any adjustments you modeled
   • expense-category clarity (so you can explain totals)
4. Draft short “reasonableness notes” tied to Wash. R.P.C. 1.5 facts:

   • nature of work, complexity, experience level, time constraints, and results (as available)
5. Run a sensitivity check:

   • adjust hours and rates slightly (e.g., ±10%) to confirm the estimate stays coherent with your record.

Related reading

• Attorney fee calculations in United States (Federal) — Full how-to guide with jurisdiction-specific rules
• Why attorney fee calculations results differ in United States (Federal) — Troubleshooting when results differ
• Attorney fee calculations reference snapshot for United States (Federal) — Rule summary with authoritative citations