How Wrongful Death Damages rules vary in Philippines
5 min read
Published April 15, 2026 • By DocketMath Team
What varies by jurisdiction
Wrongful death damages in the Philippines are shaped by a mix of statutes and—critically—how courts apply those statutes to the facts. Even when the “base” rules come from the Civil Code, the actual award can differ based on (1) the legal theory used in the pleadings, (2) the quality of proof offered, and (3) the calculation approach a court finds most persuasive in the case record.
Using DocketMath, you’ll typically see the same types of recoverable damages reflected across scenarios, but the inputs and any practical limits (such as what a claimant can prove) can shift depending on jurisdiction-aware factors and case posture.
Key “variation points” that often change outcomes in the Philippines:
Legal basis chosen by the claimant
- The Civil Code distinguishes between contractual and quasi-delict/tort contexts, which affects which damages framework tends to be applied.
- In many wrongful death fact patterns, claims commonly reference Article 2206 (death caused by breach of an obligation, depending on the scenario) and/or Article 2176 (quasi-delict).
Who is claiming and in what capacity
- Article 2206 sets out who may recover (e.g., spouse and legitimate children, and then other relatives if applicable).
- Courts can scrutinize standing and the relationship evidence submitted.
How the court characterizes the death
- Whether the incident is treated as a quasi-delict (fault-based) or as a breach of obligation can affect the structure of the damages analysis.
- The “right” to recover can also turn on proof of negligence/fault, and on whether proximate cause is established.
Proof quality for loss of earning capacity
- Even with similar legal categories, awards diverge when claimants can (or cannot) document earnings and earning capacity.
- If income is not supported, courts may still consider available evidence but may discount or reduce the claimed figures.
Duration assumptions and life expectancy modeling
- Courts may refer to life expectancy and work-life projections, but the method and the period used can differ by case.
- DocketMath helps you model different timelines, but the final computed number will still depend on the evidence you can support and the approach a court adopts.
Practical caution: If your DocketMath inputs rely on assumptions (for example, “estimated income” without supporting documents), the result can look exact even when the evidentiary basis is weak. DocketMath is only as reliable as the proof you can back up.
To access and apply the tool directly, start here: /tools/wrongful-death-damages.
What to verify
Before relying on DocketMath outputs, verify the details that commonly drive wrongful death damages calculations in the Philippines. This is not legal advice—think of it as a checklist to help you sanity-check inputs and understand which facts matter most.
1) Which statutory pathway fits your facts
Wrongful death recovery is often anchored to:
- Civil Code, Article 2206 (who may recover and what damages categories may apply)
- Civil Code, Article 2176 (quasi-delict / fault-based liability framework)
- Potentially related Civil Code provisions that inform non-pecuniary items in appropriate contexts (e.g., moral damages rules)
DocketMath is jurisdiction-aware for PH, but it can’t select the correct legal theory for your case. You should confirm which framework best matches your fact pattern and how your case is being pleaded.
2) Claimant eligibility under Article 2206
Check whether the person(s) claiming fit the categories recognized by Article 2206. Common verification items include:
- Marriage proof for a spouse
- Birth certificates (or equivalent records) for legitimate children
- Proof of relationship for other relatives, if the fact pattern requires it
3) Income and earning capacity inputs
Loss-related components typically rely on evidence such as:
- Actual earnings, if available (payslips, employer certifications, tax records, contracts)
- Work history, and a reasonable projection period tied to facts
- Special circumstances, such as multiple income streams or irregular earnings
If income is not formally documented, you should expect evidentiary challenges. A practical approach is to run multiple DocketMath scenarios (e.g., conservative vs. optimistic) so you understand sensitivity to the income input.
4) Expenses and proof of burial/interment
If your DocketMath run includes “real expenses” items (such as funeral/burial costs), verify that you can support them with credible documentation, for example:
- receipts/invoices
- supporting records showing the expenses were incurred due to the death
5) Moral damages and other non-pecuniary components
Some wrongful death outcomes include non-pecuniary damages (such as moral damages), but eligibility and amount tend to be fact- and framework-dependent. Verify:
- what legal basis supports the non-pecuniary award in your posture
- the evidentiary record showing mental anguish/grief and the claimant–decedent relationship
6) Interest, timing, and “when money was owed”
Some awards can hinge on interest and the date from which it is applied. Verify the relevant “anchor” date for your scenario (commonly tied to case milestones such as demand or judicial determination, depending on the context).
DocketMath can model interest if you provide the parameters, but you should align those parameters with the procedural posture you’re modeling.
7) Run sensitivity checks in DocketMath
A practical workflow is to model a small range of inputs:
- Scenario A (documented income): use verified earnings
- Scenario B (adjusted/estimated income): use conservative estimates supported by evidence
- Scenario C (reduced earning horizon): shorten the work-life horizon if the facts support it
This helps you see how much the computed damages change when the biggest variables shift.
Sources and references
Start with the primary authority for Philippines and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.