---
id: KB-AD-017
url: https://app.codecontract.io/help/administration/when-the-team-is-in-several-countries
idioma: en
categoria: administracion
audiencia: administrador
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-AD-011, KB-CC-016, KB-AD-010]
citadoPor: [KB-AD-014]
---

# When the team is in several countries

_Four things that stop working by themselves once people share neither time zone, language nor calendar._

**Responde a:** team across several countries · users in different time zones · working with offices abroad · alert language per user

Everything that works without thinking when a team shares an office starts failing subtly when it does not: alerts land at odd hours, deadlines get read differently, and requests go out in a language the recipient half understands.

## The four to watch

| What | What happens if ignored | What to do |
| --- | --- | --- |
| The timing of alerts | They go out overnight and get ignored | Schedule to the recipient's working day |
| Language | The request is half understood and half answered | Write to each third party in theirs |
| Public holidays | A deadline falls on a day nobody works there | Count with margin, not with your own calendar |
| Where the data is | It surfaces in the first client questionnaire | Know it and be able to answer in writing |

> [!IMPORTANT]
> The third breaks the most deadlines and is anticipated by nobody. A notice due on the 15th in your calendar may fall on a local holiday in the recipient's country, and a campaign launched during a holiday week there gets half the response with nothing having gone wrong. With distributed teams, margin stops being prudence and becomes a requirement.

## What to decide up front

1. **Which language each third party is written in** — The recipient's, not head office's. It lifts response more than anything else.
2. **Who answers in each time band** — If a client writes at seven their morning, the responder cannot be someone starting six hours later.
3. **What is centralised and what is decided locally** — Above all what documentation is required: if each country asks for its own without criteria, no system will tidy it.
4. **And how deadlines are counted** — Calendar or working days, and against which calendar. Written down, not assumed.

> [!WARNING]
> The point discovered late: **the question of where data is hosted stops being theoretical the moment you have clients or employees in another country**. It is not just a questionnaire box — it can affect what you can promise contractually. Knowing the answer and having it in writing before being asked is the difference between replying in a minute and stalling a negotiation.

## What does not change

**En corto**

- The file is the same for everyone, wherever they are.
- The activity log records the time, so "when was this done" arguments resolve the same way.
- And third parties still enter by their link, with no account and in their own language.

That last is what makes working with suppliers across countries viable without building a structure per country: whoever supplies does not need to understand your organisation, only what you are asking for.

> [!NOTE]
> Obligations about where data is processed and what may be transferred depend on the country and the type of data, and they change. **Confirm that with your adviser**; this only flags that it is a question that will arrive and is worth having an answer ready for.

**Can each user have the interface in their language?**

Yes, and it helps: it cuts interpretation errors in daily work.

**What if the team in another country wants its own organisation?**

It depends on whether someone must stop seeing the other's material; if not, you complicate administration for nothing.

**Do reminders respect the recipient's time zone?**

If scheduled, yes; launched unscheduled, they inherit the send time.

## Ejemplos

**A company with an office abroad launches its annual campaign without checking their calendar.**

- Schedules sends to local working hours and counts deadlines with margin

→ That office's response stops running two weeks behind everyone else's.

**The team is spread across countries and notices arrive at night.**

- Schedules by each person's local time

→ The notice arrives within their working day.

**Each country keeps its documentation separately.**

- Centralises with permissions per team

→ The overall picture exists without mixing.

**Notice languages do not match the recipient.**

- Records each person's language

→ The notice goes out in the right language.

**A local public holiday goes unnoticed.**

- Accounts for each country's calendar

→ Deadlines are set sensibly.

**The same permission criteria apply everywhere.**

- Adjusts to what each team needs

→ Access matches the real work.