Remote and international teams don’t fail just because of distance. They fail when people assume context, use chat as documentation, schedule meetings for everything, and expect immediate responses from colleagues in another time zone.

Good remote communication needs three things: written context, decision rules, and respect for asynchronous time.

Write complete requests

Weak message:

Can you review this?

Better message:

Can you review the onboarding proposal by Thursday, 12pm Lisbon? I need to validate that the email flow is clear before sending it to the sales team. Document: [link]. The necessary decision is to approve or point out blockages.

A good order has:

Element	Example
Context	”We are closing the onboarding flow”
Expected action	”Review email sequence”
Deadline	”Thursday, 12pm Lisbon”
Spindle	”12pm Lisbon / 1pm CET”
Link	document, ticket or dashboard
Decision	approve, comment, choose option or unblock

The less context you write, the more work you transfer to those who read.

Uses time zones unambiguously

“End of the day” does not mean the same thing in Lisbon, Berlin, Helsinki, São Paulo or Dublin. Always use date, time and zone.

Examples:

• “Tuesday, 10:00 CET”;
• “Friday, 12:00 Lisbon”;
• “2026-05-08, 15:00 UTC”;
• “until Thursday, before the 14:00 CET product meeting”.

For systems, calendars and technical documentation, formats based on ISO 8601 help avoid ambiguity between dates and time zones. For human messages, the important thing is to specify the city or time zone.

Decide what needs a meeting

Not everything needs to be synchronous.

Situation	Best format
status update	written message
simple decision with 2 options	comment on document
conflict of priorities	short meeting
ambiguous or sensitive topic	meeting
initial brainstorming	meeting or workshop
feedback on document	asynchronous comment
weekly lineup	written summary + short meeting if necessary

Before scheduling a meeting, ask:

• what decision needs to be made?
• who really needs to participate?
• what material should be read first?
• can the result be written in 5 lines?

Meetings without decisions tend to turn into alignment theater.

Document decisions in the right place

Chat is good for conversation. It’s not good as a team memory.

After making a decision, write:

Decision:
We will launch the reduced version of the form.

Reason:
It reduces delay risk and lets us validate real demand.

Owner:
Ana.

Deadline:
May 14, 17:00 CET.

Open points:
German translation and legal validation.

Good recording prevents the same discussion from coming back three days later. It also helps those who were on vacation, in another time zone or outside the meeting.

Sets the tone for multicultural teams

In international teams, the same sentence can sound direct, cold, vague or aggressive depending on the culture and language.

Exchange:

I don’t agree.

By:

I see a risk in this option: the deadline depends on the legal team, which has not yet confirmed availability.

Exchange:

Do this today.

By:

We need this today to unlock tomorrow’s shipment. Can you accept it or should we reprioritize?

Clarity is not a lack of empathy. But empathy without clarity creates ambiguity.

Sets response expectations

If the team doesn’t agree on response times, everything seems urgent.

Example of agreement:

Channel	Usage	Expected time
Slack/Teams	quick questions and coordination	same business day
Email	formal and external decisions	1-2 business days
Ticket	traceable work	according to priority
Document	review and comments	deadline defined in the request
Telephone	real urgency	exceptional use

It also defines what real urgency is. Without this agreement, each person creates their own rules.

Protects the right to disconnect

Eurofound tracks teleworking and the right to disconnect in Europe, including risks of an “always on” culture, working out of hours and insufficient rest. The European Commission has also started consultations on the right to disconnect and fair teleworking, with topics such as equipment, monitoring, data protection and occupational health.

In practice, this means:

• do not respond after hours;
• use scheduled shipping when possible;
• write “not urgent” when true;
• separate real urgency from anxiety;
• avoid recurring meetings outside of team hours;
• document decisions for those who were unable to participate.

For individual limits, read How to set limits at work without harming your career.

Useful templates

Request for review

Context:
We are preparing [topic].

Request:
I need you to review [specific part].

Decision needed:
Approve / choose an option / point out risks.

Deadline:
[date and time zone].

Link:
[document].

Meeting summary

Participants:

Decisions:

Owners:

Deadlines:

Open points:

Next update:

Discordance without noise

I see a risk in this option:
[risk].

The alternative would be:
[option].

Trade-off:
[cost/benefit].

Suggestion:
[next step].

Signs that communication has improved

• fewer meetings to clarify messages;
• fewer lost decisions in chats;
• less rework;
• deadlines with explicit time zone;
• documents with clear responsible persons;
• absent people can follow up later;
• fewer messages after hours;
• conflicts appear earlier and with more context.

Useful sources

• Eurofound: Teleworking.
• Eurofound: Telework in the EU.
• Eurofound: Right to disconnect.
• European Commission: right to disconnect and fair teleworking.
• ISO 8601, for unambiguous date and time formats.

Efficient remote communication is not about writing more. It’s writing enough so that the other person can decide, act or unlock work without being in the same room, in the same country or at the same time.