Scheduling subs across three jobs at once

You run three jobs at once. Not a big operation, just enough that you are never on all three sites in the same day. The Miller remodel, the Okafor kitchen, and the rental turnover on Fifth. And the same tile guy is on two of them, because he is the tile guy you trust and you only have one.

This is the part of small-GC life nobody warns you about. It is not the work that gets hard, it is holding four subs’ schedules across three jobs in your head while every one of those dates can move. The plumber slips, which moves the inspection, which moves the drywall, which moves the tile guy, who is now double booked because the other job did not move. You find this out at 6am the day it matters, standing in a driveway with your phone.

If you are also fighting to get replies in the first place, start with getting subs to confirm they are coming tomorrow. This guide is about the layer above that: keeping every confirmed date straight once you have more than one job in the air. It is the core problem this whole subcontractors hub circles.

One slip, traced through the week

Watch how a single delay moves through three jobs. Real dates, so you can see the cascade instead of just feeling it.

Monday morning, the inspector at Miller pushes the rough plumbing inspection from Tuesday to Thursday. Not a disaster on its own. But the drywall crew was booked for Wednesday at Miller, and you cannot rock a wall that has not passed inspection. So drywall slides to Friday.

Your tile guy was set for Friday at Okafor. The same tile guy. He cannot be at Miller closing walls on Friday, wait, he does not do drywall, but you had him penciled at Okafor Friday and now your head is full of Miller. So you call him Wednesday night to push Okafor to Monday. He says fine, he will take a Friday job somewhere else. Monday comes, and he is not at Okafor, because in his phone the job that got pushed was the other GC’s, not yours, and your Wednesday call lived in a voicemail he half heard from a ladder.

Now Okafor has no tile, the homeowner took Monday off work to let you in, and the drywall at Miller is done but the painter you booked for next Tuesday is looking at a job that is a day behind. One inspector moving one date, and by the following week you have a burned homeowner morning, an idle tile day, and a painter you have to re-sequence.

Where the money leaks

Put numbers on that week, because “it got hectic” does not tell you what to fix.

The tile guy’s missed Monday at Okafor is a lost day for you and for him. Say that stop was a $600 day of tile. It does not vanish, but it slides, and the slide pushes grout, which pushes the final walk, which pushes the last draw. On a rental turnover, a week late is a week of the owner’s lost rent, and that is the owner asking why the man he trusted cannot keep a date. Call the soft cost of that a customer who does not call you first next time.

The re-sequenced painter is the clearer number. He held Tuesday for you. When you call Monday to push him, he has already filled part of that day, so now you are fitting into his gaps instead of running your schedule. Two men waiting half a morning for a wall that is not ready is six labor-hours you either eat or pass along, and neither one is free.

None of these are catastrophes. That is the point. It is $600 here, a soured homeowner there, six hours of standing around, every week, and it all traces back to one thing: the dates lived in your head and in scattered texts, so when one moved, the move did not reliably reach the people it touched.

Post the change once, in the job it belongs to

Here is the shift that fixes it, and it is smaller than buying a scheduling suite. Stop treating a date change as five texts you have to send. Start treating it as one post in the job the change belongs to.

When the Miller inspection moves to Thursday, that fact belongs to the Miller job. Not to a group text where it scrolls past the tile guy who is not even on Miller. Not to five separate one-off texts you fire off from the driveway and then cannot remember whether you sent. You post it once, in the Miller job, where the drywall crew and the painter, the two subs that date actually touches, can see it and see that it moved.

The tile guy’s date at Okafor is a different fact, in a different job. When you push it to Monday, that goes in Okafor. He is a guest on Okafor. He reads the change in the job it affects, on his own screen, with the new date sitting there in writing instead of in a voicemail. There is no relay, no “did I tell him,” no version of the date that only exists in your memory.

The rule underneath it is plain: one job, one place, and a date change is a message posted there, not carried in your head to whoever you remember to text. When a sub blows past a date this way, the record of what he actually confirmed is right there, which also makes the harder conversation short. That is the groundwork for handling a sub who no-shows and for keeping subs accountable without babysitting: both of those get a lot easier when the confirmed date is written down in the job instead of argued about after.

What this looks like on a Monday

Run the cascade again with each job holding its own dates. The inspector pushes Miller to Thursday. You open Miller, change the date, and the drywall crew and painter on that job see it. Two people, the right two, one post.

The tile guy needs to move from Friday at Okafor to Monday. You open Okafor, change his date, and he sees it on Okafor, the actual job, with Monday in writing. He does not confuse it with the other GC’s job, because this change lives in this job and nowhere else. When Monday comes, the date he is working from is the one you set, not the one he half remembered.

You did not send fifteen texts. You did not hold four schedules in your head across a drive between three sites. You changed two dates in the two jobs they belonged to, and the people each date touched saw it. The week still had a delay in it, because inspectors move, but the delay stayed the size of the delay instead of growing a tail of missed handoffs behind it.

Getting the dates out of your head

The reason three jobs feels like ten is that all the dates live in one place: you. Every confirmation, every push, every “he said Monday” is a thing you are carrying, and the group text does not carry it with you, it just adds noise on top. That is why the fix is not trying harder to remember. It is giving each job a place to hold its own dates.

That is the shape of Crewmigo. Every job is its own thread that remembers, so a date change is posted once in the job it belongs to instead of relayed five times from your truck. Subs join the job they are working as free guests, one active job at a time, so the tile guy reads the Monday date on Okafor without you paying for a seat or making him install a suite. When he marks the tile done and posts the photo, you approve it from wherever you are standing, and the job moves without a drive-by. We are new, so try it on one job: put your next three-way scheduling week on it and see whether the dates stay out of your head.