Screen-break software an employer can deploy, and a works council can live with. This
document is written for the people who have to approve it as much as for the people who
have to buy it, so most of it is about what the software does not
collect and why that is a matter of architecture rather than of policy.
Screen-break software is not hard to buy. It is hard to still have running in six
months, and the overview opens with the three separate reasons for that: it interrupts,
so people switch it off; one schedule does not fit a workforce; and it looks like
monitoring, so nobody trusts it.
What is in it
- Three things stop this workingThe three ways these rollouts die, and
what each one demands of the software. Two are about the product and one is about the
people it is given to.
- What employees seeThe same application sold to individuals, with the
Pro features on. No sign-up, no password, nothing to enrol in.
- What administrators seeThe dashboard: licences, deployment settings,
the configuration your machines pick up, and what it does not hold at any
tier.
- Licences, day to dayLicensing people, then deploying to the people
you licensed. Reassignment, renewals, and what happens when a term ends.
- DeploymentTwo things reach each machine, your settings and the
application, in that order, because the app reads its settings when it
starts.
- Configuration, and estates without Group PolicySetting defaults
centrally and choosing setting by setting what people may change. For estates with
neither Group Policy nor Intune, the dashboard writes the whole thing out as a
script.
- Reporting, and what it deliberately cannot tell youOptional, and off
unless you turn it on. Three numbers a week, carrying no identifier of any
kind.
- Where the time wentThe number an employer expects to be hidden, which
is reminders that were never shown, on the same page as the adherence
figure.
- Privacy, and why it is architecture rather than policyNot that we
choose not to look, but that there is nothing to look at that resolves to a person.
The difference is the only part worth reviewing.
- Your security reviewThe questions an endpoint or security team asks,
answered before they ask them.
- Licensing, pilots and what to do nextPer licence, in USD, excluding
VAT. Annual and monthly can be held together and renew on their own
terms.
The other two documents
The product overview covers the application
itself in full: how the pausing works, what a break is like, and how much of it a person
can change. This document assumes it rather than repeating it.
The security and IT reference is the one-page technical
summary, written to be forwarded to whoever manages your endpoints without you having to
edit it. Deployment is the step-by-step.
Licensing, quotes and purchase orders go to
biz@20-20-20-vision.com.
Technical and security questions go to
dev@20-20-20-vision.com
and reach the people who write the code.
Pricing is on the workplaces page.