The group text audit: scroll your thread, count the lost decisions

You do not need anyone to tell you the group text is getting heavy. You feel it every morning. But feeling it and seeing it are different things, and until you count, it stays a nagging sense instead of a number you can act on.

So here is a small job for a slow evening. Open your crew thread. Scroll back two weeks. Read it top to bottom, the way a stranger would, and tally what got lost along the way. It takes fifteen minutes and it settles the argument for good, because the thread you already have is the evidence. This guide gives you the tally sheet and tells you what the score means. If you have already read up on where a group text breaks on a small crew, this is the part where you find out how far along yours is.

The five things to count

You are looking for five specific failures. Do not count the whole thread, count these. Keep a running mark for each as you scroll.

Re-asked addresses and details. Every time someone asked for a job address, a gate code, a customer name, or a start time that was already posted earlier in the thread. Each re-ask is one mark. You published it once. The thread lost it, so a man had to ask again and you had to answer again.

Unanswered questions. Every direct question that never got a reply. “Who locked up.” “Did the part come in.” “Are we on the Miller job tomorrow.” Scroll past it, see no answer, mark it. These are the questions that got buried under the next ten messages before anyone could respond.

Buried decisions and change approvals. Every schedule change, material swap, scope change, or customer approval that scrolled away. An inspector moved a date. A customer said go ahead on the extra. You told a guy to skip a step. If the decision is real but you had to scroll to find it, mark it. These are the expensive ones.

Orphan photos. Every photo posted with no caption, or a caption that does not say which job it belongs to. Your crew takes plenty of photos. The question is whether you could name the job and the date for each one without asking. If you cannot, mark it.

Crossed wires. Every time two people were clearly talking about different jobs in the same stretch of messages, or someone acted on the wrong information. Mark each one. This is the failure that turns into a wasted roll.

Five columns, two weeks, fifteen minutes. Count every mark. Nobody is watching, and the point is to see the real number, not a flattering one.

The scorecard

Add up all five marks into one total for the two weeks. Then read your band.

0 to 5: not yet, but soon. Your crew is small enough or your jobs are simple enough that the thread has not started dropping much, and that is usually where a two- or three-man shop sits. Do not read that as a clean bill. The number climbs the week you take on the fourth guy or the second job running at once, and it climbs faster than you expect. Keep the sheet, run it again in three months, and switch before the misses start costing you instead of after.

6 to 15: fraying. You are losing something every two or three days. Most of it you are catching by hand, which means you have quietly become the thread’s backup memory. You answer the re-asks, you chase the unanswered questions, you remember which photo goes where. That works right up until the morning you are sick, or driving, or on another job, and then one of these slips all the way through.

16 and up: it broke a while ago. At this level you are not catching them all, you just do not know yet which ones you missed. A shop running two or more jobs at a time with four or five people lands here routinely, and it is not a discipline problem. It is one thread being asked to hold a job’s worth of memory per job, which it cannot do. Every mark on your sheet is a small tax you paid this pay period, and the total is what it is costing you to keep running the business on a tool that has no place to keep a decision.

Whatever band you landed in, look hardest at the buried-decisions column. Those are the marks that cost real money, and that is the math the next section walks through.

Put a dollar on one buried decision

The tally makes the problem visible. A single line turns it into money.

Take one buried change approval from your sheet, the kind that scrolled away. Say it was an inspector moving a slot, and it got missed. The crew rolls to the wrong-day address: two men, half a day, call it six labor-hours gone. The inspection window is lost, so the job slips a week, which pushes the trades behind you and cools the customer. When it finally reschedules there is a re-inspection fee. One buried text, added up, clears a thousand dollars, most of it in the slip you cannot bill.

Now look at how many marks are in that column for just two weeks. You do not need every one to turn into a thousand-dollar miss. One a quarter pays for a lot. The one lost text that becomes a two-thousand-dollar callback walks the full chain if you want to see it play all the way out.

Before you decide it is a discipline problem

The right read of a high score is not that your crew is careless. Look back at the marks. Almost none of them are anyone slacking. The address got re-asked because the thread pushed it out of view. The question went unanswered because it scrolled off before a break. The photo has no job because there was no job to attach it to. Everyone did their part. The tool had no place to keep the results.

That is why the usual fixes fail. A rule that says job talk only, a second thread per job, a policy that everyone thumbs-up to confirm: those ask people to hold in their heads the structure the tool refuses to hold. They die inside two weeks, every time. If you have already tried them, why texting rules never fix the group text explains the reason they were never going to stick.

Keep your scorecard. When you look at a different way of running the work, whether that is a whiteboard, a spreadsheet, or an app, run the same five columns against it in your head. The right setup drives every one of those numbers toward zero, not because your crew got more disciplined, but because the address has a home, the decision updates the job, and the photo lands on the task it proves.

The fix that clears the sheet is a thread per job instead of one thread for everything. Give each job its own thread that remembers, and the address stays at the top where nobody re-asks it, the reschedule updates the job instead of scrolling away, the photo lands on the task it belongs to, and done is a state someone marks and someone one rank up signs off on, not a message that reads the same whether the work is finished or not. That is the whole idea behind Crewmigo. We are new, so do not take our word for it. Run your audit, keep the number, then put one job on it and run the columns again in two weeks. Let the second scorecard make the call.