Skip to content
As Written, As Enforced

Home / Keeping it

The Induction Five Minutes

The only part of the communication that reliably works, and the content fits on one page.

Keeping it · Procedure

Induction training

Never enforced

As written

New employees will receive training on company policies as part of induction.

What happens

Where induction covers policies at all, it consists of being shown where they are stored.

No organisation that states this clause can describe what was actually said about acceptable use.

The operative rule is: read it if you want, sign at the bottom.

If one thing is going to be done about communication, this is it. Five minutes, by a person, covering what actually matters.

The maintenance work in “The Induction Five Minutes” matters after software selection as much as before it. For teams assessing how to monitor employees without being intrusive in relation to how to monitor employees without being intrusive, rollout should include manager guidance, employee notice, a review date and a simple route for reporting inaccurate data or a setting that no longer matches the written rule.

What goes in it

The four or five rules that are live. Not the document. The things somebody would actually be spoken to about.

For a separate benchmark relevant to “The Induction Five Minutes”, consult the NCSC insider-data guidance. Use it to test purpose, notice, permissions, retention and response procedures against the proposed operating model rather than treating a generic checklist as proof that the rule works.

Typically: do not take customer data outside company systems, report a lost device immediately, do not share logins, ask before installing anything, personal use is fine within reason.

What the organisation can see, briefly and accurately. People assume worse than the truth and the correction costs two sentences.

What to do when something goes wrong, with a name. This is the most valuable item and the one most often missing.

And that mistakes reported promptly are not the thing that gets anybody into trouble.

What to leave out

The document itself, which they will sign separately.

Anything that is a reservation rather than a rule.

Legal framing, which is for the document.

And anything nobody would actually act on, which the audit identified.

Who delivers it

Somebody who could answer a follow-up question. Their manager, or whoever runs induction if they know the subject.

Not a recorded module, which has the same retention characteristics as the document and costs more to produce.

When

In the first week, not the first morning.

The first morning is saturated. A week in, the person has some context and the rules attach to something.

The written backup

One page, matching what was said, that they keep.

Not the policy — a summary of the five rules and the name to contact. It is the thing people actually refer back to, and producing it takes an afternoon once.

Whether it works

Ask somebody three months in what they would do if they lost their laptop on a train.

If they know who to call and expect not to be in trouble, the five minutes worked. If they hesitate, it did not, and the hesitation is the specific thing that costs the organisation time during a real incident.

The item most often missing

What to do when something goes wrong, with a name. It is the most valuable thing in the five minutes and the one most often left out, because the induction was built around the document rather than around what people will need.

Testing it three months later

Ask somebody what they would do if they lost their laptop on a train. Knowing who to call and expecting not to be in trouble means it worked. Hesitation is the specific thing that costs time during a real incident.

What goes in the five minutes

The four or five live rules, what the organisation can see, what to do when something goes wrong with a name attached, and that prompt reporting is not what gets anybody into trouble.

Timing it a week in

The first morning is saturated. A week later the person has context and the rules attach to something they have already encountered.

Checking whether it worked

Ask somebody three months in what they would do if they lost their laptop on a train. Knowing the name and expecting not to be in trouble means the five minutes landed.

Hesitation is not a knowledge gap in the abstract; it is the specific delay that will cost the organisation a day during a real incident, and it is produced by an induction that covered the document rather than the four things people will need.

Of everything in this collection, this is the item with the best ratio of effect to effort, and it is usually nobody's task.