The Agency Submission Request, Scored to Authorize, Narrow, or Decline

A third-party recruiter wants your OK to send your resume to a client, sometimes with a right-to-represent email to sign. This guide is for people running a high-volume search who get these requests often and need to make the same call well every time. It gives you six dimensions to score, thresholds that land on authorize, narrow, or decline, and the written reply that limits consent to one role, one employer, and a set number of days.

What does an agency submission request actually commit you to?

Saying yes makes the agency the party that introduced you to that employer. Under published agency terms, that introduction can tie the employer to paying that agency a fee if it hires you within 6 to 12 months, whichever route you later come in by. The document you sign is usually much shorter than the contract that actually decides the outcome.

Four terms come up in every request:

• Right to represent (RTR): a written consent that lets one agency submit you for a role. A legitimate one "covers one specific role, at one specific company, for a defined period (usually 30 to 90 days)."
• Introduction: the event that starts the agency's claim. One set of terms defines it as "the provision of a candidate's CV or details to the client".
• Ownership window: the period after introduction during which the employer owes the agency a fee if it hires you.
• Contingency versus retained: a contingency recruiter is paid only if you are hired. A retained recruiter is paid by the client to run the search, often in upfront instalments.

How long does a recruiter own a candidate?

Usually 6 or 12 months from introduction, and sometimes longer, because the clock can restart. The published terms below show the range. Nobody has published how often agencies use each window, so assume the longer one until the recruiter tells you otherwise in writing.

Two details in those terms matter more than the lengths. First, some agencies say clients "automatically agree to these Terms of Business" just by receiving a CV, so the clock can start the moment your resume lands, whether or not the client asked for you. Second, one candidate-facing declaration says consent can be given "verbally, in writing, or through engagement in the recruitment process", which means a friendly phone call may count.

Who sends these requests?

Most requests come from contingency recruiters at staffing firms, not retained search consultants. In Refolk's index of professional profiles, US profiles that mention retained executive search in their headline make up about 2.3% of agency recruiters, so the default assumption for any request is a contingency recruiter working as one of several vendors.

Refolk's index, filtered to the Staffing and Recruiting industry and recruiter titles. Title shares come from a 25-profile sample per market. Other named US employers in the sample include TEKsystems and Volt.

The two filters differ (title plus industry against a headline keyword), so read this comparison as directional, not exact.

Three practical points follow from these numbers:

• A title won't tell you if someone works at an agency. In the US, most agency recruiters are titled plain "Recruiter", the same word in-house teams use. Check the employer and industry on the profile instead.
• "Retained" is a claim, not a category you can see. Retained recruiters are rare, and 44% of the retained sample hold owner-level titles. A junior-titled recruiter at a large staffing firm who says "retained" deserves a follow-up question.
• Agency legitimacy is quick to check. One staffing writer says offshore resume-farming operations "fall apart under ten minutes of scrutiny". The FTC notes that scam recruiters use personal email and ask for personal information up front.

The six scoring dimensions

Score each request 0, 1, or 2 on six dimensions: client named and verified, prior contact with the employer, consent width and length, fee model, fee drag against a direct applicant, and rate and role disclosure. The total runs from 0 to 12, and three dimensions carry hard stops that override the total.

1. Client named and verified

What it proves: a real requisition exists, and you can check whether you have touched it before. When it lies: the recruiter names a real company with no open role, which is how resume farming works. A name only scores 2 once you find the role on the client's own careers page or confirm it "using a phone number you know to be legitimate", in the FTC's words.

2. Prior contact with that employer

What it proves: whether an agency submission would collide with a record already in the employer's system. When it lies: you think you have never applied, but an old application under a different email still matches on phone or LinkedIn URL. One major ATS "compares phone numbers using the underlying number only and ignores country codes", so a new number that keeps your old local digits still matches. If you tailor applications in Refolk, each posting you applied to already has its own tailored resume on file, so this check is a quick search instead of an inbox dig.

3. Width and length of consent

What it proves: how much of your search you give away. When it lies: a tidy 30-day RTR sits on top of a 12-month introduction clause between the agency and the client. The RTR scores 2 on paper, but your real exposure is the longer contract. Score on the longer window unless the recruiter puts the shorter one in writing.

4. Retained or contingency

What it proves: whether the client has committed to this agency, or whether several vendors may be racing to submit the same people. When it lies: "retained" gets used as reassurance by an agency that sits in the client's system as an ordinary contingent vendor. The test question is whether the client paid part of the fee upfront in instalments. If the recruiter won't say which model it is, score 0.

5. Fee drag against a direct applicant

What it proves: whether the agency fee buys you anything you couldn't get on your own. Typical contingency fees run 15% to 25% of first-year base, and retained executive search runs 25% to 33%. When it lies: people assume the fee always sinks the agency candidate. No controlled study comparing an agency candidate with an equal direct applicant has been published, and the pipeline data cuts the other way (see the section on applying directly below). Score 0 only when you hold a better route, such as a referral, that the agency would just put a fee on top of.

6. Rate and role details disclosed

What it proves: the recruiter has a real job description and has spoken to the client. When it lies: a job description pasted from a public posting looks like disclosure but proves nothing about access. No source surveys how often RTRs include the rate, so whether a missing rate is a red flag isn't established. I score it 1, not 0, and ask for it.

Reading the score: authorize, narrow, or decline

Any hard stop means decline. Otherwise, 10 to 12 means authorize, 6 to 9 means narrow, and 5 or below means decline. These thresholds are my judgement for a high-volume search and haven't been tested against outcomes. Move them if your market runs on agencies, as some legal and contract IT markets do.

Before you authorize, check your fit. A submission uses up that employer for the length of the ownership window, so a weak-fit submission costs more through an agency than through a direct application. Refolk scores how well you match the posting, which is the number to check before you lend an agency your name for six months or more.

What narrowing looks like

Narrowing isn't a soft yes. It's a yes to a smaller thing, given in writing:

• Cut the scope to one named role with a requisition or reference number.
• Cut the length to a stated number of days with an end date.
• Exclude every other office, role, and client.
• Ask which ownership window applies under the agency's terms with the client, and what starts it.
• Ask for the rate and the fee model.
• Ask to see the exact resume version they will submit.

How to decline without blocking yourself from the employer

Decline before the resume is sent. Under terms where the client agrees just by receiving a CV, the claim starts when the client receives it, not when you sign anything. A clean written decline leaves the employer with no agency record of you, so you can apply directly later or let another recruiter represent you for a different role. Never reply "sure, sounds good" while you think about it, because some declarations count any engagement as consent.

Apply directly or through a recruiter?

Apply directly when you already have a route the agency adds nothing to, especially a referral. Go through the recruiter when they bring access you don't have. Never do both for the same role, because the duplicate is a bigger risk than the fee.

The fear is that an employer will pass on you to save a fee worth a fifth of your salary. The closest evidence is pipeline data from one ATS vendor's talent trends report. Agency candidates are 0.4% of applications, but they move from application to interview at 42% against 3% for inbound applicants, about 14 times the rate. From interview to offer, agency candidates convert at 8%, inbound at 6%, and referrals at 16%.

That isn't a controlled comparison. The agency pool is pre-selected, so these numbers can't prove the fee is harmless. They do show the fee isn't visibly sinking agency candidates as a group, and that a referral beats both routes at the offer stage.

The practitioner sources disagree on what to do with a direct route. One legal recruiting firm advises against applying directly just to save the employer a fee, which tilts you toward authorizing. Another holds that a firm is locked by whichever channel your resume arrived through, so a direct application spends your one shot just as an agency submission does. Both agree on the main point: pick one channel per role.

There's one more catch. Under Oracle Recruiting's "Person Specific" agency setting, "If a candidate applies for another job on the career site and gets hired, the agency still get a referral commission." Once an agency has introduced you, applying directly may not avoid the fee you've already triggered.

The fee rarely loses you the offer. The duplicate submission does, and the ATS decides it before anyone reads your resume.

What happens when two recruiters submit you for the same job

The employer's system usually settles it on timestamp before any person gets involved. Greenhouse flags a possible duplicate "if any of the following match an existing profile: email address, phone number, or LinkedIn profile URL", but its public docs don't say who gets the credit. Oracle Recruiting is explicit: during the exclusivity period, a second agency's duplicate profile triggers a warning and "The agency can't add the candidate profile."

People who see the dispute take it seriously. A Zulily recruiter put it plainly in the Seattle Times: "Once you sign that right-to-represent, you are agreeing to not have another agency submit you." Legal recruiting is stricter still. One legal recruiter's FAQ explains why firms shy away from double-submitted candidates: "No law firm wants to risk being responsible for two search fees."

If a recruiter submitted your resume without permission

No published remedy undoes an unauthorized submission that's already in the employer's system. The legal job board guidance says that once a firm receives a resume, "it cannot be resubmitted to that firm, absent unusual circumstances, for at least six months." The same legal recruiting firm describes a recruiter who sent one candidate's resume to more than 30 firms without permission, and notes that "resumes do have a shelf life of at least six months."

What I would do, though no source sets this out as a remedy: write to the agency withdrawing any implied consent, record the date you found out, and tell any other recruiter before they submit you to that employer. The same firm says that after six months, "if the firm has not expressed any interest in you, you can have another recruiter represent you to this firm."

The procedure: from request to logged consent

Run these eight steps for every request, in order. The first five gather facts, the sixth makes the call, and the last two put it in writing and on your calendar.

Capturing the request and checking the agency each take a few minutes. That's an estimate, not a measured figure. Checking your own record is the step people skip, and it's the one that prevents the costly mistakes. As the legal recruiting firm puts it, "you are responsible for keeping track of your job search and the firms to which you have been submitted."

Use this reply for both authorize and narrow. For an authorize, the questions are a formality. For a narrow, the line asking them not to submit until you have answers is the important part.

Subject: Consent to submit - [Role title], [Employer], ref [requisition number]

Hi [Recruiter name],

Thanks for reaching out about the [Role title] role (ref [requisition number]) at [Employer], [location].

I consent to [Agency name] submitting my resume for this one role at this one employer only. This consent runs for [60] days from today, [date], and expires on [expiry date] unless I renew it in writing. It does not cover any other role, office, or client.

Before you submit, please confirm in writing:
1. Is this search retained or contingency?
2. What ownership or introduction period applies under your terms with [Employer], and what starts it?
3. The pay rate or range for the role.

Please send me the exact resume version you plan to submit, and do not submit until I have your answers.

Prior contact: I have not applied to [Employer] directly or through another agency in the last 180 days.
Prior contact: I applied to [Employer] directly on [date] for [role]. Please do not submit me if that application is still active.

Thanks,
[Your name]

Hi [Recruiter name],

Thanks for thinking of me for the [Role title] role at [Employer]. I am not authorizing a submission to [Employer], and I do not consent to my resume or details being sent to them or to any other client without my written approval for a named role.

I am happy to hear about other specific roles one at a time.

Thanks,
[Your name]

How this goes wrong

Most bad outcomes come from facts the candidate didn't know at the time of the call: an old record in the employer's system, a contract behind the RTR, or consent they didn't realise they gave. Each failure below includes the check that catches it.

1. The client is named but not verified. A real company with no open role means your resume is being farmed. Check: the role on the client's own careers page, confirmed through a number you found yourself.
2. You think you have no prior contact, but you do. An old application under a different email still matches on phone or LinkedIn URL, and country codes are ignored in phone matching. Check: search your inbox for the employer's domain and for ATS confirmation emails, under every address you have used.
3. A short RTR has a longer contract behind it. A 30-day RTR doesn't shorten a 12-month introduction clause between the agency and the client. Check: ask in writing which window applies.
4. The window restarts. Under the "whichever is the later" wording in some terms, a rejected or withdrawn offer starts the clock again. Check: read the clock-start wording, and log a new expiry date after any offer event.
5. You gave consent without realising it. Some declarations count verbal interest or simply "engagement in the recruitment process" as consent. Check: always answer with a written, scoped reply, never a casual yes.
6. "Retained" is used as reassurance. The word means little if the agency is set up as an ordinary contingent vendor in the client's system. Check: ask whether part of the fee was paid upfront in instalments.
7. You assume the fee always sinks you. That idea comes from folklore, not data. In the pipeline data, agency candidates convert to offer at 8% against 6% for inbound. The real risk is a duplicate. Check: score fee drag on whether you hold a better route, not on the fee's size.
8. You signed a blanket RTR. One RTR glossary says that "you can submit me anywhere" language "rarely holds up", but it can still put other agencies off for months. One staffing writer describes a candidate who spent five months turning recruiters away. Check: never sign scope wider than one role.

A false positive runs the other way too: a request that scores low on disclosure but comes from an honest recruiter who simply hasn't been given the rate yet. The narrow path exists for exactly that case. Ask, wait for written answers, and upgrade to authorize when they arrive.

Keeping your consents current

A consent stays safe only while your records are accurate. Log every submission with its expiry the day you send the reply, and get consent again whenever anything changes. One RTR glossary says it directly: "if the terms change, get consent again." Some RTR templates ask you to confirm you haven't been submitted elsewhere for the same role "within the last 180 days", which you can only answer honestly if your log goes back that far.

Keep one row per employer, not per agency, with the date, the channel (direct or agency name), the role, and the expiry. When a new request arrives, that row decides the prior-contact dimension in seconds. When an expiry passes with no interest from the employer, mark the row lapsed, not deleted. Under the restart wording described above, an old row can come back into play.