Problem guide
The people doing the work won't use the new system
People drop a new system when it costs them time at the end of a task for information that mostly helps the office, or when it fails where they work. The limits are often documented: Housecall Pro's app does not support editing without signal, and Jobber says a note still waiting to sync is lost if the app is force closed. In construction, a Procore-sponsored FMI study found 34% of contractors named 'not adopted by everyone' as a top technology challenge.

How it actually happens
Most rollouts follow the same path. As an example, take a contractor with a dozen technicians that buys a field service system to replace paper tickets and a whiteboard. The owner and the office manager sit through the demo. The office configures it: price book, job types, required forms, the closeout checklist, the accounting connection. Every setting is chosen by someone who will read the records, not by someone who will create them. A clinic choosing a new charting tool, or a warehouse choosing new scanners, makes the same choice the same way.
Go-live is on a Monday. The office sees the board fill with jobs and likes what it sees. In the field, the first week is mostly fine on routine calls. Then the edge cases arrive. A technician in a basement mechanical room has no signal. Depending on the app, he can work offline with some limits, or he cannot edit the job at all until he walks back out. If the office chose dynamic pricing, the price does not show offline, so he cannot quote the repair in front of the customer. He writes it on the back of the old paper ticket.
Closeout is the second pressure point. The office made a form required, then a signature, then equipment details. Each was reasonable on its own. Together, closing a ten-minute task takes several minutes of tapping while the next customer waits. Some work gets closed at the end of the day from memory, some the next morning, and some stays open until the office calls.
The third is trust. A note entered offline did not sync before the app updated overnight and is gone. The technician entered his parts, and the office changed them anyway because the item was mapped wrong in the price book. After a few of those, careful entry stops looking worth it.
By the end of the first month the office manager is typing photos of paper forms into the new system herself. The board looks full. Leadership believes the system is working. The people doing the work have quietly opted out, and nobody decided that on purpose. Each person made a reasonable choice given the screen in front of them.
What real adoption looks like in the records
Logins measure nothing useful. The number that matters is the share of completed work where the person who did it entered what the office needs, on the same day, without anyone retyping it. That number moves only when the system gets easier than the workaround at the moment of use: at the end of the task, often in a bad spot, sometimes with a customer watching. Construction surveys point the same way. The obstacles contractors report are adoption and ease of use, not whether the crew owns a smartphone.
Signs you have this problem
- People still hand in paper, texts, sticky notes or photos after the system went live
- The office types frontline information into the new system on their behalf
- Staff say they entered something and it is not there
- Jobs, orders or visits stay open for days because something required at closeout is missing
- The company now keeps two partial records instead of one complete one
What usually causes it
- The system was set up for the office, so the people doing the work do extra entry that helps someone elseThe field-to-office split
- Whatever frontline staff enter gets corrected or retyped by the office anyway, so careful entry feels pointlessThe re-entry trap
- Warranty work, rush orders, multi-day work and other odd cases do not fit the screens, so people fall back to paper for anything unusualThe exception swamp
- Office settings for pricing, required forms and permissions were never tested by anyone doing the work, and nobody owns changing themThe handoff gap
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Do people fall back to paper mostly in certain places, such as weak signal, a busy line or a crowded floor?If yes: the conditions are the cause, not attitude. Run the test where the work happens and change what you can, such as the pricing mode or where the device sits.
- Does closing a task in the system take longer than the old paper form did?If yes: closeout asks too much. Count the required items and cut the ones nobody in the office uses.
- Does the office routinely fix or retype what frontline staff enter?If yes: people have learned their entry does not count. Stop correcting silently; show them what was wrong and why it mattered.
- Do routine tasks go in the system while warranty, rush, multi-day or otherwise odd ones go on paper?If yes: the screens do not fit the odd cases. Map those types before asking for more.
- Were required forms, pricing and permissions set without anyone who does the work testing them?If yes: the friction is in setup. Review the settings with someone who closes the work every day.
How it breaks in each industry
- HVAC and refrigeration service
- The work happens in basements, mechanical rooms and on rooftops where signal drops. Closeout can require equipment details, forms and a signature, and if the office prices services dynamically, the technician offline sees no price at all.
- Residential plumbing and home services
- Small crews run on Jobber or Housecall Pro on their own phones. When the app cannot save offline, or loses a note that had not synced, the paper ticket in the truck becomes the record again.
- Logistics and third-party warehousing
- Pickers and receivers are asked to scan every move, but an exception such as a damaged carton, a short case or a mislabeled pallet has no quick screen. The exception goes on a sticky note or a shout to the lead, and the warehouse system ends up wrong in exactly the cases that matter.
- Healthcare practices and clinics
- Clinical staff are asked to document in screens built for billing and compliance, between patients. Notes get written on paper or finished at the end of the day, and front desk staff re-enter details the clinical team already said out loud.
Where it breaks between systems
- ServiceTitan Field Mobile App (offline)
- Offline, a technician can still take notes, add photos, fill forms, add equipment and invoice items, and close the job. Dynamic Pricing does not show without a connection, while Static Pricing does, and automated timesheets are not displayed until the phone reconnects.[1]
- ServiceTitan closeout
- A job cannot be completed while a required form is unfilled, required signatures are missing, required equipment details are blank, or work is still to be scheduled on a sold estimate. Each requirement is an office setting that the technician meets at the end of the visit.[2]
- ServiceTitan and QuickBooks Online (setup)
- Mapping pricebook items to QuickBooks general ledger accounts is an onboarding step for administrators, office employees, managers, accountants and bookkeepers, not technicians. If the setup is wrong, fixing the crew's entries cannot fix the numbers.[3]
- Jobber app (timers)
- Jobber's help center says timers run with no connection, but geofenced location timers do not, and past time entries and weekly totals will not load offline.[4]
- Jobber app (notes)
- A note added offline is stored only on that phone, and teammates cannot see it until it syncs. Jobber's help center says a note waiting to sync is lost if the app is logged out, deleted, force closed or updated; the app's Sync Queue shows what is pending.[5]
- Housecall Pro app (offline)
- Jobs are the only part of the app that stores data, editing without cell service or WiFi is not supported, and a job not already stored on the phone shows an error. A crew without signal has no way to record the work in the app.[6]
- Procore and Sage 300 CRE (field entry)
- New cost codes must be created in the accounting system and cannot be created in Procore, and Procore does not sync production quantities to Sage. A foreman's installed quantities stay in Procore, and a missing code has to be added on the accounting side first.[7]
By the numbers
| Figure | What it measures |
|---|---|
| 34%, 17% and 16%[8] | Top challenges contractors reported with construction technology: it was not adopted by everyone (34%), it was not easy to use (17%), it did not integrate (16%). FMI 2020 Industry Report, a study sponsored by Procore. |
| 25%, 22% and 20%[8] | Top reasons for dissatisfaction with technology vendors' solutions in the same FMI study: lack of integration, difficult to use, and poor mobile accessibility. |
| 23% and 33%[9] | Specialty contractors still doing timekeeping (23%) and daily logs and progress tracking (33%) with mostly manual methods. Dodge Data and Analytics, 2022, 537 firms across the US, Canada, the UK and Australia and New Zealand, sponsored by Procore; self-reported four-region average. |
| 92%[11] | Construction respondents who use a smartphone every day at work, in JBKnowledge's 2020 ConTech report as covered by Construction Dive (January 2021). The phone is rarely the barrier; what the app asks of the person holding it is. |
Rules that apply
- 29 CFR 516.2(a)(7) and 516.1(a), FLSA hours records[12]
- Employers must keep hours worked each workday and total hours each workweek for non-exempt employees covered by the minimum wage and overtime rules. No particular form is prescribed. If the crew stops clocking in the app, the duty to keep the record does not stop with them; paper is allowed, but a record has to exist.
Measure it in your own shop
From: Completed jobs, orders or visits from your system for the last four weeks, with completion time and who entered the notes, time and items, plus the paper forms, texts and photos the office received for the same work.
- List each person's completed work for the last four weeks.
- Mark each item as complete in the system by that person on the day, entered late, entered by the office, or paper only.
- For every item not complete in the system on the day, note the likely reason: no signal, an unusual case, a missing permission, or a customer waiting.
- Plot the weekly share of work complete in the system on the day, by person.
Reading it: That share is your real adoption rate, not the login count. The reason tags tell you which fix to make first: connectivity, closeout length, cases the screens do not fit, or settings. A person far below the others usually has a specific blocker worth asking about.
What does not fix it
- Making it mandatory
- A mandate raises logins and minimum entries, not complete records. The office still cleans up, and the crew learns the system is something done to them.
- More training
- Training fixes not knowing how. It does not fix an app that cannot edit without signal, a price that does not show offline, or a permission the technician does not have.
- Switching to a different system
- Each app has its own offline limits and closeout rules, and an office-first setup gets rebuilt in the new one. The causes come along unless the setup changes.
- Having the office enter it for them
- The system fills up and looks adopted, while the crew has quietly opted out and the office carries two jobs.
What to try this week
- Spend a full day beside the workSpend a day with one person or team and note every moment they would use the system: where they stand, whether they have signal or a free hand, whether gloves are on, whether a customer or patient is waiting. The conditions explain more than the complaints.
- Test the system where the work happensOpen a record in the worst spot: a basement, a walk-in cooler, the back of a warehouse, an exam room on shaky Wi-Fi. Add a note, an item and a photo, and close it. Then reconnect and check what actually reached the office. Write down what failed.
- Count what closeout asks forList every required form, signature, field and tap between starting and closing a task. Mark which ones the office actually uses. Everything unused is cost to the people doing the work with no return.
- Check the office settings that land on the front lineReview pricing, required forms and permissions with someone who closes the work every day. Many frontline complaints trace to a setting the office chose and can change.
- Cut the ask to one taskPick the one entry the office needs most, such as hours worked, parts or items used, or the outcome of the visit, and make that the only thing you ask for until it is reliable. Add the next one after.
Where do-it-yourself stops
These steps show why people avoid the system and shrink what it asks of them. They do not change the fact that most systems are set up around the office's records rather than the frontline work, or remove the limits built into each app. The lasting fix is a tool shaped around how your people already work, for one task, whose output lands in your office systems in the right shape without retyping. That is what a Workflow Spec designs.
Questions people ask
Why won't our crew use the new system?
Usually because it costs them time at the worst moment, at the end of a job with the next one waiting, and the benefit lands in the office. Where signal is weak, the app may also fail them outright.
Should we just make it mandatory?
A mandate gets minimum compliance. Fix what makes the app slower than paper first, then require the one entry that matters most.
Why do technicians say they entered something and it disappeared?
Sometimes they are right. Jobber says a note that has not synced is lost if the app is force closed, logged out or updated, and Housecall Pro does not support editing a job without a connection. Check the sync queue before assuming they skipped it.
Is resistance from the field common?
Yes. In FMI's 2020 report, sponsored by Procore, not being adopted by everyone was the most named challenge with construction technology, and Dodge's 2022 specialty contractor report listed resistance from field staff among the top obstacles to adoption.
Do we still need time records if the crew stops using the app?
Yes. Federal wage and hour rules require daily and weekly hours for non-exempt employees in any form. If the app is not the record, paper or a spreadsheet has to be.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
