Sent to Work Somewhere Else

An employee sent by their employer to work temporarily in another country occupies a defined category in several regulatory frameworks, with its own requirements: notification before the assignment, local minimum conditions during it, and documents that must be available at the place of work.

The workflow in “Sent to Work Somewhere Else” becomes more dependable when scheduled work, actual time and later corrections can be distinguished. For teams exploring attendance point system, Monitask resources for attendance point system can provide operational context, while policy ownership, employee explanation and consequential decisions remain with accountable people.

The category is known to specialists and routinely unknown to the manager arranging a three-week installation. The working time element is a small part of a larger obligation and it is the part this collection is about.

For an independent reference relevant to “Sent to Work Somewhere Else”, consult the NSA cybersecurity guidance. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.

When it applies

The triggers differ and the shape is consistent: an employee, employed in one country, performing work in another for a limited period, at their employer's direction.

Thresholds vary and some frameworks apply from the first day. The assumption that a short assignment is below any threshold is the most common error here, and it is an assumption rather than a finding in most organisations.

What matters for the register is identifying the population: who do we send, where, and for how long.

What is typically required

Advance notification to an authority in the host country, in a prescribed form. Application of the host country's minimum conditions during the assignment, which generally includes working time and rest. Documents available at the place of work, sometimes in the local language. And sometimes a local representative.

Each of those has a deadline and a format. Missing the notification is the most common failure and the easiest to avoid, because it is a form submitted before travel.

Which working time rules apply

Generally the host country's, for the duration, where they are more favourable than the home country's. That means a person on assignment may be under different limits, different rest requirements and a different night definition for three weeks.

The organisation's time system will be recording them under their home configuration throughout, which is the practical problem. For a short assignment that may be acceptable with a note; for a recurring pattern it is not.

Record which rules applied and when, because the records for the assignment period may be asked for by the host country rather than the home one.

Who in the organisation knows

Usually nobody in HR, because assignments are arranged operationally. A project manager books travel, a customer expects an engineer, and the arrangement happens through the travel system.

The travel booking is therefore the best available trigger. A rule that any booking for work in another country exceeding a stated duration generates a notification to a named reviewer catches most of the population without anybody having to remember.

It also surfaces the recurring short assignments — the engineer who spends a week a month in a neighbouring country — which are the pattern most likely to cross a threshold cumulatively.

The service company case

Organisations providing services across borders are frequently the ones most exposed, because the whole business model involves sending people.

For them this is not an occasional question but a standing process, and it usually already exists somewhere in the operation — often maintained by a single experienced administrator whose knowledge is undocumented.

Finding that person and writing down what they do is a better first step than building something new, and it is reliably more accurate than anything the centre would design.

The assignment register

Who was sent, where, for how long, which notification was made and when, which working time rules applied during the period, and where the records for it are held.

Six fields per assignment. On most organisations this register does not exist, and constructing it retrospectively for the last year is an informative exercise, because it shows both the volume and the pattern of what has been happening without a process.

Where to get the answer

This is the part of the collection where local advice is least avoidable. The frameworks are technical, the thresholds are specific, and the penalties for the notification failures are real.

What the organisation can do without advice is the preparation: the list of assignments, the durations, the destinations and the current practice. Arriving with that turns an open-ended question into a short, costed piece of work.

The travel booking as the only reliable signal

Nothing else in most organisations captures a short assignment: there is no letter, no HR record and no change to anybody's contract.

The travel system knows, because somebody booked a flight and a hotel against a project code. That booking is the earliest and most complete signal available.

Routing bookings above a stated duration to a reviewer catches the population without anybody having to remember a rule, which is the only arrangement that survives contact with a project manager under deadline pressure.