How to calculate Pre Post Offer Damages Split in Philippines

Quick takeaways

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

• A Pre–Post Offer Damages Split in the Philippines is a way to separate damages timing—i.e., what portion of recoverable damages is attributable to the period before an offer/settlement demand boundary and what portion is attributable to the period after that boundary.
• The split is driven mainly by:

  1. the offer date you use as the boundary, and
  2. a time-based damages basis (daily/monthly accrual, or an interest-like time factor).
• In DocketMath (PH), you typically:

  • enter your damages basis and relevant dates,
  • choose a split method consistent with how the damages accrue,
  • ensure your unit and time-counting settings match your model (days vs. months; inclusive vs. exclusive),
  • review outputs showing two totals (pre and post) and any derived shares/sanity-check metrics.
• This approach is most defensible when you can explain how damages accrue over time and show the pre/post split follows that accrual logic—not merely the calendar boundary.

Inputs you need

To run the Pre Post Offer Damages Split calculator in DocketMath (PH), gather these inputs. DocketMath uses them to compute the split and output totals.

Use this intake checklist as your baseline for Pre Post Offer Damages Split work in Philippines.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

1) Offer timing

• Offer date (YYYY-MM-DD)
  The date you want to treat as the boundary between “pre” and “post.”
• Timeline start date (YYYY-MM-DD)
  Usually the date when damages begin accruing.
• Timeline end date (YYYY-MM-DD)
  The cut-off date you want to value damages through (e.g., judgment date, filing date, or a settlement modeling end date).

2) Damages basis (match it to how damages accrue)

Pick the unit type that best matches your damages model:

• Daily accrual model

  • Daily damages amount (numeric)
  • Example: ₱X per day accruing over the timeline.
• Monthly accrual model

  • Monthly damages amount
  • Example: ₱X per month.
• **Fixed principal + time-based component (interest-like)

  • Base principal amount (numeric)
  • Time-based add-on basis (often interest-like):

    • Rate (annual %)
    • Day count basis (e.g., 360 vs. 365, depending on your modeling convention)
• Custom accrual curve

  • Accrual amounts by period (e.g., Week 1–4, then a changed rate)
  • If you cannot justify a curve, prefer the daily model for clarity.

3) Counting convention

• Day counting method

  • Inclusive (count both start and end days) or
  • Exclusive (exclude one endpoint)
• Calendar/time zone

  • For Philippines-focused filings, you’ll typically use Gregorian calendar dates.
  • DocketMath uses calendar dates as entered—so keep your entered dates consistent across scenarios.

4) Output configuration

• Which components to split

  • All damages across time, or
  • Only time-based damages, or
  • Only the interest-like portion (if you model separate components)

Practical checklist

If you’re using DocketMath, start at /tools/pre-post-offer-damages-split. For related date-interval and interest-like helpers, you can browse /tools.

How the calculation works

At a high level, DocketMath computes the split by partitioning your timeline into:

• Pre-offer period: from Timeline start date up to the day before (or including) the offer date, depending on your counting convention.
• Post-offer period: from the offer date onward to Timeline end date.

Then it allocates the damages basis proportionally to time (or to your accrual curve).

Step 1: Compute pre and post day/period counts

Define:

• S = timeline start date
• O = offer date
• E = timeline end date

DocketMath calculates pre and post counts using your inclusive/exclusive setting. That choice matters most for short timelines.

Common exclusive-style boundary logic (illustrative only—follow your tool’s selected convention):

• pre ends the day before the offer date
• post starts on the offer date

So the “off-by-one day” effect can materially change outputs when totals are computed on a daily basis.

Step 2: Allocate damages by accrual method

A) Daily accrual model

If damages accrue at a constant daily rate d:

• pre_damages = days_pre × d
• post_damages = days_post × d
• total_damages = pre_damages + post_damages

If your daily amount changes midstream, you’ll usually need either:

• a custom accrual curve, or
• multiple scenarios/runs split by the change point (then sum pre/post externally).

B) Monthly accrual model

If damages accrue monthly at rate m, DocketMath uses calendar dates to convert your timeline into month-based equivalents under the conventions selected in the calculator.

If your real model is inherently daily, monthly modeling can introduce distortion—daily is often more transparent.

C) Fixed principal + time-based component (rate-driven)

For interest-like components, DocketMath splits the time factor across the pre/post periods, then applies it to your principal using the formula/options you choose in the tool.

In practice, this means:

• the principal stays constant,
• the time factor differs between pre and post because days_pre and days_post differ.

Step 3: Output the split

Typically, the calculator returns:

• Pre-offer damages total
• Post-offer damages total
• Combined total
• Optionally: pre share / post share (%) and “effective average” sanity-check metrics

Step 4: Sanity-check results

Use these checks to catch input errors early:

• If O equals S, then pre should be ~0 (subject to your boundary convention).
• If O equals E, then post should be ~0 (subject to your boundary convention).
• If you double the daily (or monthly) amount, both pre and post should roughly double.
• Longer post windows should generally produce a larger post share (unless your accrual curve is doing something special).

Common practical error: using the wrong boundary interpretation so that your offer date becomes “day before the offer” unintentionally. When using daily accrual, this can swing results noticeably.

Common pitfalls

Below are frequent issues when calculating a Pre–Post Offer Damages Split for a Philippines case model. These are modeling pitfalls—not legal conclusions.

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

1) Mixing up “offer made” vs. “offer received”

In real disputes, the relevant triggering date can depend on proof of communication and acceptance. In modeling, be explicit:

• Are you using the offer date (made)?
• Or the receipt/serving date?

DocketMath can help you model either, but consistency matters. Keep the scenario labeled clearly (e.g., “boundary = offer made” vs “boundary = offer received”).

2) Inconsistent inclusive/exclusive settings across runs

If you switch inclusive/exclusive between scenarios, results may not reconcile.

• Stick to a single counting convention per run.
• If you want multiple conventions, treat them as separate scenarios and compare.

3) Splitting components that aren’t time-accrued

Not every damages component should be allocated by time:

• lump-sum reimbursements
• fixed penalties
• judgment components that don’t accrue over a defined time window

If a component is not time-accrued in your model, choose an option like “Only time-based components” so you don’t create misleading pre/post allocations.

4) Forcing daily damages into a monthly model

If damages accrue day-by-day in reality, monthly modeling can misstate the split.

• Prefer daily accrual for clean boundary comparisons.
• Use monthly only when your damages basis genuinely supports a monthly cadence.

5) Not reconciling totals

Always verify:

• pre + post = combined total (within rounding)
• days_pre + days_post matches your total timeline day count under the selected convention
• results align with intuition (e.g., later boundary → larger post window should generally increase post share)

Sources and references

This calculator is a math/modeling tool, not a determination of legal rights. In the Philippines, the correct treatment of how and when specific amounts accrue can depend on the cause of action and applicable authority.

• Republic Act No. 386 (Civil Code of the Philippines) — general obligations and damages concepts (for orientation).
• Philippine Supreme Court jurisprudence on damages and interest — principles vary by case type and doctrine, so confirm the applicable approach for your fact pattern before relying on any modeling output.

Because your brief did not specify a particular cause of action or issue (e.g., breach of contract vs. quasi-delict vs. statutory claims), this page focuses on date-partition allocation mechanics and encourages you to align inputs with your underlying damages basis.

Next steps

1. Open /tools/pre-post-offer-damages-split and select the accrual/basis option that matches your damages model (daily, monthly

Run the Pre Post Offer Damages Split calculator now and save the inputs alongside the result so the workflow is repeatable. You can start directly in DocketMath: Open the calculator.

Related reading

• Why Pre Post Offer Damages Split results differ in Alabama — Troubleshooting when results differ
• Why Pre Post Offer Damages Split results differ in Alaska — Troubleshooting when results differ
• Why Pre Post Offer Damages Split results differ in Arizona — Troubleshooting when results differ