Skip to content

Employment change explanation

Use this structured note to explain role/title/location/hours/salary changes and how they align with your occupation code and CoS. Keep the facts consistent with HR records and your uploads.

When to use this

  • Internal progression/promotion with duties still inside the same occupation code.
  • Location or hybrid pattern changes that need clear recording.
  • Salary or hours updates where base pay remains compliant for your code/route.
  • Explaining why a new CoS is or is not required and what sponsor action will be taken.

When not to use this (or use with caution)

  • If duties move into a different occupation code or to a new employer — that often requires a new CoS and application before switching.
  • If compliance is borderline (salary below thresholds, hours cut materially) — get tailored advice and coordinate with HR.

Good practice

  • Map duties old → new in 2–5 bullets; show continuity and scope.
  • State base salary clearly; don’t rely on allowances/bonuses unless the rules allow it.
  • Keep locations accurate; if hybrid/remote, say so plainly and ensure HR records match.
  • Say what action happens next: reporting vs new CoS/application.

Common pitfalls (and quick fixes)

  • Vague duty changes → provide 2–5 concrete bullets showing alignment with the code.
  • Salary confusion → specify base pay and hours; note that figures exclude variable extras.
  • Mismatched records → ensure the note, HR letter, contract variation, and payroll all agree.

Fill in details

Preview

Employment change explanation — Skilled Worker  
Applicant: Jane Maria Smith (DOB: 12 March 1993), passport: 123456789  
Sponsor/employer: Acme Ltd — CoS: A1B2C3D4E5  
Date: 3 October 2025

Summary of change (effective 1 November 2025)
Internal progression reflecting added responsibilities. Core duties remain in software development, architecture input, and mentoring; no material shift outside the current occupation code’s scope.

Current (as per CoS)
• Title: Software Engineer
• Occupation code: 2129
• Base salary / hours: £58,000 / 37.5h/week
• Work location(s): 100 Business Park, London, SW1A 1AA (hybrid)

New / proposed
• Title: Senior Software Engineer
• Base salary: £66,000
• Hours: 37.5h/week
• Work location(s): Same office; hybrid unchanged

Duties alignment
• Development of feature X → expands to ownership of subsystem Y
• Code reviews → adds mentoring two juniors
• On-call rota unchanged
• No shift into unrelated management/HR functions

Location / hybrid context
Primary site remains 100 Business Park, London. Hybrid pattern (3 office / 2 home) unchanged; HR records updated accordingly.

Salary / hours context
Base salary increases to reflect seniority; hours remain 37.5/week. Figures exclude variable allowances and bonuses.

Compliance & sponsor actions
The role remains genuine and at the required skill level. Sponsor records/reporting will be updated as required. Where a new CoS/application is needed, it will be completed before the change takes effect.

Action to be taken
No new CoS required; sponsor will report the change in the sponsor management system within the required timeframe.

Contact for verification
Alex Johnson, HR Manager — hr@acme.co.uk, +44 20 7123 4567

Attachments
• Current CoS summary (PDF)
• Updated job description
• HR letter confirming change & date
• Contract/variation letter
• Payroll note showing base salary

Checklist (copy/paste)

  • [ ] Duties mapped to occupation code; no material drift
  • [ ] Base salary & hours compliant and stated clearly
  • [ ] Location/hybrid recorded and consistent with HR
  • [ ] Action stated (report vs new CoS/application)
  • [ ] Attachments: CoS summary, JD, HR letter, contract variation, payroll note

Information only — not legal advice. Route rules and reporting duties change; confirm your sponsor’s obligations and whether a new CoS/application is required before any change takes effect.

More templates

Browse the full library or jump to another template.

View all

Employer letter for ILR

Ready

Confirm ongoing role, hours, salary and work locations for settlement.

Open

Employment verification (RtW share code cover)

Ready

Cover note that accompanies a Right to Work share code for onboarding.

Open

Visitor invitation letter

Ready

Invite family or friends for a Standard Visitor trip (purpose, dates, stay, support).

Open

Permission to stay at my address

Ready

Short note confirming a visitor can stay with you at your UK address for stated dates.

Open

Address / tenancy confirmation

Ready

Confirm your tenancy/mortgage details and address as accommodation evidence.

Open

Maintenance / support letter (dependants)

Ready

Confirm you’ll cover dependants’ costs and attach matching proof of funds.

Open

Sponsor maintenance confirmation

Ready

Employer confirms maintenance where the route allows sponsor certification.

Open

Proof of funds (supporting letter)

Ready

Explain available funds and match them to attached bank statements / payslips.

Open

Cover note (application clarifications)

Ready

One-pager to explain a name variance, salary rounding, or past refusal context.

Open

Name change statement

Ready

Explain and evidence a change of name; map old/new names across documents.

Open

Employment change explanation

Ready

Explain duty/title/location changes for HR or caseworkers; align with occupation code and CoS.

Open

Change of role letter (internal)

Ready

Internal confirmation of new title/duties/hours/location to keep records consistent.

Open

TB test booking note

Ready

Short note confirming TB test booking/requirement where applicable.

Open

Travel log CSV (absence tracker)

Ready

Download a CSV to track exit/entry dates and reasons — useful for ILR rolling windows.

Open