How to calculate Offer Of Judgment Analyzer in Delaware

Quick takeaways

• In Delaware civil actions, courts generally award costs to the prevailing party, and those costs include reasonable attorney’s fees, unless a statute or court rule provides otherwise. The baseline authority is 10 Del. C. § 507.
• DocketMath’s Offer Of Judgment Analyzer (US-DE) helps you model the economic effect of an offer—how changing your offer and your expected (or actual) judgment can shift the fee/cost picture. It’s a calculation aid, not a guarantee of results in a particular case.
• Delaware timing modeling here uses a default period approach because no claim-type-specific sub-rule was identified in the provided jurisdiction data. If you have a specific statutory or rule-based exception for your situation, you should incorporate it via your case inputs (where the tool allows) and/or your scenario assumptions.

Inputs you need

To run the Offer Of Judgment Analyzer in Delaware (US-DE), gather the core numbers you would typically use to evaluate whether an offer is financially “worth it.” In practice, you’re preparing inputs for a fee/cost-shifting framework anchored in Delaware’s prevailing-party statute.

Use this checklist:

• Case type / posture (civil action context for Delaware courts)
• Offer amount (the dollar value stated in the written offer of judgment)
• Expected or actual judgment value (the amount you think the court will award, or the amount it awarded)
• Attorney’s fees you incurred (for each side, if available in the tool)
• Costs you incurred (filing fees, service costs, transcript fees, etc.)
• Any statutory or rule-based fee exception flags (only if you know a specific “otherwise provides” rule applies to your situation)
• Timing inputs used by the analyzer (for example, date of offer and date of judgment), if the tool requests them

What to enter when you’re unsure

If you don’t have every detail, use the best estimates you can and keep them consistent across scenario runs. For example:

• Scenario A: Expected judgment = $250,000
• Scenario B: Expected judgment = $200,000

That lets you see how sensitive the fee/cost impact is to your judgment benchmark—even when your attorney’s fees or costs are estimates.

How the calculation works

DocketMath’s Offer Of Judgment Analyzer is built to convert your inputs into an “economic impact” model consistent with Delaware’s baseline prevailing-party cost/fee framework.

DocketMath applies the Delaware rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.

1) Delaware baseline: prevailing-party costs and attorney’s fees

Under 10 Del. C. § 507, the court “shall award costs to the prevailing party, to include reasonable attorney’s fees, unless otherwise provided by statute or rule.”

Modeling implication:

• If you model your side as the prevailing party, the tool’s output typically treats fee/cost recovery as more favorable.
• If you model your side as the non-prevailing party, the tool’s output typically treats fee/cost recovery as less favorable—and may reflect fee/cost exposure depending on how you enter figures for each side.

In other words, your inputs (especially the judgment benchmark and how the tool interprets prevailing/non-prevailing orientation) drive the direction of the modeled impact.

2) Using the offer amount vs. judgment benchmark

The analyzer uses the relationship between:

• Offer amount (what you offered), and
• Judgment value (what you expect the court outcome to be)

to estimate whether the offer is economically aligned with the prevailing outcome you’re modeling.

A practical way to think about it: the tool is comparing your offer anchor to the judgment benchmark you provide, and then translating the difference into a fee/cost impact using your fees/costs inputs.

Because it’s a calculator, not a prediction engine, it’s most helpful for side-by-side comparisons, such as:

• $150k offer vs. $250k offer, holding fees/costs constant
• higher vs. lower expected judgment, holding offer constant

3) Default timing logic (no claim-type-specific sub-rule identified)

Based on the jurisdiction data provided, there is support for a general/default period approach, and there was no claim-type-specific sub-rule identified.

What that means in practice:

• If the analyzer asks for an “offer-to-judgment timing” input, use the dates relevant to your offer and the judgment benchmark you’re modeling.
• If you have a statute or rule that creates a special timing condition or eligibility requirement, the tool’s baseline may not perfectly reflect it unless you incorporate that using the tool’s exception/flag inputs (if available) or adjust your scenario assumptions to match your case.

Pitfall reminder: If your case falls under a “statute or rule otherwise provides” scenario, 10 Del. C. § 507 is still the starting point, but your calculations may need the special rule reflected via your inputs.

4) Converting fees and costs into “impact”

Once the tool has:

• your offer amount,
• your judgment benchmark,
• your attorney’s fees and costs, and
• the prevailing/non-prevailing orientation implied by your modeled outcome,

it computes an “economic impact” output. While the exact labels/formatting depend on how DocketMath presents results, conceptually you should expect:

• a recovery component (if your side is modeled as prevailing),
• an exposure component (if your side is modeled as not prevailing), and
• a net difference tied to the offer vs. judgment relationship.

5) Run multiple scenarios like a calculator, not a forecast

Use the analyzer to answer “what if” questions:

• Scenario 1: Offer = $100,000; Expected judgment = $90,000
• Scenario 2: Offer = $100,000; Expected judgment = $120,000
• Scenario 3: Offer = $150,000; Expected judgment = $120,000

Keep your fee/cost inputs constant when comparing offer levels, so you can isolate the effect of the offer vs. the judgment benchmark.

If you’re ready to try it, open the analyzer here: /tools/offer-of-judgment-analyzer.

Common pitfalls

1. Ignoring the “unless otherwise provided by statute or rule” carve-out

   • 10 Del. C. § 507 includes the carve-out for exceptions.
   • If there’s a specific fee-shifting rule in your case, the analyzer’s baseline Delaware framework may not fully capture it unless you flag it via inputs (where supported) or otherwise account for it.

2. Changing multiple variables at once

   • If you alter the offer and also change expected fees/costs, it becomes unclear what caused the output change.
   • Compare scenarios by altering one key variable at a time where possible.

3. Confusing “judgment value” with “claim demand”

   • The tool is best used with a benchmark that reflects what is likely awarded (or what was awarded), not just what was demanded in pleadings.
   • Using the complaint’s demand as a “judgment benchmark” can distort the economics.

4. Entering only fees or only costs

   • The statute references costs and also specifies that costs include reasonable attorney’s fees.
   • If you omit either fees or other costs, your totals and net impact can skew.

5. Assuming the default timing approach applies even when special timing may exist

   • The provided jurisdiction guidance supports a default period approach in this write-up.
   • If special timing/eligibility rules apply in your specific situation, reflect them in the analyzer inputs (when possible) rather than relying solely on the default model.

Sources and references

• 10 Del. C. § 507 — Costs to prevailing party; includes reasonable attorney’s fees; unless otherwise provided by statute or rule
  Source: https://delcode.delaware.gov/title10/c507/

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

• Primary authority reference

Next steps

• Step 1: Choose scenario set(s). Pick at least 2–4 offer levels (for example, $100k, $150k, $200k) and define one expected judgment benchmark (or a small range).
• Step 2: Lock in fee/cost assumptions. Use actual invoices and tracked costs when you can. If you estimate, estimate consistently across scenarios.
• Step 3: Input timing using your case dates. If the tool requests dates, enter the offer date and the judgment date (or your modeled judgment date).
• Step 4: Review the output components. Focus on the net impact, not only totals.
• Step 5: Adjust only one variable at a time. Run again after changing the offer amount, then separately after changing the expected judgment.

To run the calculator: **/tools/offer-of-judgment-analyzer

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado