How to run Damages Allocation in DocketMath for Philippines

Step-by-step

You can run Damages Allocation in DocketMath for the Philippines (PH) by mapping your case facts into jurisdiction-aware inputs, then reviewing how DocketMath allocates amounts across covered damage categories. Use this workflow to stay consistent between what you enter and what the tool outputs.

1) Open the calculator

1. Go to the primary CTA: /tools/damages-allocation
2. Confirm you’re in the Damages Allocation workflow.
3. Set the jurisdiction selector to Philippines (PH).

If the UI offers options like a scenario type or template, choose the one that matches your goal (e.g., allocating a single claimed/awarded amount across multiple damage components).

2) Gather the minimum fact set (before typing)

Make a quick checklist so you don’t have to redo the calculation:

• Total claimed/awarded amount (the grand total you want allocated)
• Which damage categories apply (the calculator will generally allocate only across categories you select)
• Key dates (if your setup uses time-based logic—e.g., start/end for proration)
• Allocation percentages or bases (if your setup uses ratio/percentage allocation)
• Any deductions/exclusions (if your scenario requires removing part of the total from allocation)

DocketMath’s outputs change based on these inputs. Missing or inconsistent values are the fastest way to end up with an unexpected split.

3) Enter jurisdiction-aware allocation settings (PH)

Once you select Philippines (PH), align your entries with the allocation approach DocketMath expects for that jurisdiction.

Typical input patterns you’ll see include:

• Category selection

  • Tick the damage buckets you want DocketMath to distribute across.
  • If you leave out a bucket you intended to include, DocketMath may redistribute amounts across the remaining selected categories.
• Allocation method

  • Amount-based allocation: allocate based on component amounts you provide.
  • Ratio/percentage allocation: allocate by proportions (e.g., 60/40).
  • Duration/proration allocation: allocate using time boundaries (enter relevant dates and let the tool map time to dollars, if supported).

Even if you already know the “final numbers,” the method choice matters—it changes which fields are required and how the tool calculates each category.

4) Provide time inputs only when the chosen method requires them

If you choose an allocation method that uses time (or if PH configuration enables it), enter time fields carefully:

• Use the exact date format the interface expects (often YYYY-MM-DD)
• Check whether boundaries are inclusive or exclusive (the UI usually signals this)
• If you need to split across two periods (e.g., before vs. after a key event), follow the calculator’s supported approach:

  • run separate allocations per period, or
  • use multiple period fields if the tool provides them

5) Add adjustments, deductions, or constraints

Many damage allocation workflows allow you to reflect adjustments such as:

• Deductions (amounts excluded from the allocated total)
• Caps/floors (if the tool configuration supports limits)
• Rounding behavior (important when totals must reconcile exactly)

As you enter these, make sure the grand total and the sum of category allocations reconcile based on DocketMath’s rounding approach. Small rounding differences are common in allocation calculators.

6) Review output: category amounts, reconciliation, and assumptions

After you click Calculate (or the equivalent), review these sections:

• Category allocations: the amount assigned to each selected damage bucket
• Percentages (if shown): verify they align with the method you chose
• Reconciliation summary: confirm whether category totals match your provided grand total
• Assumption notes (if shown): check for messages indicating defaults like:

  • missing fields were assumed,
  • proration wasn’t applied,
  • a default ratio was used, etc.

If the result is close but not exact, the usual causes are:

• rounding,
• deductions applied differently than you intended,
• a different allocation method than you thought,
• category selection not matching what’s in your record.

7) Capture/export results for your workflow

When the output looks right:

• Copy the output breakdown into your drafting notes.
• If DocketMath supports export (e.g., PDF/CSV), use it to preserve:

  • the inputs you used,
  • the allocation table,
  • the jurisdiction label PH.

This helps when you later adjust a date or change category selection—allocations can shift as inputs change.

Common pitfalls

These are the most frequent reasons Philippines allocations don’t match expectations when running DocketMath.

• Wrong jurisdiction setting

  • Make sure Philippines (PH) is active. Jurisdiction selection can affect required fields and allocation logic.
• Choosing the wrong allocation method

  • If your scenario is truly ratio-based, but you select duration/proration, outputs may be driven by date fields you didn’t intend to use.
• Missing or incorrect date boundaries

  • For time-based proration, a one-day difference can change the computed duration and therefore the allocation.
• Double-counting exclusions

  • If your “total” already excludes an item, but you also enter it as a deduction, you may exclude it twice (depending on how the tool interprets your total).
• Rounding drift

  • Per-category rounding may cause the sum to differ slightly from the grand total. Use the tool’s reconciliation line to confirm behavior.
• Category selection mismatch

  • If the damage categories you expect aren’t selected, DocketMath reallocates the total across the remaining categories—changing the proportions without an obvious warning.

Try it

Use this mini-run to quickly validate your setup before entering your real figures:

1. Open **/tools/damages-allocation
2. Set jurisdiction to **Philippines (PH)
3. Choose the allocation method that matches your known facts:

   • amount-based if you have component amounts
   • ratio/percentage if you have proportions
4. Enter a small test total (e.g., 10,000) so you can immediately sanity-check the percentages
5. Review the output table to confirm:

   • category amounts add up to the total (per the tool’s reconciliation),
   • percentages align with the selected method,
   • the rounding behavior looks reasonable

Once your test run behaves as expected, rerun with your actual case numbers and dates.

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