How to run Offer Of Judgment Analyzer in DocketMath for Philippines
6 min read
Published July 1, 2025 • Updated April 23, 2026 • By DocketMath Team
Trust release 4
This page has legal or numeric text that still needs claim-level inventory before we can treat it as verified.
Step-by-step
Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.
DocketMath’s Offer Of Judgment Analyzer helps you model how an “offer of judgment” style settlement can play out under Philippines (PH) jurisdiction-aware rules. Use the steps below to enter the right inputs, run the calculation, and interpret how the outputs change based on your assumptions.
Note: This guide is about running the tool and interpreting its outputs, not about guaranteeing results in any specific case. Always treat the analysis as decision support.
1) Open the analyzer
- Go to the primary call-to-action: /tools/offer-of-judgment-analyzer
- Confirm the jurisdiction is set to Philippines (PH).
- If the tool shows any “mode” or “context” selector, choose the option that best matches the scenario you’re analyzing (for example, whether the offer is structured as a proposed judgment/settlement against a counterparty).
2) Enter case basics (for correct rule application)
Fill in the core fields so the analyzer can apply PH-specific assumptions.
Typical fields you’ll see include:
- Court / proceeding type (if provided)
- Civil vs. other proceeding type (if provided)
- Date of offer (or “date served”)
- Date of acceptance or rejection (if known)
- Currency (PHP is usually the default)
If the interface includes any “jurisdiction-aware rules” toggle, leave it enabled so the PH rule set is applied.
3) Add the claimant-side (or offeror-side) numbers
Next, enter the monetary values that represent what the offer is trying to resolve.
Common inputs:
- Claim amount (principal): the main damages sought
- Interest: if your offer includes accrued interest up to a cut-off date
- Costs / fees: if the tool supports separating them
- Offer amount: the total proposed settlement amount
How outputs change:
- When you increase the offer amount, the analyzer typically shifts the “advantage” indicators toward the offeree (because the offer becomes easier to beat or closer to the likely outcome baseline).
- When you include interest and costs, the comparison becomes more realistic; otherwise, the tool’s side-by-side totals may look too low relative to what a court award might consider.
4) Add the defendant-side (or offeree-side) context
Now describe what the other side did with the offer.
Inputs commonly include:
- Response: accepted / rejected / no response (depending on what the UI offers)
- Response date: if the analyzer requires it
- Whether the offer is still on the table: if applicable in the tool
If you know the timeline is tight, enter the exact dates—offer-based analyses are sensitive to deadlines.
5) Confirm the offer structure
A key step is matching the structure of the offer to what the analyzer expects.
Look for fields such as:
- Whether the offer includes interest
- Whether the offer includes costs
- Whether the offer is lump sum or itemized
- Whether the offer is limited to damages only
If you’re unsure, start with the simplest structure (e.g., principal-only) and then run a second scenario including interest and costs. DocketMath will let you compare outputs between runs.
6) Run the calculation
Once your inputs are complete:
- Click Analyze (or the tool’s equivalent button).
- Review the results panel.
The analyzer output typically provides:
- A summary comparison of offer vs. a modeled baseline award
- Outcome scoring (e.g., “more favorable to offeror/offeree”)
- Breakdown of figures (offer components, totals, and the basis for comparison)
- Timeline sensitivity (if the tool uses date logic)
Pitfall: Entering the offer amount as “principal only” while leaving interest and costs at zero can distort comparisons. If your settlement was effectively “total claim inclusive,” re-run with those components included.
7) Review results using scenario comparison
Use the results panel to answer three practical questions:
- How does the offer compare to the modeled award baseline?
- Look at the numeric difference, not just the directional indicator.
- Which side is favored under the analyzer’s assumptions?
- Pay attention to whether the output depends on deadlines.
- What changes the most if you adjust the offer?
- Change one variable at a time (for example, offer amount up by ₱100,000; include/exclude costs if supported; keep dates identical).
A productive way to use the tool is to run at least:
- Scenario A: principal-only
- Scenario B: principal + interest + costs
- Scenario C: a higher/lower offer range (for example, ±10–20%)
8) Export or save your analysis (if available)
If DocketMath offers any of these:
- Download report
- Copy results
- Save scenario
Use them to preserve your assumptions. If you don’t see export options, take a quick screenshot of:
- The inputs (dates, amounts, response)
- The results panel (comparison, scoring, breakdown)
Common pitfalls
Offer-based analyses can go wrong for predictable reasons—especially when inputs don’t match the structure of your actual offer. The most common pitfalls when running DocketMath’s Offer Of Judgment Analyzer for PH are:
- Mismatched totals
- Example: offer amount includes interest, but claim amount excludes it—this makes the comparison feel inconsistent.
- Missing or inaccurate dates
- If the tool uses “date of service” or “deadline” logic, even a few days can change which rule bucket is applied.
- Confusing acceptance vs. rejection timelines
- If you know the offer was rejected, enter the rejection date accurately rather than using a later “discussion date.”
- Leaving costs at zero when they matter
- Some cases treat costs as part of the practical settlement arithmetic even if headline damages differ.
- Over-relying on a single run
- A one-off run can mislead. Use scenario runs to understand sensitivity—especially the offer amount.
- Using the wrong structure assumptions
- If the analyzer distinguishes lump sum vs. itemized components, don’t force itemized values into a lump sum field without checking how totals are computed.
Warning: DocketMath’s Offer Of Judgment Analyzer is designed for modeling. Treat the output as a structured way to compare settlement math, not as a prediction of what a court will necessarily award.
Try it
Ready to run your first Philippines (PH) analysis?
Checklist before you hit Analyze:
Quick “first run” suggestion:
- Start with principal only to get a baseline.
- Re-run with principal + interest + costs (same dates and response).
- Compare how the outcome indicator and total comparison shift.
When you’re done, focus on the numeric deltas in the output (not just the overall direction). Those deltas show what would need to change for the offer to become more favorable under the analyzer’s modeled assumptions.
Open the tool here: /tools/offer-of-judgment-analyzer
