After hours calls and texts with subs: where the line is

It is 8:52 on a Tuesday night. You are at the table, kids are down, and you remember the electrician never told you whether he is starting the panel tomorrow or the day after. You know the answer changes what the framers do at 7am. So you call him. He picks up, a little short, tells you the day after, and you both go back to your evenings a bit more tired of each other than you were an hour ago.

Nobody wanted that call. You did not want to make it, and he did not want to take it. It happened because the question had nowhere to wait. You had one channel to reach him, your phone in his phone, and that channel is either off or it is a ringing interruption. There is no middle setting where a question sits quietly until morning. So a question that could have waited nine hours became a phone call at dinner, because waiting was not an option the tool gave you. Drawing this line is one of the quieter subcontractor problems, and it costs you good subs when you get it wrong.

Why the 9pm call keeps happening

Line up the after-hours calls you have made to a sub over the last month and almost none of them were real emergencies. They were questions. What time tomorrow. Did the material land. Is the inspector confirmed. Which unit first. These are ordinary coordination questions, and every one of them could have waited until 6am. They did not wait because the only way you had to hold a question was to hold it in your own head, and a question in your head at 9pm feels urgent whether it is or not. You call to get it out of your head, not because it truly cannot wait.

The sub feels the other side of the same problem. To him, every buzz after 6pm reads as urgent, because you only ever call when something is wrong or when you forgot something. He cannot tell your “just checking on tomorrow” from your “the customer is furious and on site right now” until he answers. So he either answers everything and resents it, or he stops answering and you stop trusting him. This is the same dynamic that makes good subs go quiet in the first place, covered in what actually gets subs to respond: when the channel punishes them, they protect themselves by pulling back.

The trap is that both of you are reasonable. You are not a pest and he is not a flake. You are two people sharing one channel that has exactly two settings, on and off, when what the work needs is a third setting: later.

The two that genuinely cannot wait

There is a line, and it is worth naming clearly, because a fair boundary has to admit that some things really are after-hours calls.

Someone or something is getting hurt or damaged. Water is coming through a ceiling. A gas smell. An open trench with no barrier and kids nearby. Anything where waiting until morning makes the damage worse or puts a person at risk. You call. He answers. Neither of you resents it, because this is what the phone is for.

Tomorrow morning is already ruined unless he knows tonight. The sub is driving ninety minutes to a site that got shut down by the inspector an hour ago, or the crane is booked for 7am and the changeout just got pushed. If letting him find out at 6am means a wasted roll or a blown day, that is a call. The test is simple: will the delay of nine hours cost real money or a lost trip. If yes, it is a call. If no, it is a question, and questions do not need to ring.

Almost everything else is a question. Once you can see that line, the real number of true after-hours calls in a normal month is one or two, not the dozen your thumb has actually made.

A boundary both sides can live with

Here is a boundary that holds because it is fair to both chairs, not just yours.

Calls are for the two things above. Everything else goes in writing, and writing is understood to be answered in the morning. You agree, out loud, at the start of the relationship: if I call you, it is one of the two. If I message you, it can wait until you are back on the clock, and I will not expect a reply at 9pm. That second half is the part owners skip, and it is the part that makes the whole thing work. A boundary only holds if you also stop expecting instant answers to the things you agreed can wait.

The reason this usually fails is not bad intentions. It is that a text and a call both land in the same place, his phone, buzzing the same way. You can promise “messages can wait until morning” all you like, but a text at 9pm still lights up his screen at 9pm, and now he is deciding whether to answer it, which is the exact interruption you were trying to avoid. The boundary needs somewhere for the question to actually go, a place that is not his personal ringer, or it collapses back into the phone within a week.

That is also the fair answer to the ritual on the other end of the day, the morning scramble of unconfirmed subs. If tonight’s question can sit in a place he checks when he starts work, you are not chasing him at 6am either. That morning confirmation problem is its own piece, getting subs to confirm they are coming tomorrow, and it gets easier the moment questions have a place to wait overnight instead of riding around in your head.

Give the question somewhere to wait

The fix is not a rule about when to text. Rules about texting die in two weeks, because the channel has no way to enforce them. The fix is structure: a place where a question about a specific job sits attached to that job, visible to both of you, and does not buzz anyone at dinner.

Put the electrician’s panel question on the panel job, at 8:52pm, in one line. Tomorrow at 6am he opens the job, sees the question at the top where it did not scroll away, and answers it before he pulls out of his driveway. You never called. He was never interrupted. The question waited exactly as long as it should have, and the answer is now written down where the framers can see it too, instead of living in a phone call only you and he remember.

That is what a thread per job does that a group text and a phone number cannot. The group text has the same flaw as the call: it buzzes everyone, every time, and the question scrolls away by morning anyway. A job thread holds the question in place, silently, until the person you asked is back on the clock. The sub joins that thread as a free guest, one active job at a time, so there is nothing for him to buy and no app he resents. He reads what got asked, answers when he starts his day, and the two of you stop training each other to dread the 9pm buzz. If you want to hear the whole thing from his side of the truck, that is what GCs do that make good subs stop calling back, and a question that waits overnight is near the top of the list.