CEST and Status Determination Statements: The Practical Guide

Where CEST and the SDS sit in the off-payroll rules

When a medium or large client engages a contractor through a personal service company, the off-payroll rules require that client to decide the worker’s deemed employment status and to record the decision in a Status Determination Statement. CEST, the Check Employment Status for Tax tool, is the free instrument HMRC provides to support that decision. The two are often conflated, but they are different things: CEST is one optional way of reaching a conclusion, while the SDS is a legal requirement with specific content rules and consequences for getting it wrong.

Both remain relevant after the small company threshold change taking effect from 6 April 2026, which moves engagements with small clients back to the contractor’s own company for determination. Contractors determining their own status under the original IR35 rules can use CEST too, and the discipline of documenting a reasoned conclusion serves them just as well as it serves a large client, even though no formal SDS is required on that side of the rules.

How CEST works and what it asks

CEST is a structured questionnaire built around the case-law tests. It opens by checking whether an intermediary is involved, then works through substitution, control and the wider business factors. The substitution section asks whether the worker has the right to send someone else, whether the client could reject a substitute, and who would pay them. The control questions cover whether the client can move the worker between tasks, who decides how the work is done, and whether working hours and location are dictated or chosen. Later sections deal with financial risk, equipment, how the worker is paid, corrections at the worker’s own cost, and whether the worker receives any employee-style benefits or holds management responsibilities within the client organisation.

The tool applies a decision engine to those answers and returns one of three outcomes: employed for tax purposes, self-employed for tax purposes, or unable to make a determination. The official tool and its guidance are published at Check Employment Status for Tax on GOV.UK. Always download and keep the result document, which records the answers given and the date, because an unrecorded CEST run has no evidential value later.

The undetermined gap and the MOO criticism

A significant share of CEST runs end with no determination at all. The undetermined outcome tends to appear in precisely the borderline cases where help is most needed: some control present, substitution theoretically possible but untested, moderate financial risk. When CEST cannot decide, the legal duty to decide does not go away. The client, or the contractor under the small-client rules, must still reach a conclusion by other means, typically by applying the case law directly or commissioning a professional review.

CEST has also been criticised for the way it handles mutuality of obligation. The tool effectively assumes that basic mutuality exists in any engagement being tested, on the logic that work in exchange for payment is present wherever a contract exists, so it does not probe MOO in depth. After the Supreme Court’s PGMOL decision in 2024, that assumption is closer to the law than critics once argued, since basic work-for-payment mutuality will almost always be found within an engagement. Even so, CEST remains a simplification of a multi-factorial legal test, and its output is only as good as the judgment behind each answer. The underlying case law is unpacked in the guide to the IR35 status tests.

When HMRC is bound by a CEST result, and when it is not

HMRC’s published position is that it will stand by a CEST outcome provided the information entered was accurate and the arrangements have not changed since the test was run. That commitment is genuinely valuable: a contemporaneous CEST result based on honest answers is strong protection in a later compliance check.

The protection falls away in specific circumstances.

• Inaccurate inputs: answers that did not reflect the real working arrangements, whether through optimism, misunderstanding or design.
• Contrived answers: inputs engineered to produce a desired outcome, which HMRC treats as removing any reliance on the result.
• Changed circumstances: a result obtained at the start of an engagement does not cover a role that has since evolved, so material changes require a re-test.
• Undetermined outcomes: there is nothing to stand by, and the status decision must be made and evidenced another way.

In an enquiry, HMRC routinely tests CEST answers against the contract and against what workers and managers say actually happened. A result that says outside IR35 because substitution was answered yes will not survive contact with a hiring manager who confirms they would never have accepted anyone but the named contractor. Accuracy at input time, with evidence for each answer, is what makes a CEST result defensible.

Reasonable care means more than running the tool

The off-payroll legislation requires the client to take reasonable care in making each determination. Fail that duty and the SDS is not valid, which leaves the tax liability sitting with the client rather than passing down the supply chain. Running CEST once and filing the printout does not, by itself, discharge the duty. Reasonable care is judged by what a prudent organisation would do given its size and resources.

In practice, taking reasonable care looks like this.

• Assessing each engagement individually rather than applying blanket determinations to whole categories of contractor.
• Gathering input from people who actually know the working arrangements, including the contractor and the hiring manager, before answering status questions.
• Ensuring the people completing assessments understand the off-payroll rules, with training or specialist support where needed.
• Checking that the contract terms and the day-to-day reality match before relying on either.
• Recording the reasoning and evidence behind each conclusion, not just the outcome.
• Reviewing determinations when an engagement is extended, the scope changes, or the role materially evolves.

Blanket inside-IR35 determinations deserve particular mention. Declaring every contractor inside without individual assessment fails the reasonable care duty just as surely as careless outside determinations do, and it pushes genuinely independent contractors into paying employment taxes they do not owe. Contractors on the receiving end of a blanket decision have a formal route to challenge it, covered below.

What a Status Determination Statement must contain

An SDS is only valid if it does three things: states the client’s conclusion on whether the off-payroll rules apply, gives the reasons for that conclusion, and is passed to both the worker and the next party in the contractual chain, typically the agency. A bare statement of outcome with no reasons is not a valid SDS. Nor is a determination the worker never receives. Until a valid SDS has been issued with reasonable care, responsibility for deducting tax cannot transfer down the chain, so the client remains the deemed employer and carries the PAYE and NIC risk itself.

There is no prescribed form. A CEST output document accompanied by a covering statement can serve, as can a bespoke assessment from a commercial tool or adviser, provided the conclusion and reasoning are clear. Good practice adds the engagement details, the date, the evidence relied on, and the name of the person who made the assessment. Contractors should keep every SDS they receive: it is a foundation document if the determination is later challenged in either direction.

Disagreeing with a determination: the 45-day window

The legislation builds in a client-led disagreement process. A worker, or the deemed employer in the chain, can make representations to the client explaining why they believe a determination is wrong. The client then has 45 days to respond. Within that window it must either confirm the original SDS with reasons or withdraw it and issue a new one. If the client fails to respond within 45 days, the consequence is sharp: the client itself becomes liable for the deduction of tax and NIC, regardless of what the SDS said.

Using the window well means treating the representation as advocacy, not a complaint. A one-line email saying the contractor disagrees invites a one-line confirmation. A strong representation works through the status tests point by point, identifies which CEST answers or assessment findings were wrong, and attaches evidence: the contract clauses on substitution and control, confirmation of working practices from the hiring manager, proof of other clients, insurance and equipment. The aim is to make confirming the original decision harder than correcting it.

Timing matters too. The disagreement process can be started at any point while the engagement conditions are met, but raising it early, before the first payment is processed under the disputed status, avoids months of deductions that are awkward to unwind. Where the client confirms a blanket or poorly reasoned decision, options remain: escalating with professional representation, renegotiating the terms and working practices and requesting a re-assessment, or pricing the inside-IR35 position into the rate. Specialist help with this process is exactly what a status determination dispute service exists for, and a specialist accountant can often spot the winning argument in an assessment the contractor has read ten times.

Independent paid status reviews versus CEST

CEST is free, quick and carries HMRC’s stand-by commitment, which no commercial alternative can offer. Its weaknesses are the mirror image: it cannot weigh nuance, it returns undetermined in many borderline cases, and its binary questions flatten facts that a tribunal would treat as matters of degree. Independent reviews, whether from a specialist consultancy or an accountant with status expertise, examine the actual contract and working practices, apply the full case law including the third-stage business factors, and produce a reasoned report. Many also review the written contract against the working reality and recommend specific amendments, which CEST never does.

The two are complements rather than rivals. A sensible approach for a borderline engagement is to run CEST with carefully evidenced answers, and to commission an independent review where CEST returns undetermined, where the result is outside but the facts are mixed, or where the contract is high-value enough that the cost of error dwarfs the review fee. For a client organisation, a documented independent review is itself persuasive evidence of reasonable care. For a contractor, it is the backbone of any future disagreement representation or enquiry defence.

Building the evidence file that wins disputes

Status disputes are decided on evidence, and the evidence that wins is gathered during the engagement, not reconstructed years later from memory. Every contractor working outside IR35, and every client issuing outside determinations, should maintain a file per engagement.

• The signed contract for each engagement and extension, plus the upper-level contract between agency and client where obtainable.
• A working practices confirmation: a short document signed by the contractor and the hiring manager describing how the engagement actually operates, covering substitution, control, equipment and integration.
• CEST result documents and any independent review reports, each dated and tied to the engagement they assessed.
• Substitution evidence where it exists: correspondence offering or arranging a substitute, and invoices showing the company paid them.
• Proof of being in business: professional indemnity and public liability insurance schedules, marketing materials, records of concurrent or sequential clients, company-funded training and equipment purchases.
• Board minutes and company records showing genuine corporate decision-making, such as approving contracts, dividends and significant purchases.
• Emails demonstrating autonomy in practice: declining work outside scope, choosing methods, setting working patterns.

The working practices confirmation deserves emphasis because it is the cheapest, most neglected document on the list. Hiring managers move on, and three years into an enquiry the person who could have confirmed your autonomy may be unreachable. A contemporaneous signed statement fixes their evidence while it is fresh and cooperative. Paired with an accurate contract and a clean CEST or independent review, it turns a status argument from assertion into proof. How HMRC actually tests that proof, and what an enquiry looks like from the inside, is covered in the companion guide to HMRC IR35 enquiries.

Treat the file as a living record rather than a one-off exercise. Refresh the working practices confirmation at each extension, re-run or re-review status whenever the role changes materially, and date every document as it is added. An engagement that drifts from project delivery into business-as-usual support is the classic way an accurate outside determination quietly becomes inaccurate, and only a maintained file catches the drift in time to fix it.