Offer of Judgment Analyzer Guide for Washington
7 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.
DocketMath’s Offer of Judgment Analyzer (Washington) helps you model what happens under Washington’s offer of judgment framework—specifically the timing and the practical “what if” outcomes tied to RCW 4.84.280 and the related exceptions in RCW 4.84.290 and RCW 4.84.260.
In plain terms, the calculator is designed to let you:
- Check the offer timing against Washington’s baseline rule in RCW 4.84.280 (serve ≥ 20 days before trial).
- Model the consequences of accepting vs. deeming rejection after the required period.
- Use the final judgment comparison concept referenced by RCW 4.84.290 (cost-shifting typically turns on whether the final judgment is not more favorable than the rejected offer).
- Track related admissibility / limitations described by RCW 4.84.260 (the offer is generally not admissible for non-cost purposes).
Pitfall: Don’t rely on the calculator alone for “strategic” decisions. It’s a computation/logic aid that explains how the statute operates—final outcomes depend on how the case is pleaded and how “not more favorable” is computed in your specific judgment.
When to use it
Use the DocketMath analyzer when you’re working with an offer process in a civil case in Washington courts and you want to understand the math and timing mechanics that commonly drive cost exposure.
Best-fit situations
- You’re drafting or reviewing an offer timeline for compliance with RCW 4.84.280.
- You want to model the effect of:
- Rejecting by inaction (deemed rejected after 20 days), or
- Acceptance within the allowed window.
- You’re trying to understand whether RCW 4.84.290’s “not more favorable” comparison could make cost recovery possible.
- You’re preparing to understand whether the offer can appear in court for non-cost purposes given RCW 4.84.260.
What this guide is not
This guide does not provide legal advice or a guaranteed estimate of what a court will award. Instead, it focuses on translating statute-driven concepts into an understandable workflow.
Step-by-step example
Let’s walk through a realistic Washington example and show how changing inputs changes the output logic.
Example setup
Assume a plaintiff is considering an offer of judgment.
Case basics (example):
- Offer served date: January 1, 2026
- Scheduled trial start date: January 30, 2026
- Offer amount: $50,000
- Acceptance window under statute: 20 days before trial (see RCW 4.84.280)
- Trial results (final judgment): $45,000
Key statute timing rule (baseline)
Under RCW 4.84.280, the offering party must serve the offer not less than twenty days before the trial. Also, if the offer isn’t accepted within twenty days, it is deemed rejected.
Source text (baseline rule):
- “...serve the offer on all other parties to the action not less than twenty days before the trial...” and
- “If the offer is not accepted within twenty days, it shall be deemed rejected.”
(See RCW 4.84.280, https://app.leg.wa.gov/rcw/default.aspx?cite=4.84.280)
Step 1: Check timing against RCW 4.84.280
From January 1, 2026 to January 30, 2026 is 29 days.
- 29 days ≥ 20 days → Timing requirement satisfied (for the serving requirement).
✅ Output the calculator should reflect: “Served ≥ 20 days before trial.”
Step 2: Model the 20-day acceptance window
If acceptance does not occur within 20 days, the offer is deemed rejected.
- 20 days from January 1, 2026 → January 21, 2026
If no acceptance is filed/communicated by then, you treat it as rejected for purposes of the offer logic.
✅ Output the calculator should reflect: “If not accepted by day 20, deemed rejected.”
Step 3: Compare final judgment to the rejected offer (RCW 4.84.290 concept)
Now apply the exception framework referenced in RCW 4.84.290:
- RCW 4.84.290 — exception: cost-shifting typically turns on whether the final judgment is not more favorable than the rejected offer.
In the example:
- Rejected offer: $50,000
- Final judgment: $45,000
Because $45,000 is not more favorable than $50,000 (for the offeree/relative comparison, depending on who offered), the “not more favorable” condition is plausibly met in the calculator’s logic.
✅ Output the calculator should reflect: “Not more favorable condition met” (subject to how “more favorable” is computed for your particular judgment structure).
Step 4: Note the admissibility limitation (RCW 4.84.260)
Under RCW 4.84.260:
- RCW 4.84.260 — exception: the offer is generally not admissible unless tied to cost recovery.
So, even though an offer can drive cost-shifting concepts, it generally shouldn’t be used as general evidence at trial except to the extent it relates to the statute’s cost recovery mechanics.
✅ Output the calculator should reflect: “Offer relevance is generally limited to cost recovery.”
What the analyzer output typically helps you answer (checklist)
- Did you serve the offer ≥ 20 days before trial under RCW 4.84.280?
- If it wasn’t accepted within 20 days, is it deemed rejected?
- Is the final judgment not more favorable than the rejected offer (RCW 4.84.290 logic)?
- Does RCW 4.84.260 limit how/when the offer can be used in court (cost recovery context)?
Common scenarios
Here are frequent Washington “offer analyzer” use cases and how the outputs tend to change when you adjust inputs.
Scenario 1: Offer served 20+ days before trial, but no acceptance within 20 days
Inputs:
- Offer served: 25 days before trial
- Acceptance: none within 20 days
Expected logic:
- RCW 4.84.280 serving requirement: met
- Deemed rejection after 20 days: true
- Next step: evaluate RCW 4.84.290 comparison using final judgment
Calculator effect: Timing shows compliant; rejection status drives the “not more favorable” check.
Scenario 2: Offer served fewer than 20 days before trial
Inputs:
- Offer served: 15 days before trial
Expected logic:
- Baseline serving requirement under RCW 4.84.280: not met
Calculator effect: The analyzer will generally flag the offer as timing-deficient, which affects whether you can rely on offer-based consequences tied to RCW 4.84.280 in your case logic.
Scenario 3: Offer accepted within the 20-day window
Inputs:
- Offer served: well in advance of trial
- Acceptance date: within 20 days
Expected logic:
- If accepted within 20 days, it’s not deemed rejected.
- That means cost-shifting style consequences tied to “rejected offer” logic (RCW 4.84.290 concept) generally won’t be triggered in the same way.
Calculator effect: Acceptance should flip the analysis away from the “rejected offer” comparison step.
Scenario 4: Final judgment is more favorable than the rejected offer
Inputs:
- Rejected offer: $50,000
- Final judgment: $70,000
Expected logic:
- RCW 4.84.290 “not more favorable” condition: not met
Calculator effect: The analyzer should show that the “not more favorable” exception logic does not apply.
Scenario 5: Trying to use an offer at trial for non-cost reasons
Even when an offer is otherwise relevant, RCW 4.84.260 limits admissibility:
- Not admissible unless related to cost recovery
Calculator effect: This affects interpretive notes in the output—your takeaway is that the offer’s legal relevance is narrower than its offer amount might suggest.
Note: The analyzer can help you understand when an offer is relevant for “cost recovery” logic, but it can’t tell you how a judge will rule on every evidentiary motion.
Tips for accuracy
To get reliable results from the DocketMath offer-of-judgment analyzer, focus on input discipline. Small date and amount mistakes can flip the analysis.
Date accuracy checklist
Statutory anchor: RCW 4.84.280 requires serving “not less than twenty days before the trial.”
