What a Frontline Survey Can't Tell You
It's frontline research season, and the surveys keep landing on the same finding: frontline employees feel short on clear, current information. The fix that tends to travel with it is one more app.
Before you act on either, be clear about what the research can carry. A frontline employee survey tells you how people feel about the information they get. It can't tell you whether the current version of your last priority update reached a given person, or whether they read it. Those are behavioral questions, and three counts on one priority update answer them.
What this season's frontline research measured
Take the research seriously, because the population behind it is large and distinct. The U.S. Bureau of Labor Statistics American Time Use Survey found that in 2025, 70% of U.S. employed people did some or all of their work at their workplace on days they worked.
That group also tends to be the least engaged. Gallup's State of the Global Workplace report puts engagement among on-site, non-remote-capable employees at 17% globally, the lowest of any work-location group, against 30% for exclusively remote employees. So frontline frustration with information is a real signal. It is also a perception measure, built on respondents reporting how often they feel they run into unclear or outdated information.
A frontline employee survey measures feelings
A survey answer is a recollection. A nurse or a line lead rating how current their information feels is averaging across every message and every week they can remember, and you then aggregate those answers across sites. Nothing in the result ties the feeling to a specific version or a specific person.
Self-reports of behavior drift from the behavior itself. A meta-analysis in Nature Human Behaviour comparing logged and self-reported digital media use found, across 106 effect sizes, that self-reported use correlates only moderately with logged measurements. That study measured digital media use and says nothing specific about internal communications, so treat it as a general caution about self-report. A survey can tell you a problem exists. It can't tell you which sites or which named employees are working from the old version.
Outdated information is a version problem
Frontline employees who say their information is outdated are usually describing something mundane. Last month's notice is still pinned in the break room. A supervisor printed the first draft of the new procedure and keeps it in a binder. Someone forwarded the PDF before the correction went out, and a pinned post in the team chat still shows the old shift rules because nobody went back to edit it. The current version is competing with copies of itself.
No survey sees versions. So the useful question for any priority update is narrower than "do people feel informed?" It is whether each person in the audience has the current version, and whether someone pulled the old one from every place it lived.
Pair the survey with behavioral data on frontline communication
For one priority update, put three behavioral numbers beside the survey's perception result, broken out by site and shift. Received means the current version reached the person or the channel they use. Opened means they opened it; for groups without an inbox, a supervisor's confirmation that the team saw it stands in. Acknowledged means an explicit "I've seen this," which belongs on any update that carries action weight, such as a safety step or a schedule change.
Read together, the two sources answer different questions. The survey tells you where people feel lost. The counts tell you who is missing the current version. Send tools that report received, opened, and acknowledged by name or audience make this repeatable. If your update is a change announcement and you want the fuller sequence, our post on how to tell whether a change message landed walks through it.
Run the check on your next priority update
Keep it to one update and five steps.
Pick the next update that matters, such as a safety procedure or a schedule or policy change, and give it a visible version marker, like an effective date on the first line.
Pull the old version from every place it lives, including boards, pinned posts, shared drives, and supervisor binders.
After the send, pull received, opened, and acknowledged on the current version, by site and shift.
Find the sites with the lowest numbers and ask those supervisors which version their teams are working from.
The next time you run a pulse survey, ask the information-confidence question at those sites and compare the answers with what you counted.
Step two is the one most teams skip, and it is the one the survey complaint is usually about.
Before you buy one more app
Consolidating onto a single app is a reasonable answer to a real complaint. But a new app is still a channel. It doesn't take the old notice off the break-room wall, and on its own it doesn't show who has the current version of anything.
Run the check first, so that whatever you buy, you'll know whether it closed the gap. Bring the survey and the counts to the next conversation about frontline communication.





Comments