Regulatory deadlines watched by the tool, not by a person

A whistleblowing channel, in an international group. Two deadlines to meet: reply to the reporter within 7 days, open the investigation within 14 days. In practice, tracking relied on one person's vigilance.

One person, other duties, time off

The issue isn't that person's rigor. It's their situation.

They have other duties. They take time off. Tracking deadlines is just one of their tasks.

The tracking holds as long as they're there and remember. The day they're absent, or busy elsewhere, the clock keeps running. Nobody is watching it.

Statistics, not negligence

My conviction fits in one sentence: a deadline watched only by humans will be missed. Not through negligence. By statistics.

On one case, vigilance is enough. On many cases, for months, with absences and shifting priorities, a slip eventually happens. It's not a question of diligence. It's a question of the number of attempts.

You can ask someone to be vigilant once. You can't ask them never to slip, all year long, on top of everything else. A machine doesn't take time off.

The rules live in the application

I took the deadlines out of people's heads and put them in the tool.

• The rules are encoded. 7 days to reply to the reporter, 14 days to open the investigation. The application knows them.
• An "Overdue" indicator. It constantly counts the cases past their deadline.
• Recalculated every time. The number is recalculated every time the dashboard is opened. It doesn't depend on any manual update.

The manager no longer has to remember the deadlines. They read one number. If it's zero, all is well. If it isn't, they know how many cases need their attention.

The calculation requires no extra data entry. The deadlines are measured from the case dates, already in the tool.

Responsibility doesn't change hands. The manager stays responsible. What changes is that they no longer need to keep count in their head.

The annual report, as a bonus

The system also has an annual report.

Before, this report took three days of digging through a mailbox.

Today, the report can be read from a dashboard. The cases and their deadlines are already in the tool, because it tracks them as they go.

That's one more benefit. A rule encoded to monitor also produces the system's memory. What was scattered across emails becomes data that can be counted, sorted and presented.

Why it matters for compliance

A regulatory deadline isn't a good intention. It's an obligation, and it gets checked.

When tracking rests on a person, the proof rests on them too: their mailbox, their notes, their memory. When tracking rests on the tool, the proof is in the tool. It doesn't go on vacation with anyone.

What this means for you

List the deadlines your department has to meet: regulatory, contractual, internal. For each one, ask yourself who watches it.

• If the answer is a name, the deadline depends on that person being there.
• If the answer is "the tracking spreadsheet", it depends on the person who updates it.
• If the answer is "the tool, which shows the number of overdue cases", the person who used to track it can go on vacation.

The goal isn't to take responsibility away from people. It's to give them a number to read, instead of a list to watch. A zero can be checked at a glance.

The same tool computes the status of each case from the facts: the status that is computed instead of entered. It also protects each report at the data level: hiding a button does not protect the data. The full project is told in the case study A whistleblowing channel that watches its own deadlines. This kind of tool is described on the page An application instead of the Excel file.

A deadline watched only by humans will be missed. Not through negligence, by statistics.