Getting a team of operatives who have never used a work app to actually use one is a change management job, not an IT job. Here is the order to do it in, and what to say when someone tells you they “don’t do apps”.
7 min read · Updated July 2026
Onboarding cleaners onto a mobile app goes wrong for a predictable reason: it is announced as a policy rather than shown as something that makes their day easier. Done well, it takes a handful of operatives about a week to go from “never installed a work app in their life” to clocking in, ticking off a checklist and uploading a photo without a second thought. This guide covers why cleaners push back in the first place, how to send invites that get opened, what a smooth first clock-in looks like, and what to do about the phone-averse and shared-device shifts that every cleaning company runs into somewhere.
Most resistance is not really about the app. It is about being handed something new with no explanation of what problem it solves for the person using it, on top of a job that already involves enough to remember. An operative who has spent years phoning the office to find out where they are working tomorrow has no reason to trust that a new screen will make that easier, until it visibly does.
The fix is to lead with what changes for them, not what changes for the office. Today and next shifts on one home screen, clock in and out without a phone call, a checklist instead of trying to remember what “General Clean” covers at that site, and a message thread to the office instead of a missed call. Roll it out with one or two operatives first, let them use the cleaner app on a real shift, and the rest of the team hears that it worked from a colleague rather than from a memo.
Each operative needs a team member record before they can be invited, so the app already knows their name, role and which bookings belong to them the moment they log in. Once the record exists, sending the app invitation is a single action against it, and the invite goes to the phone number or email you already hold, so there is no separate signup form for them to fill in from scratch.
Invite in small batches rather than the whole team on a Monday morning. Five or six operatives at a time means the first round of “how do I clock in” questions gets answered before the next batch hits the same question, and any confusion never has more than a handful of people stuck on it at once.
The first clock-in is the moment an operative decides whether the app is worth the bother, so it is worth watching over someone's shoulder for their first one rather than trusting a written guide. They open the app, see today's and next shifts on the Home screen, and tap to clock in, which captures the time and location automatically. No typing, no separate sign-in sheet at the site.
From clock-in, the app is already showing them what is next rather than leaving them to remember it. Pair that first clock-in with a quick look at the schedule tab too, so they see straight away that the shifts on their phone match what they were told, which does more to build trust than any explanation. If the rota itself still lives on a spreadsheet or a phone tree behind the scenes, this is also the natural point to move it onto proper rota software, so the shifts operatives see on their phone are the same ones being planned on the office side.
Once clock-in feels normal, the checklist is the next habit to build. Rather than explaining every field in one go, let the operative tick items off as they go through the job, the way most people already work through a mental list. A handful of photos against the parts of the job that matter, such as a washroom or reception area, get uploaded from the phone as part of finishing the booking, not as a separate step afterwards.
This matters for onboarding because it is the point where operatives sometimes feel watched rather than supported. Framing checklists and photos as their record too, evidence that protects them if a client ever questions whether a job was done, tends to land better than framing it purely as a management tool.
Every rollout has one or two operatives who genuinely dislike using a phone for work, and pushing hardest on them first is a mistake. Onboard your more willing operatives first, let the phone-averse ones watch a colleague use it without friction for a couple of weeks, and revisit it once it has stopped looking like extra hassle and started looking like normal practice.
Where a device is genuinely shared between shifts, such as a van phone used by whoever is on site that day, the fix is simple, log out before handing it over and log back in with the next operative's own details. Because clock-ins, checklists and photos are attached to whoever is signed in at the time, the record stays accurate as long as the login changes with the person, even if the handset does not.
Where a supervisor is the more comfortable app user on a team, letting them clock a job in and out on behalf of someone who does not yet have a device is a reasonable bridge, provided it is logged clearly against the right operative rather than left ambiguous.
By the end of week one, a good sign is not that every feature is being used, it is that clocking in and completing a checklist has stopped needing a reminder. Most operatives get there within a handful of shifts once they have done it once with someone next to them. Holiday requests, messaging the office and the rest of the app tend to follow naturally as those situations come up rather than needing a separate training session.
One habit worth building early is using in-app messages instead of texts and phone calls for anything work-related, so a query about a missed key or a late start is attached to the record rather than sitting in someone's personal phone. Moving that traffic onto proper team communication is a small change that saves the office from chasing information across three different channels later. If you want to see the full operative experience before rolling it out to the team, the mobile app covers what admins, operatives and clients each see once everyone is onboarded.
Straight answers to the questions cleaning companies ask when rolling out a mobile app to their team.
Start small and make the app solve a problem they already have, such as not knowing their shift until someone rings them. Send one invite, sit with that person for their first clock-in, and let the rest of the team hear it worked from a colleague rather than from a memo. Peer proof beats a company-wide announcement every time.
Add each operative as a team member first, then send the app invitation from their record so login details go straight to the phone number or email you already hold for them. Invite in small batches rather than the whole team at once, so early questions get answered before they spread.
Most operatives already carry a smartphone for personal use, so the gap is usually smaller than expected. Where someone genuinely does not have one, a supervisor can clock a job in and out on their behalf and note it against that operative, and it is worth having this fallback agreed before day one rather than working it out on the spot.
Yes, as long as whoever is on shift logs out and the next operative logs in with their own details before clocking in. Sharing a device works, sharing a login does not, because clock-ins, checklists and photos are all tied to the operative who is signed in at the time.
Most teams are clocking in and completing checklists confidently within a week, once the first few operatives have used it on a real shift. Full comfort with every feature, such as requesting holiday or messaging the office, tends to follow over the following few weeks as those situations naturally come up.
Today's shifts, clock in with GPS, checklist and photo proof, all in one place. Start your 90-day free trial of everything. No credit card, cancel any time.