5 signs your field team outgrew WhatsApp and spreadsheets

WhatsApp and a shared spreadsheet got the first jobs out the door. They are free and everyone already has them. Then the crew grows, the jobs overlap, and the record lives in five threads and a file nobody trusts.

That is not a discipline problem. It is a system that was never built to be the system of record.

1. The photo you need is 200 messages back

The group chat is three jobs at once. The panel photo sits between a parts ETA and a joke. A week later nobody can find it, and the camera roll is worse — no project, no author, no time anyone will defend.

Photos and video land on the project with time, location, and author. Annotate the defect on the image so the finding is still unambiguous six months later. Capture still works offline, then syncs. The gallery is not the record. The project is.

2. Job status lives in someone's head

Is it done? Waiting on a part? Still planned? The answer is a voice note or a message that scrolled off. A new person on the crew has to ask.

Create the project for the site. Break the visit into work orders with status, an assignee, and a due date. Overdue and due-soon work shows in the bell. Team activity on Overview shows photos, work-order updates, and checklists that just closed. That is the same project record — not a live chat view.

3. Readings sit in a sheet; the report is rebuilt at night

Field work ends and the paperwork starts: copy photos, retype readings, format a document from scratch. The sheet is a second system. The PDF is a third.

Pair a Minipa instrument and save Bluetooth readings on the asset. The report is an export of the project — cover, photos, checklist results, the nonconformities table — not a rewrite. If you talk while you shoot, those captions stay on the photos and flow into the same document. A person still reviews and signs.

4. Everyone runs a different list

The official checklist is a printout in the van, a photo of a clipboard, and a column in the sheet. New hires ask a colleague which one is current.

Publish the checklist once. Require a photo on the critical steps. The same version goes to every person on the job. If the list already exists on paper, in a PDF, or in a spreadsheet, From paper or PDF to a team template. Work style is web-only (Admin → Work style); you Accept the template. Linky does not publish for you.

5. A dispute is your word against the client's

Without a timestamped trail, a disagreement is a conversation. Time, author, and GPS on the capture are what you can point to. A nonconformity that lived in the chat is gone.

Flag the NC on the checklist item, with severity and a photo — not in a thread. It stays on the project until someone closes it. The audit log on the web keeps who, when, and where.

What replaces the thread

The same stack as One project, any procedure: project, work orders, assets when the job is equipment, the published checklist, evidence on the item, the trail. That process still sits under ISO 9001, ISO 45001, and NR-10 — Minipa Link does not certify you.

Linky can read that same record when it is on for the team. Ask what is still open. Answers stay on the photos, checklists, measurements, and findings already on this job. A person still reviews and signs.

Create your account and run the next visit as the record. See pricing when you are ready to put the whole crew on it.