How to tell the crew where to be tomorrow without ten texts

It is 8 pm and you are on the couch with your thumbs going. Marcus needs the Delgado address and the gate code. The other crew is at the new build tomorrow, so that is a different text, and you have to remind the two new guys that start is 6:30, not 7, because the concrete pour is early. Somebody asks in the family group instead of the work thread. You answer that one too. By the time you set the phone down you have sent nine, maybe ten messages, and you are already half sure one of them went to the wrong person.

Then 6 am comes and your phone lights up anyway. Where am I today. What was that address. Is it 6:30 or 7. The dispatch you did last night, the whole hour of it, did not survive the night. It scrolled away under a meme and two coffee jokes, and now you are running the same dispatch again from the truck with one hand.

This is the nightly ritual almost every small shop runs, and it is not a character flaw. You are doing the responsible thing: making sure everyone knows where to be. The trouble is the tool. A group text has no place to put tomorrow so it stays put. Everything you send tonight is a message, and a message gets buried by the next message. If you run more than one crew, it gets buried faster.

The 8 pm ritual, hour by hour

Watch what actually happens on a three-crew night, because the shape of it is the problem.

You start around 8 pm. Crew one is finishing the Delgado remodel, so that thread gets the address, the gate code, and a note that the homeowner works from home so keep the radio down. Crew two is at the new build, so they get a different address, a 6:30 start for the pour, and a reminder to bring the extra cords. Crew three is doing two service calls, so they get two addresses and the order to hit them in.

Now the questions start coming back, one at a time, out of order. One guy asks which truck. Another asks if the pour is still on given the rain. A third texts just a thumbs-up, which tells you nothing about whether he read the part that mattered. You answer each one as it lands, so the real information, the address and the start time, is now sitting above four replies about trucks and weather.

By 9 pm you have sent your ten messages and you think you are done. You are not. The information is in the thread, but it is not anywhere a man can find it at 6 am without scrolling past the whole evening. So tomorrow you will send a lot of it again. You did the work twice and called the second time normal.

If this is the whole ritual for you, the pieces of it are worth reading on their own: the reason the addresses keep getting re-asked is covered in why your job site runs on a group text, and the way a change like a rained-out pour sinks without a trace is the exact failure in how one lost text turns into a two thousand dollar callback.

What the ten texts actually cost

Put a plain number on it, because it is bigger than it feels.

Ten minutes of thumbs going at 8 pm is not the cost. The cost is the morning. Say three of your guys text you at 6 am because last night’s plan was not findable. You are answering from the truck, half dressed, one thumb, and each of those three exchanges takes a couple of minutes and pulls your head off your own drive. Call it fifteen minutes of your morning, five days a week. That is over an hour a week of you re-dispatching work you already dispatched.

The worse cost is the one that does not show up as a text at all: the crew that rolled to the wrong start time. The 6:30 pour note scrolled away, the guy read 7, and now a two man crew is standing around for half an hour waiting on nothing, or worse, the pour is going without them. That is real labor, a few hours of it, and if it slips the pour it is a lot more. One buried start time is the whole ball game.

The reason it stings is that you did tell them. You typed it last night. The group text just had no place to keep it true until morning.

One post per job, the night before

The fix is not to text harder or text earlier. It is to stop sending tomorrow as ten separate messages and start putting it in ten separate places: one per job, where it stays.

Instead of a wall of texts in one thread, each job has its own thread that remembers. Tomorrow’s Delgado job holds the Delgado address, the gate code, the 6:30 or 7 start, and the one homeowner rule, and it holds them at the top, not four replies deep. The new build holds its own. The service calls hold theirs. A man opens the job he is on and sees the plan for that job, and only that job, with nothing to scroll past. The questions that used to come back at 6 am do not come back, because the answer is already sitting in the one place he would look.

You can write it the same way you already text it. Here is a template you can copy tonight, one post per job:

Job: Delgado remodel Address + gate: 214 Alder, gate code 4471 Start: 6:30 sharp (pour is early) Who: Marcus, Ray Bring: extra cords Note: homeowner works from home, keep it down

That is the whole dispatch. It is not more work than the text you were going to send; it is the same words, dropped into the job instead of into a stream that loses them. The difference is that at 6 am nobody has to ask, because the plan did not move.

If you want to tighten this further, two neighbors in this hub go deeper on the pieces: how to keep the crew straight without windshield time in how to keep track of multiple crews without driving to every job, and why a rule like “confirm with a thumbs-up” never sticks in a group text in why texting rules never fix the group text.

Silence stops meaning yes

One more thing the ten-text ritual costs you: you never really know who read the plan. A thumbs-up in the thread might mean he read the address, or it might mean he read the coffee joke below it. When each job is its own thread, you can see who has opened it, so the guy who has not seen tomorrow’s start time is a name you can catch tonight instead of a no-show you discover at 6:30. You are not chasing confirmations across a stream anymore. The confirmation is where the job is.

That is the difference between texting the plan and posting it. A text is gone the moment the next one lands. A post to the job stays until the job is done.

The nightly dispatch got your shop this far, and the instinct behind it is right, you are making sure everyone knows where to be. The tool is what fails you. A stream that buries tomorrow by 6 am cannot hold a plan, and past three or four people it drops one most weeks, which is a wasted roll every time it does. This is the whole idea behind Crewmigo: a thread per job, so tomorrow’s address and start time live in the job instead of in a stream that buries them by morning. You post it once, the night before, and it is still there at 6 am when the crew opens the job. We are new, so put one job on it tonight and watch whether the 6 am questions stop coming. That is the only test that matters.