Turn Right-to-Work checks into one clean evidence packet.
WorkRight helps care, hospitality, cleaning, security, and recruiting teams stop running pre-hire compliance through email threads, photocopies, and spreadsheet memory.
Landing-page validation only. Workflow support, not legal advice or a compliance guarantee.
workright packet
Candidate starts Monday · evidence incomplete
Check route
Online share-code path selected; share code missing from candidate email
Evidence file
Passport scan attached but reviewer note and timestamp are not stored
Recheck date
Time-limited permission may need an expiry reminder before onboarding
Export preview
“Candidate RTW packet includes check route, missing evidence, reviewer sign-off, timestamp, expiry reminder, and retained source files.”
Narrow customer
UK care agencies, hospitality groups, cleaning/security firms, and small recruiters hiring 5-100 frontline workers without compliance ops.
Paid problem
Every hire needs a defensible check path; missing evidence can create penalty, start-date, and reputation risk.
Landing test
Join to test whether a manual-first packet beats email, photocopies, folders, and spreadsheet reminders before integrations exist.
Day-in-the-life pain
A candidate is ready. The evidence trail is not.
A manager needs someone on shift. The candidate sent a share code in one email and a document scan in another. The owner knows a check happened, but the status spreadsheet, attachment folder, reviewer note, and recheck reminder do not agree. WorkRight makes the candidate packet the operational object.
Input
Candidate role, start date, share code or document route, document images/screenshots, reviewer notes, and any expiry date already known.
Checks
WorkRight turns the requirement into a checklist, flags missing evidence, separates candidate messages from reviewer sign-off, and timestamps the decision trail.
Output
A candidate-specific RTW packet: check route, evidence links, reviewer sign-off, expiry reminder, and an export your HR consultant or manager can review.
Why the workaround breaks
Email stores fragments. Compliance needs a packet.
Spreadsheets can say “done,” but they rarely prove who reviewed what, which route was used, what was missing, or when a time-limited permission needs a recheck. The first promise is deliberately narrow: one candidate, one packet, one reviewer trail.
Candidate evidence inbox
Stop mixing share codes, passport scans, screenshots, and manager questions inside long email threads.
Check-route checklist
Guide the reviewer through online share-code, original-document, or IDSP-assisted paths without pretending to provide legal advice.
Expiry and recheck queue
Keep visa/time-limited permission rechecks visible before they become last-minute spreadsheet archaeology.
Audit-ready export
Package evidence, timestamps, reviewer, and decision status into a clean PDF/ZIP for owner, HR consultant, or internal review.
Concierge-first setup
Early users get one real hiring workflow mapped manually before integrations with ATS, payroll, or ID vendors are promised.
Evidence, not proof
The workflow pain is visible. Will small employers join?
Public sources show the manual RTW evidence pattern and official check burden. They do not prove demand. This landing page tests whether operators want a guided packet before buying full HR or ID-verification infrastructure.
Hacker News · builder pain signal
A public HRKYC post describes UK Right-to-Work and ID checks as slow, inconsistent, and still handled through email threads, photocopies, and spreadsheets; it also calls existing tooling fragmented and expensive.
GOV.UK · check paths
GOV.UK describes employer check paths through online share-code checks, original documents, or an identity service provider route — a procedural workflow that has to be completed before work starts.
GOV.UK · penalty risk
Official penalty guidance turns this from admin work into a risk-backed hiring process: employers can face consequences when someone is employed without the right to work.
Research caveat · Reddit blocked
Reddit was searched first, but direct fetches returned network-security blocks in this run. This page cites only sources that were actually accessible and captured.
Objections
Not another folder. Not legal advice.
Why not just use email and a spreadsheet?
That works until a start date is tomorrow, a document is missing, or nobody knows which screenshot proves which check. WorkRight makes the packet the unit of work.
Why not an enterprise HRIS or IDSP?
Those can be right later. This test is for smaller employers that need repeatable evidence before they are ready for heavyweight procurement or API integration.
Is this legal advice?
No. The first product is evidence workflow and reviewer discipline around official check paths, not legal interpretation or a guarantee of compliance.
What about sensitive documents?
Validation starts with redacted or minimal evidence flows and a strict retention/export story before asking for production documents.
Early waitlist
Map one hiring case into a Right-to-Work packet.
Early users get a redaction checklist, one manual candidate-packet review, a recheck-date template, and a short comparison against their current email/spreadsheet process.