Worked example: Pre Post Offer Damages Split in Philippines

6 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Example inputs

Below is a worked example of how DocketMath applies a Pre / Post Offer Damages split for a Philippines (PH) scenario using the pre-post-offer-damages-split calculator.

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 (assumptions for illustration)

Assume you are tracking damages in a dispute where:

There is a single damages claim that accrues over time (for example, rent, unpaid services, or other measurable sums).
A formal offer is made on a specific date.
You want to split the damages into:
- Pre-offer damages: amounts attributable to the period before the offer date
- Post-offer damages: amounts attributable to the period on/after the offer date

Note: This is a worked example to show mechanics. It doesn’t replace case-specific legal analysis of how accrual, proof periods, and the “offer” concept are treated in filings.

Inputs you would enter in DocketMath

Use the following inputs (the names below reflect the typical inputs the pre-post-offer-damages-split calculator is designed to consume). Adjust the dates/amounts to match your docket.

Jurisdiction code: PH
Offer date: 2024-06-01
Accrual start date: 2024-01-01
Accrual end date: 2024-12-31
Total claimed damages: ₱ 1,200,000
Accrual pattern: Linear
- Meaning: damages accrue evenly per day across the accrual period.
Unit of split: Daily
- Pre vs. post is determined by counting days across the accrual period, and the calculator applies its PH jurisdiction boundary rule for the offer date.

Day-count logic (to make the split auditable)

To keep the output explainable, this example uses an explicit day-bucket approach.

Accrual period: 2024-01-01 through 2024-12-31
Days in 2024 (leap year): 366
Offer date: 2024-06-01

If the split counts as:

Pre-offer: from 2024-01-01 up to 2024-05-31
Post-offer: from 2024-06-01 up to 2024-12-31

Then:

Pre-offer days = 152
Post-offer days = 214
(152 + 214 = 366)

Mapping days to pesos

With linear accrual, the calculator allocates damages proportionally to the share of days in each bucket:

Bucket	Days	Share of total	Allocated amount
Pre-offer	152	152 / 366	₱ 497,269.68
Post-offer	214	214 / 366	₱ 702,730.32

What the PH rules do in this calculator

For PH, the pre/post split is implemented in a jurisdiction-aware way so that:

The calculator applies the PH-specific boundary rule around how the offer date is treated (i.e., which side gets the boundary day).
Date handling is consistent with the tool’s PH configuration.
The day-counts shown in the output can be used to reconcile your split with your docket timeline.

Practical tip: If your pleadings treat the offer date differently (for example, “offer date counts as pre” vs “offer date counts as post”), verify the calculator’s “days counted” fields match your intended bucket before relying on the outputs.

Example run

You can reproduce this using DocketMath here: /tools/pre-post-offer-damages-split.

Run the Pre Post Offer Damages Split 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 (using the inputs above)

Select Calculator: pre-post-offer-damages-split
Set Jurisdiction: PH
Enter:
- Accrual start: 2024-01-01
- Offer date: 2024-06-01
- Accrual end: 2024-12-31
- Total damages: ₱ 1,200,000
- Accrual pattern: Linear
- Split unit: Daily
Run the calculation.

Output you should expect (format varies slightly by tool version)

A typical result set includes:

**Pre-offer damages (PHP)
**Post-offer damages (PHP)
Days counted in each bucket
Effective allocation percentages (implied or explicit)

Using the day-count logic above, the computed amounts are:

Pre-offer damages: ₱ 497,269.68
Post-offer damages: ₱ 702,730.32

Sensitivity check

Next, see how results change when you adjust common inputs that may vary between drafts, amendments, or proof timelines.

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 1: Move the offer date by 10 days

Keep everything the same except the offer date.

Change: Offer date from 2024-06-01 → 2024-06-11

Pre-offer days become 162
Post-offer days become 204

With linear accrual:

Offer date	Pre-offer share	Pre-offer damages	Post-offer damages
2024-06-01	152/366	₱ 497,269.68	₱ 702,730.32
2024-06-11	162/366	₱ 530,054.64	₱ 669,945.36

Observed effect:
Moving the offer date later shifts roughly ₱ 32,784.96 from post-offer to pre-offer (consistent with gaining 10 additional days in the pre bucket).

Sensitivity 2: Change accrual pattern (Linear → Step)

If damages do not accrue evenly, a day-based proportional split may misstate the pre/post allocation.

Suppose damages accrue with a front/back imbalance. For example:

Step pattern: 50% accrues evenly across the first half of the accrual period
the other 50% accrues evenly across the second half

In that case:

Allocation is no longer driven purely by “days share.”
The offer date’s position relative to the “step” boundary becomes critical.

A typical outcome (conceptually) is:

Pre-offer damages decrease if the heavier accrual portion occurs after the offer date.
Post-offer damages increase for the opposite reason.

Pitfall: Don’t assume a day-based split is always the right proxy if your damages are event-driven (e.g., penalties that trigger on specific dates). Use the accrual pattern that best matches your proof timeline.

Sensitivity 3: Reduce the accrual end date

In practice, the “accrual end” may be the termination date, payment date, or the cutoff for a measurable obligation.

Change: Accrual end date from 2024-12-31 → 2024-09-30

Now the accrual period shortens (Jan 1 to Sep 30 in 2024), reducing the total days considered. With the same offer date (2024-06-01), the buckets change because:

fewer total days are allocated overall
the pre/post shares depend on how much of the accrual window falls before vs after the offer date

What to watch for in the DocketMath output:

Total days used
Pre days / Post days
Whether (under linear accrual) allocation still tracks proportional day shares

Quick checklist for interpreting sensitivity results

Use this when comparing outputs across versions of complaints, amended computation, or settlement offers: