The best subcontractor software in the world is useless if operatives keep texting photos to the office and filling in paper sheets. Most failed rollouts don't fail because the app is hard; they fail because nothing else changed. Here's a rollout plan that works on real sites.
Why do operatives push back?
| Objection | What's really behind it | Answer |
|---|---|---|
| "I haven't got time" | It looks like extra admin | Replace the paper sheet, don't add to it |
| "It won't work on site" | No signal in the plot | Use an app that works offline and syncs later |
| "The office will use it against us" | Fear of being monitored | Use it to get them paid faster and correctly |
| "I'll forget my password" | Logins are a pain | Face ID or fingerprint login |
| "Nobody looks at it anyway" | Past systems went nowhere | The office approves submissions quickly and visibly |
What is a good rollout plan?
1. Start with one site and one job. Work submissions are the best first step, because they're tied to pay. Tasks, drawings and orders can follow.
2. Remove what it replaces. If the paper sheet still works, people will use it. Set a date after which only app submissions are paid.
3. Train on site, in short sessions. Ten minutes at the van with a real plot beats an hour in the office. Show them their own tasks.
4. Make the office fast. Approve or reject submissions within a day or two, with a reason when rejecting. Operatives see the totals move in their app; that builds trust.
5. Use gang leaders. Let a gang leader submit for the gang at first, with the payment split recorded, then bring individuals on.
6. Add tasks and drawings next. Once submissions are routine, move tasks and site messages off WhatsApp and onto the task, and put drawings in the app so nobody uses old revisions.
A worked example
Fictional example. A plastering subcontractor rolls out the app on one 80-plot site. Week 1: gang leaders submit work for their gangs; the office approves within 24 hours. Week 3: paper sheets stop being accepted on that site. Week 5: tasks and drawings go live. By the next month the second site starts at week 3, because the gang leaders who moved over already know it.
What makes an app easy for operatives?
- Native app on the phone they already carry
- Face ID login
- Works offline, syncs when the signal returns
- Shows only what they need for their role
- Totals visible: approved, pending, rejected and submitted
- Push notifications when the office replies
Where SubbieNow fits
SubbieNow's native iOS app has Face ID login, offline-tolerant site information, tasks with a messenger, work submissions with live totals and payment splits, and orders from site. See mobile app synchronisation for how offline working is handled, or the features page.
Onboarding and training are included in the subscription. Book a demo and we'll plan a rollout around your first site.
Frequently asked questions
What should operatives use the app for first?
Work submissions, because it ties directly to how they get paid. Tasks, drawings and orders follow once they trust it.
What if an operative doesn't have a smartphone?
Usually a gang leader submits for the gang, with payment splits recorded on each submission, until everyone is set up.
How long does rollout take?
For most subcontractors, one site for a few weeks, then the rest in stages. The office side and the first application cycle matter more than the app training itself.
