TL;DR
- Contractor management software exists to hold a paperwork trail: who is engaged, under what terms, with which checks completed and which documents expiring. The value shows up in an audit or a dispute, which is exactly when a spreadsheet lets you down.
- In the United Kingdom the off-payroll rules put the status decision on the client in most cases, with a status determination statement setting out the reasons. A system that cannot store that statement and evidence when it was issued is missing the central record.
- Treat contractors differently in the system as well as in the contract. Onboarding them exactly like employees creates evidence that undermines the status position you have taken. This article describes the United Kingdom position and is general information, not tax or legal advice.
The question that catches organisations out is never "who is working here". It is "prove it". Prove what this person was engaged to do, who decided their tax status and why, that their right to work was checked, that their insurance was in date in March, and that access was removed when the engagement ended.
This article covers what contractor management software has to hold, the United Kingdom status question that sits at the centre of it, how contractor onboarding should differ from employee onboarding, and the questions to ask a provider. It names no products and is general information rather than tax or legal advice.
Contractors still need to know what good work looks like on your terms. See how New Dynamics goals and OKRs keep outcomes clear without turning an engagement into supervision.
If the question is what a contractor actually is, our post on the independent contractor covers status, the tests and the labels.
The five records
- The engagement. Who, through which intermediary or agency, for what work, for how long, at what rate, under which contract version.
- The status determination. The decision, the reasons and the date it was issued.
- Right to work evidence, held separately with its own retention rule.
- Insurance, licences and qualifications, with expiry dates and automatic chasing.
- The ending. Last day, access removed, equipment returned, final invoice, records retained for the right period.
The third is a legal duty in its own right: government guidance states that "You must check that a job applicant is allowed to work for you in the UK before you employ them", and the same diligence applies to the people you engage through an agency or an intermediary.
Most organisations have one to four spread across email, a shared drive and somebody's memory. That is fine until the question arrives.
The status question sits at the centre
Government guidance on the off-payroll working rules is clear about where the decision lands: "If the rules apply, the client is responsible for determining the worker's employment status for tax, and they should produce a status determination statement (SDS) including the reasons for their determination." Who carries that responsibility depends on the sector and the size of the client, and the rules cover the worker, the client and any agency in the chain.
For software, that produces concrete requirements:
- Store the statement itself, not a tick that one exists.
- Record when it was issued and to whom, including the agency where there is one.
- Keep the reasons, because a determination without reasoning is not a determination.
- Handle disagreement, since a worker can dispute the conclusion and you need a record of the response.
- Version it. A change in how the work is done can change the answer, and the previous assessment still matters.
A system that treats status as a dropdown value is storing a conclusion with no evidence behind it.
Contractors are not employees, including in the system
It is tempting to run contractors through the employee onboarding path because it already exists. Resist it. The way you manage someone is evidence about the relationship, and the system is part of that evidence.
Practical differences worth preserving:
- Engagement, not employment, in the records and the language.
- Deliverables rather than duties, with outcomes and dates instead of a job description.
- No performance review cycle, no objectives cascade, no development plan.
- Access and equipment scoped to the work, and removed promptly at the end.
- A separate induction that covers safety, systems and the point of contact, without the culture-and-career material.
None of this is about being unwelcoming. It is about the paperwork matching what is actually happening.
What good software does
- Chases expiry automatically: insurance, licences, certifications, visas. This is the single most useful thing it does.
- Holds documents against the engagement, not against a person record shared with employees.
- Shows who is on site or active today, which is a question that gets asked in an incident.
- Separates agency relationships from direct ones, with the chain visible.
- Reports spend by engagement, since contractor cost is usually visible only in finance.
- Deletes on a schedule, because contractor records contain identity documents.
Questions for the demo
- Show me a status determination statement stored with its reasons and issue date.
- Show me an expiring insurance certificate and what happens as the date passes.
- Show me the end of an engagement: access, equipment, final documents, retention.
- Show me an agency-supplied worker, with the chain recorded.
- What is the retention setting for identity documents, and who can view them?
- What does the contractor themselves see, and how do they update a document?
- What is the export at the end of the contract?
What usually goes wrong
- Status decided once and never revisited, even when the work changes.
- Identity documents kept indefinitely in a shared folder with no deletion rule.
- No owner for expiry, so a certificate lapses and nobody notices until an audit.
- Contractors added to employee processes, which muddies the status position.
- Access left live after the last day, which is a security problem and a licensing cost.
- Spend invisible to HR, so workforce planning is based on headcount that excludes a third of the people doing the work.
Frequently asked questions
What is contractor management software?
It is a system for engaging and tracking non-employee workers: the engagement and its terms, employment status records, right to work and identity checks, insurance and qualification expiry, access and equipment, spend and the end of the engagement.
Who decides a contractor's employment status for tax in the UK?
Under the off-payroll working rules it is usually the client who must determine the worker's status for tax and issue a status determination statement with the reasons, though responsibility differs for small private-sector clients. The rules also touch agencies in the chain, so the record needs to show who decided and when.
Should contractors go through employee onboarding?
No. Give them a separate route that covers safety, systems and the point of contact, with deliverables rather than duties and no performance cycle. Running contractors through employee processes creates evidence that conflicts with the status position you have taken.
What contractor documents do you have to keep?
At least the engagement terms, the status determination and its reasons, right to work evidence, and any insurance, licence or qualification the work requires, each with an expiry date and a retention rule. Identity documents in particular should be deleted on a schedule rather than kept indefinitely.
Do small businesses need contractor management software?
Not usually at low volumes, provided someone owns the checks and the expiry dates are diarised. The argument grows with the number of concurrent engagements, the presence of agencies in the chain, and any requirement to evidence compliance to a client or regulator.
How do you keep contractor records compliant?
Decide retention periods for each document type, restrict who can view identity documents, review status determinations when the work changes, and keep an auditable record of who checked what and when. The test is whether you could answer the question six months after the engagement ended.
Your next step: try to prove it
- Pick one contractor who worked for you last year and try to produce the five records above.
- Note which ones took more than five minutes, and which do not exist.
- Check whether any status determination has been revisited since the work changed.
- Set a retention rule for identity documents and apply it.
For the wider duties around worker data, read and download our employee data protection guide. The guide is free to read, and the PDF uses our short download form.
Want outcomes clear for everyone doing the work, however they are engaged? Book a New Dynamics demo and bring your current engagement list. You can also email contact@new-dynamics.com.
