One-man band to three techs: dispatching without forwarding texts

For years you were the whole company. A property manager texts you a leaking faucet in unit 7A, you drive over, you fix it, you text back a photo, you send the invoice. The phone was the whole system, and the whole system fit in one pocket. It worked because there was only one of you, and every message either came to you or came from you.

Then you hired a second guy, and then a third, and the phone that used to be the system turned into a switchboard. The PM still texts you the leaking faucet. Now you have to figure out which tech is near 7A, forward it to him, wait for him to text back a photo, then forward that photo to the PM. Do that forty times a day across three techs and a dozen properties, and you have quietly taken on a second full-time job: moving other people’s information from one phone to another. Nobody hired you for that. You hired yourself into it the day tech two started.

The relay is a job, and it is eating your day

Here is the part that is easy to miss because it happens in ninety-second chunks. Sit down at the end of a normal week and actually count the forwards.

A PM emails you a make-ready punch list Monday morning. You retype the relevant items into a text and send them to whichever tech is going. A tenant texts your tech directly, because you gave out his number once, and now the tech is screenshotting that conversation to you so you know what was promised. A photo of a finished repair comes into your phone with no caption, and you forward it to the PM with a line explaining which unit it is, because the tech did not say. The PM replies with a question, you forward the question to the tech, the tech answers you, you answer the PM. One repair, five forwards, and you never touched a tool.

Count a real week and the number lands somewhere north of ten hours. That is ten hours of retyping information that already existed somewhere: the PM already wrote the punch list, the tenant already described the problem, the tech already took the photo. You are not creating anything in those ten hours. You are a courier for facts that were already written down, just written down in the wrong place. Ten hours a week is more than a full day. It is the day you meant to spend quoting the next job, or getting off the tools, or going home at five.

Why forwarding loses things on top of costing time

The hours are the obvious cost. The quiet cost is that a forward is a copy, and every copy is a chance to drop something. This is the same failure a group text runs into once you are running more than one job, and it gets worse, not better, with three techs and a stack of properties.

The relay drops the details. You forward the punch list, but you leave off the tenant’s note about the dog, because it was in a different email. The tech shows up, the dog is out, and now you are on the phone about that instead of the faucet.

The proof lands on the wrong phone. The tech’s before-and-after photos live in his personal camera roll. When the PM disputes the work three weeks later, the photo that would end it in one message is on a device you do not control, and if that tech has moved on, it is gone. This is exactly the fight covered in tenant says the repair never happened, and forwarding is what makes it possible to lose.

The approval never gets recorded. A tech finds more damage behind the wall, texts you a photo, you glance at it between other things and text back “go ahead.” That approval now lives in a thread nobody can find, and when the invoice is questioned, you are reconstructing it from memory. The same problem shows up when a tech finds more damage behind the dishwasher and the go-ahead lives only in your forwarded texts.

None of these are your techs being careless. They are all the same structural fact: when the record has to be relayed by a person, the person is the single point of failure, and the person is you, all day, every day.

What changes when the job holds its own record

The fix is not a rule about forwarding faster or a policy that everyone caption their photos. Those die in a week, because the tool is still a pile of one-to-one texts and you are still the hub they all pass through. The fix is to stop being the hub.

Give the work order its own thread, and put the three people who care about that job into it: the tech doing the work, the PM who requested it, and you. Now the leaking faucet in 7A is not a text you received and have to forward. It is a thread. The PM posts the request into the thread once. The tech reads it in the thread, does the work, and posts the finished photo onto the task, in the thread. The PM sees the photo the moment it lands, because the PM is already in the thread. You did not forward anything. You did not retype the punch list. You did not caption the photo. The information stayed in one place, and everyone who needed it was already standing in front of it.

That is the shape of the day changing. When a job is a thread instead of a chain of forwards, dispatching a new repair is one post, not a round of relays. When the tech marks a task done and you approve it, the approval is a state on the task, not a “go ahead” buried in your texts. And the record belongs to the company, so when a tech leaves, his photos do not leave with him.

The dispatch that does not run through you

The reason the one-man-band system worked was that you were the whole record. The reason it breaks at tech two is that you can no longer be the whole record and also swing a hammer, and forwarding is the doomed attempt to be both. Ten hours a week of couriering facts is the tax you pay for keeping the job in your phone instead of in the job.

Crewmigo is built for exactly this seam. Each work order is its own thread that the tech, the PM, and you all read. Photo proof lands on the task it belongs to, so nothing gets forwarded and nothing gets lost. Done, then approve, then sign off is a state anyone can see, not a message you have to relay. The PM joins the job like a guest joins a group text, at no cost to you, and you pay only for your own crew. We are new, so put one property on it, the noisiest one, and watch how many forwards disappear in the first week.