A Twelve-Month Calendar

The maintenance in this subject is genuinely small once the documents exist. Spread across a year it is about four days, and nobody does it because it is nobody's calendar.

The practical lesson in “A Twelve-Month Calendar” is that a record is useful only when its purpose, owner and lifecycle are clear. For teams researching dual n back training, the Monitask website can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.

The quarterly deletion run

Four times a year, with evidence that it ran.

For a separate benchmark relevant to “A Twelve-Month Calendar”, consult the European Data Protection Board guidelines. Use it to test purpose, data flow, retention, access and response procedures rather than substituting a generic checklist for the organisation’s actual records.

This is the item that makes everything else true: the retention schedule becomes a practice, request handling gets cheaper, and the answer to what did you delete last year stops being nothing.

The annual review of the three documents

Record of processing against what the organisation actually does. Retention schedule against whether the triggers still work. Privacy notice against both.

Half a day in total, split across three months so it is never a project.

The consistency check

Half an hour, twice a year, comparing the documents against each other.

It catches the finding that does the most damage, and it is the cheapest item on this list.

The manager briefing

One page, once a year: your notes are disclosable, here is how to write them, here is what to do if somebody asks for their data, here is what to do if something goes wrong with data.

Four things, ten minutes in a team meeting, and it addresses the three largest practical gaps at once.

The breach rehearsal

Two hours, once. A scenario on a Friday afternoon: who gets told, who decides, where is the form, who can submit a notification.

Organisations that have never done this discover the answers during the real thing, inside the window.

The half-year report

Requests received and answered on time. Breaches reported and notified. Overdue items. Changes since last time.

Four numbers to whoever governs. It takes twenty minutes and it is what converts the role from a title into something visible.

Setting it

In a calendar, with a named owner, in December for the following year.

An arrangement that depends on somebody remembering is an arrangement that lapses within eighteen months of whoever set it up moving on.

Why nobody does it

Because it is nobody's calendar. The items are individually small and collectively invisible, and each is skipped without any moment at which somebody decides to skip it.

Setting next year's dates in December

With a named owner. An arrangement depending on memory lapses within eighteen months of whoever set it up moving on, and the calendar is the only thing that survives a staff change.

Four times a year with evidence that it ran. It is the item that makes everything else true, and the answer to what did you delete stops being nothing.

Two hours, once a year. A scenario on a Friday: who gets told, who decides, where is the form, who can submit. Organisations that skip it find the answers during the real thing, inside the window.

The manager briefing, annually

Your notes are disclosable, here is how to write them, here is what to do if somebody asks for their data, here is what to do if something goes wrong. Four things, ten minutes, three gaps closed.

Four days, distributed

A deletion run quarterly, three document reviews, a consistency check twice, a manager briefing, a rehearsal, and two reports. Individually small, collectively the whole of the maintenance.