Guide
Can Notion calculate court deadlines? No, and the safe way to track them
Can Notion calculate court deadlines? No. How to track them safely: record the trigger event and rule, get a second check and review the next 30 days weekly.
By Raghav R Handa, practising lawyer16 min read
TL;DR
- Notion cannot calculate court deadlines: it has no court rules, does not know holidays or service methods, and does not update when rules change.
- It tracks deadlines very well once calculated: owner, source, reminders, status and a weekly review.
- Record every date with its trigger event and rule so it can be audited, and make a second person confirm critical dates.
- Calculate in a rules-based tool or from the rule itself, and keep two independent alarms for anything critical.
No, Notion cannot calculate court deadlines. It has no court rules, does not know about holidays or service methods, and will not tell you when a rule changes. It is, though, a very good place to track a deadline once it has been calculated properly, and a missed deadline is almost always a tracking failure and not a calculation failure. This guide shows the structure, the formulas that are safe, the two-person rule and the weekly review that together make a deadline system you can defend.
Missed deadlines are among the commonest causes of professional negligence claims. Treat this page as practical information, not legal advice, and verify every critical date against the governing rule.
Why a formula is not enough
It is tempting to write a formula that adds 30 days to a service date. It will be right until something intervenes, which on a real file is most of the time. Here is what a simple formula does not know:
- Weekends and holidays. Many systems roll a deadline that falls on a non-court day to the next court day; the rules for doing so, and which days count, vary by court.
- Service method. Some rules add time depending on how a document was served, and which method applied is a fact about the file.
- Counting conventions. Whether day one is the day of the event or the next day, whether periods are calendar or business days, and how short periods are counted differ and change.
- Counting backwards. Deadlines set relative to a hearing or trial date count backwards, which formulas often get wrong.
- Orders and agreements. A court order or a stipulation can override the default rule, and the order is the real source.
- Time zone and cut-off. The deadline may be a time as well as a date, in the court's time zone.
- Rule changes. A formula does not update when the rule does.
A hypothetical shows the risk. Suppose a document is served on a Friday and the applicable rule gives 30 days. A naive formula returns a date 30 days later; if that is a Sunday the rule may move it to Monday, or may not, and the service method may add days. Two plausible calculations, a few days apart, one of which is wrong. Only the rule, applied to the actual facts, answers it.
Rules-based calendaring: what it is and how to choose one
Rules-based calendaring software (a standalone service, or a feature of your court's e-filing system or your practice-management product) takes the trigger event and jurisdiction and produces the resulting deadlines from encoded rules, updating when rules change. Notion does not do this. If you litigate, use one. When choosing, ask:
| Question | What good looks like |
|---|---|
| Does it cover your courts and jurisdictions? | Stated coverage including local rules |
| How is it updated when rules change? | A stated update process, with notice of changes |
| Does it show its working? | The rule relied on is visible per deadline |
| Does it handle service methods and holidays? | Yes, with the court's calendar |
| Is there an audit trail? | Changes are recorded |
| Can you export the result? | So you can record it in your tracker |
Even then, treat its output as an input to be confirmed, not as gospel, particularly for limitation periods and appeal windows (see limitation period tracking).
What Notion should hold: three databases
The most robust structure separates the event from the deadline, so you can recalculate when an event changes.
| Database | One row is | Key properties |
|---|---|---|
| Trigger events | An event that starts a clock | Event type, date, source document, Matter, Changed (checkbox), Date recorded, Recorded by |
| Deadlines | A date that matters | Deadline date and time, Time zone, Trigger (relation), Rule relied on, Calculated by, Confirmed by, Critical (checkbox), Status, Owner, Matter |
| Rules reference | A rule you rely on | Name, jurisdiction and court, period and counting convention (text), source link, last checked |
Relating Deadlines to Trigger events means a changed order (a new trigger date) flags every deadline derived from it. Relating Deadlines to the Rules reference means a rule change flags every deadline that relied on it.
Deadline properties in full
| Property | Type | Why |
|---|---|---|
| Deadline | Date (with time) | The date to protect, in the court's time |
| Time zone | Select | So a cut-off time is unambiguous |
| Trigger | Relation to Trigger events | What started the clock |
| Rule relied on | Relation to Rules reference | The authority, so it can be rechecked |
| Calculated by | Person | Accountability |
| Confirmed by | Person | A different person for critical dates |
| Critical | Checkbox | Triggers the two-person rule and extra alarms |
| Status | Select: Open, Filed, Extended, Vacated | Lifecycle |
| Owner | Person | Who acts |
| Matter | Relation to Matters | Shows the date on the file and the dashboard |
| Needs recalculation | Formula or checkbox | Set when the trigger changed after the deadline was confirmed |
Formulas that are safe (they display, they do not decide)
Formulas are good for showing how close a date is and for staging reminders, as long as the date itself came from the rule. In Notion's formula language, along these lines (check them on real rows before you rely on them):
// Days remaining (negative if past)
dateBetween(prop("Deadline"), now(), "days")
// Warning dates
dateSubtract(prop("Deadline"), 14, "days")
dateSubtract(prop("Deadline"), 7, "days")
dateSubtract(prop("Deadline"), 3, "days")
// Display status
if(prop("Status") != "Open", prop("Status"),
if(dateBetween(prop("Deadline"), now(), "days") < 0, "OVERDUE",
if(dateBetween(prop("Deadline"), now(), "days") <= 3, "CRITICAL",
if(dateBetween(prop("Deadline"), now(), "days") <= 14, "Soon", "Open"))))
// Not yet confirmed although critical
and(prop("Critical"), empty(prop("Confirmed by")))Note what these do not do: none calculates a deadline. They are display aids on a date somebody else calculated and confirmed.
Views that make it safe
- Next 14 days, sorted soonest first, on the Today dashboard.
- Critical and not confirmed: should always be empty.
- Needs recalculation: deadlines whose trigger changed after confirmation.
- By owner: each person's dates, for a fair view of load.
- Overdue and still open: should always be empty, and a red flag if not.
- Calendar view, per matter and firm-wide, for orientation only.
- Calculated and confirmed by the same person: an audit view.
The two-person rule in practice
- The calculator enters the deadline with trigger, rule and their name.
- A second person, working from the trigger document and the rule (not from the calculator's date), recalculates independently.
- They compare. If they agree, the second person records their name in Confirmed by. If not, they find out why.
- Only confirmed dates count as confirmed. The "critical and not confirmed" view keeps everyone honest.
In a solo practice, a second person can be a colleague at another firm, a paralegal, or a structured self-review done the next day from the source document, with the calculation done afresh. It is weaker than a second person, and better than nothing.
Alarms: never rely on one
A single reminder in a single system is a single point of failure. For critical dates keep at least two independent alarms: for example the staged reminders in Notion plus an entry in your firm calendar (or your rules-based tool's own reminders) that does not depend on Notion. Test that notifications actually reach you, and that a changed date updates both.
The weekly docket review (30 minutes)
- Open Next 30 days. For each date, open the file and confirm the date, the trigger and the plan to meet it.
- Open Critical and not confirmed and Needs recalculation. Clear both.
- Scan each matter for new orders or events since last week and record any new triggers.
- Check overdue-open: investigate anything there at once.
- Record that the review happened, with the date and reviewer.
A monthly audit: sample five confirmed deadlines and re-derive them from the source. A quarterly refresh: check the Rules reference for changes to rules you rely on.
Why deadlines are really missed
| Cause | Safeguard |
|---|---|
| A trigger was never recorded (an order was received and not diarised) | Record every order and event the day it arrives; weekly scan of each matter |
| The wrong rule or period was used | Rule recorded on every deadline; second person recalculates |
| Arithmetic or counting error | Rules-based tool; second check |
| The date lived in one person's calendar | Firm-wide system of record; two alarms |
| A change to an order was not propagated | Trigger events database with 'needs recalculation' |
| A person left or was absent | Owner and backup on every critical date; weekly review that does not depend on one person |
| Notifications were off or ignored | Test alarms; escalate critical dates to more than one person |
Where to find the rules
Your court's own website and rules of procedure are the primary source; many courts publish current rules, holiday calendars and practice directions. Record the source link in the Rules reference database, with the date you last checked it. For the wider system, the deadlines guide and a malpractice-proof deadline system go through the full build, and the litigation tracker shows how deadlines fit a case file.
Common mistakes
- Building a clever formula that calculates the deadline and trusting it.
- Entering a date without recording the trigger and rule behind it.
- Letting the person who calculated also be the person who confirms.
- Relying on Notion notifications as the only alarm.
- Not recording orders and events promptly, so triggers are missing.
- Skipping the weekly review when busy, which is exactly when it matters.
For the wider limits of the tool, read when not to use Notion for legal work and the best way to use Notion for lawyers.
Frequently asked questions
Can Notion calculate court deadlines automatically?
No. Notion has no built-in knowledge of court rules, holidays, service methods or local practice, so it cannot calculate filing deadlines. You can build formulas that add days to a date, but they will be wrong whenever a rule has an exception, which is often.
Can I use Notion to track deadlines at all?
Yes, and well. Store each deadline with its trigger event, the rule relied on, who calculated it, who confirmed it, its reminders and its status, then view them by matter, by owner and by week. The tracking is reliable; the calculation should come from a rules-based tool or a verified source.
What is a trigger event?
The event that starts a time period running, for example service of a document, the entry of an order or the date of a hearing. Deadlines are calculated from triggers, so recording the trigger separately lets you recalculate if it changes.
What deadline tools should I use with Notion?
Lawyers commonly use rules-based calendaring services or the calendaring built into their court's e-filing system or their practice-management product. Check that any tool you rely on covers your court and jurisdiction and states how and when it is updated.
How many reminders should a critical deadline have?
Several, at decreasing intervals, and at least one outside Notion. A common scheme is a warning two weeks out, a week out, three days out and a day out, with the final alarms going to more than one person.
Why does a deadline need a second check?
Because a single person's calculation, however careful, is the single point of failure in the commonest negligence claim. A second person recalculating independently catches wrong triggers, wrong rules and arithmetic slips.
Can I sync Notion deadlines to my calendar?
You can show a calendar view in Notion and, depending on your setup, subscribe to or sync dates with a calendar app. Treat any sync as a convenience and a second alarm, not the system of record, and test that it updates when a date changes.
What if a rule changes after I entered the date?
That is why you record the rule relied on. Search your deadlines by rule when a rule changes, flag the affected dates for recalculation, and have them re-confirmed.