Why Damages Allocation results differ in Philippines

The top 5 reasons results differ

When you run DocketMath’s damages-allocation calculator for the Philippines (PH), differences in the results usually come from jurisdiction-aware inputs and assumptions. Even small changes—especially around how damages are framed, when interest starts, and what’s included in total damages—can shift how total damages are allocated across categories (e.g., compensatory buckets, interest, and timing-related components).

Here are the top 5 reasons PH results differ:

1. **Wrong damage type mapping (civil vs. quasi-delict vs. breach context)

   • The calculator’s PH logic depends on how the matter is framed in your inputs (e.g., a tort/quasi-delict-like treatment vs. a contract/breach-like treatment).
   • If you keep one “damage type” selection while the facts you’re modeling align with another, DocketMath may allocate amounts using a different internal treatment—so totals move between categories.

2. **Interest timing assumptions (filing date vs. demand date vs. accrual date)

   • For PH scenarios, the interest component is sensitive to your chosen start/accrual/demand date(s) and the rule set tied to that choice.
   • If you change only the date inputs (or accidentally switch the interest basis), the interest amount changes first, and then the allocation may rebalance across categories afterward.

3. Inconsistent “total damages” figure or coverage boundaries

   • DocketMath can only allocate what you provide. If your “total damages” differs between runs—because you included/excluded certain lines—the category allocations will also differ.
   • Common boundary mismatches: medical expenses included in one run but excluded in another, loss of earnings handled differently, repair costs grouped differently, or costs/carrying expenses omitted.

4. Unaligned inputs for evidence strength / quantification per category

   • In PH mode, DocketMath can treat “proven/quantified” amounts differently from “estimated/unquantified” amounts depending on how you enter or toggle evidence maturity.
   • If two runs use different proof levels (or different amounts for the same category under different assumptions), the calculator may allocate the “same overall story” into different category totals.

5. Multiple defendants / partial liability attribution

   • If your inputs represent joint vs. several attribution or use different liability percentages across parties, then party-level shares (and sometimes category-level rebalancing) will differ.
   • Even if the total looks similar, the distribution across parties and categories can shift when liability split changes.

If you want to reproduce and compare consistently, start from DocketMath: /tools/damages-allocation.

How to isolate the variable

Use a controlled one-change-at-a-time workflow. The goal is to identify which input (framing, interest dates, included components, evidence maturity, or liability splits) is driving the differences.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Suggested debug workflow (repeatable)

• Damage type framing (PH case context)

  • Interest start/accrual/demand date (or selected interest rule basis)
  • Evidence/quantification level per category
  • “Total damages” coverage (which cost lines are included)
  • Liability split / number of liable parties / attribution mode
  • Category totals (medical, loss, repairs, etc.)
  • Interest amount and how it feeds the allocation
  • Any residual/rebalancing behavior (i.e., what the calculator does after interest or fixed components change)

What to compare (quick checklist)

Next steps

1. Lock the framing first

   • Confirm the case context you’re modeling (e.g., quasi-delict-like vs. contractual-like mapping in your dataset).
   • Keep framing constant across all comparison runs.

2. Normalize your dates

   • Choose one interest timing approach for your comparison (e.g., consistent accrual basis).
   • Record the exact date(s) entered and reuse them unchanged.

3. Audit what’s included in “total damages”

   • Write a simple item list of included components (e.g., medical expenses, lost earnings, repair costs).
   • Ensure Run A and Run B include the same set of components.

4. Re-run with only one variable changed

   • Once you identify the driver (framing, interest dates, coverage boundaries, evidence level, or liability split), standardize that choice for future calculations.

5. Document assumptions

   • Keep a short changelog: what you changed, the date range used, and which category totals moved.
   • This makes it easier to explain differences to stakeholders without relying on guesswork.

A gentle note: DocketMath outputs are diagnostic/modeling results. They’re meant to help you understand sensitivities and scenario impacts, but they don’t replace how courts evaluate evidence, credibility, and the final award structure.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules