How to Get Field Crews to Actually Use a New App
Why crews ignore new apps, and a practical rollout plan: make it easier than the old way, train in the truck, pilot with two people, and stop accepting the old method.
Key Takeaways
- The app has to be easier than the old way for the crew, not just the office. Count taps. If logging a day takes longer than writing it on a card, expect cards.
- Give the crew something they want from it. Their own hours for the week, tomorrow’s jobs the night before, fewer 6 a.m. calls. If the only benefit goes to the office, adoption stalls.
- Pilot with two people before the whole company. One patient foreman finds what’s missing. One impatient crew member finds what’s slow.
- Train in their language, on their phone, on the clock. Training time that is required and job-related is generally paid time, and instructions only work in a language people understand.
- Stop accepting the old way on a set date. As long as texts and paper still work, the app is optional.
Quick-Start Prioritization Framework
| Week | Who uses it | Goal |
|---|---|---|
| Before launch | Owner, office, one foreman | Set up jobs, crews and the 3 actions crews need; fix anything that takes too many taps |
| Week 1–2 | One foreman and one crew member | Find missing fields and slow screens; old method still runs alongside |
| Week 3–4 | First full crew | Daily use; office answers everything through the app |
| Week 5+ | One more crew per week | Each crew gets a 15-minute start in the truck |
| Cutover date | Everyone | Old method no longer accepted for anything the app handles |
Most crew apps don’t fail because of the software. They fail on a Tuesday in week three, when a foreman texts a photo to the office instead of uploading it, the office accepts it, and everyone quietly goes back to the old way. Crews aren’t being difficult. They’re doing what anyone does with a tool that makes their day harder and someone else’s day easier. This guide covers why crews resist, how to pick and set up a tool they’ll accept, a week-by-week rollout plan, and the small decisions that make the habit stick. It applies whether you buy software or build your own.
Why crews ignore new apps
Before blaming the crew, look at the trade they’re being offered.
It adds work to their day
A paper timecard takes 30 seconds at the end of the day. An app that needs a login, a job search, three dropdowns and a confirmation screen takes three minutes in a truck with gloves on. The office saves an hour of retyping; the crew loses three minutes and gains nothing they can see.
They suspect it’s for watching them
Especially if the app has location features. If nobody explains what is collected and why, crews fill in the worst version themselves. Several states, including New Jersey and Connecticut, require written notice before certain kinds of tracking or electronic monitoring, so you have to tell them anyway. Do it before launch, plainly.
Phones, data and signal
Not everyone has a new phone, unlimited data or space for another app. Some sites have no signal. If the app assumes all three, it fails for exactly the people with the least patience for it.
Language and reading
A crew that reads Spanish best won’t learn an English-only app from an English-only video. Labels in the words the crew already uses, and in the language they read best, matter more than any feature.
Choosing and setting up a tool crews will accept
Adoption is decided mostly before launch, by what you choose and how you set it up.
Write down what it replaces
List every way crews communicate with the office today: timecards, texted photos, calls about tomorrow, receipts in the glovebox, the whiteboard. Decide which ones the app replaces in phase one. Usually that is hours, photos and tomorrow’s jobs. Everything else can wait.
Count taps for the three daily actions
For most crews the daily actions are: start time, add a photo, stop time with break. Open the app on a mid-range phone, outside, with work gloves, and count taps for each. Aim for two or three. If it’s eight, fix the setup or pick a different tool.
Show crews only what’s theirs
A home screen with every job in the company is overwhelming and leaks information crews don’t need. Each person should see today’s jobs and their own hours. Foremen see their crew. The office sees everything.
Ask a foreman before you buy
Have your most respected foreman try the shortlisted tool for a day. If they hate it, the crew will too, and you’ve learned that for the price of a trial.
A worked comparison: the old way versus the app
Here is what a day looks like for a foreman with a three-person crew, before and after, with times that are rough examples, not measurements.
| Task | Old way | With a well set-up app |
|---|---|---|
| Find out tomorrow’s jobs | Call or text the office at night, or wait for a 6 a.m. text | Jobs appear the night before; one notification |
| Log crew hours | Write three timecards on Friday from memory | Tap start and stop for the crew each day; about a minute |
| Send photos | Text 15 photos to the office; office files them | Take photos from the job card; filed automatically |
| Report a problem | Call the office, explain, call back with photos | Pick a reason, add a photo, send |
| Check own hours | Ask the office | Open the app |
Lead with what the crew gains
Notice the rows that help the crew directly: knowing tomorrow’s plan the night before, not rebuilding the week’s hours on Friday, seeing their own hours. Lead with those when you introduce the app. “You’ll get tomorrow’s jobs by 5 and you can check your hours any time” lands better than “the office needs cleaner data.”
Training that works for crews
Crews don’t need a webinar. They need someone to sit in the truck with them for 15 minutes and do a real day’s actions on their own phone.
On their phone, on a real job
Install it together. Log in together. Clock in on today’s real job, take a real photo, clock out. People remember what they did with their own hands, not what they watched.
In a language they understand
For safety training, OSHA’s 2010 Training Standards Policy Statement says required training must be presented in a manner employees can understand, which includes language and vocabulary. An app isn’t a safety standard, but the principle carries over: if the crew can’t read the instructions, they weren’t trained.
Pay for the time
The Department of Labor’s Fact Sheet 22 says training counts as hours worked unless it is outside normal hours, voluntary, not job-related, and no other work is done, all four together. Required training on the tool crews use to log their time fails that test, so it’s paid. Do it during the workday.
A one-page cheat sheet
Three pictures: how to start, how to add a photo, how to stop. Tape it in the truck. Put the office number on it.
Rolling out crew by crew
Launching to every crew on the same Monday guarantees that every problem hits everyone at once and the office drowns in calls.
Two-person pilot
Start with one foreman who is patient and respected, and one crew member who is quick to complain. Run the app alongside the old method for one or two weeks. Fix what they find every day. You want the complaints now, from two people, not later from twenty.
First full crew
Move the pilot foreman’s whole crew onto the app. From this point the office answers that crew only through the app. If they text a photo, the office replies “please add it on the job.”
One crew a week
Add a crew each week. Have the pilot foreman help with the 15-minute start in the truck. Crews trust another foreman more than they trust the office.
Pick a cutover date
Announce it two weeks ahead: after this date, paper timecards and texted photos aren’t accepted for anything the app handles. Then keep to it. The first time someone’s paper timecard is accepted after the cutover, the app becomes optional again.
Making the habit stick
Prosci’s ADKAR model describes individual change in five steps: awareness of why, desire to take part, knowledge of how, ability to do it day to day, and reinforcement so people don’t slide back. Most rollouts cover knowledge with a training session and skip the rest. The parts below are the reinforcement.
The office has to use it too
If the office still sends tomorrow’s jobs by text, crews will look at texts. Every schedule change, note and question to a crew goes through the app.
Respond to what crews submit
When a foreman reports a problem in the app, answer in the app the same day. When photos come in, occasionally say they were useful. Silence teaches people that nobody reads it.
Measure a few things
Track three numbers weekly by crew: share of workdays with hours submitted the same day, share of jobs with before and after photos, and number of problems reported through the app instead of by phone. They tell you which crew needs a visit.
Fix the small annoyances fast
A field that’s always irrelevant, a list that’s in the wrong order, a button that’s too small. Each one is minor; together they’re why people stop. Ask foremen monthly what annoys them and fix the top one.
Phones, data and dead zones
Decide the device question before launch, not after the first complaint.
- Company phones avoid personal-device questions but cost money and get lost. Personal phones are cheaper; some businesses pay a monthly stipend, and you should check whether your state requires reimbursing employees for work use of personal devices.
- Test the app on the oldest phone in the crew, not the newest.
- Find out whether the tool you choose documents offline use. If it doesn’t, set a simple rule for dead zones, such as logging from the truck before leaving the site.
- If the app collects location, give the written notice your state requires before anyone installs it.
Common mistakes
These are the patterns behind most abandoned crew apps.
- Choosing the tool without letting a foreman try it.
- Setting it up with every feature on, so the crew screen is crowded.
- Training once in the shop and never again.
- Launching to every crew the same day.
- Accepting the old method after the cutover date.
- The office still texting schedules and changes.
- Never responding to what crews submit.
- Not explaining what is tracked, especially location.
- English-only labels for crews who read another language best.
If the tool is the problem
Sometimes crews resist because the product really doesn’t fit how they work: the wrong words, too many steps, fields that don’t apply. If you’d rather shape the app to your crews than the other way around, Floot can build one from a plain-English description, with your job types, your words and only the three or four actions your crews need. It’s free to start.
Frequently Asked Questions
Why won’t my crew use the new app?
Usually because it adds work to their day and the benefit goes to the office. Count the taps for their daily actions, give them something they want from it, such as tomorrow’s jobs and their own hours, and stop accepting the old method on a set date.
How long does it take crews to adopt a new app?
It varies, but a staged rollout with a two-person pilot, then one crew at a time, typically runs over several weeks. Set a cutover date only once the pilot crew is using it daily.
Should I pay employees for time spent learning a new app?
Required, job-related training during or outside work hours is generally hours worked under the federal FLSA. The Department of Labor says training is unpaid only if it is outside normal hours, voluntary, not job-related and no other work is done.
Can I require employees to use their personal phones?
Many businesses do, but think about cost, privacy and data. Some pay a monthly stipend, and some states require reimbursing work use of personal devices. If the app collects location, check your state’s notice rules first.
How do I train crews who don’t speak English well?
Use labels and a cheat sheet in the language they read best, train one-on-one on their own phone, and pair them with a bilingual foreman. OSHA’s policy for safety training is that it must be presented in a language and vocabulary employees understand, and the same principle applies to any tool.
What if crews still text photos to the office?
Reply asking them to add it on the job in the app, every time, starting with the first crew on the app. Once the office stops accepting texts for things the app handles, the habit shifts.
Sources
- Prosci, The Prosci ADKAR Model https://www.prosci.com/methodology/adkar
- OSHA, Training Standards Policy Statement, April 28, 2010 https://www.osha.gov/laws-regs/standardinterpretations/2010-04-28
- U.S. Department of Labor, Fact Sheet #22: Hours Worked under the FLSA, 2008 https://www.dol.gov/agencies/whd/fact-sheets/22-flsa-hours-worked
- Connecticut General Assembly, Public Act 26-73, An Act Concerning the Electronic Surveillance of Employees, 2026 https://prdext3.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00073-R00SB-00472-PA.PDF
- Jackson Lewis, New Jersey: Notice to Employees Required Before Using Tracking Devices on Vehicles, 2022 https://www.jacksonlewis.com/insights/new-jersey-notice-employees-required-using-tracking-devices-vehicles-used-employees