Make time explicit
For cross-border work, include a date, time, and time zone in meeting invitations and deadlines. “3 p.m. tomorrow” is ambiguous when colleagues are in different locations. Check daylight-saving changes when scheduling beyond the current week.
Set response expectations
Agree on which channels are asynchronous, what counts as urgent, and how people can escalate a time-sensitive issue. A visible activity indicator, if a service provides one, is not a reliable measure of whether someone can respond.
Respect working hours
Use delayed delivery or notification schedules if the product offers them and company policy allows it. Otherwise, state clearly that an after-hours message does not require an immediate response. Check local employment and team policies rather than assuming one rule fits everyone.
Schedule across two locations
Instead of “send this by 3 p.m.,” write the calendar date, time, and time zone. For example, “Tuesday, 15:00 Europe/Sofia” is more precise than a time alone; confirm the conversion in the shared calendar because daylight-saving rules can change. For an asynchronous request, state the expected response window and what should happen if the owner is away. Avoid using an activity indicator as a substitute for that agreement.
Choose the next step
| Situation | What to check |
|---|---|
| A deadline spans time zones | Include the date, time, and named time zone. |
| A teammate is away | Name a backup or the next available response window. |
| An incident is urgent | Use the documented on-call or escalation route. |
A practical checklist
- Include a time zone with deadlines.
- Agree on expected response windows.
- Use the team’s escalation path for urgent issues.
- Check working hours before scheduling.