Monday morning. She opens the dashboard on her laptop and checks the entries from the past few days. Nine workers. Three entries.

Marie-Ève picks up the phone. Her foreman answers on the second ring.

"The guys didn't really figure out the clock-in thing," he says. "I'll get them to do it this morning."

Two weeks in. Same call as last Monday.

The real reasons adoption stalls

The easy explanation is resistance — people don't like change. And sometimes that's true. But on most construction sites, the blockers are practical, not attitudinal.

What actually stalls adoption:

Cell coverage. On rural sites, or inside certain structures, there's no reliable signal at end of shift. The app won't load. The worker shrugs and drives home. That's not resistance — that's a dead connection.
First-use friction. Creating an account, finding the right project, choosing the right occupation code — the first time someone does all that standing next to a running generator at 5 PM on a Friday, it doesn't go well. That moment shapes how they feel about the tool going forward.
The foreman habit. If hours have always been collected by one person, that reflex doesn't disappear because you bought a subscription. The crew hands it off. The foreman enters it. You didn't actually save any time.

The result: the system is live, the accounts are created, but everything still flows through one person. The foreman is doing data entry every evening. The owner is puzzled. Nobody got what they expected.

What to sort out before you go live

Rollouts that stick don't start on launch day. They start a week or two before.

Put one person in charge on site. Not a group email, not a training session with fifteen people in a lunch room. One person — your foreman, your lead hand — who understands the app well enough to answer questions in real conditions on the site. That person is your bridge. Train them first, thoroughly.

Run a dry week. Before you go live, enter a full week of fake data. You'll find the misconfigured occupation codes, the projects that don't exist in the system yet, the devices that won't sync. Much better to catch those problems with dummy data than with a real payroll cycle.

Plan for no-signal days. On some sites it's unavoidable. Check whether the app has an offline mode that queues entries and syncs when connectivity returns. If it doesn't, have a paper backup process for the exceptions. Knowing this in advance means you're not improvising the first time it happens.

The first two weeks are where it's won or lost

The old habit doesn't vanish because there's a new app on everyone's phone. It gets replaced over a few weeks — and those weeks need some active attention.

Check entries every evening for the first two weeks. Not to micromanage — to catch the gaps before they become patterns. Someone who forgets to clock out on Monday, with no feedback until Friday, is going to keep forgetting to clock out. A quick look in the evening catches it before it compounds.

Make corrections easy. There will be errors in the first few weeks: wrong project code, missed punch-out, double entry. If fixing an error takes ten minutes and a phone call, nobody will report mistakes. The correction needs to take thirty seconds and be something anyone can do themselves without going through the foreman.

Keep human review in place. Your foreman should still look over the entries before you submit, at least for the first two or three weeks. It keeps a safety net in place and surfaces any configuration problems that slipped through the dry run.

If it's still broken after a month

Four weeks in, if two or three people are still handing their hours to the foreman, there's almost always a specific reason to find.

Data plan. No mobile data means no app, full stop. Some contractors reimburse a flat monthly amount for their crew's data usage. It's a small cost compared to what you lose in foreman time and entry errors.

Interface language. If the app is English-only and the crew is more comfortable in French, that's a real barrier. Check the language settings — most tools have them.

Fear of getting it wrong. Some workers would rather hand a number to someone else than enter something incorrect themselves. The message has to be clear: mistakes in the app get corrected. Nothing is permanent. Showing someone how to fix an error once is usually enough.

The contractor in our case study ran 18 employees across three active sites. Adoption wasn't instant, but it happened — because they took time to configure the occupation codes correctly and ran a dry week before going live for real.

If you want to see how that looks for a team like yours, Heuro's features are here. Or take 20 minutes with us if you'd rather talk it through first.

Key takeaways

Adoption stalls are almost always logistical, not attitudinal — find the specific blocker
Run a dry week with fake data before you go live, and plan for no-signal days from the start
Train one person thoroughly on site rather than sending a guide to everyone
Check entries every evening for the first two weeks to catch gaps before they become habits
If it's still broken after a month, look for a concrete cause: data plan, language settings, or a configuration problem