Ten requirements follow from the six ways frontline communication fails: reach without corporate identity, phone-first and device-agnostic design, offline access, translation at publish, targeting by site, role, shift, and language, delegated local publishing, a built-in return path, answers alongside the work of the shift, message-level acknowledgment, and a governed channel workers prefer. Write them down before any demo. A desk-built product usually satisfies five. A frontline-built product starts with the first four, because nothing else matters until delivery works.
The demo always goes well. The feed looks clean, the composer is quick, and the analytics dashboard fills with tidy charts drawn from a sample tenant where every employee has a company email address and a laptop. Nobody in the room asks what happens to the stock associate hired on Tuesday, who has neither.
That question is the evaluation. Everything else is presentation.
Why requirements come before demos
Requirements come first because a demo shows features and requirements test architecture. If frontline communication fails because sending is not reaching, then a better feature set on the same channel changes nothing, and the evaluation has to be about infrastructure.
Hold onto one rule through every vendor meeting. The order in which a vendor can satisfy the ten requirements below tells you what the product was originally built for. Here they are, written as a buyer's list rather than a feature list.
| # | Requirement | Why it is non-negotiable | Gap it closes |
|---|---|---|---|
| 1 | Reach without corporate identity | A worker with no company email must be provisioned and reachable in minutes, not excluded by default. | Gap 1, delivery |
| 2 | Phone-first and device-agnostic | Personal phones, shared devices, kiosks, and screens on the floor. A responsive website is not the same capability. | Gap 1, delivery |
| 3 | Offline capability | Plant floors, cold storage, basements, vehicles, remote sites. Content has to be readable without a live connection. | Gap 1, delivery |
| 4 | Translation at the moment of publishing | Mixed-language crews share one shift. Translation as a separate project arrives late and drifts from the original. | Gap 1, delivery |
| 5 | Targeting by site, role, shift, and language | Reaching the right subset directly takes load off the supervisor instead of adding to it. | Gap 2, the manager |
| 6 | Delegated local publishing | Local leaders publish what is true at their site, inside guardrails set centrally. | Gap 2, the manager |
| 7 | A return path built in | Surveys, pulses, and anonymous feedback on the same audience model, not a separate tool. | Gap 3, the return path |
| 8 | Answers and the work of the shift together | Policy, pay, schedule, training, and tasks in one place, or the question goes to the supervisor. | Gap 4, answers |
| 9 | Acknowledgment at the message level | Must-read tracking, confirmation, and escalation. Sent is not received. | Gap 5, proof |
| 10 | A governed channel workers prefer | Governance only works if the sanctioned channel beats the group chat it competes with. | Gap 6, governance |
1. Reach without corporate identity
A worker with no company email address has to be provisioned and reachable within minutes of being hired, not excluded by default. Every other requirement depends on this one.
In practice, a new hire gets in with no password and no corporate email, and without a laptop or a VPN. Single sign-on, multifactor authentication, and SCIM provisioning are supported where they already exist and required nowhere. Provisioning follows from one employee record, so site, role, shift, language, and audience membership arrive together instead of being set up by hand in four places.
The app should be published under your name in both app stores, with your branding on the login screen and every notification. That sounds cosmetic. It isn't, because an app carrying the company's name reads as the company's app rather than software the company bought. Santee Cooper, a public electric and water utility in South Carolina with more than 1,600 employees, ran a naming contest, and its employees called theirs The Coop.
"People in the field can sometimes be disconnected with what's happening corporate-wide. That's just a natural result when your jobsite is a turbine floor or a bucket truck. That means a lot of our folks have limited access to a computer. The Coop gives us a way to close that gap."
Jeffrey Straight, Public Relations Specialist, Santee Cooper
Most of this workforce will use a personal phone, so look for an app-level PIN, remote wipe, and containerized company data. Where phones are impractical, kiosk mode on a shared device covers the rest.
Why is this non-negotiable? Retail frontline turnover runs above 60% a year (McKinsey, 2024). At that rate provisioning isn't an edge case IT handles once a quarter. It's a weekly operation. A.S. Watson's Kruidvat stores show what happens when it works: most store staff have no company email, employees onboarded themselves with no training materials needed, and active user adoption passed 80% across more than 16,000 Kruidvat employees.
In the demo, ask the vendor to provision a fictional new hire with no email address and show what that person sees on a phone. Give them five minutes.
2. Phone-first and device-agnostic
The app has to reach workers on whatever device is actually in front of them, whether that is a personal phone, a shared handheld at the station, a kiosk, or a screen on the floor. A responsive website is not the same capability. It is a desk experience rendered on a smaller screen, still reached through a sign-in built for a desk identity, which is why a mobile intranet and a frontline employee app are different products even when they look alike on a phone.
Screens matter more than buyers expect. Some workers will never open an app mid-shift, and some environments make a phone unsafe. A break-room display carrying the same post as the app reaches those people without anyone rebuilding the content.
In the demo, ask to see one message, published once, on a personal phone, a shared device, and a break-room screen.
3. Offline capability
Content has to be readable without a live connection, because much of frontline work happens where there isn't one. Plant floors, cold storage, basements, delivery vehicles, and remote sites all break any feature that assumes a signal.
The test is practical. A safety data sheet that needs a desktop, or a live connection, is not available to the person standing next to the chemical. A field technician in a van at a customer site has no break room and no supervisor three aisles away. If the procedure won't open where they are, there is no second channel behind it.
In the demo, put the phone in airplane mode and ask to open the current procedure and the last must-read post.
4. Translation at the moment of publishing
Every language version of a message has to exist the moment the message goes out, because a single shift often runs in three or four languages and a translation project always arrives late. Delay is only half the problem. Someone fixes a date in the English post, the Spanish copy made as a separate job keeps the old one, and three weeks later half the crew is working from a version nobody meant to publish.
The requirement is that translation happens to the content itself, at publish, rather than to a copy of it. Correct the original and every language corrects with it. The translation should also cover the whole platform, not just the posts. A worker who reads Spanish, Portuguese, Tagalog, or Polish should get the app in that language rather than an English shell around translated messages. MangoApps translates at publish in more than 100 languages.
Machine translation needs guardrails. Safety language, internal terminology, and brand terms often must not be machine translated, so look for overrides that hold those phrases fixed, plus regional defaults so each site starts in the languages its crews actually work in.
A major windows and doors manufacturer is a useful reference point. Two-thirds of its 14,000-person workforce is on the frontline, and four years ago most of those employees had no email access. More than 90% now actively engage, reached through audience segmentation, multilingual access, local champions at each site, and a design built around the phone and connected to its HR systems. Language was one of four levers, not a finishing touch.
In the demo, ask the vendor to publish a post in English, correct one word, and show the correction in three languages without anyone republishing.
5. Targeting by site, role, shift, and language
Precise targeting is what takes load off the supervisor rather than adding to it. When a message can only go to everyone, the supervisor becomes the filter, deciding what applies to their team and relaying it in person. When it can go straight to second-shift pickers at two warehouses who work in Spanish, the supervisor has nothing to filter or repeat.
What separates real targeting from a list tool is where the audiences come from. They should be built from employee attributes, not static lists, so a campaign for second-shift warehouse staff stays correct as people join and leave. A static list is accurate on the day someone builds it and wrong by the next payroll run.
In the demo, ask for an audience built from site, shift, and language, then add a matching new hire and show that they join it automatically.
6. Delegated local publishing
Local leaders must be able to publish what is true at their site, inside guardrails set centrally. Buyers miss this requirement more than any other, because it looks like an administrative detail. It's the difference between a channel that carries relevant content and one that carries only corporate content, and workers can tell which one they're looking at within a week.
A screen showing only headquarters content stops being read.
In practice, departmental and site owners publish and maintain their own sites and content within a structure the central team sets. Regional and site administrators are scoped to what they own, so a distribution center manages its own audiences and posts without holding the keys to the whole platform.
Behind this sits an ownership question most evaluations skip. The function that owns employee communication is almost never the function that owns IT. If every audience change, new site, or template needs a ticket and a sprint, the platform stops reflecting the organization within a quarter, and the workarounds start. Audiences, templates, sites, branding, approval routing, and permissions should all be configurable without code or a developer, from one admin surface.
Adoption and usage should also be reported by site, so a location that is drifting away shows up while someone can still do something about it.
In the demo, ask a site administrator, not the vendor's central admin, to create a local audience and publish to it without help.
Download Frontline Worker Communication & Engagement. It sets these ten requirements against the six reach gaps they come from, with the capability detail behind each one. Get the book
7. A return path built in
Surveys, pulses, and anonymous feedback have to be first-class capabilities on the same audience model as communication, not a separate tool. The reason is the follow-up. The group you surveyed should be the group you close the loop with, defined once. Closing the loop is the strongest single influence on whether anyone answers the next survey, and it is nearly impossible when the survey tool and the communication tool each keep their own audience definitions.
Anonymity has to be structural as well, enforced by minimum response thresholds before site or team results appear. A sixty-second check-in at shift end only produces honest answers if the person giving them believes the promise.
In the demo, ask to survey one site, then send the follow-up to exactly the people who were asked, with no export in between.
8. Answers and the work of the shift together
Policy, pay, schedule, training, and tasks need to live in one place, or every question goes to the supervisor by default. A worker with a two-minute question and nowhere obvious to ask will ask the person already running the floor.
The schedule deserves a closer look. It is the single most reliable reason a frontline employee opens an app, which makes it the strongest adoption driver for everything else in that app. A news feed people have to remember to check competes for attention. A feed beside next week's shifts doesn't have to.
This is also where AI either works or doesn't. An assistant can only answer from content that is current, governed, and held in one place. Take an employee who wants to know how holiday pay works for a shift that crosses midnight. The right answer comes from the actual policy document, scoped to that person's site and employment type, with the source attached. Whether that answer is possible gets decided by the platform underneath, long before anyone picks a model.
In the demo, ask a pay question in plain language from a frontline account and check that the answer cites the policy it came from.
9. Acknowledgment at the message level
Critical messages need must-read tracking and confirmation from each employee, with automatic escalation for anyone who has not responded. Sent is not received, and received is not understood. Publishing metrics tell you a post went out. They cannot tell you whether the night-shift nurse saw the protocol change before the next patient.
The architectural test is where the confirmation lands. Acknowledgment should be written to the same employee record the compliance view reads from, with no export and no reconciliation window during which the two disagree. That is what turns acknowledgment tracking into evidence rather than a report someone assembles after the fact. In healthcare, documented acknowledgment is not a reporting nicety. It is the audit.
In the demo, ask the vendor to name the sites below target on a recent critical message, then show the automatic re-send to everyone who has not viewed it.
10. A governed channel workers prefer
Governance only works if the sanctioned channel is better than the group chat it competes with. Policy doesn't achieve it. Making the governed channel the one people would choose anyway does, and that is the requirement no feature list states plainly.
Workers are not waiting for permission. When the company channel doesn't reach them, coordination moves to personal messaging groups the company does not own and cannot produce in an audit. Combined SEC and CFTC fines for work conducted on unapproved personal messaging channels passed $2.5 billion (SEC and CFTC enforcement actions, 2021 to 2024). The gap created that exposure, not the employees.
So the governed channel has to do what the personal group already does well, including group rooms for a site or shift team and voice notes for when hands are busy. Retention and eDiscovery then apply to conversations people were going to have anyway.
In the demo, ask to see a shift team's group chat, then the retention and eDiscovery settings that govern it.
How the ten sort vendors
A product built for desk workers can usually satisfy five of the ten. Typically those are targeting, the return path, and acknowledgment, with partial credit on devices and on governance. A product built for the frontline starts with requirements 1 through 4, because nothing downstream is measurable until delivery works. Acknowledgment data is meaningless if a third of the workforce never opened the app.
The split is architectural. A platform designed as one system shares a data model. A platform assembled from acquisitions and integrations shares a login screen. On a demo they can look identical, but under load they behave nothing alike. Five tests show the difference:
- Acknowledgment becomes a record, not a report.
- A survey and its follow-up share one audience, defined once.
- A new hire is provisioned once, from one record.
- A translated message is the same message, so a correction reaches every language.
- Governance and AI read from the same library, so the engine that flags a stale policy page and the assistant answering questions about that policy look at one source.
Each of those is a sentence about architecture, and each shows up as something an employee can or cannot do on a Tuesday. That is why the platform decision comes first.
Where to start
Start with the capability area that closes your widest gap. The five areas build on each other because they share one data layer, so nobody has to start everywhere.
| Capability area | Gaps it closes | Start here if |
|---|---|---|
| The Front Door | Gaps 1 and 4 | A meaningful share of your workforce cannot be reached directly today |
| Communications | Gaps 1, 2, and 5 | Delivery broadly works, but you cannot target precisely, escalate a critical message, or prove what landed |
| Engagement and Listening | Gap 3 | You have reach and no return path |
| Knowledge and Answers | Gap 4 | Supervisors are acting as the help desk for questions that have documented answers |
| Governance, Security, and Proof | Gaps 5 and 6 | The immediate risk is content nobody owns, or work happening in channels you cannot produce in an audit |
The Front Door is the most common starting point, and every other area depends on it. Bring your score from the six-gap audit, because the widest gap on your own scorecard is a better guide than any vendor's preferred sequence. A frontline employee app that passes the first four requirements gives every later capability a whole workforce to measure, instead of the subset that happens to have a laptop.
Take the ten requirements into the vendor evaluation scorecard and score every vendor on your shortlist, including us.
Download the book for the detail behind each requirement, or see it configured for your sites.
The AI Platform for the Frontline Workforce.
Frequently asked questions
What features does a frontline employee app need?
A frontline employee app needs ten capabilities: reach without corporate identity, support for any device, offline access, translation at publish, precise targeting, delegated local publishing, a built-in return path, answers alongside the work of the shift, message-level acknowledgment, and a governed channel workers prefer. The first four decide whether a message arrives at all. The other six decide what happens after it does.
How do employees sign in to a company app without a corporate email address?
They are provisioned from the employee record, so a new hire gets in with no password and no corporate email. Site, role, shift, language, and audience membership follow from that one record. Single sign-on, multifactor authentication, and SCIM are supported where an organization already runs them, but none of them is required for a worker to be reached.
Does a frontline app need to work offline?
Yes, because a large share of frontline work happens where there is no reliable connection. Plant floors, cold storage, basements, delivery vehicles, and remote sites all qualify. Procedures and safety data have to open without a live signal, or they are not available when they are needed.
Why does translation need to happen at publish rather than afterwards?
Translation done afterwards arrives late and drifts from the original. When translation happens to the content itself at publish, every language exists the moment the message goes out, and a correction to the original reaches every version. Overrides keep safety language and brand terms fixed where machine translation is not appropriate.
What is delegated local publishing?
Delegated local publishing lets site and departmental leaders publish and maintain their own content inside a structure set centrally. It is the requirement buyers miss most often because it looks administrative. Without it, the channel carries only corporate content, and local teams stop reading it.
Who should administer an employee communication platform?
Communications and HR should run it day to day, while IT owns the identity perimeter. Audiences, templates, sites, and approval routing need to be configurable without a developer, or every change becomes a ticket. IT keeps control of sign-on and security policy.
Is a personal phone secure enough for company communication?
It can be, provided company content is protected separately from the rest of the phone. An app-level PIN and containerized company data keep content inside the app, and remote wipe means it does not leave with an employee who leaves. Kiosk mode on a shared device covers roles where a personal phone is impractical.
How is a frontline employee app different from a mobile intranet?
A mobile intranet is a desk experience rendered on a smaller screen, still reached through a sign-in built for a desk identity. A frontline employee app is designed first for the worker with no company email and a few minutes between tasks. The comparison of the two walks through where each one fits.
What should I ask a vendor to demonstrate?
Ask for things that test architecture rather than features. Have the vendor provision a new hire with no email in under five minutes, then open content in airplane mode and correct a published word in three languages. Next, have a site administrator publish locally without central help, and ask for the sites below target on a recent critical message.
The MangoApps Team
We're the product, research, and strategy team behind MangoApps — the unified frontline workforce management platform and employee communication and engagement suite trusted by organizations in healthcare, manufacturing, retail, hospitality, and the public sector to connect every employee — deskless or desk-based — to the people, tools, and information they need.
We write about enterprise AI for the workplace, internal communications, AI-powered intranets, workforce management, and the operating patterns behind highly engaged frontline teams. Our perspective is grounded in a decade of building for frontline-heavy industries and shipping AI agents, employee apps, and integrated HR workflows that real employees actually use.
For short-form takes, product news, and field notes from customer rollouts, follow Frontline Wire — our ongoing stream on AI, frontline work, and the modern digital workplace — or learn more about MangoApps.
