A contract expiration, an invoice due date or an approaching order deadline - here's how to build an automation that alerts you ahead of time, not on the day it's already too late.
A missed deadline almost never happens out of carelessness - it happens because nobody remembered it on the right day. A calendar in your head or a note in a notebook works fine until you have more deadlines piling up than one person can keep track of. The solution isn't to watch deadlines more carefully, but to let the system watch them.
The basic formula: time plus condition
Deadline tracking can be built from two building blocks that are often combined:
Time trigger - the automation runs on a schedule (for example, every day at 8:00) and goes through the relevant records.
Condition - for each record, it checks whether less than a set number of days remain until the deadline (say 30 days for a contract expiration, 7 days for an invoice due date).
If the condition holds, the automation sends an alert - to you, to a colleague, or straight to the client.
An approaching deadline triggers an alert on its own.
A time trigger checks deadlines every day, a condition decides whether it's time to alert yet, and the alert goes out without anyone manually watching a calendar.
What kinds of deadlines are typically tracked this way
- Contract expirations - an alert far enough in advance to renew or terminate the contract on time.
- Invoice due dates - a reminder to the client before the due date, and escalation after it if needed.
- Order deadlines - checking an approaching deadline before it becomes urgent.
- Certificate, license or inspection renewals - recurring deadlines that easily get lost in day-to-day operations.
An overdue deadline shouldn't disappear without a trace
Besides the alert before the deadline, it's worth also watching what happens once a deadline has passed without a response. A record that's past due or past expiration should stay visibly distinct - a different color, a tag, or its own view - so it doesn't get lost among the other, active records.
How to set up escalation
For more important deadlines, it makes sense to add a second step: if nobody responds within a set time after the first alert, the automation sends another one - this time perhaps to a manager or the whole team. This pattern (alert → wait → escalate) can be built from the same blocks as the first alert, just with a second condition added.
Watching deadlines is one of five things you can hand to AI in a company straight away - the other four, and three to avoid, are in 5 things AI can do in your company.
Frequently asked questions about deadline tracking
How far in advance should a deadline alert arrive?
It depends on the type of deadline - for an invoice due date, 3–7 days ahead is common, while for a contract or license expiration it's more like 30 days, to leave time to react or renew.
Can the alert also be sent to the client, not just the internal team?
Yes, the same automation can send a message both inside the company and directly to the client - for example a reminder before an invoice's due date.
What if nobody notices the deadline even after the alert?
For this case you add an escalation step - a second condition that, once another period passes without a response, sends the alert further up, say to a manager or the whole team.