Inputs you need for Wrongful Death Damages in Philippines
5 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Wrongful Death Damages calculator.
To run DocketMath (wrongful-death-damages) for the Philippines (PH), collect the facts and numbers below. Treat these as damage inputs (for estimating and scenario-checking), not as legal strategy. Also, the exact way wrongful death damages are computed can vary by case facts and the assumptions baked into any calculator—so use the output as an estimate you can refine.
Input checklist (PH)
- For each beneficiary:
Note: Your DocketMath outputs can change a lot depending on inputs like income definition (gross vs net), dependency/contribution, and duration. Two runs with different (but reasonable) assumptions may produce meaningfully different totals.
Where to find each input
Below are practical sources and how they usually map to the checklist fields.
Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.
Core timeline & identity
- Date of death / date of incident
- From: death certificate, police blotter/incident report, or hospital admission/discharge timeline.
- Age at death / date of birth
- From: death certificate and birth certificate.
- If you only have one, compute the other for consistency.
Income and support
- Monthly income
- Employed: payslips, Certificate of Employment, payroll records, employment contracts.
- Self-employed/business: business financials (income statements), invoices/receipts summaries, tax/permit documentation where available.
- Dependency / contribution
- From: spending/support patterns you can support with documents and a defensible estimate.
- If DocketMath asks for a percentage, choose a conservative figure you can explain with your notes (and update it if your documentation strengthens).
Beneficiaries
- Beneficiaries & ages
- Spouse: marriage certificate.
- Children: birth certificates and/or school enrollment records for age confirmation.
- Dependency status
- From: household arrangements, documented remittances/allowances, school records (for minors), and other corroboration you keep internally.
Expenses (only if your DocketMath run includes them)
- Medical expenses
- Hospital billing statements, ORs/receipts, and discharge summaries.
- Funeral/burial expenses
- Funeral receipts, burial permits, and itemized bills.
Insurance/benefits (only if your workflow includes netting)
- SSS/GSIS and employer benefits
- Benefit award letters, claim approval documents, and payout proofs.
Warning: Keep units and definitions consistent (PHP/month vs PHP/year; gross vs net). Mixing units/definitions is a common reason estimates look “precise” but are actually off.
Run it
Use DocketMath’s Philippines wrongful death tool here: /tools/wrongful-death-damages.
Enter the inputs in DocketMath and run the Wrongful Death Damages calculation to generate a clean breakdown: Run the calculator.
When rules change, rerun the calculation with updated inputs and store the revision in the matter record.
Step-by-step in DocketMath (wrongful-death-damages)
- Open: /tools/wrongful-death-damages
- Enter the required timeline:
- Date of death
- Date of incident
- Enter decedent details:
- Age at death (or DOB)
- Work status
- Add income and contribution inputs:
- Monthly income (PHP)
- Contribution amount or percentage to beneficiaries
- Add beneficiaries:
- Relationship and dependency inputs (as applicable)
- Each beneficiary’s age (or DOB)
- Add optional expenses (only if included in your run):
- Medical expenses total (PHP)
- Funeral/burial expenses total (PHP)
- Choose the duration model:
- Default support duration or a custom horizon supported by your records
- Review outputs:
- Projected support component (based on your income + dependency + duration assumptions)
- Any expense components included
- Any netting adjustments if benefits are entered in the workflow
How outputs change when you change inputs
Use these “sensitivity levers” to sanity-check your estimate:
| Lever you change | Typical effect on output | Why |
|---|---|---|
| Monthly income increases | Up (often proportionally) | Support math often scales with income |
| Dependency % increases | Up | Larger share allocated to beneficiaries |
| Shorter support duration | Down | Smaller time horizon for projections |
| Older beneficiary ages entered | Often Up or mixed | Alters duration rules and dependency mapping |
| Switching gross → net income | Down | Net is usually lower than gross |
| Adding medical/funeral totals | Up | Adds expense components (if your run includes them) |
Pitfall to avoid: Entering “assumed average income” without any basis can make results look more certain than they are. If you’re estimating, note the assumption and rerun with low/base/high scenarios.
Practical workflow tip: run scenarios
To keep your numbers credible, consider running:
- Scenario A (conservative): lower dependency % and shorter duration
- Scenario B (base case): your best-supported income, dependency, and duration inputs
- Optional Scenario C (upper bound): higher contribution if documentation supports it
Then compare results to catch input mistakes (wrong unit, wrong income type, missing beneficiary, etc.). Finally, confirm the computed totals reflect the assumptions you intended: income definition, duration horizon, and beneficiary list.