The life of a deadline

Beyond its date, a deadline carries a few settings that shape how Kimori handles it over time.

Criticality

Three levels, chosen at creation: Info, Important, Critical.

It helps you spot at a glance what matters most in a long list, but it also does something concrete: each level has its own alert threshold. The more critical a deadline, the earlier it becomes “expiring soon” and surfaces in your lists.

Criticality	Becomes “expiring soon”
Critical	120 days before expiry
Important	90 days before expiry
Info	30 days before expiry

So reserve “Critical” for what halts the business if forgotten — a mandatory insurance policy, a certification without which an employee can no longer work: you will be warned four months ahead. Conversely, “Info” suits whatever can wait until the final month without cluttering your dashboard.

These three thresholds are detailed in Understanding statuses and an administrator can adjust them for the whole organisation: see Setting the “due soon” thresholds.

Criticality sends no email on its own

Marking a deadline “Critical” changes when it appears in orange, not the messages you receive. What gets sent depends solely on the alerts you set. A critical deadline with no alert will never write to you.

Recurrence

A deadline can be one-off or recurring:

Recurrence	Typical cases
One-off	A file to be submitted once.
Every 3 or 6 months	Frequent checks, internal inspections.
Every year	Insurance, subscriptions, most cases.
Every 2 years	Roadworthiness test for a passenger vehicle.
Every 3, 5 or 10 years	Heavy inspections, long-lived certifications.

The detail screen then shows the calculated next occurrence.

When you pick a template, a recurrence is already suggested: it matches common practice for that kind of deadline. Nothing obliges you to keep it.

Renewing

Once you have done what was needed — the new certificate has arrived, the inspection has been passed — the “Renewed” button moves the deadline on to its next date without you having to work anything out.

Renew rather than editing the date

Renewing preserves the deadline’s history and its settings. Overwriting the date by hand erases the trace of the previous cycle.

Snoozing

The “Snooze” button puts the deadline to sleep until a date of your choosing: it stops alerting you without leaving the register. The screen then shows until when.

This is the right answer to “I am dealing with it, but the supplier is dragging their feet” — far better than deleting the alert, which you then forget to put back.

Archiving

When the deadline no longer applies — the vehicle has been sold, the employee has left — archive it. It leaves the lists and the alerts but stays available. An archived deadline does not count towards your plan’s limits, and disappears from your calendar.

The record of what was sent

Each deadline keeps a trace of the reminders actually sent, with their outcome:

Outcome	What it means
Sent	The message went out.
Opened	The recipient opened it.
Failed	The send did not go through.
Bounced	The recipient’s server rejected it — wrong address or full mailbox.

Alert and reminder: two words for two things

An alert is what you set. A reminder is the email that results from it. So the history lists only the latter: an alert with its email switched off will never appear there.

This is the place to look when someone claims they received nothing: a Bounced status on an external address tells you immediately that the problem lies with the address, not with Kimori.