How to Assign Jobs to Your Crew in a Group Chat Without Things Falling Through

A job sticks when one named person, one verb, one date and one clear finish line sit in the same message, and the finished job leaves a record somebody can check later. Almost every dropped job in a crew chat is missing at least two of those five. That is the whole answer, and the rest of this page is how to make it true on a Tuesday morning when you are holding a phone in one hand and a ladder in the other.

If you run a crew, you already know the shape of the problem. You posted it in the chat. Four people reacted with a thumbs up. Nobody did it. Now you are on the phone with a customer explaining why the truck did not show, and the crew is genuinely confused, because as far as each of them was concerned, somebody else had it.

This guide is for the person in the middle of that: the foreman, the crew lead, the owner who still swings a tool, the shop manager who dispatches four vans from a phone. Not for a project manager with a certification. The advice assumes you have no patience for a rollout, no appetite for training anybody, and no interest in a tool your guys will quietly stop opening by the second week.

There is a forty-second game further down that shows you the difference faster than this paragraph can, a slider that totals what dropped jobs cost you a year, and a card at the end you can paste straight into your crew chat.

Why a message to everyone is a message to nobody

Start with the mechanism, because the fix follows from it and the fix is not what most people try first.

In Darley and Latané's 1968 bystander experiment, people who believed they were the only witness to an emergency went for help about 85 percent of the time. When those same conditions were run with the participant believing four other people were also present and also aware, help dropped to about 31 percent. Nobody in that room was lazy or careless. Each person was doing a reasonable thing: assuming that with this many people aware, someone better positioned had it handled.

A group chat is not an emergency, and that study was about a stranger in distress, not a punch list. The mechanism transfers anyway, and every crew lead recognizes it the moment it is named. "Can someone grab the permit before Thursday" broadcast to six people is the exact condition of that experiment. Six people read it. Six people reasonably assume one of the other five is closer to the county office. The permit does not get pulled.

So your crew is not ignoring you. The message is shaped in a way that reliably produces inaction, and it would do the same to a crew of saints. That is good news: structural problems have structural fixes, and those work the same in month six as in week one.

The four ways a job dies in a chat

Watch your own thread for a week. Every loss lands in one of four.

1. No owner. Addressed to the group. Absorbed by nobody. The most common death by a wide margin.
2. The scroll. It had an owner, but eleven messages about lunch, a photo of a cracked fitting and a meme buried it inside forty minutes. A chat is a river, not a list, and things you put in a river leave. The customer-facing version of this is covered in How Do Small Teams Keep Up With Customer Messages?
3. The verbal yes. Somebody replied "got it." That is a promise, not a record. Nobody can check a promise on Thursday. A thumbs up is the weakest possible acknowledgment and it is the one crews use most.
4. No finish line. "Handle the Morrison site" means five different things to five people. One guy swept it and considers it handled. You meant the walkthrough, the photos and the invoice.

Notice what is not on that list: the crew's work ethic, the chat app you chose, and whether you bought software. Those are the three things owners usually blame, in that order, and all three are the wrong suspect.

The five-part anatomy of an assignment that sticks

Here is the shape. Five parts, in this order, and it takes about eight seconds longer to type than the version that fails.

1. One name, first

Not "someone." Not "you guys." A name, at the very front of the message, before the job. Front matters because it is what people see in the notification preview without opening the chat. "Marcus, pull the permit" arrives as a different object than "we need to pull the permit, Marcus can you get it." The first one has an owner before the reader has finished the sentence.

If the job genuinely needs two people, that is two assignments, not one. "Marcus and Dee, load the trailer" is an assignment with a fifty percent chance of nobody loading the trailer. "Marcus, load the trailer. Dee, check the straps before it moves" is two jobs and two owners.

2. One verb

A verb is the difference between a job and a topic. "The Morrison drain" is a topic. "Snake the Morrison drain" is a job. Topics are what crew chats fill up with, and a crew cannot do a topic.

Use the verb the crew says out loud. Pull, snake, load, haul, patch, torque, invoice, order, call. Corporate verbs like "action" and "circle back on" describe a category of effort instead of a motion of the hands.

3. A date, not a vibe

"ASAP" is not a date. "End of week" is not a date on Tuesday, because Tuesday's end of week and Thursday's are different beliefs held by different people. Include a time whenever the job blocks someone else, because "Thursday" with no time means 11:59pm to anyone looking for room and 8am to you.

A real date does a second job too: it is what lets a follow-up happen without a human being annoyed. More on that below.

4. What done looks like

One clause. Not a spec document. "Snake the Morrison drain by Thursday noon, send a photo of the clear line when it runs." The photo is the finish line. Nobody has to interpret anything, and nobody has to take anybody's word for it.

Good finish lines are physical or verifiable: a photo, a signature, a paid invoice, a text to the customer, a key back on the board. Bad ones are internal states: "make sure the customer is happy," "get it sorted." You cannot check an internal state on Thursday at noon.

5. A record somebody can check

This is the one crews skip and it is the one that decides whether any of this survives past week two. After the job is done, there has to be a place where "done" is recorded, that is not the chat scroll, and that a person can open on Thursday without reading four hundred messages.

It can be genuinely low-tech. A whiteboard in the shop. A pinned message you edit. A shared note. What it cannot be is "I remember him saying he did it," because that is the thing that turns into an argument in front of a customer.

Play it: will this message get done?

Eight messages, pulled from the shapes crew chats actually produce. Tap whether each one gets done or gets dropped. No typing, about forty seconds, and you will know the five parts by the end without having to memorize them.

The card to keep

This is the whole method on one card. Copy it, paste it in your crew chat, pin it. It is the only thing from this page you actually need.

Four more, rewritten

Four more, rewritten. Not more polite, just more finishable.

None of those runs past about twenty words. This is not bureaucracy. It is the information already in your head, arranged so it survives the trip into somebody else's.

A week of running a crew from the chat

The shape above is the unit. Here is how a week of them fits together for a four-person crew, because the daily rhythm is what makes the shape stick.

Monday morning, 6:50am, before the trucks roll

One message, not a meeting. The week's jobs, each with a name and a day. Four assignments, not a paragraph. It costs four minutes in the yard and it is the highest-return four minutes of the week, because everything after it is an adjustment rather than an instruction.

The mistake here is writing a status update instead of assignments. "Big week, Morrison Tuesday and Wednesday, the Kelleher job pushed" is information, and nobody can do information.

Monday through Wednesday, as things change

Jobs move. A customer reschedules, a part does not arrive, somebody calls out. The rule that keeps this from unraveling: when a job moves, reassign it out loud in the same shape. Do not let a job change owners in a phone call that only two people heard. Half the dropped jobs in a crew chat were assigned correctly on Monday and changed hands invisibly on Tuesday.

Thursday, the day it would have fallen through

Thursday is when Monday's dates come due, so it is the day the system either worked or did not. Check the record, not your memory. Anything without a finish line recorded gets exactly one message, and it is a question about the job, not a comment about the person: "Marcus, where did the permit land?" Not "did anybody do the permit."

If you run this check by scrolling, you will stop running it within three weeks. That is the honest limit of a plain chat, worth knowing now rather than in month two.

Friday afternoon, five minutes

Two things. What got finished, named by person, posted publicly. And what is rolling into next week with a new date. The naming matters more than it sounds: a crew that never hears which jobs landed learns that only failure gets attention, and crews that learn that stop volunteering.

That is the whole week. Four minutes Monday, one rule mid-week, one check Thursday, five minutes Friday. No software required for any of it.

What dropped jobs are actually costing you

Most crew leads live with this problem for years because each individual drop feels small. A rescheduled trip. A callback. An hour of your evening. The annual total is the number that changes minds, so here it is with your own figures.

Drag those to your real numbers. Two things are usually true: the total is bigger than owners expected, and bigger than anything they would have spent to fix it. That gap is the whole argument.

Who does the chasing, and why it should not be you

Here is the part that structure alone does not solve. Even with perfect assignments, somebody has to notice on Thursday that the permit is not pulled, and say something. If that somebody is always you, two things happen, both bad.

First, you become the system. Nothing runs when you are on a roof, on vacation, or asleep. Second, and worse, you become the nag. Every reminder you deliver personally carries a small charge of disapproval, whether you meant it or not, and the crew starts hearing your name in the notification as a complaint. We wrote about this pattern in a household context in How Do I Stop Being the Nag in My House?, and it is identical on a job site: nagging is a role the structure assigns to somebody, not a personality trait.

The fix is to make the follow-up impersonal and automatic, so it comes from the date rather than from the boss. A reminder that arrives because Thursday noon passed reads completely differently from the same words typed by you at 12:05. Same information, no charge on it, and the crew can respond to the job instead of managing your mood.

This is also the honest boundary of a plain group chat. A chat can hold a well-shaped assignment perfectly well. What it cannot do is notice that Thursday came. Somebody or something has to do that part, and if it is always you, the system has a single point of failure wearing your boots.

Five mistakes that undo all of this

1. Moving the crew to software instead of fixing the message

The most common and most expensive mistake. An owner buys a project tool, spends a weekend setting it up, and by week three the crew is back in the group chat because that is where the photos and the jokes and the actual conversation live. The chat won because it was already where everybody was. Any fix that starts with "everybody download this and stop using the chat" is fighting the strongest force in the situation.

2. Treating a thumbs up as a commitment

A reaction is an acknowledgment that a message existed. Ask for the finish line, not the acknowledgment. If you want confirmation of receipt, ask for something with content in it: "say got it when it is in your truck."

3. Letting jobs change hands in private

The reassignment has to be as public as the assignment. A job handed off by phone call is a job with no owner in the record, and the record is what you will check on Thursday.

4. Only speaking up when something is late

A crew where the boss appears in the chat exclusively to chase will route around the chat. They will handle things verbally, out of your view, precisely to avoid the pattern. Name the finished work out loud on Friday and that stops happening.

5. Writing the job for yourself instead of for them

"Morrison Thursday" makes complete sense to the person holding the whole schedule in their head. It makes no sense to a guy who has been on a different site for three days. Write the version that works for somebody with no context, because that is who is reading it.

If you are keeping it in plain SMS or WhatsApp

Plenty of crews will, and there is no shame in it. The five-part shape works in any thread on earth. Three habits get you most of the benefit with no new tool:

• Pin one message and edit it. One pinned "this week" message, updated as things finish, is a record that survives the scroll. Free, and it is the single highest-value habit on this list.
• One thread per job for anything over a day. Reply in-thread so a job's whole life is in one place instead of scattered through a week of river.
• Set your own alarms for the dates you assign. If you are the follow-up mechanism, at least be a mechanism rather than a memory. Your phone can hold Thursday noon; your head, at 60 miles an hour between sites, cannot.

Be clear-eyed about what that does not solve: you are still the one noticing, so the week you are buried is the week it stops. If that is fine at your size, stop here. If you have outgrown it, the question is what to add.

What to look for if you do add something

The market is full of tools for this and most of them were designed for a company with an office, a full-time coordinator and an onboarding budget. For a crew, four things decide whether it survives past week three.

Do not buy anything if your honest answer to "how many jobs did we drop last month" is zero or one. The shape in this article is free and it is most of the value. The case for adding a tool starts when the Thursday check has become a job in itself, or when you have stopped doing it.

How we built this into Tarvis AI

Tarvis AI is the agent we built at Class Company US, and this problem is why its team chat works the way it does.

The AI sits in the thread with the crew, so the conversation and the tracking are the same screen. When a job is assigned in the chat it becomes a real task with an owner and a date, and assigning it is also how you invite that person, so there is no separate onboarding step for a new guy. Projects carry real dates and countdowns, so Thursday noon is something the system knows rather than something you have to remember. Money is tracked per project, which is how you find out whether the job that ate your week actually made anything. And the weekly status report gets drafted from what actually happened, rather than from your memory of it on a Friday evening.

Two free teammates come with every brand, it is free while in beta, and it installs straight from the browser to your home screen with no app store and no download page. If you want the fuller picture of how an AI behaves as a member of a thread rather than a chatbot in a sidebar, we wrote that up in What Is Team AI Chat?, and the message-overload version of this same problem is covered in How Do Small Teams Keep Up With Customer Messages?.

Honest limits, since this page is not a brochure. Tarvis does not dispatch trucks, does not do payroll, and will not make a crew that does not read the chat start reading the chat. If your team genuinely does not open the thread, no software fixes that and you have a different conversation to have with them first.

Frequently asked questions

Why do jobs get dropped when I post them in the group chat?

Because a message sent to everyone is owned by no one. A job sticks when one named person, one verb, one date, and one clear finish line are in the same message, and the finished job leaves a record somebody can check later.

Should I stop using a group chat to run my crew?

No. The chat is where your crew already is, and moving them to software they will not open is the most common failed fix. Keep the chat and change the shape of the message, or add something to the chat that turns a message into a tracked job.

What is the fastest change I can make today?

Put one name at the front of every job message and one date at the end. Those two changes alone remove the two ways a job dies most often: nobody claimed it and nobody knew when it was due.

How do I follow up without nagging my crew?

Make the follow-up automatic and impersonal so it is not coming from you. When a reminder arrives because a date passed rather than because the boss is annoyed, the crew stops hearing it as a complaint and the relationship stops paying for the reminder.

Do I need project management software to fix this?

Not necessarily. Most crews do not fail for lack of features, they fail because the tool is a second place nobody opens. Either fix the message shape in the chat you already use, or pick something where the chat and the tracking are the same screen.

What does a dropped job actually cost?

Add the value of the job at risk, the hours somebody spends fixing it, and the callback or rescheduled trip it causes. Most crew leads who total one month of this find the annual number is larger than the software they refused to buy.

How do I get a crew to adopt this without a meeting?

Do not announce it. Just start writing your own messages in the five-part shape and answer questions about jobs by restating them in that shape. Crews copy the format of the person assigning work within about two weeks, because clear assignments are easier to satisfy and people prefer being able to finish something.

Test yourself

You just read about four thousand words on this. See how much stuck. Answer the five questions and we will email you the answer key with a short explanation for each, written for crew leads, not consultants.

Help us make this better

These guides are written for people who actually run crews, and the best ideas for them come from people who actually run crews. What was missing? What should we go deeper on next? Thirty seconds, and we read every one: