A system that survives its author
Documented, owned and operable by whoever holds the role next, not only by the person who built it.
Corporate immigration
Compliance systems.
A sponsor licence is not kept by having applied successfully. It is kept by an organisation doing a set of unglamorous things consistently, usually while nobody is watching, for as long as it employs sponsored people.
What this looks like when it goes wrong
The commonest version is a system that depends on one person. Somebody in HR understood it, built a way of doing it and held most of it in their head. They left, and what remains is a folder nobody can explain and a set of tasks that quietly stopped happening. Nothing looks wrong from the inside.
The next is checks that were done and cannot be shown. The organisation genuinely looked at documents for everybody it hired, and it did not keep them in the way required, or did not record when it looked, or did not repeat the exercise where the rules expect repetition. Having done the right thing and being able to prove it are separate achievements, and only one of them counts.
Then there is the change that was never reported. Somebody's role, pay, location or working pattern changed, an employee left, a project ended, or the business moved premises. Reporting obligations attach to changes of that kind, and the ordinary HR process does not know about them. The failure is not misconduct. It is an information flow nobody built.
The quietest version is a workforce that has moved on without anybody tracking it. Permissions come to an end, and an organisation that is not monitoring them is relying on individual employees to manage something the employer is responsible for. Continuing to employ somebody without the permission they need is a serious position for a business to be in, and it is reached by inattention rather than by intent.
What actually decides it
The obligations attach to the organisation, not to a department. Duties around checking permission to work, keeping records, monitoring the workforce and reporting changes sit with the sponsor as a whole. The rules setting out what is required are guidance that is revised frequently, so a system built to one version of it needs somebody responsible for noticing when it moves.
Checking has to be done in a way that gives the employer protection. There are prescribed ways of establishing that a person may work, and following one of them properly is what stands between the organisation and liability if it later turns out that somebody could not. Doing something reasonable that is not the prescribed thing does not achieve the same result. What the prescribed routes are has itself changed more than once and should be checked.
Reporting is really about information reaching the right person while it still matters. Most reporting failures happen because a line manager made a normal decision, a payroll change went through, or somebody resigned, and nothing in the process told whoever holds the licence. The fix is rarely a new policy. It is a trigger inside the systems the business already uses.
Then there is evidence. Every part of this is assessed on what the organisation can produce, in order, on request. Files that are complete, dated and consistent are the difference between a routine visit and a difficult one. Where records are partial, the organisation is left arguing about what it probably did, which is a poor position from which to defend a licence.
What we do
Checking permission to work
Done in a way that protects the employer, and recorded so it can be produced without a search.
Reporting triggers
The events that have to be reported wired into the HR and payroll processes that already exist.
Monitoring the workforce
Permissions, changes and departures tracked by the organisation rather than left to individuals.
Training the people who decide
Line managers and HR who know which ordinary decisions carry consequences for the licence.
Records that can be produced
Files kept so the organisation can show what it did and when, without reconstructing it later.
When to spend nothing
An organisation with a small sponsored workforce does not need a compliance function. It needs a named owner, a checklist that matches the rules as they currently stand, and a diary. Much of what is sold as a compliance programme is documentation, and documentation is not usually what fails. What fails is that nobody was told when something changed.
It is also worth being clear that software does not discharge the duty. Systems help with reminders and storage and they decide nothing. Where an organisation is choosing between buying a platform and giving somebody the time and the authority to run this properly, the second is the better purchase.
Before anything is sent
Positions harden the moment the other side takes advice, and the quiet routes stop being available once a demand has gone out. While nothing has been sent, everything is still open.