Inputs you need for Damages Allocation in Philippines

5 min read

Published April 15, 2026 • By DocketMath Team

Inputs you will need

Damages allocation in the Philippines usually comes down to translating the facts you already have (contracts, invoices, receipts, medical records, proof of loss, timing) into the “buckets” a calculator needs: what was caused by the event, what can be quantified, and how much each claimant is entitled to recover. DocketMath’s damages-allocation tool is built for this kind of structured input.

Use this checklist to gather the exact details before you run DocketMath:

Claim and case basics

Parties and allocation targets

Gentle reminder: DocketMath helps structure your computation, but it can’t replace judgment about what categories are legally available or how a court will treat the evidence. Use these steps as a practical preparation tool.

Damages components (what you are allocating)

  • Example items: repairs, medical expenses, lost income, replacement costs

Time and interest-related inputs

Evidence hooks (for traceability)

Warning: Damages allocation can be rejected or reduced if amounts are not tied to proof. DocketMath won’t “invent” missing amounts—your outputs will reflect the items and amounts you enter, item-by-item.

Where to find each input

Below is a practical “evidence-to-input” map you can use to populate DocketMath. Even if you’re not preparing a full trial packet, this workflow helps you keep damages computation defensible and auditable.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Actual/compensatory damages inputs

Look in:

  • Contracts and amendments (for price terms, milestones, liquidated damages clauses)
  • Invoices and official receipts (for repair costs, parts, services)
  • Medical records (for expenses, treatment dates, assessments)
  • Payroll records or proof of business interruptions (for lost income claims)
  • Demand letters and responses (for when claims were asserted)

What to extract:

  • Each loss item amount (PHP)
  • The event date or treatment date linked to each item
  • Document reference(s) you can point to later

2) Moral/exemplary-type and attorneys’ fees inputs

Look in:

  • Your complaint / position paper / quantified prayer portion
  • Contract provisions (for attorneys’ fees clauses)
  • Your narrative of acts and surrounding circumstances (so you can decide whether these categories apply in your allocation run)

What to extract:

  • Whether you’re claiming each category in your prayer
  • Requested amounts (or how you calculated them)
  • Any stated basis you want reflected in the run narrative (so the category inputs match your theory)

3) Time, interest, and payment inputs

Look in:

  • The demand letter date and when the obligation was allegedly breached
  • Payment history (bank transfer records, official receipts, acknowledgments)
  • Dates appearing in pleadings and supporting documents

What to extract:

  • Start date for the computation period
  • End date for the calculation run (or “as of” date)
  • Payment dates and amounts to reduce remaining damages
  • Interest rate you want DocketMath to apply for your PH calculation run

Run it

Once you’ve gathered the inputs, you’re ready to compute allocation using DocketMath.

Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.

Capture the source for each input so another team member can verify the same result quickly.

Step-by-step workflow in DocketMath (PH)

  1. Open the tool here: ** /tools/damages-allocation
  2. Select Jurisdiction: PH (DocketMath will apply PH-aware rulesets and assumptions)
  3. Enter:
    • Claimants/liable parties identifiers
    • Damages components (actual, moral, exemplary/penal-type, liquidated, attorneys’ fees)
    • Line-item amounts for actual damages
    • Dates (for any time-based computation such as interest)
    • Any payments already made
  4. Choose the allocation method that matches your evidence strategy:
    • By line-item loss (best when each claimant’s damages are separately documented)
    • By percentage split (best when parties’ rights or fault percentages are supported in your record)
    • By contractual/ownership allocation (best when a contract or relationship dictates distribution)

Practical tip: If you have multiple claimants, try to keep your actual damages in itemized form first. Then allocate. This reduces mismatches between your “master list” and the tool’s totals.

What to expect from the output

DocketMath’s damages-allocation run typically produces:

  • Total damages per category (e.g., actual vs other categories you entered)
  • Allocated amount per claimant (based on your selection)
  • Net payable per claimant after any reductions you input (like partial payments)
  • Interest and timing effects if your PH run includes them

Quick sanity-check table (use before submitting outputs)

CheckIf you see this…Usual fix in inputs
Line items sum correctlyTotal actual damages doesn’t match your master listRe-check each item amount and currency/decimals
Dates are consistentInterest/time output starts earlier than expectedUpdate “start date” and any “as of” date
Category totals alignMoral/exemplary categories appear too high or too lowConfirm the category amounts you entered and whether to include them
Payments reduce correctlyNet payable doesn’t decrease after paymentsAdd payment dates/amounts accurately, per PHP receipt/bank proof

Pitfall to avoid: Entering moral or exemplary-type damages “as totals” without aligning them to your claimant list or allocation method can produce a distribution that doesn’t match your evidence theory. For cleaner allocation, enter category amounts and pair them with the allocation method you can support.

Related reading