Back to Blog
Industry Trends

Automating IR35 Determination Tracking in Candidate Pipelines

CVSense® InsightsCircle
5 views
0 comments
Share:
Automating IR35 Determination Tracking in Candidate Pipelines

IR35 status is not an afterthought to be filed once a contractor starts, it is a field your pipeline should carry from first contact. This guide shows how to structure and filter off-payroll status across a contract desk.

Ask a contract desk where their off-payroll compliance information lives and the answer is usually a version of "in a few places". Determinations sit in email threads, the client's position on status is in someone's notes, the worker's engagement preference is in the CRM free-text field, and the actual statement is a PDF attached to a record somewhere. It works until a client asks for a pipeline-wide position, or until HMRC does. Automating IR35 determination tracking in candidate pipelines is mostly a data structuring problem that has been left as an administrative one.


This piece covers what the off-payroll rules actually require you to hold, which fields belong on a candidate record, and how to make status filterable rather than archaeological.

What the Rules Require, in Structural Terms

The off-payroll working rules apply where a worker provides services through an intermediary, most commonly their own limited company. The essential mechanics, stated as data requirements rather than as tax law:

  • For public authorities and medium or large private sector clients, the client determines employment status for tax purposes and must issue a Status Determination Statement to the worker and to the party it contracts with, stating the conclusion and the reasons for it.
  • The client must take reasonable care in reaching that determination. Blanket determinations applied across a category of workers without individual assessment do not constitute reasonable care, and a failure to take reasonable care can move the tax liability to the client.
  • There must be a client-led disagreement process so a worker or fee-payer can challenge a determination and receive a response.
  • Where the engagement is inside the rules, the fee-payer: the party paying the intermediary, operates PAYE and National Insurance, with the associated employer costs.
  • Where the client is a small private sector company, the responsibility sits differently and the intermediary determines its own status. Small status turns on thresholds for turnover, balance sheet total and employee numbers, so client size is itself a field you need.

Read as a list of data obligations rather than tax rules, the implication is obvious. Every contract engagement carries a determination, a reason, an issuing party, a date, a distribution record, a disagreement state and a fee-payer position. That is a structured record, and free-text notes cannot hold it reliably.

The Fields a Contract Pipeline Should Carry

Treat these as first-class, filterable fields on the engagement rather than attachments or notes.

On the Role or Engagement

  • Client size classification: small, or medium/large, or public authority. This determines who is responsible for the determination, so it belongs at the top of the record.
  • Determination outcome: inside, outside, or not yet determined.
  • Determination date and issuing party.
  • Statement issued: whether it has been provided to the worker and to the contracting party, with dates. Issuance is a specific obligation, not an inference from the determination existing.
  • Reasons recorded: the substantive basis, not just the conclusion.
  • Assessment method and evidence retained, whether that was a status tool output, an external review, or internal assessment.
  • Disagreement status: none, raised, under review, concluded, with dates.
  • Fee-payer identification, and confirmation of who is operating payroll where the engagement is inside.
  • Review date, because a determination reflects the engagement as described. Material changes to working practices should trigger reassessment.

On the Candidate

  • Engagement models the candidate will accept: own limited company, umbrella, agency PAYE, permanent. This is the single most valuable filter on a contract desk and it is usually buried in a note.
  • Current engagement structure, where relevant.
  • Rate expectations by model, since inside and outside rates are not comparable and treating them as one number causes avoidable friction.
  • Umbrella preference, where the candidate has one.
  • History of determinations across your engagements, which is useful context and is not itself a determination for a new role.

That last point needs stating clearly because it is a common and serious error. A previous outside determination for a different engagement does not carry over. Status attaches to the specific engagement and its working practices. Reusing an old determination for a new role is close to the definition of failing to take reasonable care.

What Automation Can and Cannot Do Here

Being precise about this protects you, because the failure mode is a tool that appears to determine status and quietly erodes the reasonable care position.


Automation can structure the fields above, enforce that they are populated before a placement can progress, filter and segment the pipeline by status, flag engagements where the statement was never issued, surface determinations approaching a review date, track disagreement states against response times, and report a whole-desk position instantly rather than through a manual audit.


Automation cannot determine employment status. Status rests on the substance of the working arrangement, the degree of control over how, when and where the work is done, whether personal service is required or substitution is genuinely permitted, mutuality of obligation, financial risk, and how integrated the worker is into the client's organisation. Those are facts about a relationship, most of which are not in a CV or a job specification. A screening layer cannot see them and should not pretend to.


Nor can automation supply reasonable care. Reasonable care is demonstrated by individual assessment of the actual engagement, documented. A workflow that helps ensure every engagement is individually assessed and recorded supports reasonable care. A tool that auto-applies a status by role type actively undermines it, because that is the blanket determination the rules were written to prevent.

Where CV Screening Does Connect

There is a legitimate and narrower role for screening in this picture, and it is worth naming because it is genuinely useful.


Contractor CVs often contain evidence bearing on the status picture: whether the candidate operates through their own company, whether they have run concurrent client engagements, whether they describe delivering defined outcomes rather than occupying a role, whether they supply their own equipment, and whether the work described looks project-shaped or position-shaped.


None of that determines status. All of it is useful context for whoever performs the assessment, and surfacing it at screening stage means the determination conversation starts with information rather than from scratch. The correct output framing is "factors relevant to assessment" and never "suggested status".

The Operational Payoff

Three things change once status is structured rather than filed.


Matching gets faster and less wasteful. Filtering candidates by acceptable engagement model stops the recurring waste of taking a limited-company contractor through three stages of an inside-IR35 role before the rate and structure conversation happens.


Client conversations get easier. A client asking about your compliance position on their contingent workforce gets a report rather than a fortnight of collation.


Gaps surface before they matter. Engagements missing a statement, determinations past review date, and disagreements without a response are visible as exceptions rather than discovered during a review.

Frequently Asked Questions

Can Software Determine IR35 Status Automatically?

No. Status depends on the substance of the working relationship, control, personal service and substitution, mutuality of obligation, financial risk and integration, which is not derivable from a CV or a job advert. Software should structure, enforce and report the determination process, not perform the determination.

Who Is Responsible for the Determination?

For public authorities and medium or large private sector clients, the client determines status and issues the Status Determination Statement. Where the client is a small private sector company, the responsibility sits with the worker's intermediary. Client size classification therefore needs to be a recorded field, not an assumption.

Does an Outside Determination Carry Across to a New Contract?

No. Determinations are engagement-specific because status depends on the working practices of that engagement. Reusing a previous determination for a new role is a straightforward failure to take reasonable care.

What Does Reasonable Care Require in Practice?

Individual assessment of the actual engagement, based on its real working arrangements, with the conclusion and reasons documented, and a route for the determination to be challenged. Blanket determinations by role type or by category of worker do not satisfy it.

How Does This Affect Umbrella Placements?

Where an engagement is inside the rules, umbrella employment is a common route because the umbrella employs the worker and operates payroll. The pipeline still needs to record the determination, the statement issuance and the fee-payer position, and candidate records still need to carry umbrella preference and the rate expectations attached to each model.

Making It Stick

The reason off-payroll tracking stays messy is not that anyone disputes its importance. It is that the information is treated as paperwork produced at placement rather than as structured data carried from first contact. Move it into fields, make them mandatory at the right stage, make them filterable, and the compliance position becomes a query instead of a project.


CVSense supports custom structured fields and filtering across candidate and engagement records, which is what allows off-payroll status to be segmented and reported rather than reconstructed. The determination stays where it belongs, with the party responsible for making it, properly documented, which is the only version of this that holds up under scrutiny.


Sources

HM Revenue and Customs. Understanding Off-payroll Working (IR35).
https://www.gov.uk/guidance/understanding-off-payroll-working-ir35

HM Revenue and Customs. Check Employment Status for Tax.
https://www.gov.uk/guidance/check-employment-status-for-tax

Chartered Institute of Personnel and Development.
https://www.cipd.org/uk/


InsightCircle

Comments

Start the discussion

Be the first to comment on this article.

Loading comments…
Powered by CVSense

Follow @CVSense on LinkedIn

Get recruitment best practices, career guides, and insights that can help you succeed.

Tags
#ir35#offpayrollworking#contractrecruitment#statusdeterminationstatement#compliancetracking
CI

About CVSense® InsightsCircle

At CVSense, we have built technologies that help you present your skills most compellingly, in addition to helping recruiters ensure that they get the right candidates.

Supercharge Your Job Search with CVSense

Apply to jobs faster and smarter with CVSense's browser extension. Autofill applications, get AI-powered recommendations, and track your progress - all from your browser.

Start Landing Job Interviews

More Articles You Might Like