Personal Things During Paid Time

This is the least measurable category and the one that generates the most heat, because it is about expectations rather than about records.

What it covers

A phone call about a child, a parent, a delivery.

A medical appointment booked during a break that overruns.

Personal messages.

An errand during a quiet period.

Almost every workplace tolerates some of this, and the ones that tolerate none discover what rigidity costs.

Why it resists measurement

It leaves no timestamp.

Systems that do capture it — application logs, screen monitoring — collect far more than this question needs and change the workplace in ways the question does not justify.

Which means the honest position is that you cannot measure it and should not build a control on the assumption that you can.

The reciprocity nobody counts

The same people answer messages in the evening, take a call at the weekend, stay late when something breaks.

An organisation that counts the personal call during work and not the work call during the evening is counting one side of a transaction.

And the workers involved are keeping both columns, even if the employer is not.

Stating the norm

Most of the friction here comes from the norm being unstated and therefore applied inconsistently.

Say it plainly: personal calls and messages are fine within reason; anything that affects cover or safety needs arranging.

One sentence, and it removes most of the ambiguity.

Where the work genuinely cannot accommodate it — a production line, a ward, a customer-facing queue — say that, and say why, because the reason is usually obvious and accepted once stated.

When it becomes a problem

When it affects the work, which is visible without any measurement.

When it falls unevenly, so colleagues carry it.

When it is a change in someone's pattern, which is usually something happening in their life and is a conversation rather than a process.

What not to do

Do not deploy activity monitoring to measure this. It is the question that most often gets used to justify screen capture, and it is not a question screen capture answers proportionately.

Do not enforce selectively, which is how a tolerated norm becomes a grievance.

And do not count it in a time-theft total, because you have not measured it and the number would be invented.

Say the norm out loud

Once, plainly, and most of the friction goes.

"Personal calls and messages are fine within reason; anything affecting cover or safety needs arranging."

Where the work genuinely cannot accommodate it, say that and say why — the reason is usually obvious and accepted once stated.

An unstated norm is enforced inconsistently, which is how a tolerated practice becomes a grievance.

A practical configuration prompt

During configuration, use see the operational example to prompt questions about identifiers, ownership and output. Treat the page as a starting point and document each assumption.

Independent reference

For a thematic point of reference, see the CIPD. Use this established source as an outside check before turning the principle into a system rule.