Inputs you need for Deadline in Philippines
4 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Deadline calculator.
To calculate a Deadline in the Philippines with DocketMath (Jurisdiction: PH), gather these inputs first. Having them ready prevents the most common “wrong deadline” problems—especially around start dates, filing calendars, and tolling/extension triggers.
Note: This walkthrough is guidance for using DocketMath and organizing your facts. It’s not legal advice.
Use this checklist before you open /tools/deadline:
Keep an eye on the differences between the inputs—especially Trigger date / event date versus From receipt—because those two alone can shift results by weeks.
Where to find each input
Below is a practical way to locate each input in your documents and workflow. The goal is to point you to the kinds of sources you typically already have (not to hunt for new ones).
| DocketMath input | Where you typically find it | What to copy exactly |
|---|---|---|
| Deadline type | Court order, notice of hearing, subpoena, government letter, rule reference in the case | The name of the deadline (e.g., “file within ___ days,” “answer within ___ days”) |
| Trigger date / event date | The face of the order/notice, registry stamps, proof of service, docket entries | The specific date shown as the operative event date |
| From-event vs. from-receipt basis | Service/proof of service, mail registry, acknowledgment receipt, return card | The clause showing whether counting starts at service or receipt |
| Time computation rule | The document text (e.g., “within X days” / “after receipt”) and any stated counting method | The exact instruction for counting days and “day zero” handling |
| Any known extensions | Written extension order, resolution, or consent order | Start date of extension effect and the extension deadline date |
| Exclusions (non-working days) | Official calendar used by your office; docketing guidelines; sometimes the order itself | The set of dates you need DocketMath to treat as excluded (if your deadline type supports it) |
| Filing/receipt location assumption | Proof of service details (place), internal office practice | The place where receipt is deemed to occur for your facts |
| Time of day | Order/notice may include a filing time cutoff | The cutoff time (if specified) |
A quick “fact hygiene” checklist before you run the calculator:
Pitfall: Many deadlines get calculated from the wrong “day 0.” If your deadline language is “within X days from receipt,” using the notice’s issuance date instead of the receipt date can invalidate the computation.
Run it
Once you’ve assembled the inputs, you can calculate the Deadline using DocketMath:
- Go to /tools/deadline.
- Make sure the Jurisdiction is set to PH.
- Select your deadline type in the tool (or choose the closest match).
- Enter:
- Trigger date / event date
- Whether it is from-event or from-receipt
- The day-count rule (calendar vs. business days; whether “day zero” is counted)
- Add any extensions:
- If an extension order changes the counting window, enter the extension effect dates (not just the final deadline).
- Apply exclusions (if your deadline type supports excluded dates):
- Include only the dates that legally/operationally qualify under your deadline type’s counting instruction.
After you run, DocketMath will output at least two practical items:
- Computed deadline date (the “last day” you need to meet)
- Intermediate checkpoints (where the counting crosses certain thresholds, if the tool provides them for your selected deadline type)
How outputs change when you adjust inputs
Use these quick sensitivity tests to sanity-check the output:
- Changing Trigger date by +1 day
Expect the deadline to shift by +1 day (or possibly +2 days if crossing a non-working boundary). - Switching from-event to from-receipt
The deadline often moves significantly—especially if service/receipt occurred weeks after issuance. - Calendar days vs. business days
In weeks with holidays or weekends, business-day rules can extend the deadline even when “X days” looks the same.
If your computed deadline looks implausible (e.g., deadline lands before the trigger event), stop and re-check:
- You didn’t reverse event date vs. receipt date
- You chose the correct day-count rule
- Your extension dates weren’t entered as the original trigger instead of the extension effect
Practical workflow suggestion
If you want, you can also rerun with alternative assumptions to bracket the risk—for example, “served date vs. received date.” Keep the assumptions documented with your case notes.
Related reading
- Why deadlines results differ in Canada — Troubleshooting when results differ
- Worked example: deadlines in New York — Worked example with real statute citations
- Deadlines reference snapshot for New Hampshire — Rule summary with authoritative citations