How to interpret Damages Allocation results in Philippines

What each output means

DocketMath’s Damages Allocation calculator (Philippines / PH) is designed to help you translate a damages claim into a structured set of categories and allocation outcomes. Because damages rules can be technical and fact-dependent, treat the results as a budgeting and scenario-planning view, not a final determination of entitlement.

Below are the common outputs you’ll see and how to read them in a PH context.

1) Total damages estimate

This is the calculator’s aggregated figure based on the inputs you selected (for example, damages categories, amounts, and any inputs that drive scaling or modifiers).

How to read it in PH matters

• Treat this number as the starting pool that the calculator distributes across categories.
• If your case facts affect which type of damages is legally supported (for example, whether your scenario is modeled as compensatory vs. other components), the allocation breakdown can matter more than the grand total—because strategy often turns on which categories are included and how strongly they are weighted.

2) Allocation by damages category

The calculator typically divides the total into one or more buckets (such as):

• Actual / compensatory components
• Moral components (where your selected PH scenario supports them)
• Nominal components (if triggered by your inputs)
• Exemplary / punitive-like components (if triggered by your inputs and scenario logic)

Practical reading

• If one category dominates (for example, a very large share of the total), then small changes to the inputs that feed that category will usually create the biggest swings.
• If multiple categories are present, compare their ratios/relative shares, not only their amounts. Ratios show where the model places emphasis under your chosen scenario inputs.

3) Percent allocation

You may see a percentage per category that adds up to (or closely approximates) the modeled total.

How to use it

• The percentages quickly reveal which category is carrying the modeled argument.
• If you are comparing scenarios (different fact assumptions, dates, or selected damage descriptions), percent allocation is often the fastest way to spot what changed and why—especially when total damages looks similar.

4) Jurisdiction-aware rule flags (PH)

In PH mode, jurisdiction-aware logic usually shows up as:

• Inclusion/exclusion of categories based on your scenario inputs, or
• Modifiers that scale certain amounts for the PH-modeled scenario.

How to read flags

• A category shown as triggered typically means your inputs match a scenario pattern that the calculator associates with that category.
• If a category is not triggered, the calculator will allocate less (or nothing) to that bucket, reflecting that your entered facts did not match the scenario pattern the model expects for that component.

Gentle reminder: DocketMath’s PH-aware logic is scenario-driven based on your inputs. Use the triggers as interpretation aids for your fact pattern—not as a substitute for legal analysis.

5) Outstanding/remaining balance (if shown)

Some versions show a “remaining” or “unallocated” portion when the entered categories and amounts don’t fully reconcile into allocatable outputs (for example, missing paired inputs).

How to read it

• A non-trivial remaining balance often signals missing, inconsistent, or incomplete inputs (such as selecting a category without providing the associated amounts/inputs the model expects).
• Before refining your narrative, check whether the model can actually compute what you intended.

What changes the result most

The biggest movements in PH Damages Allocation outputs usually come from a small set of input levers. Use this checklist to identify what your scenario is doing.

These inputs have the biggest impact on the final number. Adjust them one at a time if you need a sensitivity check.

• date range
• rate changes
• assumption changes

High-impact input levers (commonly)

Review the inputs you changed and look for these levers:

What to look for when you change one input

Run a tight comparison after each change:

PH-specific interpretation caution

Even when the total changes only slightly, the more meaningful change may be the composition:

• If moral or exemplary-like components appear, it’s because your scenario inputs matched a pattern the PH logic associates with that bucket.
• If you expected a bucket but it does not appear, your inputs likely didn’t satisfy the pattern the calculator uses to populate that component.

Pitfall to avoid: Don’t judge the tool only by the final “Total damages estimate.” A small total change can reflect a big shift in which legal theory the model is modeling—often where the real case strategy differences sit.

Next steps

Use DocketMath’s output interpretation like an iterative worksheet for PH matters.

Use the Damages Allocation tool to produce a first pass, then share the output with the team for review. You can start directly in DocketMath: Open the calculator.

Step 1: Reconcile categories to your fact pattern

• Match each non-zero category to something in your case narrative.
• If a category appears but you can’t connect it to facts you intended to include, adjust your scenario inputs.

Checklist:

Step 2: Stress-test with 2–3 scenario variants

Create small variants that isolate one lever at a time:

• Variant A: Most conservative (fewer categories enabled)
• Variant B: Balanced (your primary expected categories)
• Variant C: Aggressive (additional categories enabled based on your scenario)

Compare:

• Category percentages (not only totals)
• Whether PH rule flags flip between variants

Step 3: Turn results into a reusable narrative map

Convert outputs into short, plain-language notes you can reuse:

• “We allocate X% to category Y because…”
• “When we adjust input Z, category Y increases by approximately N%…”

This helps you keep assumptions clear and reduces the chance that input mistakes look like legal conclusions.

Step 4: Use DocketMath as a calculator-first step

If you haven’t run the tool yet:

• Run or refine the calculation: DocketMath Damages Allocation

Then return to this guide and interpret what changed.

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