Common Pre Post Offer Damages Split mistakes 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.

The top mistakes

Run this scenario in DocketMath using the Pre Post Offer Damages Split calculator.

In Philippines practice, DocketMath’s Pre-Post Offer Damages Split calculator helps separate damages into amounts incurred before and incurred after an operative offer trigger. This matters because the timing of when losses occurred (and when interest-type components attach) can shift the pre vs post allocation.

The most common errors aren’t math mistakes—they’re timing, event selection, and inconsistent input mapping.

Below are the frequent mistakes we see when teams feed inputs into DocketMath (PH) for /tools/pre-post-offer-damages-split.

1) Using the wrong “offer date” (or mixing it up with filing dates)

Common slip: treating the date the offer was served/received as the same as the date of filing, even though procedural timelines can differ.

Typical impact on output

If you enter the filing date instead of the operative offer trigger date, the calculator’s “post-offer” window may start too early.
That can inflate (or deflate) the portion of damages DocketMath labels as post-offer, even if your total damages are otherwise accurate.

2) Splitting damages by invoice/billing date instead of damage incidence date

People often assume “the date an invoice was issued” equals “when the damage was incurred.”

Why it breaks the split

In damages computations, the relevant timeline is usually tied to when the loss occurred (or when the performance/impact happened), not when paperwork was generated.

DocketMath symptom

Post-offer damages jump in ways that don’t match the case narrative, because invoices may be issued in clusters while the actual loss is continuous or spans different periods.

3) Double-counting overlapping components across pre- and post-offer amounts

Another frequent issue: entering overlapping heads (or repeating totals) so the same category is effectively counted twice—once in pre-offer and again in post-offer.

Examples of overlap

Entering “Total damages” as one figure and separately adding the same items again as line items.
Treating the damages base inconsistently—e.g., putting interest-like amounts into principal while also using an option that already computes or allocates interest-like accrual for the post-offer period.

Pitfall: You can get a split that looks internally consistent while being wrong relative to the case timeline—especially if interest is effectively counted twice.

4) Misinterpreting what “pre-offer” vs “post-offer” means in your chosen setup

Teams sometimes interpret “post-offer” as “after the court admits the offer,” rather than tying it to the legal/operative effect window used by the computation.

Why this causes trouble

DocketMath’s split logic depends on the operative trigger and how the tool is configured through its inputs.
If your “post” period is anchored to a different event than what your inputs imply, the split can drift.

5) Selecting an offer type or configuration that doesn’t align with the timeline rules

Offer-based computations can vary depending on what the offer is and when it is made/served, even if the underlying damages amounts are unchanged.

Outcome

DocketMath may apply split logic based on the selected structure.
If that structure doesn’t match the procedural posture you’re modeling, the split can be skewed even when dates are correct.

6) Leaving interest parameters implicit (or mixing compounding assumptions)

Interest handling is where pre/post splits can become misleading fastest. Typical input problems include:

using a yearly rate but applying it as if it were a daily rate, or
assuming compounding when the scenario calls for simple interest (or vice versa).

DocketMath symptom

The post-offer portion dominates more than expected because interest accrues faster under the entered convention.

Gentle note: This guide focuses on input quality and interpretation for internal consistency. It isn’t legal advice; interest mechanics can depend on the specific claims and how the record is framed.

How to avoid them

You can reduce these mistakes with a disciplined checklist before running DocketMath via /tools/pre-post-offer-damages-split.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

A) Lock the operative “offer start” event first

Before entering anything, identify the operative date with documentary support from the record you’re using for the computation.

Use this checklist:

Small practice tip: If you have to choose between two dates, run a quick comparison—shift the offer date by a few days and observe whether pre/post changes in a direction that matches your theory.

B) Map each damages component to a “damage incidence” timeline

Instead of feeding dates based on invoices, feed dates based on when the loss occurred.

Practical mapping options:

One-time loss → use the event date.
Continuing loss → use a start and end range.
Periodic loss → use the month-to-month (or period-to-period) dates.

Then translate that mapping into the calculator inputs:

C) Keep interest separate from principal where the tool expects a split

If your inputs include both principal damages and interest-type components, ensure you’re not stacking them twice.

A safe input workflow:

Enter principal loss amounts with their relevant timing (incidence dates/ranges).
Enter interest parameters only once, in the place DocketMath expects them.
Confirm whether DocketMath’s computed output already includes interest-like accrual for the post-offer window.

Checklist:

Reminder: even if the grand total looks reasonable, an incorrect principal/interest separation can still produce a wrong pre vs post split.

D) Run two sanity checks after every calculation

After you compute with /tools/pre-post-offer-damages-split, do:

Check 1: timeline coherence
- If the majority of losses happened after the operative offer date, post-offer should be the larger portion.
- If most losses happened before, pre-offer should dominate.
Check 2: add-up consistency
- Confirm that pre-offer + post-offer = the computed total (or matches how the tool reconciles totals, based on its documented behavior).

E) Document your assumptions in the case narrative

DocketMath won’t “know” your case theory; it will only compute from your inputs. To keep the split defensible internally:

Offer date definition used (what you treated as the operative trigger)
How each component’s damage incidence date (or range) was chosen
Whether interest was included in principal inputs
Whether any amendments/revised offers were excluded or included

This makes it easier to rerun the split if pleadings clarify operative dates.