A message sent at 11 p.m. does not always need an answer at 11 p.m. The trouble is that a notification gives no clue whether a request can wait. In music work, a routine poster question can arrive alongside a real problem with tomorrow’s show. Agreeing on what needs an immediate response—before either message arrives—takes the guesswork out of it.
That agreement needs more than “I don’t answer after six.” Collaborators need to know when you check messages, where to raise an urgent issue and what qualifies as urgent. They also need to know when you work: a venue technician’s evening may be a publication editor’s time off. Nobody has to keep the same hours, but they do need to understand one another’s.
Start with the work, not the notification setting
Before switching off alerts, look at the requests you receive in a typical week. Which decisions need a prompt answer, and which only feel immediate because they arrived in a chat window? A change to an artist’s arrival time on show day may need attention. A suggestion for next month’s newsletter usually does not.
For a small team, three categories are often enough:
- Scheduled work: Planning, drafts, approvals, invoices and other tasks that can wait for normal working time.
- Time-sensitive work: Matters tied to a stated deadline, such as final print approval or a travel change before departure.
- Live incidents: Issues affecting safety, access or the ability of an event or scheduled release to go ahead.
Fit those categories to your responsibilities. A freelancer preparing advance coverage is not necessarily the person who can resolve a venue access problem. And an “urgent” label is little help if nobody knows who owns the incident. Assign an owner and, where the work calls for one, a backup.

State when you are available
Choose a response window you can keep, rather than one that merely sounds accommodating. For example: “I check project messages on weekdays between 10 a.m. and 6 p.m. in my time zone. Please allow one working day for a reply.” The time zone matters when an artist, publicist and venue are in different countries. So does the difference between checking a message and finishing the work it asks for.
If your hours change around shows, say so. A promoter might handle messages later on event days and start later the following morning. A touring crew member may be reachable during travel and show hours but unavailable on a day off. Put any exception on the shared calendar or in the project brief, with a start and end time, so the boundary stays clear.
It also helps to separate when someone sends a message from when they expect an answer. A colleague may email after a late set because that is when they have the information; you can agree to deal with it during your next working period. Scheduled send can spare people an alert, but it cannot replace that shared understanding.
Make response expectations specific
“I’ll reply when I can” leaves too much room for different assumptions. Try naming both a channel and an interval: “For routine production questions, use the project email thread; I normally respond by the next working day.” If an approval needs a decision by a certain hour, the sender should include the deadline and what happens if it is missed, rather than sending repeated pings.
Do not promise a response time you cannot maintain. If another job, caregiving or irregular shifts affect your availability, a narrower commitment is better than an ambitious one you routinely miss.
Give urgent work a separate route
If every channel can carry an emergency, you have to watch every channel. Choose one route for matters that cannot wait: perhaps a call to the show-day contact or a dedicated group chat monitored by whoever is on duty. Keep the route limited, and tell people when to use it.
For example: “Call the on-duty contact if a problem requires a decision before doors open, affects someone’s safety or prevents a scheduled performance from going ahead.” That gives people more to work with than “call if it’s important.” A minor typo on a page can matter without warranting an overnight call.
Check that the route is actually covered. If the named person is onstage, driving or asleep in another time zone, arrange a backup or a clear handoff. For safety matters, follow the venue’s or employer’s incident procedures; a personal messaging rule is no substitute.
Put the agreement where people will find it
A boundary mentioned once in conversation is easily forgotten. Put it where people already look: an email signature, project kickoff note, team channel description or show-day contact sheet. Keep it short enough to scan. For example:
“Project email: weekdays, 10 a.m.–6 p.m. UK time; routine replies by the next working day. On show days, call the listed duty contact for safety, access or performance-stopping issues. Please include a deadline for approvals.”
This tells senders how to get an answer, rather than simply listing restrictions. They need not guess whether you saw a late message. If several people share an inbox, say who monitors it and when. An unattended “urgent” mailbox offers false reassurance.

Choose a channel for each kind of request
Chat works for quick coordination, but decisions can get buried among reactions and side conversations. Email or a shared task record is often better when an approval needs a trail. Calls suit issues that need an immediate exchange. The system does not have to be elaborate; it does have to be consistent.
- Keep non-urgent requests in one project thread or task, with relevant files and deadlines attached.
- Reserve the designated live channel for periods when an event or release is actively being handled.
- After a call, record any decision others need to act on in the shared project space.
Otherwise, people end up watching every direct message in case one contains the decision that matters.
Use language that is firm without making it personal
Describe the process, not the sender’s behaviour. “Please email non-urgent changes so I can track them during working hours” gives someone a next step; “Stop messaging me late” does not. You can acknowledge a deadline without agreeing to be permanently available.
When a request arrives outside your window, you usually do not need to reply immediately to explain why you are not replying. Answer during your stated hours. If you have regularly answered routine midnight messages, though, people may have come to expect it. A brief reset can help: “I’m changing how I handle project messages. From Monday, I’ll review routine requests during my listed hours; for show-day incidents, use the duty number.”
Managers and project leads have a particular responsibility here. Late messages paired with praise for instant replies can make a written boundary feel unsafe to follow. They can say explicitly that delayed responses are expected, schedule non-urgent messages where practical and avoid treating online status as proof of availability. For employees, contractual hours, on-call arrangements and applicable workplace policies must be clear; a personal auto-reply cannot replace those agreements.
Keep exceptions limited and visible
Festivals, tours and release days can demand intense coordination. The trouble starts when an exception has no end date. Before a busy period, agree who is on call, during which hours, through which channel and for which decisions. Where the working arrangement allows it, discuss time off or adjusted hours afterward.
If ordinary tasks keep arriving as urgent requests, look at the workflow rather than stretching everyone’s availability. Repeated last-minute artwork approvals may point to an unclear deadline or a missing decision-maker. A recurring guest-access question may belong in the event brief. Better information earlier can prevent a late message later.
Review the arrangement after a few weeks or after the next event. Note missed handoffs, unnecessary calls and requests sent to the wrong place, then change one instruction at a time. If artists keep sending routine travel questions to your personal chat, add the travel coordinator’s email and working hours to the next advance sheet before it goes out.