Part 1

Foundations

What the coordinator role actually is, and the five principles the rest of the guide is built on.

About this guide

The personnel coordinator is the hub of all offshore crewing. It is the coordinator who makes sure the right person, with the right competence and valid certificates, is standing at the right heliport at the right time. When this works, nobody notices. When it fails, it costs money, trust and in the worst case safety.

The guide covers two realities that often sit side by side in the same company:

  • Fixed rotation, where personnel work known patterns and the plan can be set months ahead.
  • Job-driven crewing at short notice, typical of service companies in well services, inspection, maintenance campaigns and specialist work, where a confirmed job can arrive with weeks, days or hours of notice because the timing is set by rig schedules, operational progress and weather windows.

The principles are the same in both modes. What changes is when the work is done: at short notice, everything that can be prepared has to be done before the job exists. Chapter 4 is given over to this.

The guide covers the full breadth of the coordinator role: the daily lifecycle from plan to time off, the employee's journey through the operator's systems, the special cases (first-time travellers, international assignments), what has to be in place when something goes wrong (emergency preparedness, on-call rota), the documentation that has to stand up to inspection and audit, and what builds trust over time (pay, welfare). It is written for Norwegian conditions, but the principles apply equally to onshore rotation, workshop crewing and international operations. It can be used as training material for new coordinators, as a day-to-day reference, and as the basis for building your own routines and checklists.

The guide is tool-neutral. Where it sets requirements for what "the system" must be able to do, the requirement holds whether the system is a spreadsheet, an inbox or a platform. What matters is not which tool is used, but whether the requirements are actually met, every day, including when key people are ill or on holiday. Appendix E is a self-test for exactly that.

How to read "should" in this guide. Where it says something should be done, that is the guide's recommendation for what a good routine requires. It is not the same as a legal requirement. Where something genuinely follows from law, regulation or a tariffavtale (collective agreement), the text says so explicitly and names the source, and uses "must". Everything else is experience set down as routine, and you can choose differently as long as you know that you are doing so.

The guide is not legal advice. The requirements depend on the type of business, the agreement area and your contracts, and they change. Always verify against current regulations, your own collective agreement and legal counsel where relevant before building a routine on anything you read here.


1. The coordinator role: more than logistics

A personnel coordinator connects the calendar, certificates, ID and helicopter travel for an offshore worker.

A good personnel coordinator does three jobs at once:

Logistician. Rotation plans, travel, hotels, helicopter bookings, POB registration and documentation have to be right, every time.

Compliance checkpoint. The coordinator is often the last line of defence before someone is mobilised without a valid helseattest (offshore medical certificate), with an expired safety course, or in breach of the rest-period rules. Errors here are not merely impractical; they can be regulatory breaches with consequences for both the company and the employee.

Relationship builder. For the employee, the coordinator is often the most important face of the employer. Personnel who experience predictability, respect for their time off and clear communication are the ones who stay. In a market where experienced offshore workers are scarce, good coordination is a competitive advantage in recruitment and retention.

The role also has a fourth dimension that rarely appears in the job description but matters more than any of the others: the coordinator's data is the basis for emergency preparedness. Who is on board, where they are, and who to notify if something happens is information that has to be correct every single minute, not only when things are quiet. Chapter 11 is about this.

Everything in this guide rests on these roles being connected. Precise logistics without good communication produces unhappy employees. A good manner without control of compliance produces risk.


2. Five basic principles

These principles recur through every phase described later in the guide, whether the notice is three months or three hours.

2.1 Be proactive, never reactive

The employee should never have to ring and ask "when am I going out?" or "have you booked a hotel?". All the information the employee needs should arrive unprompted and as early as the situation allows. Every incoming query about something the coordinator ought to have communicated is a signal that the routine has a hole in it. At short notice, being proactive also means flagging likely jobs before they are confirmed (see 4.3).

2.2 One source of truth

The rotation plan, mobilisation details and certificate status should exist in one place that both the coordinator and the employee can reach. When the plan lives in a spreadsheet held by the coordinator, an email thread held by the employee and a whiteboard in the office, discrepancies appear. When something changes, update the source first and notify the employee second. Never the other way round.

2.3 Close every loop with a confirmation

Sent is not the same as received, and received is not the same as understood. All time-critical information should be actively confirmed by the recipient. "Confirm that you have received the mobilisation letter" is not bureaucracy; it is the only way to know that the person is actually coming. Unanswered notices should be followed up against a defined deadline, not assumed to be fine. The shorter the notice, the shorter the deadline and the faster the escalation to a phone call.

2.4 Respect time off

Time off belongs to the employee. Contact during time off should be limited to what has been agreed or is strictly necessary: confirmation of the next assignment, time-critical changes, and requests the person has made themselves. Course bookings, appraisals and administrative tasks belong in the work period as a rule, or should be agreed explicitly. In job-driven operations, where the line between "time off" and "available" is less sharp, this principle matters more rather than less: availability should be agreed and compensated, not assumed (see 4.2). Companies known for chasing people outside agreed hours lose them.

2.5 Everything in writing, everything traceable

Verbal agreements about mobilisation dates, extensions or shift swaps should always be confirmed in writing the same day. At short notice the phone comes first, but the written confirmation follows immediately after. In a dispute, an inspection or a pay disagreement, the documentation is decisive. Putting it in writing protects both parties.