Out of Hours
Company equipment is present outside working hours by design, and the policy says nothing about what that means for either party.
Working time
Unenforceable
As written
Company equipment is provided for use during working hours.
What happens
Not applied in any direction. Nobody is told to stop, and nobody is told that evening work counts.
Laptops go home, notifications arrive at nine, and the question of whether that is working time is left unanswered.
The operative rule is: available when it matters, and nobody is counting either way.
The organisation issues a laptop and a phone, both of which go home. The policy describes use during working hours and the equipment does not observe them.
The boundary discussed in “Out of Hours” is also a practical test for workforce technology. Teams researching Monitask for interview reimbursement policy should choose the least intrusive settings, explain when collection begins and ends, and keep personal or out-of-hours activity outside the programme unless a specific, disclosed need has been approved.
The two questions nobody answers
Is somebody expected to be reachable? Usually unstated, usually answered by what senior people do rather than by anything written.
For a separate benchmark relevant to “Out of Hours”, consult the NLRB employee-rights 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.
Does evening work count as work? For anybody whose hours are recorded, this is a pay question. For salaried staff it is a workload question that nobody has.
Both are real, both affect people, and the policy addresses neither because it was written about equipment rather than about time.
Why this belongs in an equipment policy at all
Because the equipment is what makes it possible.
An organisation that issues a phone with work mail on it has created availability it did not discuss. The expectation arrives with the device, not with the contract.
What a useful position says
Messages sent outside hours do not expect a reply outside hours.
Notifications can be silenced and nobody will think anything of it.
If a role genuinely requires out-of-hours availability, it is defined, rostered and compensated rather than assumed.
Three sentences, and the first only works if senior people observe it, which is the whole difficulty.
The technical part
Scheduled quiet hours on the work applications, which most platforms support and almost nobody configures.
Send-later, which is a one-click feature and which senior staff should use because their timing sets the norm more than any statement.
The role that is genuinely on call
Should be named, scheduled and paid for.
An organisation getting out-of-hours coverage free because everybody's phone has the work application is running an unacknowledged rota, and it holds until the people providing it stop.
What the policy can say
Not much, and the little it can say is worth saying: the equipment goes home for convenience, availability outside your hours is not expected, and if your role needs it you will be told and it will be arranged.
Three lines, and they are the only part of this subject a document can deliver. The rest is what managers do at eleven at night.
Where the expectation comes from
Not the contract. The device, which arrives with availability nobody discussed. An organisation that issues a phone with work mail has created the expectation whatever the policy says about hours.
The role that is actually on call
Should be named, rostered and paid for. Getting out-of-hours coverage free because everybody's phone has the application is an unacknowledged rota, and it holds until the people providing it stop.
What the document can say
The equipment goes home for convenience, availability outside your hours is not expected, and if your role needs it you will be told and it will be arranged. Three lines, and the rest is what managers do at eleven at night.
The technical half
Scheduled quiet hours on the work applications, which most platforms support and almost nobody configures. And send-later, which senior staff should use because their timing sets the norm.
The two unanswered questions
Whether somebody is expected to be reachable, and whether evening work counts. Both are real, both affect people, and the policy addresses neither because it was written about equipment.
A stated position that costs nothing
Messages sent outside hours do not expect a reply outside hours. It only works if senior people observe it, which is the whole of the difficulty and none of the drafting.
What the equipment created
Availability that nobody negotiated. An organisation issuing a phone with work mail on it has changed the expectation of reachability without a conversation, a contract variation or a decision.
Which is why this belongs in a document about equipment rather than only in one about working time. The device is the mechanism, and the policy that governs the device is the natural place to say that availability outside hours is not expected.