Employment Contracts: What Must Be Included (UK & UAE)

If you hire without a solid contract, you’re not being ‘agile’, you’re being exposed. You’ll feel it later, when performance dips, a termination goes sideways, or IP walks out the door. If you want the wider compliance context, read Legal, Risk & Compliance: The Practical Framework Every Founder Needs to Protect Their Business first, then come back here and tighten your hiring.

In this article, we’re going to discuss how to:

Build contracts that meet UK and UAE minimum standards without overlawyering the role
Use simple artefacts and quick tests to validate the job, the pay and the commercial logic
Put guardrails in place that protect IP, confidentiality, margin and your time when things change

Employment Contract Requirements In Plain English

An employment contract is your operating manual for the relationship: what the person will do, what you’ll pay, how you’ll measure it, and what happens when it doesn’t work out. The point isn’t to ‘win’ a future dispute, it’s to stop today’s ambiguity becoming tomorrow’s cost.

When people ask about employment contract requirements, they usually mean two things: what the law forces you to include, and what experienced operators include because they’ve paid the price of not doing so.

Here’s the practical framing I use:

Mandatory: Clauses you must provide by law or regulation in that jurisdiction.
Operational: Clauses that make the role run smoothly in real life (hours, hybrid working, equipment, travel, expenses).
Risk controls: Clauses that protect your work, data, customers and cash (IP, confidentiality, restrictive covenants, termination, deductions).

Quick sense check before you send anything: can a smart stranger read the contract and explain the job, the pay, the probation and how either side ends it, in 2 minutes? If not, it’s not founder ready.

What UK Law Actually Requires (And What It Doesn’t)

In the UK, the big rule is that employees and workers are entitled to a written statement of employment particulars. In practice, founders treat this as ‘your contract must state X’. You can issue it as a contract or a statement, but it needs to be accurate and complete.

For UK employment contract requirements, make sure your written terms cover the core particulars. At a minimum, pressure test that you’ve addressed:

Identity and start date: Employer name, employee name, start date, continuous service date if different.
Job and place of work: Title, duties, location, mobility expectations if relevant.
Pay: Salary or hourly rate, frequency, method, any commission or bonus rules.
Hours and working pattern: Core hours, overtime approach, shift patterns if relevant.
Holiday and leave: Entitlement, holiday year, carry rules, bank holidays approach.
Sick pay: Statutory and any company sick pay, reporting process.
Probation: Length, review points, notice during probation (not legally mandatory, but practically vital).
Notice periods: What you and the employee must give.
Benefits: Pension auto-enrolment, private health, allowances if offered.
Training: Any required training and whether you pay, plus repayment terms if appropriate.
Disciplinary and grievance: Reference to procedures and where they’re found.
Collective agreements: If any apply.

What UK law doesn’t do for you: it won’t save you from vague job scope, undefined variable pay, or a missing IP clause when your first product lead builds something valuable on evenings and weekends.

Practical founder add-ons that pay for themselves fast:

IP assignment (and moral rights waiver where appropriate): Who owns what’s created, during and in connection with employment.
Confidentiality: Define what is confidential, how it must be handled, and that it survives termination.
Data and security: Device rules, password manager requirement, access removal on exit.
Post-termination restrictions: Use carefully, tailored to the role and territory.

What UAE Law Actually Requires (Mainland, DIFC And ADGM)

The UAE is not one system in practice. You’ve got mainland UAE labour law, and you’ve got free zones with their own employment regimes such as DIFC and ADGM. The employment contract requirements differ in detail, and it matters because enforcement, notice, end of service and disputes follow the applicable framework.

At an operator level, you should treat the UAE contract as having three non-negotiables:

Correct jurisdiction and entity: Mainland vs DIFC vs ADGM, plus the employing entity on the visa or work permit.
Clear compensation structure: Basic salary, allowances, variable pay, overtime treatment if relevant.
Clean termination mechanics: Notice, final settlement steps, handover, return of property, access removal.

Founders trip up when they copy a UK template into the UAE and assume it’s ‘close enough’. It usually isn’t, especially around end of service benefits, local regulatory forms, Arabic requirements in some contexts, and what happens if you terminate during probation.

If you’re hiring in the UAE and you’re not 100% sure which regime applies, don’t guess. Cross-reference your overall approach with Legal, Risk & Compliance: The Practical Framework Every Founder Needs to Protect Their Business and align your contract to your actual operating structure.

Data To Gather In 3 Hours Before You Draft Anything

Most contract issues aren’t ‘legal’ issues, they’re missing inputs. Before you write a single clause, gather the data that will force clarity. Do it internal first, then public.

Internal Signals (60 To 90 Minutes)

Pull these from your own systems and conversations:

Work that needs doing: 10 to 20 specific tasks, not a job title. Example: ‘Ship weekly outbound campaigns’, ‘Own renewals for top 20 accounts’, ‘Close monthly books by day 5’.
Success measures: 3 to 5 metrics and the reporting cadence. Example: pipeline created per week, churn %, bugs resolved, NPS movement.
Risk surface: What they’ll touch, such as customer data, payment info, source code, supplier terms, pricing.
Decision rights: Spending limit, signing authority, ability to approve discounts, ability to hire.
Exit realities: What would a safe offboarding look like, including credentials, handover, equipment return.

Public Signals (60 To 90 Minutes)

Then sanity check against the market:

Pay bands: 5 comparable roles, same city or remote market, note base vs variable split.
Role shape: How others define seniority and scope, so your title matches your expectations.
Competitor covenants: If you’re adding restrictions, know what’s typical so you don’t write unenforceable fantasy clauses.

Output: a one-page role brief that feeds directly into the contract. If you can’t write the one pager, you can’t write the contract.

The One-Sentence Offer Template That Stops Negotiation Drift

Most offers go wrong because the conversation is friendly and the paperwork is vague. Use a simple, fill-in template that forces alignment before the contract even lands.

Offer template: ‘We’re hiring you as [Role] starting [Date] on a [Permanent/Fixed term] basis, paid £[X] / AED [X] plus [Bonus/Commission] tied to [Metric], with a [X]-month probation, [X] weeks’ notice after probation, and you’ll be responsible for [3 outcomes] with success measured weekly.’

Send that in writing, then mirror it inside the contract. If the offer and the contract disagree, the deal will wobble later.

Validation In 7 To 14 Days: Test The Role Before You Lock It In

If you’re early stage, you don’t need a 6-month planning cycle, you need proof. Validate the role and the working relationship in days, not months, then formalise.

Here’s a practical path that works without turning you into a bureaucrat:

Day 1: Paid work sample or structured project brief, 2 to 4 hours, scored against clear criteria.
Day 3: References focused on behaviour, not vibes: reliability, response to pressure, quality bar.
Day 7: Trial deliverable in your environment (with limited access), such as fixing 3 bugs, writing a campaign, producing a finance pack.
Day 14: Probation plan agreed: first 30/60/90 days, weekly check-ins, measurable outputs.

Contracts are better when the role is real. Your probation clause should reference review points and expectations, not just a duration.

Pricing, Pay Bands And Unit Economics For Hiring That Doesn’t Break You

Founders often think contracts are just legal paperwork. They’re actually a commercial decision. If you hire someone at a number your unit economics can’t support, no clause will fix it.

Do two quick calculations before you finalise pay and variable structures:

Fully Loaded Cost

Estimate the real monthly cost:

UK example: £60k salary = £5k/month, add employer costs and benefits (use a rough 15% to 25% placeholder if you don’t have exacts), plus tools and kit. You’re quickly at £6k to £7k/month.
UAE example: AED 25k/month package, add visa, medical, onboarding, equipment, and any allowances you’ve promised. Don’t forget time cost of management.

Completion check: if you can’t say ‘this role costs us £X per month all-in’, you’re guessing.

Breakeven Output

Then ask what the person must produce for the hire to make sense:

Revenue role: Required gross profit per month = (Fully loaded cost) / (Gross margin %). Example: £7k cost and 70% gross margin means you need £10k/month new gross profit contribution to break even.
Ops role: Required time saved = (Fully loaded cost) / (Your effective hourly value). If your time is worth £200/hour, a £7k/month role needs to save or create about 35 hours/month of founder time to breakeven. That’s under 2 hours per day.

Now set variable pay with teeth: tie it to outcomes you can measure weekly, and cap it to protect cashflow.

Operational Guardrails That Protect Margin And Time

Contracts fail when your operation is sloppy. You need a few rules that are easy to run every week.

These are the guardrails I’d put in place immediately:

Access by role: Least privilege access, reviewed monthly. New starters don’t get admin rights on day 1.
Company devices and tools: Work stays in company accounts, not personal Google Drives or WhatsApp histories.
Written variations: Any change to role, pay, hours or location must be confirmed in writing within 48 hours.
Performance cadence: Weekly 1:1, monthly scorecard, probation reviews documented.
Exit checklist: Handover notes, access removal, device return, customer comms plan if they were client facing.

These guardrails make your employment contract requirements easier to meet because your paperwork reflects how you actually operate.

Risks And Hedges To Avoid Naïve Mistakes

The biggest risks aren’t dramatic courtroom battles. They’re small leaks that add up, like underperformers lingering, unclear IP ownership, and accidental promises in Slack that contradict the contract.

Here are common founder mistakes and how to hedge them:

Risk: Overpromising variable pay. Hedge: Define the metric, the measurement date, who signs off, and the right to adjust targets on notice.
Risk: Unenforceable restrictions. Hedge: Keep restrictions narrow, role-specific, and time-limited. Use confidentiality and IP controls as your primary protection, not fantasy non-competes.
Risk: Remote work ambiguity. Hedge: Put location, travel expectations, and equipment rules in writing. Specify time zone overlap hours if you need them.
Risk: Data handling shortcuts. Hedge: Add a simple security schedule: device encryption, MFA, approved storage, incident reporting within 24 hours.
Risk: Termination surprises. Hedge: Keep probation meaningful, document feedback, and ensure notice and final pay steps are clear for your jurisdiction.

If you’re running both UK and UAE teams, don’t force a single global contract. Standardise your principles, localise your clauses.

A Do And Don’t Checklist For UK And UAE Employment Contracts

Use this as a final pass before you send the contract out.

Do: Match the contract to the employing entity and jurisdiction, especially in the UAE.
Do: Write scope as outcomes, then list key duties underneath.
Do: Define variable pay with measurable rules and a paper trail.
Do: Include IP, confidentiality and data security expectations in plain English.
Don’t: Copy clauses that you can’t enforce or won’t operationalise.
Don’t: Leave probation vague, it’s your lowest-cost safety valve.
Don’t: Rely on ‘we discussed it verbally’, it won’t scale and it won’t protect you.

Mini Cases From Real Founder Situations

Case 1: UK marketing lead, commission confusion
A founder promised ‘10% on revenue’ in a hiring call, but the contract said ‘discretionary bonus’. Six months later, the hire chased commission on gross revenue, including refunds. Fix: define commission on collected revenue, net of VAT and refunds, with a monthly statement and a disputes window.

Case 2: UAE ops manager, the wrong jurisdiction
A business hired in the UAE but issued a contract from the UK entity. Visa and payroll were under a different entity. When termination came, final settlement became a mess. Fix: align the employing entity to the visa and payroll reality, then mirror notice, benefits and end of service mechanics in the correct form.

Case 3: Remote developer, IP leakage
A contractor moved into an employment role, but the company didn’t update IP assignment terms. A key library ended up sitting in a personal repo. Fix: clean IP assignment and a clear rule that all work product lives in company-controlled systems, with a simple offboarding checklist.

Case 4: Sales hire, unlimited discounts
A new AE offered 30% discounts to close deals, killing margin. No clause covered authority limits, and the founder was travelling. Fix: a contract and policy that sets discount authority thresholds, plus written approval for anything beyond the cap.

Download The Employment And HR Compliance Pack And Tighten Your Contracts

If you want to get this done properly without drowning in templates, download the Employment & HR Compliance Pack (UK/UAE): Hiring, Policies & Legal Basics and use it to standardise your offer process, contract basics and onboarding steps this week.

Write the contract from inputs: Role outcomes, pay mechanics and jurisdiction first, then clauses.
Validate fast: Use 7 to 14 day tests and a real probation plan, then lock the terms in with confidence.
Protect operations: Add IP, confidentiality, data controls and exit steps that match how you actually run the business.

FAQ For Employment Contracts In The UK And UAE

What are the minimum employment contract requirements in the UK?

At a practical level, you need to provide a written statement of key terms, including pay, hours, holiday, place of work and notice. You should also add operational clauses like IP, confidentiality and data security because they prevent expensive grey areas.

Do I need a different contract for mainland UAE vs DIFC or ADGM?

Yes, because the legal framework and processes differ, and enforcement follows the applicable regime. Start by confirming the employing entity and where the employment sits, then use a contract built for that jurisdiction.

Is an offer letter enough, or do I need a full contract?

An offer letter can confirm headline terms, but it won’t usually cover the risk controls and operational detail you need to run a team. If you’re hiring anyone who touches customers, data, code or money, use a full contract and keep the offer aligned to it.

How long should probation be in the UK and UAE?

Probation length is a commercial choice, but it should match the time needed to see real output, often 3 to 6 months for senior roles. More important than duration is having documented review points, measurable outcomes and a shorter notice period during probation where permitted.

Can I enforce non-compete clauses in the UK or UAE?

Restrictive covenants are heavily dependent on how narrowly they’re drafted and whether they protect a legitimate business interest. Keep them role-specific, limited in time and territory, and back them up with strong confidentiality and IP clauses.

What should I include for remote and hybrid working?

Define the work location, required time zone overlap, travel expectations and who pays for equipment and expenses. Add a simple security schedule so remote work doesn’t become a data risk.

How do I change terms once someone is employed?

Don’t rely on informal conversations, confirm any variation in writing and update the contract or issue a written amendment. Operationally, track changes in a single source of truth so payroll, HR and the manager aren’t working off different versions.

What if I’m using an EOR to hire in the UAE?

Your worker’s legal employer may be the EOR, but you still need clear commercial terms, confidentiality, IP handling and operational rules in place. Make sure the EOR paperwork and your internal agreements don’t conflict, especially on IP ownership and offboarding steps.