When job details are scattered across chats, inboxes and spreadsheets

The short version#

• Scattered job details are rarely a discipline problem. Nobody has agreed where the current version of a job lives, so information stays wherever it landed.
• Give every job a reference that never changes, and use it in every message, file and invoice.
• Keep one record per job: a few fields, links to the evidence, what’s missing, and who’s doing what next, by when.
• Keep the group chat. Make it feed the record, the same day.

First step: give every open job a reference, an owner and a dated next action this week. Download the job record starter (.xlsx)

What it looks like#

It’s 7:40 on a Thursday and the question comes in again: what’s the access arrangement for the Ryde job? The strata manager emailed it. Or the site lead put it in the group chat. Or it’s in the spreadsheet, in the column called ‘Notes 2’.

Nothing is lost, exactly. Every detail is somewhere. But each channel holds a different piece, and the full picture lives in a few people’s heads. Usually including yours.

Signs it’s happening:

• The same question gets asked about the same job more than once.
• A decision was made in a chat, and nobody can find it when the invoice is queried.
• One job goes by three names: ‘Ryde’, ‘the Chen job’, ‘the leak at Example St’.

Why it happens#

Each channel is good at something, so information lands wherever it was sent and stays there. Three things turn that into a problem:

• No agreed current record. If nobody has said where the current version of a job lives, every channel is equally official.
• No single name. When a job is an address in one place and a customer’s name in another, you can’t search across channels.
• Moving information is nobody’s job. Someone has to carry a decision from a conversation into the record. If that isn’t anyone’s responsibility, it doesn’t happen.

So the owner, or one long-serving admin, becomes the search engine. That works until they’re on leave, the team grows, or they move on.

How to set it up#

Here’s the test for a good job record. Someone who wasn’t involved can answer five questions from it in under a minute:

1. What is this job, and what did we agree to do?
2. Where is it at right now?
3. What’s missing?
4. Who’s responsible for the next step, and by when?
5. Where’s the evidence: photos, documents, approvals?

1. Choose where the record lives

   Use what you already have. If you run job management software, the job in that system is probably the record; the work is making it complete, not replacing it. Otherwise a shared spreadsheet is a fine start. It needs to open on a phone, hold links, filter by status and owner, and be backed up.

   Don’t buy anything yet. A new system without an agreement just gives the scatter a new home.

2. Give every job a reference

   A short code that never changes, like J-2417, assigned when the job is booked. Put it at the start of chat messages, in email subjects, folder names and on the invoice. That one habit makes every channel searchable by job.

   Don’t build in things that change, like the address, and never reuse a reference. If your software already numbers jobs, use that number. Two numbering systems is one too many.

3. Agree the minimum fields

   A record with forty fields becomes a form nobody fills in. Start with these:

   Field	What it’s for
   Job reference	The key everything else hangs off.
   Customer and site	Who it’s for and where, plus the site contact if it’s someone else.
   Job type	Inspection, repair, delivery run, maintenance visit. Different types need different things later.
   Agreed scope	One or two sentences, and where the agreement is: quote, work order or email.
   Status	Where the job is at, from a short fixed list.
   Owner	The person responsible for the next action, not necessarily the one doing the work.
   Next action and due date	A verb, an object and a date. A next action without a date is a hope.
   Access and site notes	Parking, hazards, preferred times, who holds keys. Codes go somewhere secure, not here.
   Evidence	A link to the job’s folder.
   Missing items	What’s needed before the job can move on. Named, not blank.
   Last updated	When, and by whom.

   If a column stays empty for a month, ask what it’s for before removing it. Some fields are only needed for the occasional job, or as evidence when something is questioned.

4. Link the evidence and name what’s missing

   Give every job one folder, named with the reference first (‘J-2417 Ryde leak repair’), and link it from the record. Copying photos or emails into the record creates a second version that drifts. Save approvals, and anything the invoice depends on, into the folder deliberately.

   Then write down what’s actually missing: ‘Written approval for extra sealant, east side’, not a blank. Named items can be chased. Blanks can’t.

5. Give every open job an owner and a dated next action

   The owner makes the next step happen. They don’t have to do the work. Write the next action as something a person could do today (‘Call strata manager about access’, not ‘Access?’) and give it a date. A job with no next action is either finished or stuck, and the record should show which.

6. Let the chat feed the record

   Don’t ban the group chat. Agree how it relates to the record:

   • Start job messages with the reference: ‘J-2417: building manager has the key on Thursdays.’
   • Decisions that change scope, dates, access, cost or approvals go into the record the same day, entered by the job’s owner, with where they came from.
   • When the chat and the record disagree, don’t assume either is right. Check who made the change and whether they could approve it, then update the record and note where the change came from.
   • A thumbs-up in a group chat is a weak approval. If extra work matters for the invoice, get the approval in a form you can file.

7. Review open jobs every week

   Fifteen minutes, same time each week. Look for open jobs with no owner or next action, next actions that are overdue, and missing items older than a week. The first few reviews take longer. That’s where the gaps show up.

Worked example: one job, before and after#

Start this week#

Don’t try to fix every old job. Draw a line and start with what’s open.

1. Decide where the record lives, and tell the team.
2. Give every open job a reference.
3. From Monday, start job messages with the reference.
4. For each open job, fill in the owner, next action and due date. The rest can wait.
5. Book a fifteen-minute review for the same time next week.

Template: Job record starter#

When the spreadsheet stops being enough#

The spreadsheet is the right start. These are the signs it’s time to build more, and what that looks like:

1. Updates arrive from the field on phonesA short capture form (job reference, what changed, who said so, a photo) that adds to the record instead of the chat.
2. The same job lives in two systemsA connection between your job and accounting software, so references and statuses aren’t retyped.
3. Decisions arrive as messages and voice notesAn AI step that turns a forwarded message or voice note into a suggested update for the job’s owner to accept or reject. Nothing changes until a person agrees.
4. Next actions go overdue unnoticedReminders to the owner, and a weekly list of what’s stuck.

For whoever builds it

Setup notes#

Structure

• One row per job, keyed on the reference, stored as text so prefixes and leading zeros survive.
• Status is a fixed list and owner is a person. Free-text statuses can’t be filtered, and ‘Office’ as an owner usually means nobody.
• When jobs regularly have several missing items, give them their own table, linked by job reference, each with an owner and a date.
• Generate references in one place. If two systems number jobs, pick a master and store the other as a secondary reference.

Privacy and permissions

• Reading group chats automatically is fragile and raises privacy questions for everyone in the chat. A deliberate capture step is more reliable.
• Keep lockbox and alarm codes where only the people who need them can see them. When someone leaves, remove them from chats, folders and the record.

Checking it’s working

• For a week before you start, list every ‘where is…?’ question: what was asked, where the answer was, who found it. Count again a month later, and watch the age of the oldest missing item.

Where this goes wrong#

• Too many fields. If filling in the record feels like a tax, people stop.
• A new tool before an agreement. New software without agreed references, fields and owners just moves the scatter.
• One person maintains everything. Then you’ve moved the bottleneck, not removed it. Each job’s owner keeps that job current.
• The record drifts from reality. When people stop trusting it, they go back to asking. The weekly review is what keeps it honest.

Want it built into your business?#

You can do all of this with the template. Where I help is fitting it to how your jobs actually run: which tool holds the record, how references flow between your job and accounting systems, and getting field updates in without double handling.

Book a free 30-minute call How working together works