Should You Block Distracting Websites at Work?

Blocking distracting websites at work sounds like the obvious fix, and on an office network with a firewall it is at least possible. For a remote team it barely works at all: the blocklist never ends, the phone next to the keyboard is not on your network, and a filter cannot tell a designer studying a YouTube tutorial from someone watching a series. What keeps remote employees focused in practice is not a wall but a number: measuring how much paid time goes to distracting apps and sites, showing the same number to both sides, and giving the employee a fair way to say that a flagged item was actually work. This article covers why blocking fails remote teams, what quiet measurement does differently, and how it works in SCREENish, as of September 2026.

Why blocking distracting websites fails for remote teams

A website blocker is a list, and the list is never finished. Block youtube.com and the video moves to a mirror, an embedded player or the app on the phone lying next to the keyboard. Every week brings a new site to add, and every addition is a small administrative task that lands on whoever manages the filter. Offices absorb this cost because one firewall covers everyone; a remote team has no shared network to filter, so blocking means installing filtering software on every machine, keeping it updated on machines you do not physically control, and hoping nobody figures out that a free VPN gets around all of it in one click. Most people figure that out in the first week.

The deeper problem is that a block is binary and work is not. The same site is a distraction for one role and a tool for another. YouTube hosts both lo-fi playlists and the tutorial your designer needs right now. A social media manager cannot do the job with social media blocked. When the filter stops a legitimate task, the employee routes around it, and once they are around it, they are around it for everything. The filter then protects nothing and still costs trust, because what it says to the team is: we assume you cannot be left alone with a browser.

A measured number changes behaviour where a wall cannot

Learn how SCREENish saves you money Time tracking with screenshots, honest reports and hands-off payroll. Free to try — no credit card. Start free →

Almost everyone underestimates their own drift. Twenty minutes on a news site feels like five; a quick scroll after lunch turns into forty minutes nobody remembers. A weekly number, in minutes, attached to named apps and sites, ends the guessing on both sides. The employee sees it and usually corrects course on their own, because the number is theirs and nobody had to say anything. The manager sees patterns instead of moments: not "was she on Twitch at 14:03" but "video sites took four hours of this project's week", which is a conversation about a workload, a habit or a rule, not an ambush about an afternoon.

Measurement also fails more gracefully than blocking. A wrongly blocked page stops work right now and demands an urgent exception. A wrongly counted minute costs nothing today; it gets corrected later, in review, without anyone's flow being broken. That is also why the counting itself should be quiet. A popup that tells someone they are distracted is itself a distraction, and a nag on the screen turns a measuring tool into a nanny. The tool's job is to write the minute down, not to interrupt; people are interrupted enough.

What counts as a distraction is your call, not the tool's

Monitoring tools that ship a fixed productive and unproductive label for every app get this wrong constantly, because the labels encode someone else's idea of your work. A better shape is categories the employer switches on per project. SCREENish ships six: Social media, Video & streaming, Games, Shopping, News, and Music & audio, each covering the sites and apps you would expect, from Facebook and TikTok through Netflix and Twitch to Steam and eBay. You tick the categories that count as distractions for this project and leave the rest off.

Music is the honest test case. For many teams a music player is background, the thing that keeps a developer in flow, and counting it as a distraction would be absurd; those teams leave the Music & audio category off. A team doing client calls all day may see it differently. There is no universally right answer, which is exactly why it is a switch and not a verdict. Note that only the active window is ever classified, so even with the category on, music playing in the background costs nothing; what gets counted is the time spent in the player itself, choosing songs and curating playlists. For anything the categories do not cover, a custom rule takes an app name or a word from a window title, so an internal tool, a specific forum or a particular game that eats your team's afternoons can be counted too.

When the tool is wrong, the employee can say so

Any automatic classifier is sometimes wrong, and a monitoring feature with no correction path punishes the employee for the tool's mistake. In SCREENish the employee sees their own distraction minutes in their dashboard, listed by app and site, the same numbers the employer sees. Next to each item there is a button that says This is work. Clicking it sends a request to the employer with the item attached.

The employer sees the pending request flagged in red on their own dashboard, opens it, and decides. Approving it does two things: the current week's minutes are recalculated with that item removed, so the correction is retroactive and the employee is not stuck with a number both sides know is wrong, and the item stops being counted going forward, for that entry, for its whole category, or for the whole project, whichever the employer picks. A request can also be denied. Either way the disagreement is settled in the open, once, instead of festering as a quiet grievance about a tool that cannot be argued with.

Where SCREENish fits

Prevent Distractions is part of SCREENish's program reporting: the desktop tracker records which applications and window titles received time during tracked hours, and the server classifies that record against the categories and rules you chose. Because the classification is built on program reports, the feature requires them, and turning it on for a project is two switches and a few ticks in the project's advanced options. The setup walkthrough is in Setting Up Distraction Rules, and Using the Prevent Distractions Feature shows what both sides see day to day.

The results appear where you already look: a distractions line in each day's work log next to the screenshots and activity levels, and a per-person summary in the team overview, with totals settled overnight in your own timezone and a weekly rollup every Monday. Nothing is blocked, nothing pops up on the employee's screen, and the employee's dashboard shows the same minutes the employer's does, with the This is work button right there. If you arrived here searching for a way to block distracting websites, what you most likely want is a focused team. Measure first. Most teams that see the numbers never end up needing the wall.