Spreadsheet checks before running Wrongful Death Damages in Philippines
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
Before you calculate wrongful death damages in the Philippines, you can save hours of rework by running a spreadsheet checks pass. In DocketMath, the Wrongful Death Damages calculator is most reliable when your spreadsheet inputs match the kind of facts the tool expects—such as the names of parties, correct dates, and consistent numeric fields.
DocketMath’s spreadsheet-checker focuses on data integrity problems that can silently distort damages outputs. For PH (Philippines) workflows, it commonly catches issues like these:
1) Date logic errors that break period-based computations
Typical problems include:
- Accident/incident date after death date (or vice versa)
- Death date missing while the spreadsheet still includes later “loss” periods
- Wrong format (e.g., dates stored as text strings instead of real dates)
Impact on output: damages may compute as zero, NaN, or using the wrong time window, which can cascade into every later component.
2) Missing or mismatched identifiers
These are input issues that affect how the model allocates value across people:
- Blank claimant/dependent names or rows that are effectively empty
- Multiple rows with the same claimant but inconsistent demographic/details
- Inconsistent unit labels (for example, age or income stored as “months” in one place and “years” in another)
Impact on output: beneficiary allocation can be misapplied even if totals look “reasonable” at first glance.
3) Earnings fields that conflict with each other
Common spreadsheet pitfalls:
- Net vs. gross confusion (e.g., both are present, but treated as different inputs)
- Numeric cells that contain currency symbols or commas pasted as text
- Negative or implausible values (e.g., monthly income < 0)
Impact on output: even with correct dates, the calculator can inflate or depress amounts due to mismatched earnings assumptions.
4) “Double counting” rows
Spreadsheet models sometimes repeat the same cost in multiple places:
- Medical expenses entered per person when they were actually recorded as a total
- The same funeral cost captured twice (for example, once in a “funeral” column and again under “other expenses”)
Impact on output: total wrongful death damages can exceed what you intended, making later review much harder.
5) Wrong jurisdiction flag / PH-specific rule selection
DocketMath is designed to be jurisdiction-aware. If your sheet accidentally uses a non-PH pattern:
- Wrong wrongful death configuration/toggles
- Incorrect selection of PH-related damage components
Impact on output: the structure can still appear plausible, but it may not reflect the intended PH damage categories.
Pitfall to avoid: a spreadsheet can look “complete” and still be wrong—especially when dates and income exist but are stored in formats the tool can’t interpret correctly. The checker helps detect these problems before you run the damages calculator.
Gentle note: This guidance is about spreadsheet quality control, not legal advice. Use the tool to validate your data and assumptions, and consult qualified counsel or relevant authorities for legal conclusions.
When to run it
Run the checker at three points in your workflow. Each pass catches a different class of errors.
Run the checker before importing a spreadsheet into the Wrongful Death Damages workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.
1) Before you calculate (for new sheets)
Use it right after you populate:
- death/incident dates
- claimant/dependent rows
- earnings and expense inputs
This prevents expensive revisions after calculations are already based on incorrect time windows or misformatted numbers.
2) After you import or paste data (recommended after every new pull)
If you paste values from:
- payroll exports,
- PDFs,
- docket documents,
- internal reports,
run the checker immediately after import/paste. Then fix only the fields it flags before moving on.
3) Before you finalize numbers for submission or review
Even with a stable template, run it again if you changed any of the following:
- any date cell
- any income/expense figure
- any beneficiary list or allocation logic
A short pre-flight check reduces “compare-to-previous-run” confusion and helps ensure you’re not carrying forward a hidden formatting issue.
Try the checker
If you’re ready to validate your spreadsheet inputs for PH wrongful death damages, you can use the DocketMath workflow and run the spreadsheet checks before computing totals.
Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.
Quick start: use DocketMath
- Open DocketMath’s Wrongful Death Damages tool:
- Primary CTA: /tools/wrongful-death-damages
- Paste or map your sheet inputs into the calculator fields (or upload, if your workflow supports it).
- Run the spreadsheet checks step first.
- Fix flagged cells, then rerun the calculator to confirm your totals stabilize.
What to look for in the checker output
DocketMath typically groups issues by category. Use these quick checklists to clean your data:
Date integrity
Income/expense consistency
Beneficiary structure
PH rule selection
Warning: If the checker flags multiple categories (e.g., dates + income units), prioritize fixing date logic first. Once the time window is correct, it’s easier to diagnose income/expense mismatches.
How outputs change when inputs are fixed
After you correct flagged issues, you should expect more stability, such as:
- Total damages stop “jumping” between runs
(often a sign date parsing or negative values were affecting calculations) - Beneficiary allocations become stable
(often a sign row identifiers and row-level amounts are consistent) - Totals reconcile with your intended expense scope
(often a sign duplication was removed)
If you’re iterating, keep a brief change log (which fields you corrected and when). It makes internal review and re-checking much easier.