Worked example: Treble Damages in Philippines

Example inputs

Below is a worked example showing how DocketMath applies a jurisdiction-aware “treble damages” calculation for the Philippines (PH). This example is for demonstration of the calculator workflow—not a legal opinion.

Here is a simple illustration for Philippines. These values are for demonstration only and should be replaced with your actual inputs.

• Principal or amount: $100,000
• Rate or cap: 10%
• Start date: 2025-01-15
• End/as-of date: 2025-09-30

Scenario (what we’re calculating)

A supplier files a civil action after a contractual dispute. The plaintiff argues for treble damages due to a qualifying statutory basis and seeks damages consistent with PH treble-damages rules.

To run the Treble Damages calculator in DocketMath, we’ll use these inputs:

What you should decide before running

Check these points in your own dataset before you click /tools/treble-damages :

• ✅ What is your “base” number? Trebling is computed off a defined base (here: PHP 250,000).
• ✅ Is there a qualifying basis for trebling in PH? In the calculator, that’s represented by qualifying_basis = statutory_treble.
• ✅ Do you want interest included? If yes, you must supply a rate and time window (interest_rate_annual and days_from_demand_to_payment).

Gentle caution: Treble-damages outcomes depend heavily on whether the claim truly meets the statutory/qualifying criteria. This example assumes the qualifying basis is satisfied so we can focus on calculation mechanics.

Example run

You can reproduce this run using DocketMath via the tool:

• ** /tools/treble-damages

Assume the user enters the inputs from the table above. DocketMath then performs a PH “treble” computation using the provided base damages.

Run the Treble Damages calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step-by-step (as DocketMath would conceptually calculate it)

1. **Compute treble amount (core multiple)

   • Base damages: PHP 250,000
   • Treble multiple: 3×
   • Treble damages (principal component): PHP 750,000

2. **Optional interest timing (only if interest is enabled in the model)

   • Annual interest rate: 6%
   • Time: 90 days
   • Simple interest approximation for illustration (if the calculator uses a simple-interest style model):

     • Interest ≈ PHP 750,000 × 0.06 × (90/365)
     • Interest ≈ PHP 11,096 (rounded)

3. Total damages output

   • Principal (treble): PHP 750,000
   • • Interest (estimated): ~PHP 11,096
   • Total: ~PHP 761,096

Example output summary

Here’s what you should expect DocketMath to show as outputs (rounded to the nearest peso for display):

How to sanity-check the output quickly

Use these quick checks before relying on the figure in drafts or settlement discussions:

• Treble check:

  • PHP 250,000 × 3 = PHP 750,000
    If DocketMath’s “principal” differs materially, revisit the base_damages input or whether the run correctly uses the treble route (qualifying_basis).

• Interest check (if enabled):

  • Increasing days_from_demand_to_payment should increase interest in a roughly linear manner for simple-interest models.

Sensitivity check

Let’s stress-test how the result changes when key inputs move. This is where DocketMath is especially useful: it helps you identify which numbers drive the outcome most.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity set A: changing base_damages (largest driver)

Keep everything else constant (qualifying_basis = statutory_treble, interest same assumptions).

Observation: Treble damages scale linearly with base_damages. A PHP 50,000 increase in base damages adds roughly PHP 150,000 to the treble principal.

Sensitivity set B: changing timing (days_from_demand_to_payment)

Assume base damages and treble principal are fixed at PHP 750,000 and interest rate stays at 6%.

If interest is computed, the interest component should rise with time.

Observation: For simple interest, interest grows roughly proportionally with days. Doubling days roughly doubles interest (keeping principal fixed).

Sensitivity set C: changing whether the treble route is activated

This is the “mode switch” sensitivity.

• If qualifying_basis = statutory_treble → principal uses 3×.
• If qualifying_basis is not treble → the calculator should route to a non-treble damages model (often 1× base, or a different computation depending on the tool’s PH ruleset).

Example contrast (holding base damages at PHP 250,000):

Related reading

• Treble Damages Calculator Guide for Alabama
• Treble Damages Calculator Guide for Arizona
• Treble Damages Calculator Guide for Colorado