Right to Represent (RTR) in IT Staffing, Explained

A right to represent (RTR) is a written confirmation from a candidate that a particular staffing firm may submit them for a particular role, usually at a stated rate and for a stated period. Vendors and clients ask for RTRs to establish who represents the candidate for that opportunity and to avoid disputes when more than one firm tries to submit the same person.

This article is general information, not legal advice. For questions about a specific agreement, consult a qualified attorney.

Why RTRs exist

IT staffing requirements often pass through several layers: an end client, a managed service provider or prime vendor, and one or more sub-vendors. Each layer may contact the same pool of consultants. Without some record of consent, it would be hard to tell which firm had the candidate's permission to submit them, and whether the candidate even knew they were being submitted.

An RTR addresses three problems:

• Consent. It confirms the candidate agreed to be submitted for this specific role.
• Ownership. It gives the vendor a record of which firm represents the candidate for that opportunity.
• Duplicates. It discourages the same candidate from being submitted by multiple firms. For more, see duplicate submissions in staffing.

What an RTR usually includes

RTRs vary in format. Some are a short email the candidate replies to; others are a one-page document. Common elements include:

• Candidate's full name and contact details.
• Name of the staffing firm being authorized.
• Role title and, where shared, the end client and location.
• Requisition or job ID if one exists.
• The rate the candidate agrees to be submitted at, and the tax arrangement, such as W2 or C2C.
• A statement that the candidate has not been submitted, and will not allow submission by another firm, for the same role during a defined period.
• Date and the candidate's confirmation or signature.

Some RTRs also mention the vendor chain, contract duration, or start date. The more specific the RTR, the less room for misunderstanding.

How the RTR process typically works

1. The recruiter finds a match. A requirement fits the candidate's skills and preferences.
2. The recruiter explains the role. Client, location or remote terms, duration, rate, and what is known about the vendor chain.
3. The candidate decides. They confirm they want to be submitted and have not already been submitted for this role elsewhere.
4. The recruiter sends the RTR. Usually an email with the details listed above.
5. The candidate replies or signs. A clear written confirmation, not a verbal yes.
6. The recruiter submits and logs it. The RTR is stored with the submission record and often forwarded to the vendor.

Good practices for recruiters

Recruiters who handle RTRs carefully build trust with both candidates and vendors.

• One role per RTR. Avoid blanket RTRs that authorize submission to "any opportunity." They tend to erode trust and create disputes.
• Share real details. Candidates should know at least the end client or enough detail to recognize the role if another recruiter calls about it.
• Be accurate about the rate. The rate on the RTR should match what is actually submitted.
• Never submit before the RTR. Submitting first and asking later puts the candidate at risk.
• Keep records. Store the RTR with the submission so it can be produced if a vendor asks.
• Respect a no. If the candidate declines, do not submit.

Good practices for consultants

Consultants receive many RTR requests, sometimes for the same role from different firms.

• Ask for the end client. Without it, you cannot tell whether two recruiters are calling about the same job.
• Keep your own log. Note each RTR you give: firm, role, client, rate, and date.
• Give one RTR per role. If you have already authorized a firm for a role, tell other recruiters so.
• Read before confirming. Check the rate, the exclusivity period, and any terms that go beyond a simple submission.
• Ask questions. If language about restrictions or fees is unclear, ask the recruiter to explain, and consider professional advice for anything that looks like a binding commitment.

RTRs and rate confidentiality

RTRs often state a rate, and that rate may differ from what the end client pays, since each layer in the vendor chain takes a margin. Practices around rate transparency differ between firms. Consultants should understand whether the stated rate is their pay rate or a bill rate, and on what tax basis. For background on tax arrangements, see C2C vs W2 vs 1099.

Common RTR mistakes

• Submitting a candidate without any written consent.
• RTRs that omit the client or role, making them hard to match against other submissions.
• Giving RTRs to several firms for the same role.
• Stating one rate on the RTR and submitting at another.
• Not storing the RTR, then being unable to show it when a vendor asks.

RTRs as part of a submission routine

An RTR is one step in a broader process that also covers resume quality, candidate details, and duplicate checks. For the full sequence, see the recruiter's checklist before submitting a candidate.

Staffing teams use Knuckler AI to prepare tailored, ATS-checked resumes and cover letters for each role, get a duplicate-submission warning before sending a candidate somewhere they may already be in play, and keep every submission in one pipeline, so the consent step and the record of where a candidate was sent stay easy to find.

Key takeaways

• An RTR is a written confirmation that a specific firm may submit a candidate for a specific role, usually at a stated rate.
• It establishes consent and representation and helps prevent duplicate submissions.
• Keep RTRs specific: one role, real client details, accurate rate, clear date.
• Consultants should log every RTR they give and never authorize two firms for the same role.
• When terms look binding or unclear, seek qualified legal advice.

Frequently asked questions

What is an RTR in staffing?

An RTR, or right to represent, is a written confirmation from a candidate that a specific staffing firm may submit them for a specific role, usually at a stated rate. It helps establish which firm represents the candidate for that opportunity.

Is an RTR legally binding?

It depends on the wording and the circumstances. Many RTRs are simple email confirmations rather than formal contracts. Candidates and firms with questions about enforceability should consult a qualified attorney.

Should a consultant sign an RTR for every recruiter who asks?

No. A consultant should only give an RTR for a specific role they want to be submitted to, and should not give RTRs to multiple firms for the same role, since that typically causes a duplicate submission.