The short version
- Many managers think best late at night. The problem is not when you write, it is when the team is asked.
- Separate composing from sending. Scheduled send is the single highest-return habit available to a manager.
- A message from you is never just a message. It carries an implicit question about what committed people do at 22:00.
- For questions rather than instructions, write it to their StandIn: it answers from the record now, and nothing lands on them until they are on.
Plenty of managers do their clearest thinking after the household is quiet. That is a legitimate working pattern and it is not the thing causing harm. The harm is in the send button.
"I write at 22:00 because that's when I think. They read it because it's me."
Writing late is fine. Sending is not.
These are two separate acts and most guidance conflates them. Composing at 22:00 costs nobody anything. Delivering at 22:00 costs whoever receives it their evening, and costs everyone who hears about it a recalibration of what is expected.
The asymmetry is worth being precise about. You send one message and move on. They receive a message from their manager, at night, and now have to decide: reply now, reply in the morning and wonder whether that was slow, or think about it until they sleep. There is no version of that where the cost is symmetrical.
What a manager's message carries
Three things travel with it whether you intend them or not.
An implicit expectation. The recipient cannot know you did not want a reply tonight unless you say so, and even then they are weighing the risk of being wrong.
A model of the role. If the person whose job they might want next works at 22:00, the message says that is what the job involves.
Permission for everyone else. Norms come from the most senior visible behaviour. One manager messaging at night makes it acceptable for peers to do the same, and then for anyone.
The fix, in three habits
Schedule everything outside their hours. Set the default to the recipient's next working morning. This is one setting and it removes most of the problem permanently.
Separate the question from the instruction. Instructions can wait until morning with no cost to you. Questions are the ones that feel urgent at 22:00, and they have a better destination.
Ask the record before writing to the person at all. With StandIn, your engineer's brief is answerable while they are off: you ask where the export stands and get their words with a source under them, at 22:00, without composing anything. It never guesses, so if the answer is not in the record you find out immediately and can decide whether it genuinely needs them tonight.
That third habit is what makes the first two sustainable. Scheduled send alone means you still spend the evening without your answer, which is the pressure that eventually breaks the habit. See retire your out-of-office.
Why "no rush" does not work
Adding "no rush, tomorrow is fine" to a 22:00 message helps a little and less than managers believe, for two reasons.
It has to be perfectly consistent to mean anything. If you add it four times out of five, the fifth message without it reads as urgent, and the recipient is now interpreting your phrasing rather than relying on a norm.
And it does not remove the notification. The message still arrived at 22:00, they still saw it, and the thinking has already started. What "no rush" removes is your discomfort rather than their evening.
Scheduled send removes the notification. That is the difference, and it is why it is the habit worth building.
Common Questions
Is it bad for a manager to send messages at night?
Sending is; writing is not. Compose whenever suits you and schedule delivery for the recipient's working hours. A message from a manager at 22:00 sets an expectation no amount of wording undoes.
Does adding "no rush" make it acceptable?
Only partly, and only if you do it every single time. Inconsistency makes the absence of the phrase meaningful, and it never removes the notification that already interrupted their evening.
What if I need the answer before morning?
Then look in the record first, because most night questions are retrieval. If the answer genuinely is not there and it genuinely cannot wait, call rather than message, and say why in the first sentence.
My team works different hours by choice. Does this still apply?
Yes, with the recipient's declared hours as the reference rather than a company standard. The rule is that you send into someone's working day, whenever that is, not that everyone works nine to five.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.