A right to represent (RTR) is a document that gives a staffing vendor permission to submit you or your corporation to a client for C2C work. Vendors require it so they can pitch you without a competing vendor cutting them out of the deal, and so they have proof you consented.
Here is the catch. Recruiters say "RTR" for more than one document. Sign the wrong one without reading it and you can lock yourself out of other vendors for months. This page covers every version, what each one binds you to, and what to check before you put your name on it.
What are the different types of right to represent documents?
Three documents travel under the "RTR" label. They look similar in an email thread. They do very different things.
| Document | What it is | What it binds | Main risk |
|---|---|---|---|
| Right to Represent (RTR) letter | Your signed consent for a vendor to submit you to a named client for a specific role | You, for that client and that role, for an exclusivity window | Vague client or role wording, plus hidden non-compete or finder's fee language |
| C2C Right to Represent agreement | A broader contract that gives a vendor authority to market your corporation across their client base | Your corp, for a defined period (usually 6 to 12 months), plus a tail after it ends | Wide scope, long tail, no exit if the vendor goes silent |
| C2C Right-to-Represent letter (authority letter) | A letter from your LLC or S-Corp stating you are authorized to contract on its behalf | Your entity's statement about you, not an exclusivity promise | Rejection for missing details, wrong signer or a stale date |
The first two are about exclusivity: who gets to pitch you. The third is about authority: whether you are allowed to sign for your company at all. Ask the recruiter which one they mean before you reply. A one-line question saves you a bad signature.
Why do vendors require a right to represent?
Vendors spend time and money finding clients, pitching contractors and running submissions. If you could sign with Vendor A and then with Vendor B for the same gig, Vendor A loses the deal and the margin. The RTR removes that dispute.
There are three practical reasons behind the request:
- Proof of consent. If the client asks "did this contractor actually authorize you?", the vendor points to the signed document.
- Protected margin. Vendors work on thin margins. A placement can earn them 20-30% of the first-year bill rate, so duplicate submissions are a real threat. Only the vendor you signed with gets paid.
- Liability control. If you lack authority to work through your entity, or a non-compete bars you from the engagement, the vendor becomes liable. The authority letter moves that burden onto you.
In short: the vendor is buying certainty. You are paying for it with flexibility. If you want the background on who sits where in the chain, read what a vendor is in C2C staffing (prime, sub, layer).
What does a per-role RTR letter lock you into?
A per-role RTR letter says: "You have my permission to submit my C2C contract to [Client Name] for this specific role." Once you sign, you are tied to that vendor for that client and that role. You cannot shop yourself to other vendors for the same opening. Break it and you risk a breach-of-contract claim.
Vendors usually ask for it before they send your profile to the client, not after. A typical exclusivity window runs 90 days or 6 months on that specific client and role. When the window closes and the deal did not land or has ended, you are free to work with another vendor on a different role at the same company.
Two traps hide in these letters:
- Loose scope. You think you are signing for one deal at Client X. The letter says "Client X and its affiliates" or "any similar roles within the technology sector." Now you are blocked from other vendors' roles at Client X's subsidiaries and overlapping roles at the same company.
- Embedded non-compete. Some vendors add language saying you cannot work for the client directly for a set period. If you do, they claim a finder's fee or a percentage of your rate. That can be enforceable in many states when the wording is clear.
Also watch for blanket versions: permission to pitch you to multiple clients for multiple roles. You lose track of what you are locked into until deals come back.
What is in a C2C right to represent agreement?
A C2C right to represent agreement is a contract that gives a vendor exclusive or first-call authority to market your corporation to clients and submit you for contract roles. It is not tied to one posting. It covers your entity across the vendor's client network for a defined period, usually 6 to 12 months.
Read it for three things.
Geographic scope
North America, one region or worldwide? Narrower is better for you.
Role scope
"All contract roles" is a cage. Specific skill sets (Java, Oracle, DevOps) leave you room to work with other vendors outside that scope. If the agreement covers only Oracle EBS roles, you have wiggle room. If it covers all contract roles in North America, you do not.
Duration and tail
Standard is 12 months active with a 60 day tail. The tail means the vendor still earns commission after the agreement ends if you land at a company they pitched you to while it was active. Push back. Ask for 30 days or none.
Vendors often sweeten it: "We'll offer you a 22% markup if you sign a 12-month RTR." That markup only matters if placements actually happen. Without active vendor effort, the agreement is a chain with no upside.
If you are negotiating on scope and tail, ask for a performance trigger too. Example: if they do not submit you to at least 3 roles per month, the agreement ends early.
What does a right-to-represent authority letter include, and who signs it?
This version comes from your own company. It states that you have the authority and legal standing to contract work for your LLC, S-Corp or incorporated entity, and that nothing blocks you from the engagement. Think of it as your entity's permission slip.
A standard letter contains:
- Company name and registration details: LLC number, state of incorporation, registered agent.
- Your full legal name: the individual authorized to represent the company.
- A statement of authority: for example, "We hereby authorize [your name] to represent [Company Name] in contract negotiations and work engagements."
- Confirmation of no conflicts: an explicit line that you have no non-compete or conflict of interest tied to the engagement.
- An authorized officer's signature.
- Date and letterhead or seal if your entity has one.
Who signs depends on your structure. In a solo LLC, you as the member sign. In an S-Corp or multi-member LLC, a designated officer or the registered agent signs, not the contractor. The point is someone other than you vouching for you. Not sure who your registered agent is? Check your formation documents or your state's Secretary of State website.
How do you get one?
- Use the vendor's template. It already matches their risk tolerance.
- Ask your formation service (Stripe Atlas, Gust or a local law firm). Some include a template.
- Hire a business lawyer. A flat-fee letter typically runs $100-300 and makes sense if you contract often or work in regulated industries.
- Draft it on company letterhead. A sole member can do this, and notarizing it is optional but adds weight.
Once you have a good version, keep it as a template. You will reuse it with every new vendor.
Why do vendors reject these letters?
- It is unsigned or not on letterhead.
- It is dated more than 12 months ago.
- It says "may be authorized" instead of stating authority outright.
- It leaves out the registration number or state of incorporation.
- The signer is not listed as an officer or registered agent on public records.
If a vendor rejects yours, ask what they need. Formatting problems get fixed fast. Refresh the letter yearly or whenever your company status changes.
Large, regulated or risk-averse clients (finance, healthcare, government) trigger this request most often. So do senior roles, roles with sensitive data access, and a first engagement through your entity with a given vendor.
What should you check before signing any RTR?
Run this checklist on every document with "represent" in the title.
- Confirm the client and role are named. "Senior Network Architect for BlueCross BlueShield" is clear. "Healthcare IT contractor" is not.
- Read the exclusivity window. Shorter is better unless the rate justifies it. Common terms are 30, 60 or 90 days. Some vendors ask for 6 months to 1 year.
- Check the scope. Does it cover only this role, or this role plus similar roles and affiliates?
- Find the direct-hire language. Can you accept a direct offer from the client without owing a fee? Get that in writing.
- Read the termination clause. If the client cancels, are you still locked in?
- Define "competing." If there is non-compete language, know what it means and for how long.
- Look for the tail. How long after expiry does the vendor still earn commission?
- Verify the opportunity is real. Ask for the client name and role before signing, and confirm the vendor has actually been told the client is hiring.
Order matters here. A legitimate vendor submits you, you interview, then you sign if you are moving forward. A vendor that wants an RTR before pitching you is locking you in speculatively. Treat that as a red flag. For how to tell real vendors from fake ones, see how to spot a real vendor versus a scam.
What are the red flags in an RTR agreement?
- No termination clause. If you cannot exit even when the vendor goes silent, walk.
- Automatic renewal. Some renew silently unless you opt out in writing 30 days before expiry. Get the date in writing and calendar it.
- Clawback on direct placements. If the vendor can claim commission on roles you land yourself at companies they pitched, the scope is too broad.
- Binding arbitration only. Disputes go to arbitration and the vendor holds the cards. Ask for court jurisdiction in your home state.
- "All roles" or "all industries" wording. Insist on specifics.
- An RTR request before a real opportunity exists.
An RTR makes sense when the vendor has a proven record placing people in your skill set, the scope is narrow, the tail is 30 days or less, and there is a performance trigger or exit. It is a trap when the vendor has no recent placements in your niche, the scope is broad, the tail runs 90 days or longer, and you cannot leave if they ghost you.
How is an RTR different from an MSA, a W9 or an SOW?
Contractors mix these up constantly.
| Document | What it does | How often you sign it |
|---|---|---|
| RTR letter | Your consent for one vendor to submit you to one client for one role | Per placement |
| RTR agreement | Broad marketing authority over your corp for a period | Per vendor relationship, with a term |
| Authority letter | Proves you can act for your entity | Per vendor, refreshed yearly |
| MSA | General terms, payment terms and liability for all future deals | Once per vendor |
| W9 | Your tax ID form | Per vendor, for payment |
A W9 proves you exist and pay taxes. A business license proves you are registered in your state. The authority letter proves you are allowed to act for the company, which is a higher legal bar, so you need it even if you filed a W9. For the document that defines the actual work, see SOW versus MSA in C2C contracting.
Can you work with multiple vendors while under an RTR?
Yes, as long as they are not on the same client and role, and not inside the scope of an exclusive agreement. If Vendor A has you for a role at Client X, Vendor B can still pitch you for a different role at Client Y. Vendor B can also pitch a different role at Client X after Vendor A's window expires.
It depends on the scope. An agreement covering "all contract roles" shuts the door on other vendors. One limited to specific skills or geography leaves room.
Track every RTR you sign. A simple sheet works: vendor, client, role, start date, end date, exclusivity window, tail end date, renewal opt-out date. When a window closes, you are free again. An undocumented RTR is weaker legally, but it may still bind you. You just have less clarity about what you owe. If you want that tracked automatically, GiraffyReach has a C2C module built for it.
When should you decline or negotiate an RTR?
Decline if the vendor cannot name a specific client, or the window is unreasonably long. A 12 month lock on a 6 month contract is the example. Good vendors adjust terms to close the deal, so you have leverage.
Negotiate when the document includes non-compete language that stops you from working for the client directly. Use this line:
I'll agree to an RTR for the duration of this contract, but if I'm offered a direct hire, I should be free to accept it without owing you a fee.
Most vendors agree, because they are already capturing margin on the first placement.
Timing matters too. Once you sign, you lose leverage. If the bill rate comes back lower than promised or the start date drifts, you cannot take the role to another vendor. So settle the bill rate, start date and contract length first, and get verbal confirmation that the client wants to move forward. Then sign.
A vendor who will not move on any RTR term is telling you they care more about locking you in than placing you. For help with the rate side, see how to calculate your C2C rate against a W2 salary.
Does the RTR slow down your C2C job search?
It should not. The RTR is rarely what costs you contracts. Speed is. Most contractors lose deals because they submit third or fourth, not because they signed the wrong document. Read carefully, negotiate the key terms, and move on.
That is the logic behind how we built GiraffyReach: catch fresh C2C postings the moment they go live, get your profile in front of the vendor first, and handle the paperwork once a real opportunity is on the table. Keep your authority letter ready, keep your RTR tracker current, and be first, or be forgotten.