Job search
Right to Represent Requests: Check the Client, Role, Rate, and Exclusivity Before Agreeing
Check a recruiter’s right-to-represent request for the named client, requisition, candidate pay, duration, data sharing and exclusivity before agreeing.
Before agreeing to a right-to-represent request, identify the staffing firm, end client and exact opening, then check the candidate pay, work arrangement, information to be shared and exclusivity terms. Read the attached and linked terms as well as the email. If a material detail is missing or conflicts with what you discussed, withhold authorization and tell the recruiter which point needs clarification before they submit your profile.
An RTR can serve a legitimate purpose: recording permission for a recruiter to present you for an opportunity. Its scope still depends on the actual wording. We checked public agency terms, an untouched TEEMA form and FTC guidance on October 13, 2026; no agreement was signed, form submitted or recruiter contacted. The examples below are fictional. LandOffer publishes this guide and offers recent tech-job discovery, with employer and agency verification still needed for each role.

Separate permission to submit from a job offer
A representation request concerns an agency's proposed action on your behalf. It does not establish that the client has selected you, that the recruiter has already submitted you or that a particular assignment is guaranteed. Keep those events separate in your application record.
The title “Right to Represent” does not tell you everything in the document. It may include statements about previous applications, restrictions on other routes, information sharing, incorporated policies or a separate non-circumvention provision. An email mentioning one role can accompany terms that discuss a wider client relationship.
Do not assume a reply saying “I agree” is merely an acknowledgement or that only a handwritten signature matters. Read what the request says constitutes agreement. This article supplies a review workflow, not a determination of a particular agreement's legal effect. If you cannot understand a restriction or its consequences, obtain qualified advice about the actual document and jurisdiction before accepting it.
Establish the agency, client and requisition
Record who is asking, which organization would receive your profile and which organization would employ or contract with you. The agency, payroll employer and end client may be different entities. A recognizable client name does not independently establish that the sender is authorized to recruit for it.
Verify the recruiter through a route located independently on the agency's official website when needed. Then ask for the client's name, requisition ID, title and location, to the extent disclosure is permitted. If the client is confidential, ask what identifying information can be provided before authorization and how existing submissions will be checked. You may decide that the available detail is insufficient to proceed.
Compare the written request with the conversation. A different client, office, seniority level or requisition needs explanation before you agree. Matching these details gives you and the recruiter the same opportunity to discuss, rather than relying on a broad title. Similar job descriptions can also hide an existing application. Keep earlier direct applications and agency submissions available so you can answer a prior-submission declaration honestly.
If another recruiter approaches you about a potentially identical role, pause the second authorization while comparing client and requisition details. Do not assume the first person to call you automatically controls the role, or that every client handles duplicate submissions the same way. Preserve the actual documents and request instructions about the existing record.
Confirm that the rate is your pay
Ask whether the quoted figure is the amount paid to you, the agency's bill rate to the client or a budget range. Record currency, hourly or annual unit, proposed employment arrangement, expected hours and any stated benefits or expenses. A higher-looking number is difficult to evaluate until those details are clear.
For a proposed US W-2 assignment, ask which entity would employ and pay you and which benefits or deductions are described in the actual terms. For a 1099 or business-to-business proposal, obtain the relevant written arrangement rather than treating its headline rate as equivalent to employee compensation. A label in an email does not settle legal classification, tax treatment or work eligibility.
Ask how paid hours, overtime, leave, travel and equipment are handled where relevant. “Twelve-week assignment” is a proposed duration; it does not by itself promise 480 paid hours. Keep compensation clarification separate from any statement agreeing to representation or accepting employment.
Read each time period and exclusivity clause separately
Find the event that starts each period: signing, submission to a client, introduction, placement or something else. Then read what the period restricts, how it ends, any notice requirement and whether another provision survives termination. Write down both the start event and the action restricted. Do not treat every number in the document as the date your representation ends.
Three official examples illustrate why the title alone is insufficient. These are the agencies' published terms, not findings that every provision is enforceable or applies to your situation.
| Public example checked | What the provider's wording says | What to inspect in your own request |
|---|---|---|
| Staffactory terms, updated April 30, 2026 | Describes a 90-day restriction for the same role and client after signing an RTR; separately addresses placements within 12 months of an introduction, including affiliates | Do not confuse the role-specific period with the separate non-circumvention provision |
| High Cliff Partners RTR, a Toronto SAP recruiter | Requests disclosure of applications within the previous 12 months, including other SAP roles at the client; also restricts other submissions to the same position or client/end client while under consideration | A prior-application lookback is not automatically an authorization expiry date; inspect client-wide wording too |
| TEEMA RTR | Names job/requisition and end-client fields, duplicate-authorization declarations and a linked Candidate Code of Conduct | Review each declaration and incorporated document before checking agreement boxes |
Staffactory also describes sharing provided information with the named client, including pay expectations and the RTR. Its terms contain provisions that survive account termination. Do not assume closing an account cancels every restriction.
The TEEMA code asks candidates to track direct and agency applications and directs follow-up through its recruiter. Those are TEEMA's stated expectations. Another agency's communication rules may differ. In our native observation, TEEMA's public agreement boxes remained unchecked; no personal details were entered.
Worked review: Mira holds an incomplete authorization
Mira is a fictional backend engineer. Fictional Clearbrook Staffing discusses an API assignment at fictional Harbor Data, requisition HD-217. The email mentions USD 68 per hour on a proposed W-2 arrangement, a twelve-week assignment and two office days a week in Seattle. The attached authorization instead refers to “any client opportunities” for twelve months and links additional terms.
Mira has also found a March 2026 direct application to another Harbor Data role. No real agency, vacancy or candidate agreement is represented by this example. Her completed review reads:
| Item | What the fictional packet establishes | Mira's decision |
|---|---|---|
| Role and client | Email names Harbor Data and HD-217; authorization is broader | Ask for a consistent, named scope; hold the authorization |
| Candidate rate | Email says USD 68/hour W-2, without a full employment document | Confirm this is candidate gross pay and identify the employing entity |
| Work arrangement | Twelve weeks, two Seattle office days weekly | Confirm schedule, expected paid hours and any travel conditions |
| Prior application | March 2026 direct application to another client role | Disclose the record accurately; ask whether it affects this request |
| Exclusivity | Attachment says any client opportunities for twelve months | Ask what roles, clients and routes it restricts and when the period begins |
| Linked terms | Additional document supplied but not yet reconciled | Read it before accepting; record conflicts for clarification |
| Profile sharing | Intended resume is known; wider distribution scope is unclear | Identify recipients and resume version before permission |
The result is not authorized; clarification required. Mira does not sign the broad form and rely on the email to narrow it automatically. She also does not delete the older application or answer that she has never applied to Harbor Data. Whether the prior record creates a problem remains an agency/client-process question in this scenario.
Worked rate check and clarification response
Suppose Clearbrook's fictional response distinguishes USD 68/hour as Mira's candidate gross pay from a USD 95/hour client bill rate. That resolves which number belongs in her compensation comparison; it does not resolve the exclusivity or linked terms.
At 40 paid hours a week for twelve paid weeks, USD 68/hour would produce USD 32,640 gross. That is conditional arithmetic, not guaranteed earnings, take-home pay or an annual salary. Mira still needs the employing entity, actual paid-hours conditions, benefits, expenses and assignment terms in writing. This calculation does not establish that the proposed classification is correct. The client bill rate is not an amount promised to her.
Her completed, unsent clarification draft reads:
Thank you for clarifying the proposed candidate gross pay of USD 68/hour. Before I authorize submission, please confirm Harbor Data, requisition HD-217, the API role, employing entity and Seattle attendance requirements in the written request. I previously applied directly to a different Harbor Data role in March 2026 and can provide the relevant record. The attachment refers to any client opportunities for twelve months. Can you explain that scope and provide a revised request limited to the agreed opportunity if that is available? I would also like to discuss a defined representation period, for example 30 days from an agreed start event, and understand any separate restrictions in the linked terms. I have not authorized submission while these points remain unresolved.
The suggested 30 days is a fictional discussion proposal, not an industry standard, legal template or term the agency has accepted. A revised document would need another review. A recruiter saying “that's fine” does not by itself demonstrate that conflicting written provisions were amended.
Mira's state record remains precise: pay basis clarified within the example; scope unresolved; request drafted but unsent; no authorization or submission completed. Both the calculation and the response are finished preparation assets without inventing a signed agreement or a client outcome.

Check the resume and information-sharing scope
Identify the exact resume version the agency would send. Ask to review changes to titles, dates, skills, ownership claims or results before that version is submitted. Reformatting should not turn assisted work into ownership, add technologies you have not used or change dates. Keep a copy of the version you actually approve.
Read what information may be shared and with whom. A permission to submit a resume can sit beside broader acknowledgements. TEEMA's public form, for example, separately states that agreement confirmation and its code may be shared with future clients. That wording should be read separately from the named-role submission authorization; it is not proof that you approved applications to every future role.
Keep passwords, verification codes and unrelated private documents out of a representation conversation. If sensitive records are requested later, verify the recipient, purpose and channel for that stage. An agency logo or an RTR form does not establish the legitimacy of every subsequent upload request.
The FTC's job-scam guidance warns about placement services requesting candidate fees, especially upfront, and paying for a promised job. It also explains that finding no complaints does not establish honesty. A request for representation is neither automatically fraudulent nor sufficient proof that the recruiter and opportunity are verified.
Save authorization and submission as separate records
If you decide to proceed after reviewing the actual terms, retain the accepted version, named client and requisition, resume version, pay basis, date and relevant correspondence. Ask how you will be informed that the agency submitted your profile. Record an agency-reported submission as reported unless you have additional confirmation.
If you want to stop or change representation, read the document's notice and termination provisions and request written clarification about the specific role and any surviving restrictions. Do not assume that silence, account deletion or a new recruiter contact cancels an earlier agreement. A disagreement over scope may require advice beyond a routine recruiting email.
For the next tech role you discover on LandOffer, keep the client, requisition, candidate pay and submission permission together. Make the decision visible: ready to review, held for clarification, authorized under retained terms or submission reported. Keep the version and evidence behind each status. A request stays a request until you actually authorize the stated scope; authorization remains separate from an agency-reported submission or a client response.
Sources and Further Reading
- Staffactory: Terms & services, updated April 30, 2026; checked October 13, 2026.
- High Cliff Partners: Right to represent, provider-specific Canadian SAP recruiting terms; checked October 13, 2026.
- TEEMA: Right To Represent Agreement, public form inspected without entering data or accepting terms, October 13, 2026.
- TEEMA: Candidate Code of Conduct, linked two-page document checked October 13, 2026.
- FTC: Job Scams, March 2023 guidance; checked October 13, 2026.


