Common Wrongful Death Damages mistakes in Philippines
6 min read
Published April 15, 2026 • By DocketMath Team
The top mistakes
Run this scenario in DocketMath using the Wrongful Death Damages calculator.
When people look at wrongful death damages in the Philippines, they often focus on the “headline amount” and miss the inputs that drive the result. Using DocketMath (tool: /tools/wrongful-death-damages), the most common mistakes usually come down to how you enter (1) income/support, (2) actual expenses, (3) non-pecuniary categories, and (4) the timeframe.
Below are the most frequent pitfalls that can change the output—even if your final number “looks reasonable.”
1) Treating “loss of income” as a single lump-sum without the right structure
A common error is entering an estimate like “₱1,200,000 total income loss” into a model that expects period-based computation (for example, monthly/annual income × the number of months/years projected).
What this breaks in practice
- Overstates loss by unintentionally counting the same period twice (or by mismatching what the tool assumes is “per period”).
- Undercounts loss when the lump sum was meant to represent only one portion (like wages only, excluding support or other assumed components).
2) Using the wrong income basis (gross vs. net/support)
Wrongful death claims generally depend on what the deceased would likely have contributed. Many inputs are inconsistent with what the tool expects.
Common mix-ups:
- using gross salary (before deductions), when the tool’s support concept aligns better with net/what-contributed, or
- using take-home pay when the tool expects a different basis.
Quick check: make sure the income number you enter matches the tool’s intended meaning of “support” rather than just the payslip figure you have.
3) Skipping documentation for income and expense proof
Even when the arithmetic is correct, damages can become harder to justify if the “why” is missing.
Typical documentation gaps:
- no proof of employment/income,
- unclear explanation of how the support amount was derived,
- missing receipts or records for medical/burial-related expenses.
Gentle reality check: DocketMath helps structure numbers consistently, but it doesn’t replace the need to document where your income, support, and expense figures came from.
4) Confusing actual damages with non-pecuniary categories (moral/exemplary)
Another recurring error is trying to roll everything into one “damages” bucket. In practice, wrongful death-related computations may separate different categories (and DocketMath can reflect that separation).
Examples of what goes wrong:
- putting medical/burial expenses into the same category field where you intended moral damages, or
- expecting one category to automatically “cover” another without matching the tool’s category fields.
5) Ignoring the correct periods (date of death / incident and time span)
Timeframe errors are one of the biggest output drivers.
Common issues:
- using “income from the incident date to today” when the tool’s computation method expects a different start/end period,
- entering the wrong age or projection horizon.
Even a small timeframe mismatch can significantly affect totals if the tool projects across multiple years/months.
6) Applying “income-loss scaling” assumptions to non-pecuniary damages
Some people assume moral and exemplary damages scale linearly with income loss. That may not reflect how these categories are commonly analyzed in wrongful death contexts.
Practical takeaway: non-pecuniary amounts often depend on the circumstances and category assumptions you input—not just the magnitude of lost income. If your DocketMath setup uses category fields, don’t back into them purely from income loss.
7) Double-counting the same item (especially medical/burial)
Medical and burial costs can appear more than once in a damages narrative if you’re not careful.
Examples:
- entering medical/burial expenses as actual expenses, and again treating them as part of net loss/support, or
- implicitly assuming they’re covered while still adding them again.
Result: your total can inflate if the same ₱X ends up in two different fields.
8) Using the wrong jurisdictional setup inside the calculator
DocketMath is jurisdiction-aware. If the Philippines profile isn’t correctly selected (or if you accidentally switch tool settings), the computation assumptions and category handling may not match PH expectations.
Warning: a wrong jurisdiction setup can produce results that look precise but are based on mismatched rules.
How to avoid them
A practical approach is to treat wrongful death inputs like a checklist: each figure should have (1) a source, (2) a timeframe, and (3) a category. Then you can use DocketMath to compute the totals without silently mixing concepts.
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) Confirm your categories before entering numbers
Use this quick self-audit:
B) Use consistent time units
Pick one:
- monthly income + monthly timeframe, or
- annual income + annual timeframe
Then keep it consistent across related entries. If your death occurred on a specific date, ensure the tool’s date selection or period boundaries reflect the projection horizon you intend.
C) Match income basis to the tool’s expected concept
If you have both gross and net:
- choose which basis you will use,
- enter it consistently,
- and be prepared to explain how it connects to “support” in the way the tool models it.
If you only have gross income, document the approximation step you used to estimate the support figure you entered.
D) Separate “proof needed” from “math performed”
Before finalizing a DocketMath run, gather what supports each input:
| Input you enter | What to prepare (examples) | What happens if missing/misaligned |
|---|---|---|
| Income/support | employment docs, payslips, payroll summaries | affects projected support loss |
| Timeframe dates | incident/death dates, computation start/end | changes the number of periods |
| Medical/burial expenses | receipts, statements, affidavits | affects actual expense components |
| Non-pecuniary assumptions | case narrative details used in the model | changes moral/exemplary components |
E) Run two scenarios to catch double-counting and timeframe mistakes
Try:
- Scenario 1: conservative timeframe + one set of expenses
- Scenario 2: expanded timeframe + re-check expenses
If Scenario 2 increases without a corresponding explanation (for example, medical expenses jump despite no new receipts), you likely duplicated an item or changed the unit/time basis.
F) Keep jurisdiction settings locked to Philippines (PH)
Before you calculate:
- ensure you’re using the PH jurisdiction configuration in DocketMath, and
- avoid mixing assumptions that belong to another jurisdiction’s setup.
This is especially important because the tool may change how it categorizes components based on jurisdiction selection.
G) Use DocketMath output to build (and verify) your damages breakdown
Don’t treat the tool as a single “magic number.” If DocketMath provides a breakdown by category, use that as a guide to confirm:
- every category has a matching input,
- each input is documented,
- and nothing is counted twice.
Finally, this content is educational and not legal advice. If facts are unusual (disputed employment status, contested expenses, complex dependency arrangements), consider having your assumptions reviewed carefully.