Common Damages Allocation mistakes in Philippines

The top mistakes

Run this scenario in DocketMath using the Damages Allocation calculator.

Damages allocation in the Philippines can derail a claim even when the “right” legal basis exists. In practice, many errors come from mixing up what type of damages you’re claiming, what facts support each, and how to allocate them across time or causes.

Below are the most frequent mistakes DocketMath users run into when running the /tools/damages-allocation calculator for PH (Philippines).

1) Treating all damages as if they’re the same kind

A common filing gap is lumping everything into one bucket (e.g., “damages” or “actual damages”) without separating categories that the rules treat differently—such as:

• Actual/compensatory damages (grounded on receipts, proof of loss, repair costs, lost earnings with evidence)
• Moral damages (requires a qualifying basis under the Civil Code; not every case supports moral damages)
• Temperate/exemplary damages (only in specific circumstances; not automatic)

Impact in DocketMath: if you enter everything as a single figure, the calculator can’t properly allocate across categories, so your output may misstate totals and lead to inconsistent narrative support.

2) Misallocating damages to the wrong time period

Another frequent error: allocating amounts to “today” instead of splitting pre-filing vs. post-filing periods (where applicable to the narrative and how interest/claims are handled). Even when you’re not explicitly computing interest, time-based allocation affects what portion is attributed to:

• losses that occurred before a cause of action ripened / claim was made, versus
• losses that accrue after demand or filing (depending on what you’re modeling)

Impact in DocketMath: the calculator’s totals will reflect your period inputs; wrong period boundaries produce totals that don’t match your supporting timeline.

3) Using “net” figures without showing the breakdown

People often input a single “net amount” (e.g., “I paid ₱120,000 but got ₱30,000 back”) without indicating what the ₱30,000 represents and whether it reduces the same damage category.

A clean damages narrative typically distinguishes:

• out-of-pocket expenses,
• reimbursements/offsets, and
• whether any offset belongs to the same damage head.

Impact in DocketMath: offsets can change the allocated category totals. If you apply offsets inconsistently, the output totals may conflict with your exhibits.

4) Over-including unsupported components in “actual damages”

Common examples:

• Future costs entered as if they are already incurred
• General estimates entered with no basis
• Costs that resemble attorneys’ fees or litigation expenses treated as ordinary actual damages

Impact in DocketMath: the tool will sum what you enter. If you include costs that belong to a different claim type or a later period, the calculator output will still look mathematically consistent—yet legally inconsistent with your proof.

5) Skipping the “proof level” that matches each damage type

Even if DocketMath computes correctly, the allocation can be undermined if the claim posture doesn’t align with evidentiary expectations. A frequent mismatch:

• claiming moral damages while providing no factual basis for the qualifying circumstances, or
• claiming temperate/exemplary damages without facts that trigger the recognized basis.

Impact in DocketMath: you may still get totals, but your narrative may fail to match the allocation you used.

6) Not validating category totals against the narrative

After allocation, people rarely do a “sanity check” comparing:

• your summary in the pleading
• your own computation
• the exhibits
• and DocketMath’s category totals

Impact in DocketMath: outputs may be correct for the inputs, yet the pleading might reference different numbers than what your inputs implied.

How to avoid them

Use DocketMath as a jurisdiction-aware checklist. The calculator is only as reliable as the inputs, so the goal is to feed it inputs that map cleanly to the damages categories you intend to claim.

Note (not legal advice): This is practical guidance for building consistent computations and narratives. Consider reviewing your specific case with a qualified professional.

1) Map each entry to a damages head before you type numbers

Before using /tools/damages-allocation, create a quick allocation table. The aim is to keep each number tied to a distinct proof set.

• Use separate lines for each damage head.
• Add a short label for the source of the amount (receipt category, payroll record, repair estimate, etc.).
• Split amounts by time period where your narrative requires it.

Example layout (mirror this in your working notes):

2) Use consistent “inputs → outputs” logic

When you enter figures in DocketMath:

• If the input represents gross outlay, include reimbursements as a separate line item (or offset it in the correct category—consistently).
• If an amount is estimate-based, distinguish it from incurred amounts.
• If a cost is clearly tied to a later period, allocate it there rather than pooling it into past losses.

Simple workflow:

• Step A: Input actual amounts you already incurred.
• Step B: Add only those future amounts if your modeling is designed to include them (otherwise, keep them out of the “already incurred” category).
• Step C: Reconcile your narrative totals after the calculator returns.

3) Validate with a “category sum” sanity check

After running DocketMath, do this quick verification:

• Total of all category outputs = your pleading total (or your pleading total minus intentionally excluded items).
• No category includes a component listed under a different head.
• Period splits align with your timeline.

4) Fix the most common data-entry issues

Use these checkboxes while preparing inputs:

5) Keep the tool outputs aligned to the story you’ll tell

Once the calculator generates allocated totals, convert those totals into a narrative structure:

• Identify which category drives most of the sum.
• Point to the factual basis for each category you included.
• Ensure your exhibits match the category breakdown (not just the final total).

This reduces the risk that your pleading says one thing while your allocation model calculates another.

6) Use DocketMath to compare alternate scenarios—carefully

If your facts allow multiple models (for example, different time splits or different proof-based amounts), use DocketMath to:

• run Scenario 1 (conservative incurred-only),
• run Scenario 2 (expanded period),
• compare category outputs side-by-side.

What you’re doing isn’t “guessing”—you’re testing how sensitive your allocation is to input boundaries.

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