Case study · Software

LicenceGuard, the multi-tenant compliance and HR platform for UK licensed sponsors: deadlines that chase themselves

LicenceGuard is a multi-tenant platform for UK employers who hold a sponsor licence. It tracks right to work and Disclosure and Barring Service checks, Home Office sponsor duties and mandatory training, and emails the right person before each deadline lands. ILMOTECH designed and built the whole product end to end: the architecture, the backend, the encrypted file service, the web app, payroll, the AI help assistant, the cloud infrastructure and the deployment pipeline.

Client
LicenceGuard, in partnership
Timeline
2026 to present
Role
End-to-end design and build, led by Sikandar Waheed
Stack
NestJS, TypeORM, PostgreSQL, Redis, BullMQ, Next.js
The LicenceGuard Compliance Hub for a demo care provider: a 97% organisation compliance score, a low, medium and high risk split across 51 employees, and the sponsor licence card, with the compliance modules in the sidebar

The challenge

A UK employer that sponsors overseas workers carries duties that do not forgive a missed date. The sponsor licence has to be renewed. Changes have to be reported to UK Visas and Immigration inside a window counted in working days. Every worker's right to work has to be checked, recorded and re-checked before it lapses. Disclosure and Barring Service certificates, mandatory training and role reviews all expire on their own schedules. Getting any of it wrong risks the licence itself, and with it the ability to employ the people the business already depends on.

Most teams track this in spreadsheets and calendar invites, which fail quietly. The record says a check was done; nobody notices that the visa behind it expires in three weeks. So the platform had to do more than store the data: it had to know what was coming due, work out who could actually do something about it, and tell them in time.

On top of that it is a multi-tenant product. Many organisations share one system, each needing certainty that their people data is isolated, that every change is attributable, and that nothing is ever silently lost.

Approach

The compliance side is built around a nightly sweep rather than a dashboard nobody opens. Each family of obligations carries its own reminder cadence, because the urgency genuinely differs: a sponsor licence is renewed over months through the Home Office, so it warns at ninety, sixty and thirty days, while right to work and Disclosure and Barring Service expiries warn at sixty, thirty and seven. Mandatory training, which is usually a same-week fix, warns at thirty and seven.

Two things stop the reminders becoming noise or becoming silence. Each notice is aimed at an audience that can act on it: the employee hears about their own expiring document, while duties that belong to the organisation go only to the administrators, because telling someone about a deadline they are powerless to meet is how people learn to ignore a channel. And once a date has passed, overdue reminders fire from the date itself, on a schedule held in code that an organisation cannot turn off. Cadences are theirs to tune; the compliance family cannot be silenced.

The Disclosure and Barring Service check register, showing each person's check level, certificate number, status, issue date and valid-until date, with pending, completed and overdue counts above the table
Disclosure and Barring Service checks move through a status workflow, and anything past three years surfaces as overdue. Demo data throughout.
The right to work register: totals for overdue, due soon, scheduled and completed checks and follow-ups, above a list of employees with their department, status, last check and next check dates
Right to work checks carry their own next-check and follow-up dates, so a time-limited permission is chased before it lapses.

There is also a monthly report for the opposite problem: not what has a date, but what is missing. An active employee whose right to work was never checked, or whose check failed and therefore left no expiry date behind, appears on no dated reminder at all. That report is the surface that catches them.

Sponsored workers carry the most detail of all. Each record holds the Certificate of Sponsorship, the occupation code, the immigration route and the permission dates, and checks the salary against the minimum that applies to that worker, so a pay change that would breach the route shows up on the record itself.

A sponsored worker's record on the Sponsorship tab: a meets-minimum salary badge, the Certificate of Sponsorship number, occupation code, job title, immigration route, weekly hours and permission start and expiry dates
A sponsored worker's record, with the salary checked against the minimum for that worker. Demo data throughout.

Architecture

  • A NestJS modular monolith of seventy-four modules over PostgreSQL, from right to work and Disclosure and Barring Service checks, sponsor licence and key personnel records, Sponsorship Management System duties and role reviews, through to leave, payroll, HMRC Real Time Information submissions and onboarding.
  • Multi-tenancy as a shared schema with an organisation discriminator, enforced in one place rather than in every query, with the tenant always resolved from request context and never from the request body.
  • Auditing and history written by entity subscribers, not by hand: every core table has a history twin that receives an append-only copy of each version, created in the same migration as the table it mirrors.
  • Permissions resolved per request from the database, never serialised into tokens, so a change to someone's role takes effect immediately. The backend also returns the filtered menu, so the interface cannot offer what the guards would refuse.
  • Redis and BullMQ for the reminder sweep, digests and exports, so nothing slow runs inside an HTTP request. The sweep matches a reminder offset exactly on the day, which makes it idempotent without a ledger table to keep in step.
  • A separate file service holding documents under envelope encryption, reached through short-lived signed URLs. It knows nothing about users or roles; the main backend stays the single access authority.
  • A Next.js front end with a typed API client generated from the backend's OpenAPI specification, so any drift between the two fails at compile time.
The pay runs list: draft, calculated, awaiting signature, approved and paid counts with gross pay for the tax year, above monthly runs showing period, pay date, status, employee count, gross and net
UK payroll runs from draft through calculation, sign-off and payment, with PAYE and National Insurance worked out per payslip. Demo data throughout.

Results

LicenceGuard is live at licenceguard.co.uk, where UK employers can start a free trial. The compliance engine runs in production: the reminder cadences, the split between employee and administrator audiences, the unsilenceable overdue notices and the monthly gap report, backed by more than three thousand end-to-end tests across the API.

The platform also chooses sponsor duties from each organisation's industry and licence routes, with reporting deadlines counted in working days, and every account includes Ask LicenceGuard, an AI help assistant that answers from the product's own guides for the role of whoever is asking.

Figures on adoption and on deadlines met will be published once there is enough real use to report them honestly.

  • 3,000+
    End-to-end tests guarding the API
  • 74
    Modules, from right to work checks to payroll
  • 0
    Hard deletes: every record is soft-deleted and audited
  • UK GDPR
    Built for UK GDPR: personal data is anonymised on erasure and never used for our own purposes
  • Encrypted
    Security by design: documents under envelope encryption behind short-lived signed links, permissions checked on every request, and every change audited
Back to all work
Next projectOrder and campaign automation on a 14M-user platform

Have a similar challenge?

Book a call and we will walk through how this would apply to your situation.