How to calculate Offer Of Judgment Analyzer in Philippines

Quick takeaways

• DocketMath’s Offer of Judgment Analyzer (PH) helps you model the expected value of an offer in Philippine civil cases by translating your inputs (offer amount, acceptance assumptions, and case status) into outcome metrics you can compare.
• You’ll typically use it in scenarios involving monetary claims (e.g., damages, sums of money) where a structured settlement-style offer can change the financial risk profile.
• The analyzer is jurisdiction-aware for PH, but you still control key assumptions—especially timing and which costs/charges you include.
• Use the output to decide what to negotiate next, not to predict a courtroom outcome with certainty.

Inputs you need

Before you open /tools/offer-of-judgment-analyzer, collect the inputs that drive DocketMath’s calculation logic. For Philippine civil matters, the biggest drivers are usually what you’re offering, what you expect the other side to claim, and how you model costs and timing.

Check the items below:

• Example: total principal damages sought (and optionally include interest assumptions if you already have them)
• If you already have a contractual or statutory interest figure or a computed interest to a target date, input it consistently.
• Typical categories you might include in your model: filing/notice-related costs, expert costs, document production, and other expenses you intend to treat as “out-of-pocket.”
• Example stages: pre-trial, during trial, post-trial (choose the closest fit you can justify from your case posture)
• Use a percentage or a low/medium/high slider—pick what you can defend based on negotiations and settlement history.
• A number representing what happens if the offer is rejected and the case proceeds under your best estimate (e.g., expected judgment range midpoint).

If you’re missing something, you can still run the analyzer—just expect sensitivity: small changes in alternative outcome valuation or acceptance probability can materially shift the results.

How the calculation works

DocketMath’s Offer of Judgment Analyzer models a decision comparison between:

1. Accept offer (the other side receives the offer amount; your side avoids some modeled costs/risk), and
2. Reject offer (the matter continues; you incur modeled costs/risk and the case results at your alternative valuation).

Even when procedural law in the Philippines is fact-specific, a practical analyzer benefits from consistent inputs and transparent assumptions. Here’s how to think about the typical PH workflow in the tool.

1) Normalize the monetary inputs

First, ensure these amounts align:

• Offer amount: the lump sum you are analyzing.
• Baseline / alternative valuation: the amount you think the case could end up at if the offer is not accepted (principal plus any interest you decide to model).
• Costs: modeled costs for each scenario (accept vs. reject).

A mismatch (for example, offer includes interest but baseline does not) can skew conclusions.

2) Model scenario totals

DocketMath then builds comparable “scenario totals.” In plain terms:

• Scenario A (Accept):

  • Net = Offer amount minus any costs you assume you won’t need to pay if acceptance occurs.

• Scenario B (Reject):

  • Net = Alternative outcome valuation minus costs you assume you still pay.

Because DocketMath is a calculator workflow, you should select a consistent cost rule:

• Either use total costs for the reject scenario and minimal costs for accept, or
• Split costs by phase if your stage assumption is reliable.

3) Weight by acceptance probability (expected value)

Next, the analyzer combines scenarios using your acceptance probability:

• Expected value (EV) ≈

  • (Acceptance probability × Scenario A outcome) + (Rejection probability × Scenario B outcome)

This gives you a single decision-oriented metric you can compare across different offer amounts.

4) Produce decision metrics you can compare

The analyzer typically returns multiple outputs so you can see how sensitive results are to your inputs, such as:

• EV at this offer
• Difference vs. baseline
• Implied break-even offer range (the offer where EV crosses your baseline assumption)
• Sensitivity notes (e.g., “results change strongly if acceptance probability changes”)

If you run multiple offers, keep your other inputs constant and vary only:

• the offer amount, or
• timing/cost assumptions if you’re comparing negotiation strategies across stages.

5) Where jurisdiction-aware “PH” rules matter in your inputs

In the Philippines, procedural timing and how parties structure litigation and settlement negotiations can affect modeled expectations. DocketMath’s PH jurisdiction setup doesn’t require you to master courtroom doctrine, but it does expect you to enter information in a way that reflects typical practice.

Practically, that means:

• Use a timing stage that matches your case posture.
• If you’re modeling interest, make sure it’s computed to a consistent reference date.
• If you include costs, keep categories consistent across runs.

Common pitfalls

Avoid these issues—each one can produce misleading “best offer” results in the analyzer.

1. Mixing principal-only and principal+interest

   • If the offer includes interest but the alternative valuation doesn’t, your comparison is distorted.
   • Fix: decide on a single basis (e.g., “principal only” or “principal + interest to date X”) for both.

2. Ignoring cost symmetry

   • Some users input costs only on the reject side. That can be reasonable, but only if acceptance truly collapses most cost exposure.
   • Fix: in early stages, acceptance may still involve admin and motion preparation. Enter costs consistently with your stage assumption.

3. Overconfident acceptance probability

   • A 70–90% acceptance assumption can make an offer look “obviously” superior even when the realistic chance of acceptance is lower.
   • Fix: test 3–4 probability values (e.g., 25%, 40%, 60%) and see whether your recommendation changes.

4. Changing multiple inputs at once

   • Running a new offer and also changing costs and timing makes it impossible to attribute differences to the offer amount.
   • Fix: for offer comparisons, change one variable at a time.

5. Using an alternative valuation that’s not actually comparable

   • Example: alternative valuation is based on a different legal theory, different damages head, or different computation method.
   • Fix: align alternative valuation with what you would realistically seek or expect as a consolidated amount.

Sources and references

• DocketMath Tool: Offer of Judgment Analyzer (PH) — **/tools/offer-of-judgment-analyzer
• Philippine civil procedure and damages practice are inherently fact-specific; this guide focuses on calculator mechanics rather than prescribing procedural steps.

Start with the primary authority for Philippines 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

1. Open the analyzer: **/tools/offer-of-judgment-analyzer
2. Enter your:

   • claim/baseline valuation
   • offer amount
   • stage/timing assumption
   • costs you want included (optional but strongly recommended)
   • alternative valuation and acceptance probability
3. Run at least three offers:

   • the current proposed offer,
   • one increment higher, and
   • one increment lower,
     keeping all other inputs fixed.
4. If your results are volatile, run a probability sensitivity test:

   • 25%, 40%, 60% acceptance probability (or your own defensible points).
5. Export or note the output metrics and use them for negotiation planning—specifically to set:

   • a target offer,
   • a minimum “defensible” offer, and
   • a range where EV meaningfully improves.

You can also use other DocketMath calculators to triangulate litigation exposure. For example, start from the main tools area at /tools to explore related models.

Related reading

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