UN compensatory time off and overtime explained

A staff member asked to stay late for a mission deadline or a weekend deployment often assumes the extra hours simply disappear into the job. Sometimes that is true — and sometimes it isn't. The UN common system draws a sharp line between categories on this point: whether extra hours become overtime pay, compensatory time off, or nothing at all depends heavily on grade, not on how hard the assignment was. This guide explains the general pattern, why it exists, and what to actually do when you are asked to work beyond your normal schedule.

The line that matters: General Service vs Professional

Across most of the common system, overtime — paid extra compensation for hours worked beyond the normal schedule — is generally available to the General Service category and related locally recruited categories such as security and trades and crafts staff, when the extra hours are officially required and authorized in advance. Internationally recruited Professional and higher-graded staff are, as a general rule, not entitled to overtime pay at all. The underlying logic organizations apply is that a Professional post's base salary already reflects a level of responsibility that includes some variable, unscheduled extra effort — the post is priced for outcomes, not clocked hours.

What Professional staff get instead: compensatory time off

The absence of overtime pay does not mean unlimited unpaid extra hours are simply expected without any recognition. Many organizations allow supervisors to grant compensatory time off (CTO) — additional paid time off, not cash — to Professional staff who have worked substantial, sustained extra hours under exceptional circumstances: an intense mission surge, a crisis response, or a sustained period covering an unfilled post. CTO is discretionary and tied to the specific circumstances, not a running ledger every late evening feeds automatically. A single late night rarely qualifies; a sustained multi-week stretch of genuinely extended hours, properly documented, is the more typical trigger.

Approval has to come first, not after the fact

The detail that catches people out is sequencing: in most organizations, both overtime and CTO require the extra hours to be officially required and, ideally, authorized by a supervisor in advance — not simply logged afterward because the work happened to run long. Showing up voluntarily on a weekend without being asked, or staying late by personal choice rather than operational need, typically does not generate a CTO or overtime claim on its own. If a deadline genuinely requires extra hours, the practical move is to flag it to your supervisor as it is happening, not to assume the record will speak for itself later.

CTO usually has to be used within a limited window

Where CTO is granted, it is typically meant to be taken as time off within a defined period afterward — commonly framed in months rather than treated as an indefinite balance — after which an unused balance can lapse rather than convert to pay or carry forward indefinitely. This is a different mechanism from annual leave, which accrues and carries over under its own separate rules. Because the exact window, approval chain and documentation requirements are set by each organization's own administrative issuances rather than one common-system-wide number, confirm the current rule with your HR or administrative office rather than assuming the pattern from one organization applies at another.

Related but distinct: night differential and standby duty

Two adjacent concepts are worth not confusing with overtime. Night differential is a separate additional payment some organizations apply to General Service staff for hours worked during defined night periods, independent of whether those hours were also "extra" in the overtime sense. Standby or on-call duty — being required to remain reachable and available to respond outside normal hours, without necessarily being called in — is typically compensated through its own distinct allowance or arrangement rather than through the overtime or CTO mechanism, and is more common in duty stations with field or security operations running around the clock.

What this means in practice

• Know your category first. Whether you can realistically expect overtime pay, CTO, or neither starts almost entirely with whether you sit in the General Service or Professional category, not with how demanding a specific assignment feels.
• Get extra hours authorized before, not after. A conversation with your supervisor when the extra-hours need becomes clear is what actually creates a claim; a personal log kept after the fact usually is not enough on its own.
• Use CTO inside its window. Treat a granted balance as something with an expiry, and schedule it rather than letting it sit unused until it lapses.
• Check your organization's own administrative issuance. The pattern above holds broadly across the common system, but the specific eligibility thresholds, approval levels and time windows are set individually — ask HR for the current instruction rather than relying on a colleague's experience from a different duty station or agency.

None of this is unusual to ask about before or after accepting an offer — it's routine administration, not a red flag to raise cautiously. Current openings across the UN system are on the board, and a free changemaker profile keeps the details that matter to you organized alongside every offer you compare.