Inputs you need for deadlines in United Kingdom
3 min read
Published April 8, 2026 • By DocketMath Team
Inputs you will need
Run this scenario in DocketMath using the Deadline calculator.
To run a UK deadline calculation in DocketMath (Jurisdiction: United Kingdom (UK)), you’ll need the specific “starting point” and the “rule-set” details that determine the due date. In practice, this means collecting the metadata that DocketMath uses to count forward (and to decide which days to include or exclude).
Use this checklist to gather the inputs before you open /tools/deadline.
Pitfall: The most common “wrong deadline” situation is mixing up the trigger date (event vs. service vs. receipt) or using “calendar days” when the calculation logic expects “working days” (or vice versa).
Where to find each input
You’ll typically source these inputs from your case management notes and the court/tribunal paperwork. Use this mapping to reduce guesswork.
Deadline type & time limit mechanics
**Start date (trigger date)
How the date is triggered
**Calendar rules (calendar days vs. working days)
**Service method (if service is involved)
Any known adjustments
If you’re building this into your workflow, open /tools/deadline next to align your extracted details with the fields DocketMath expects.
A practical order of operations is:
- Identify the rule statement (deadline period + measurement)
- Confirm the trigger basis (event vs. service vs. receipt)
- Extract the exact start date
- Choose the correct calculation convention (calendar vs. working days, plus holiday logic)
- Check whether an order or direction has already adjusted the clock
Run it
Once you have the inputs, you can run the calculation in DocketMath. The aim is consistency: the mechanics you select should match the wording that created the deadline.
Enter the inputs in DocketMath and run the Deadline calculation to generate a clean breakdown: Run the calculator.
Quick run checklist (before clicking calculate)
What to expect from the output
While exact fields can vary depending on the tool configuration, deadline calculators typically return outcomes like:
- Calculated due date: the date by which the action must be completed
- Computed end-of-period date: driven by the selected mechanics:
- If using calendar days, weekends count.
- If using working days, weekends (and potentially holidays, depending on the settings) are excluded.
- If using months, the resulting day-of-month and month-boundary behaviour can matter—especially for starts late in a month (e.g., 29th–31st).
Verification step (high confidence in ~1 minute)
After running DocketMath, do a fast sanity check:
- Compare the due date against the direction of the count:
- “14 days from X” → due date should land roughly two weeks later.
- “2 months from X” → due date should land in the corresponding target month (with month-arithmetic rules determining the exact day).
- Re-check the trigger basis:
- If the deadline is “from service,” using the “date on the document” instead of the service/trigger basis can shift the outcome.
Warning: Don’t just trust the first result—if the tool is configured for the wrong trigger basis or the wrong day-count convention, the output can be confidently wrong.
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
