The specific problem with work-hours screen time is that most screen-time advice is built for reducing overall use, and that framing doesn't apply to a job that requires the screen — the actual goal during working hours isn't fewer hours on the phone or laptop, it's fewer of those hours going to the wrong apps while the right ones sit untouched. A generic screen-time total tells you nothing about whether the hours you spent were spent on the spreadsheet or on your feed. The confusion is understandable, since most consumer screen-time tools were originally built with a fairly simple assumption in mind — less time on the phone is generally better — and that assumption breaks down completely the moment the phone or laptop is also the primary tool for doing the job itself.
What you've probably already tried
A total daily screen-time limit that gets hit by legitimate work use before lunch and then has to be dismissed for the rest of the day, a work-hours Focus mode that silences notifications but doesn't stop you opening an app yourself, separate work and personal phones. These address volume, not which apps the volume went to, which is usually the actual issue during work hours. Some people try manually tracking time spent per app using a time-tracking tool, which produces useful data about where the hours actually went, but reviewing that data after the fact doesn't do anything to prevent the same pattern from repeating again tomorrow, since awareness alone rarely changes behavior on its own. Some workplaces provide managed devices with their own restrictions built in, which removes some of this burden from the individual entirely, though most remote and hybrid workers are still relying on a personal device for at least part of the job. Where a managed device isn't available, a personal blocklist is the more practical middle ground most remote and hybrid workers actually have.
Why generic blocking advice fails specifically here
A blanket screen-time limit treats every app the same, whether it's the CRM you're paid to use or the app you open when the CRM gets tedious, which means the limit either has to be set so loose it doesn't do anything, or so tight it blocks legitimate work along with everything else. It also creates a frustrating daily ritual of hitting the limit, dismissing it because legitimate work is still pending, and then having no protection at all for the rest of the day — which is often worse than no limit in the first place, since it trains you to routinely override your own safeguards. It's also worth noting that dismissing a screen-time limit repeatedly tends to erode trust in the tool itself over time, making it feel more like an obstacle to route around than a genuine support for focus. Trust in a self-imposed limit erodes fast once it's been overridden a few times in a row for legitimate reasons.
The honest fit
A quiz-gated block fits this well because it targets specific apps rather than total time, which means work tools stay fully accessible while the actual distraction — a small number of specific, identifiable apps — gets the friction, letting the workday's actual screen time stay high without the distracting portion of it staying easy. Because the distinction is at the app level rather than the total-time level, it also produces a much more accurate picture of what's actually happening during work hours — high total screen time that's genuinely mostly work, rather than an ambiguous number that could mean either focus or its opposite. It also adapts more easily as a role changes, since updating a blocklist to reflect new job tools takes moments, compared with reconfiguring a broader, less granular time-based system. That precision is worth the small extra setup effort compared with a blunter, total-time-based limit.
Where it isn't the right fit
If work itself requires using an app that would otherwise be blocklisted — social media management for a marketing role, for instance — a blanket block on that category will constantly get in the way of the job itself, and the blocklist needs to be built around the real distraction, not a generic category that happens to include tools you're paid to use. It's worth reviewing the specific blocklist periodically too, since job responsibilities and the tools that come with them tend to shift over time, and a blocklist built for a role from a year ago may quietly be blocking something that's now a legitimate part of the job. A quarterly check of the actual blocklist against current job responsibilities is a reasonable habit to build alongside using the tool day to day. Five minutes spent reviewing the list each quarter is a small cost against the frustration of a stale, poorly-fitted block. It's a small habit, but one that keeps the tool matching the actual shape of the job over time.