Last month a plant head sent us a compliance calendar. It was colour coded, twelve months deep, and marked with every POSH and POCSO training date, every statutory filing window, every internal review. It looked like the work of someone who cared. So we asked the obvious question: who owns this?

The room went quiet. Then somebody said, "It's on the shared drive."

That answer, we have learned, is usually the whole story. A calendar can exist for years and have no owner. It gets built by an enthusiastic person, survives a role change or two, and then drifts. The dates stay on the page. The responsibility behind them quietly leaves the building.

We keep meeting this. A document that looks like control, with nobody's name against it.

A calendar is a list, not a system

Every compliance calendar we have seen is, at heart, a list of dates. That is fine as far as it goes. But a list only works if someone is checking it, chasing it, and answering for it when a date passes. Without a name attached, the list becomes decoration. It reassures the people who glance at it and does nothing for the people who depend on it.

Think about what a deadline actually needs. It needs a person who knows it is coming, a person who prepares the groundwork in the weeks before, and a person who is accountable if the work is not ready. Those can be three different people. Often they are zero.

When we audit, we ask a simple set of questions. Who gets the reminder? Who acts on it? Who escalates when the first two fail? Who signs off that it happened? If the answers are vague, the calendar is not a control. It is a hope.

Where the dates actually slip

Deadlines rarely slip because people are lazy. They slip in the gap between the person who knows and the person who acts.

Take a training date. The calendar says the annual awareness session runs in August. In July, nothing happens, because the person who used to book the room has left. In August, someone notices the date has passed. In September, a hurried session is arranged for whoever is free. In October, the attendance sheet is filed, incomplete, and nobody looks at it again until the next audit.

Or take a filing window. The calendar marks the last date. Nobody marks the eight weeks of preparation that have to come before it. The date arrives, the paperwork is half built, and the team spends a stressful week doing badly what should have taken a calm month. The calendar did its job. The work did not.

We see the same shape again and again:

• The date is recorded, but not the preparation it needs.
• The reminder goes to a group, not a person.
• The escalation path stops at the first missed reply.
• The evidence of completion is collected but never reviewed.
• The calendar is updated after an audit, then left alone until the next one.

None of these is dramatic. Together they mean the calendar survives on paper while the work underneath it thins out.

The handover problem

Most of these calendars were built by one person. That person usually built it well. They knew the dates, they knew the quirks, they knew which department always needed a nudge. Then they moved on.

What they left behind was a file. What they did not leave behind was the knowledge of how to run it. The new holder inherited the dates but not the instincts. So the calendar ran on momentum for a while, then slowed, then stopped being checked.

This is a quiet failure. Nobody announces it. The file still opens. The dates still sit in their neat rows. It is only when a deadline passes unnoticed that the gap becomes visible, and by then the cost is already paid.

What ownership actually looks like

An owned calendar looks different in small, unglamorous ways. There is a name against each category, not just each date. There is a standing review, weekly or monthly, where someone opens the calendar and says out loud what is coming. There is a rule that says if a date is at risk, it gets raised early, not apologised for later.

We ask clients to write down, for every recurring obligation, four things: who prepares, who approves, who is told if it slips, and where the proof lives. That is it. Four lines per obligation. It is not sophisticated. It is the difference between a calendar that works and a calendar that merely looks like it does.

The hardest part is not the writing. It is deciding that the calendar belongs to someone. Naming an owner feels like an admission that the work needs managing. It is. That is the point.

The cost of an orphan

An unowned calendar does not fail loudly. It fails in the margins. A training that never quite happens. A filing that goes in late. A complaint that sits because nobody remembered the next step. Each is survivable alone. Together they build a record that, when examined, shows a pattern of drift.

And that record matters. When a dispute or an inspection arrives, the question is never "did you have a calendar." It is "can you show what happened." An orphaned calendar shows dates. It rarely shows action.

We have watched organisations spend money on new software to fix this. The software arrives, the dates move into it, and nothing changes, because the problem was never the tool. The problem was that no one was standing behind the dates.

Start with one name

If you take one thing from this, take the smallest one. Pick your compliance calendar up today and put a name at the top of it. One person who owns the whole thing, even if they delegate the parts. Then ask that person to walk you through the next ninety days and tell you, for each date, who is doing what.

You will learn more in that half hour than in a year of tidy filing. You will find the dates with no preparation behind them, the reminders going to nobody, the evidence nobody reads. Those are the places the calendar is pretending.

A calendar is not a promise that things will happen. It is a map of what should. Someone has to walk the map. Until a name sits at the top, you have a document, not a control, and the quiet slippage will continue exactly as before.