From paper job sheets to a phone app
What changes when a trades business moves from paper job sheets to a phone app, including how the app copes with no signal.
·
4 min read
When WhatsApp is running your jobs, the job board is a group chat, and the only record of who's doing what sits on a handful of personal phones. A proper ops system moves the job itself (address, status, owner, notes, photos) into one shared record. Your team still uses their phones; they just stop using a chat thread as the database.
It happens without anyone deciding it. The office posts new work in the team group and someone replies to claim it. Addresses arrive as screenshots. The scope of work is a voice note recorded between jobs. Before long, the group holds the diary and half the customer history.
And for a while it works. People already have the app, nobody needs training, and replies come back fast. The trouble is that a chat is ordered by time, not by job. Ask "what's still open from last month?" and the honest answer is a long scroll.
These are the failures that show up once a team grows past a few people:
The quiet one is staff turnover. When an engineer leaves, their phone leaves with them, and so do the photos and private chats with customers. The business never owned that history. We've written separately about quotes and invoices stuck in email and the info@ inbox nobody owns; WhatsApp is the same problem with a faster scroll.
It doesn't replace the phone. It replaces the group chat as the place where the truth lives. In practice that means a job record with a status, a named owner and the customer's details attached, so the address is entered once and carried through.
In TradeOps, our own product for trade and service businesses, an accepted quote becomes a job with the customer and quoted lines carried across. The job holds the site address and access notes. The job sheet has a checklist, materials, photos tagged before, during, after or issue, and notes. Statuses run from draft and scheduled through to completed and signed off, and the customer can sign on the device on site. The invoice is raised from the same record. Roles decide which team members can see and change what.
So the engineer still opens a phone. They open the job instead of the group. TradeOps is a web app that runs on the phones and computers your team already has; there's no app-store download to roll out. The details are on the TradeOps jobs page.
Keep WhatsApp for quick conversation between colleagues. Just don't let a job exist only there.
One honest limitation. TradeOps isn't built for offline use, so if your engineers spend their day in basements or rural sites with no signal, a browser app will frustrate them. For that, we build custom Flutter apps for iOS and Android that work locally and sync later. We covered the trade-offs in from paper job sheets to a phone app, so I won't repeat them here. Custom work starts with a free scoping conversation and is quoted at a fixed price per agreed release, and you own the code and the cloud accounts it runs on.
If you're a one-person outfit, or two people doing a few jobs a week, a chat and a diary is a perfectly reasonable system. We'd advise against a disruptive move if your simple setup is working well.
The signs you've outgrown it are specific. You can't answer "which jobs are open?" without scrolling. Two people have turned up to the same job, or nobody has. You've had to ask a former employee for photos. Customers are getting quotes from one place and updates from another. If that sounds familiar, the question isn't whether to ban WhatsApp. It's when WhatsApp is running your jobs, what should be holding them instead.
TradeOps also puts your public website on the same system as your enquiries, so a contact form lands as a lead rather than another message to forward. If you only need the site, see our websites service.
My view: the phones were never the problem. The problem is a business whose memory lives in a chat it doesn't own. If your job board is a WhatsApp group and you'd like to see what moving it into one record would look like for your team, talk to an engineer.
What changes when a trades business moves from paper job sheets to a phone app, including how the app copes with no signal.
·
4 min read
CRM for a small firm off the shelf or built: when HubSpot-class tools fit, and when a system on your own job data serves trades and clinics better.
·
4 min read
If your website form still emails one person's Gmail, enquiries vanish when they're away, and a shared lead list with an owner fixes it.
·
4 min read
Quotes and invoices stuck in email fail as a system of record. Use one quote→job→invoice workflow with clear status instead.
·
3 min read
Why your AWS bill and your management fee are two different bills, what the fee should cover, and how to keep usage charges predictable.
·
4 min read
What managed AWS hosting includes, and what stays on you: patching, backups, monitoring, and the account, app, data and access decisions you still own.
·
4 min read
What to check before you inherit a custom app: code and deploy-key control, tests, patches, and whether a fix can ship tomorrow.
·
4 min read
What a website quote should include beyond the build: hosting, domain ownership, care and who fixes the site at 2am.
·
4 min read
When the office broadband dies and nobody has a backup, work stops. What fails, why a hotspot is not a plan and what tested failover looks like.
·
3 min read
The agency that built your website has disappeared. How to recover access, move hosting and DNS into the business, and choose care or a rebuild.
·
4 min read
Leaving a freelancer with your AWS root login is a risk even after a good build. How to take back control with named IAM, MFA and a handoff.
·
4 min read
Uptime monitoring for a small business website only works with a named engineer and response path. What a care plan or managed hosting should cover.
·
3 min read
Who actually owns your business domain name? How to check the registrant and account holder, and move both into company hands.
·
4 min read
What the NCSC's China-linked botnet alert means for a small business: check the router and remote access kit you already own.
·
4 min read
GDPR and cookies on a small business website: when cookies need consent under the 2026 rules, and how long to keep contact form data.
·
4 min read
The info@ inbox nobody owns is where a UK SME's enquiries sit with no named owner and no reply time.
·
4 min read
How to approach moving off Wix or Squarespace without losing your Google ranking, from exporting content to setting up 301 redirects.
·
4 min read
A plain-English guide to Cyber Essentials for small businesses, covering what the scheme checks and when a contract will ask for it.
·
4 min read
Why your quotes land in spam: SPF, DKIM and DMARC explained for business owners, and how to check your own domain with free tools.
·
3 min read
Offboarding staff from Microsoft 365 or Google Workspace, step by step: cut access, revoke devices, keep mail and files, and stop paying for the licence.
·
4 min read