Right to Represent Agreements for UK Contractors

A role appears on a Tuesday morning. The advert is thin, the client is "a leading organisation", the rate is a range, and three recruiters have found your phone number before lunch.

One says they need to move quickly. Another says the client is reviewing CVs today. A third sends a Right to Represent agreement before they have confirmed the end client, location, IR35 status, contract length, or whether the role is even the same one the other two recruiters are chasing.

That is the moment to slow down. Not argue, not panic, and not assume the recruiter is doing something underhand. Just slow down.

Not because every Right to Represent agreement is a scam. It is not. The problem is that the pressure to sign often arrives before the contractor has enough information to make a clean commercial decision.

An RTR is not the danger by itself. A vague RTR is.

What an Rtr is Supposed to Do

A Right to Represent agreement, usually shortened to RTR, is permission for a recruiter or agency to represent you for an opportunity.

The narrow version is straightforward. You allow one agency to put you forward for one named client, one named role, on known terms, for a short period. That can protect the agency from another supplier claiming the fee after doing no work. It can also protect you from blind submissions, where your CV is sent to a client without a clear conversation or consent.

That is the clean version.

The messy version asks for broad permission to represent you for "current and future opportunities", does not name the end client, does not name the role, does not include a requisition number, does not state the rate, does not mention IR35 status, and does not expire quickly. That is no longer a simple representation note. It is an unnecessary control claim over where your CV can go.

This is practical contractor guidance, not legal advice. If the wording could affect a live dispute, fee claim, restrictive covenant, data‑protection complaint, or contract negotiation, get proper advice. But most contractors do not need a lawyer to spot the obvious problem: if the recruiter cannot define what they are representing you for, you should not grant representation.

Why Recruiters Push for It Quickly

Recruiters push for RTRs because their commercial risk is real.

In many hiring routes, the agency is not rewarded simply for finding a good contractor. It gets paid if it becomes the recognised supplier attached to the successful submission. In a direct client relationship, that may be handled through agency terms. In vendor‑managed hiring, it may run through a managed service provider, a vendor management system, or a preferred supplier list.

The exact rules vary. Some processes care about the first clean submission. Some care about which supplier has the client relationship. Some RPO or hirer terms give the client discretion. Some require evidence that the candidate agreed to be represented. Lawspeed's note on agency conflicts and right to represent is useful precisely because it does not pretend there is one universal rule: fee entitlement usually comes down to the terms in place, and an RTR alone does not settle every argument.

That matters for contractors because the urgency is not always about your opportunity. Sometimes it is about the agency trying to secure its place in the submission chain before another supplier does.

That does not make the recruiter dishonest. It does mean their incentive is not identical to yours.

Duplicate Submissions Can Damage the Contractor

Contractors often hear "I just need your permission to submit" as if the permission is admin. It is more than admin.

A duplicate submission can make you look disorganised. It can delay the process whilst the client, MSP, or internal hiring team works out which agency is allowed to represent you. In some cases, it can lead to the submission being rejected because the client does not want a supplier dispute attached to the candidate.

That is especially irritating when the contractor did nothing wrong.

The worst version is when one agency submits your CV speculatively, another agency submits you properly, and the client sees noise before seeing the value you bring. The practical harm is not only legal or contractual. It is reputational. You want to arrive as a serious contractor attached to a clear role, not as a procurement argument with a CV.

The UK rules already point away from casual submission. GOV.UK's Conduct Regulations guidance says agencies and employment businesses need enough assignment information from the hirer to select a suitable work‑seeker before an introduction or CV submission. It also says they must confirm that the work‑seeker is willing to work in the position.

That does not create a neat rule that every recruiter must reveal every sensitive client detail in the first message. It does support the practical point: there should be enough assignment information to establish willingness, suitability, and basic commercial fit before a contractor gives representation consent.

"Sign this first and I will tell you later" is the wrong order.

Why This Feels Sharper Now

RTR pressure is not new, but the current market makes it more visible.

Hybrid work has not disappeared. The ONS found that 28% of working adults in Great Britain hybrid worked between January and March 2025, and hybrid work remains common in managerial, professional, IT, and technical work.

But the looseness has tightened. Indeed Hiring Lab's UK analysis found that 85% of hybrid postings mentioning a schedule required at least two days a week in the office in 2025, compared with 65% in 2022. Two days has become the most common minimum, three days has become more common, and software development was listed amongst the roles with higher average in‑office requirements.

Office attendance has also moved up from the post‑pandemic floor. Remit Consulting's ReTurn project tracks office occupancy across major UK cities, and Guardian coverage of its March 2026 data reported UK office attendance above 40% every week from early January, still below pre‑pandemic norms but the highest since Covid.

Set those signals alongside a softer, choppier hiring market and RTR pressure becomes easier to understand, without pretending one thing neatly causes the other. The REC/KPMG Report on Jobs summary for June 2026 describes a labour market still under pressure, with weak confidence, higher candidate availability, subdued pay growth, and firms turning more heavily to short‑term staffing.

That is a choppy market, not a clean one.

In that kind of market, recruiters can become more protective of viable candidates and cleaner submissions. When roles need two or three office days, the pool may narrow again. A contractor who can sensibly attend London, Brighton, the South East, or another UK office is not just "less remote". They may be easier to place into roles that have become awkward to staff from offshore or from distant UK locations.

That can give the contractor leverage, but only whilst permission is still theirs to grant.

Location Can Be a Commercial Filter Again

I wrote in Why Remote Work Did Not Make Brighton Web Developers Less Local that remote work changed what local means rather than deleting geography. That is even more obvious in contracting now.

A London role asking for two days near Liverpool Street is not the same market as a fully remote role. A Brighton or South East contractor who can attend a client site without turning the week into a travel problem is not the same candidate as someone who can only work remotely. A bank, retailer, agency, or product team may not say that elegantly, but the filter can be real.

This is not a reason for on‑site contractors to act smug. It is a reason not to behave as though they have no leverage.

If a recruiter is calling because your location, rate, background, and availability match a role with attendance requirements, they need something from you. Your permission has value. Treat it that way.

What a Safe Rtr Should Include

A safe RTR should be boringly specific.

It should name:

• the end client
• the role title or requisition number
• the location and on‑site expectation
• the contract length
• the rate and whether it is day rate, hourly, PAYE, umbrella, or limited company where relevant
• the IR35 position, if known
• the agency representing you
• the short period for which the permission applies
• a clear statement that it applies only to that role

That is the practical rule: one named client, one named role, one rate, one IR35 position, one short expiry.

The exact duration depends on the role and process, but open‑ended representation is a bad default. A few working days may be enough for an active submission. A few weeks may be reasonable where the client process is slower. Six or twelve months for unnamed future roles is not a normal administrative convenience. It is an attempt to reserve more control than the role justifies.

What to Refuse

Refuse broad wording.

Be careful with phrases such as:

• any role with the client
• any associated company
• current or future vacancies
• all opportunities introduced by us
• exclusive representation
• until withdrawn in writing
• for twelve months
• permission to share with clients and partners
• rate to be confirmed
• client confidential at this stage

Some of those phrases can be reasonable in another context. In an RTR sent before proper role disclosure, they are warning signs.

Also refuse pressure that treats questions as disloyalty. A serious recruiter should be able to confirm the client, role, rate, working pattern, and representation window before asking you to sign. If they cannot disclose the client name yet, they can at least explain why, confirm enough detail to avoid duplicate submissions, and keep the permission conditional until the client is named.

The ICO's recruitment and selection draft guidance is a useful reminder that recruitment involves processing candidate information across a sometimes complex supply chain. Your CV, rate, availability, location, work history, and contact details are not confetti. They are personal and commercial information. You are entitled to ask where they are going and on what basis.

A Reply You Can Send Back

You do not need to make this dramatic. Keep it calm and specific.

"Thanks. I'm happy to give permission for you to represent me, but only for the specific role we have discussed. Please confirm the end client, role title or requisition number, location and office requirement, contract length, rate, IR35 status, and the period for which the RTR applies before I agree to anything. I will not sign a broad or open‑ended RTR."

If they need wording from you, send something like this:

"Permission is granted only for [named client], [named role or requisition number], [location], [rate], [IR35 status], for [x] days. This permission does not apply to any other role, client, vacancy, future opportunity, speculative submission, or onward sharing."

That is not hostile. It is tidy.

A good recruiter may even appreciate it because it gives them cleaner evidence and reduces the chance of a messy duplicate. A weak recruiter may push back because the vague wording was the point.

The Contractor Test

Before signing an RTR, ask yourself one question:

Would I be comfortable if this exact wording was forwarded to the end client, the MSP, another agency, and a lawyer?

If the answer is no because the wording is too broad, too vague, or too detached from the actual role, do not sign it.

This is the same kind of commercial discipline I would apply to choosing between a freelancer, agency, or lead‑level contractor for serious platform work. The label matters less than the responsibility being created. A vague engagement creates vague accountability. A vague RTR creates vague control.

The same applies to pricing. A day rate, fixed quote, or retainer only makes sense when the risk and scope are understood, which is why I have written about buying senior web development work without creating risk. Representation is another boundary. Keep it explicit.

Wrapping Up

RTRs are not inherently scams. They are also not harmless admin.

They are a control surface in a market where agencies, managed‑service processes, supplier rules, hirer terms, candidate availability, office requirements, and fee protection all rub against each other. Some recruiters use them cleanly. Some use them lazily. Some use them to get ahead of competitors before the contractor has enough information to judge the opportunity.

The contractor's answer should be boring and firm.

Name the client. Name the role. Name the rate. Name the location. Name the IR35 position. Set a short expiry. Exclude every other opportunity.

If the recruiter cannot live with that, the RTR was probably doing more than they said.