UK eVisa + Share Codes: Right to Work & Right to Rent (Doctor Edition): IMG guide for UK practice (2026)

Key points

A share code lasts 90 days. Generate it when you’re ready to pass checks (offer stage / tenancy referencing), not weeks before.
If you have a BRP, you may still be able to use it for online right-to-work share codes for a period after the expiry date printed on the card—check the official wording and don’t assume.
Treat UKVI access as mission critical: keep your sign-in method stable, update your details early, and always know the “report an error” route.

For most IMGs, the single biggest non-clinical blocker to starting work (or renting) is a simple one: your employer/landlord needs you to prove status digitally, and you generate the proof at the wrong time (or with the wrong account details). This page gives you the practical workflow so you don’t lose weeks to “computer says no”.

The hidden failure mode

If you change passport/phone/email and don’t update your UKVI account before generating share codes, you can lock yourself into repeated verification loops. Do account hygiene first, then produce the code.

Step 1 — Identify which proof route you’re using

There are multiple online routes (eVisa/UKVI account, right-to-work service, right-to-rent service). Don’t guess. Use the official “View eVisa + get share code” flow if you have an eVisa; use the right-to-work flow if requested by HR.

Step 2 — Stabilise your UKVI sign-in method

Before you generate anything, confirm you can reliably sign in (same phone/email access). If your number changed, fix access first. Share codes are easy—account recovery is the time sink.

Step 3 — Generate the correct share code (work vs rent)

Generate a share code specifically for the check being performed. If you’re doing both employer and landlord checks, generate separate codes close to when you’ll actually submit them.

Step 4 — Time it properly (avoid “expired code” churn)

Share codes expire. If you generate early and the trust/agency delays checks, you create unnecessary back-and-forth. Generate when HR sends the pre-employment checklist or when referencing starts.

Step 5 — Provide what the checker needs (not more)

The checker typically needs the share code + your date of birth. You generally do not need to share screenshots of sensitive pages unless explicitly requested.

Step 6 — If the checker can’t validate, escalate the right way

Ask HR to use the official checker service and confirm they’re entering the details exactly. If the issue is your eVisa record, use the official “report an error” route rather than emailing random inboxes.

Step 7 — Keep a simple audit trail

Maintain a minimal log: date code generated, who it was sent to, and whether it validated. This prevents circular email threads and speeds re-issue if needed.

Doctor-specific nuance

Trust onboarding often involves multiple systems (NHS Jobs/TRAC + local HR + lead employer). It’s common to be asked for status proof more than once. That’s normal—plan for repeat share code generation.

SourceGOV.UK: Prove your right to work (overview)

Open Link

SourceGOV.UK: Get a share code to prove right to work

Open Link

SourceGOV.UK: View your eVisa and get a share code to prove immigration status

Open Link

SourceGOV.UK: Employer/landlord check service (share code check)

Open Link

Your learning path

Save your place and choose what comes next

Work through this guide (7 steps)

Use the actions from this article to track what you have worked through.

Step 1 — Identify which proof route you’re using
There are multiple online routes (eVisa/UKVI account, right-to-work service, right-to-rent service). Don’t guess. Use the official “View eVisa + get share code” flow if you have an eVisa; use the right-to-work flow if requested by HR.
Return to this section
Step 2 — Stabilise your UKVI sign-in method
Before you generate anything, confirm you can reliably sign in (same phone/email access). If your number changed, fix access first. Share codes are easy—account recovery is the time sink.
Return to this section
Step 3 — Generate the correct share code (work vs rent)
Generate a share code specifically for the check being performed. If you’re doing both employer and landlord checks, generate separate codes close to when you’ll actually submit them.
Return to this section
Step 4 — Time it properly (avoid “expired code” churn)
Share codes expire. If you generate early and the trust/agency delays checks, you create unnecessary back-and-forth. Generate when HR sends the pre-employment checklist or when referencing starts.
Return to this section
Step 5 — Provide what the checker needs (not more)
The checker typically needs the share code + your date of birth. You generally do not need to share screenshots of sensitive pages unless explicitly requested.
Return to this section
Step 6 — If the checker can’t validate, escalate the right way
Ask HR to use the official checker service and confirm they’re entering the details exactly. If the issue is your eVisa record, use the official “report an error” route rather than emailing random inboxes.
Return to this section
Step 7 — Keep a simple audit trail
Maintain a minimal log: date code generated, who it was sent to, and whether it validated. This prevents circular email threads and speeds re-issue if needed.
Return to this section

United Kingdom · Visas · Article 1 of 7