HR Outsourcing SLA & Governance Checklist for UAE Businesses

An HR outsourcing proposal can look clear until work begins. The fee is visible, the service list sounds comprehensive and both sides assume they understand what “managed HR” means. Then the first urgent employee matter arrives, payroll inputs are late, a manager expects advice outside the agreed remit, or the provider needs a decision that nobody owns.

The weakness is rarely the absence of a long contract. It is the absence of an operating model.

A useful HR outsourcing agreement should make five things explicit before mobilisation: what the provider will deliver, which decisions remain with management, what information must move between both sides, how service quality will be measured and how exceptions will be escalated. This guide gives UAE leadership and finance teams a practical structure for doing that work.

It is designed for managed HR and embedded people-operations arrangements. It is not a substitute for legal advice, and it should be adapted to the company’s licence, workforce, locations, systems and risk profile.

Start with three layers, not one service list

Most scopes describe activities: contracts, employee queries, payroll coordination, onboarding, policies or performance cycles. Activities matter, but they are only one layer.

A workable operating model has three connected layers:

1. Decision rights — who recommends, decides, approves and communicates.

2. Service catalogue — what work is included, excluded and triggered by an additional instruction.

3. Service controls — response standards, input deadlines, quality checks, reporting, escalation and review.

If one layer is missing, the arrangement becomes dependent on goodwill and memory. That may survive quiet weeks. It usually fails when the business is growing, restructuring or handling a sensitive employee issue.

For an overview of the delivery model, see element’s managed HR outsourcing service. If the business is still deciding whether it needs a project or an ongoing operating partner, use the HR consulting versus HR outsourcing decision framework first.

1. Define the service boundary in operational language

Avoid headings such as “employee relations support” without describing what the support includes. A better scope identifies the trigger, provider action, client input, output and decision owner.

For example:

• Trigger: a manager reports a conduct or performance concern.

• Provider action: clarify the issue, assess the process required, prepare the manager, draft documentation and maintain the case record.

• Client input: facts, prior records, manager availability and the authorised decision maker.

• Output: a recommended process, documents, meeting support and a case log.

• Decision owner: the authorised company leader, with legal advice obtained where required.

Build the catalogue across the work the company actually needs. Typical areas include employee lifecycle administration, contracts and letters, onboarding and exits, HR queries, leave administration, payroll-input governance, employee relations, performance cycles, policy operation, management reporting and workforce planning.

Then state exclusions. Common exclusions include legal representation, immigration processing, medical or occupational-health decisions, benefits brokerage, recruitment fees, payroll funding, government fines, specialist investigations and major organisation-design projects unless expressly included.

An exclusion is not a weakness. An undisclosed exclusion is.

2. Set decision rights before the first difficult case

Outsourcing HR does not outsource management accountability. Line managers still lead their teams. Executives still make material people decisions. The provider supplies infrastructure, judgement, process discipline and delivery capacity.

Create a simple responsibility map for recurring decisions:

• Who approves a new position and budget?

• Who approves an offer outside the salary range?

• Who decides the outcome of a disciplinary or grievance process?

• Who approves a payroll cut-off exception?

• Who signs employment documents?

• Who owns communication during restructuring?

• Who can instruct the provider to start additional work?

Use four roles where helpful: responsible, accountable, consulted and informed. The label matters less than naming one accountable person for each decision.

The chief executive should not become the default approver for every letter, and the provider should not become the de facto employer. A good model moves routine work quickly while reserving high-consequence decisions for the right leadership level.

3. Design service levels around business risk

An SLA should not promise that every request is urgent. It should classify requests so the provider can respond proportionately.

Use three or four service tiers. For example:

• Critical: an immediate employee-safety concern, active workplace crisis, payroll failure affecting a material group or another issue requiring same-day triage.

• High: a time-sensitive employee-relations matter, executive hire, regulatory deadline or business decision that will be delayed without HR input.

• Standard: routine letters, employee queries, onboarding steps, reports and scheduled policy or performance work.

• Planned: organisation design, workforce planning, capability programmes and other work delivered through an agreed project plan.

For each tier, define:

• acknowledgement time;

• time to first substantive response;

• target resolution or agreed action plan;

• information the client must provide;

• working-hour and out-of-hours rules;

• escalation point when the target cannot be met.

Measure quality as well as speed. A fast response that creates rework is not good service. Useful measures can include first-time-right documents, payroll-input accuracy, open-case ageing, onboarding completion, manager satisfaction, overdue approvals, policy exceptions and action-plan closure.

Do not copy generic SLA times into the agreement. Set standards the provider can operate and the company can support. If managers routinely submit incomplete inputs after the cut-off, the SLA must show how the clock pauses and how exceptions are handled.

Make the service report auditable

Agree the reporting cohort before comparing percentages: which requests were due in the period, which required inputs were complete, and which clock rules applied. Keep acknowledgement, substantive response and resolution as separate measures.

Illustrative example—not an element service result or industry benchmark: 100 requests are due for review; 80 have complete inputs and 20 are waiting for named client actions. If 72 of the 80 eligible requests meet the agreed standard, eligible-request performance is 90%. The report must still show the eight missed standards and the 20 blocked requests. Reporting only “90% achieved” conceals work that remains unresolved.

For each blocked or overdue request, record its age, the missing input or failure, the accountable owner, the next action and the escalation date. Preserve the original receipt time and any authorised clock pause so a case cannot be made to look timely by resetting its history.

Ask the service owner and client sponsor to review a small sample against the underlying records. If reported performance improves while rework, repeated queries or old cases increase, investigate the definitions before concluding that service quality has improved.

4. Make input obligations visible

Service failure is often an information-flow failure. The provider cannot prepare an accurate contract without approved terms, run a clean payroll-control process without complete inputs or close a case without management evidence.

For each recurring process, identify:

• the required input;

• its owner;

• the format or system;

• the cut-off;

• the validation check;

• the consequence of a late or incomplete input.

This should be especially clear for payroll inputs, new joiners, exits, variable pay, leave, attendance, employee master data and management approvals.

A shared tracker is useful only when it has named owners and ageing rules. Avoid creating a second system of record that conflicts with the company’s HR platform, payroll system or controlled employee files.

5. Establish data and document controls

The operating model should state where employee data is stored, who can access it, how documents are approved, how information is transferred and what happens when the engagement ends.

Confirm at least:

• the system of record for employee and case data;

• access roles and approval authority;

• secure transfer methods;

• version control for policies and templates;

• retention and deletion responsibilities;

• handling of sensitive medical, grievance and investigation information;

• incident notification and escalation;

• export and handover requirements at exit.

The provider should use the minimum information needed for the task. Sensitive case files should not sit in broad shared folders or routine email chains. Access should follow role and purpose, not convenience.

6. Create a governance rhythm that produces decisions

Governance is not a monthly presentation. It is a decision mechanism.

A practical rhythm may include:

• Weekly operating review: new joiners, exits, employee cases, payroll inputs, overdue actions and decisions required.

• Monthly service review: volumes, SLA performance, recurring failure points, workforce movement, manager dependencies and improvement actions.

• Quarterly people review: workforce plan, organisation risks, capability, succession, engagement, cost and priorities for the next quarter.

Each forum should have a standard pack, named chair, decision log and action owners. Remove metrics that do not change a decision.

The dashboard should separate provider performance from client dependencies. Otherwise both sides debate who caused the problem instead of correcting the process.

7. Write the escalation route before you need it

An escalation model should answer four questions:

1. What event triggers escalation?

2. Who is contacted first?

3. What information must be provided?

4. Who can decide the resolution?

Triggers may include a missed critical deadline, repeated quality error, unresolved management dependency, data incident, serious employee allegation, payroll-impacting exception or work outside scope.

Escalation should not be treated as failure. Early escalation is a control. The failure is allowing a known risk to age without a decision.

Include a route for commercial scope questions as well as operational incidents. If new work repeatedly enters through informal requests, the arrangement will become expensive and unclear for both sides.

8. Mobilise through a controlled 30/60/90 transition

Do not switch responsibility on the contract start date without a mobilisation plan.

The 30/60/90 sequence below is an illustrative planning structure, not a universal implementation timetable or a promised completion date. Agree the pace after checking data readiness, open cases, systems access, decision authority and internal capacity. Move between phases when the relevant controls work; record any unresolved dependency rather than treating the calendar as proof of readiness.

Days 1–30: discover and stabilise. Confirm workforce data, open cases, payroll calendar, templates, approvals, systems, statutory or licence-specific requirements, immediate risks and the first service catalogue. Resolve critical gaps before optimising the model.

Days 31–60: operate and control. Start the agreed processes, test approvals and hand-offs, run the first service review, refine the SLA and establish the case and action trackers.

Days 61–90: embed and improve. Close transition gaps, train managers, agree the quarterly people agenda, baseline service measures and move from reactive delivery to planned workforce priorities.

The 90-day HR outsourcing transition plan provides a fuller mobilisation sequence.

9. Align pricing with the operating model

Compare proposals on scope and assumptions, not headline fee alone.

Ask providers to state:

• workforce and entity assumptions;

• included locations and employee groups;

• expected service volumes;

• included senior advisory time;

• system and payroll responsibilities;

• implementation or mobilisation fees;

• out-of-scope rates and approval rules;

• third-party costs;

• annual review or volume-adjustment mechanism;

• exit and handover support.

Two proposals can use the same phrase—“full HR outsourcing”—while pricing very different work. The UAE HR outsourcing cost and scope benchmark explains how to compare those differences.

10. Protect continuity at exit

An outsourcing relationship should be designed to end cleanly, even when both sides expect it to continue.

Define ownership and handover for employee files, templates, case logs, calendars, payroll-control records, system access, reports, open actions and knowledge held by named practitioners. State the required format, timing and support period.

Avoid arrangements where essential knowledge lives only in one person’s inbox. Continuity is part of service quality.

The 25-question buyer checklist

Use these questions before approving an HR outsourcing proposal.

Scope

1. Which employee groups, entities and locations are covered?

2. What recurring processes are included?

3. What is explicitly excluded?

4. What volume assumptions underpin the fee?

5. How is additional work authorised?

Decisions and accountability

1. Which decisions remain with executives and line managers?

2. Who can instruct the provider?

3. Who signs employment documents?

4. Who decides employee-relations outcomes?

5. Where is specialist legal or other advice required?

Service levels and quality

1. How are critical, high, standard and planned requests classified?

2. What are the acknowledgement and response standards?

3. When does the service clock pause for missing inputs?

4. Which quality and ageing measures will be reported?

5. What happens after a repeated service failure?

Information and systems

1. What is the system of record?

2. Who owns each input and cut-off?

3. How is sensitive information protected?

4. How are versions, approvals and access controlled?

5. What data and documents are handed back at exit?

Governance and change

1. What weekly, monthly and quarterly forums will run?

2. Which decisions must each forum make?

3. How are risks and dependencies escalated?

4. What is the 90-day mobilisation plan?

5. How will scope, workforce volume and pricing be reviewed as the business changes?

Five warning signs in an outsourcing proposal

• The scope is a list of broad HR headings with no outputs or exclusions.

• The provider owns every action but the company’s decision responsibilities are absent.

• Service levels measure response speed but not quality, ageing or client dependencies.

• The proposal jumps from signature to steady-state delivery with no mobilisation plan.

• Data ownership, access and exit handover are left for later.

None of these automatically makes the provider wrong. They mean the operating model is unfinished.

What a strong proposal should leave you with

By the time the arrangement is approved, a leadership team should be able to answer:

• what the provider will do each week and month;

• what managers and executives still own;

• how urgent and routine requests move;

• where employee information and decisions are recorded;

• how service quality and workforce outcomes are reviewed;

• how the model changes as the business grows;

• how the company remains in control if the provider changes.

That clarity is the difference between buying HR activity and installing a dependable people operating capability.

If you are reviewing an outsourcing proposal or replacing a fragmented HR model, request a senior business conversation with element. Bring the current scope, workforce profile and the three issues that create the most management drag. We will help you diagnose the operating requirement before discussing a solution.

To connect service governance with the wider people operating model, explore the element knowledge hub. Start with the business decision and identify the right guide before selecting a service.