# The Agency Recruiter Playbook, From Intake to Controlled Submissions

*You will grant or withhold submission consent per role, prevent duplicate submissions, and keep a log proving who was authorized to submit you where and when.*

- Canonical URL: https://www.refolk.ai/candidates/guides/agency-recruiter-controlled-submissions
- Pillar: Applying at volume
- Format: Playbook
- Published: 2026-09-07
- Last reviewed: 2026-09-07
- Reading time: 14 min

A staffing recruiter wants to put your resume in front of their client. This guide is for the job seeker running several agency recruiter relationships at once, and it gives you the control procedure to say yes on your own terms: granting or withholding submission consent per role, preventing any employer from receiving you twice, and keeping a log that proves who was authorized to submit you where and when.

Most public guides explain how agencies work in the abstract and stop at "keep records." That advice fails at volume, where the real failure mode is not paperwork but getting quietly knocked out of a job you wanted. This is the procedure for engineering against that.

## Why the risk is a pulled offer, not a candidate ban

The candidate is rarely "blocked" from a job in any formal sense. The documented risk is that a duplicate submission triggers a fee dispute between two agencies, and the client retracts the offer to avoid paying two fees. That is the outcome you are engineering against.

This matters because it changes what your log is for. If the danger were an automatic ban, you would only need to know you were first. But fee disputes can turn on which agency was the "effective cause" of the hire rather than which one submitted first. No named large employer publishes a specific lockout day-count for candidates, so the ban is not the thing to fear. The thing to fear is a client who sees your name arrive from two sources, decides the fee fight is not worth it, and moves on.

So the value of your record is not proving you were first. It is proving that no second submission ever happened. That single reframing drives every step below.

**21,727 - US agency and technical recruiters in Refolk's index**

Against 680 UK technical recruiters, a roughly 32:1 gap that sets how easily you can walk from a bad agreement.

## What a right-to-represent must specify before you sign

A safe right-to-represent, or RTR, is a written authorization for the agency to present you to one specific job. It must name one requisition and one company, and nothing more.

An RTR is the document that gives an agency the right to submit you. The senior recruiters quoted across the sources are consistent: make sure the RTR is for one single, specific job, and that it includes the job number and description. Refuse a blanket RTR that grants exclusivity for every position. If the document is too broad, ask for it to be amended to name the exact position, exact company, and nothing else, in writing, before you sign.

Practitioner red-flag thresholds give you concrete triggers to reject or amend:

- Exclusivity windows longer than 7 days.
- Any clause letting the agency submit you without per-submission consent.
- Buried non-compete language.
- Any RTR from an agency you cannot verify as a real, approved supplier of that client.

> **Rule:** One req, one company, one expiry
>
> A right-to-represent you sign must name a single requisition number, a single client, and a stated expiry date. If it grants "any suitable opening" or omits a req number, it is a blanket agreement wearing a single-role disguise. Do not sign it.

### Why "successful submission" needs a definition

There is a subtler trap in the RTR text. Recruiters often accept exclusivity without defining what a "successful submission" even is. If the window protects an undefined event, the count can be disputed later. Define submission in writing as documented consent that you gave, not a casual introduction the recruiter made on their own. An exclusivity window that protects a phone call the client never acted on protects nothing.

## The ownership and exclusivity windows you are agreeing to

The windows in an RTR and in the agency's contract with the employer are contract-specific, not set by law. But the numbers cluster, and knowing the range tells you when a proposed window is out of line.

| Source type | Stated window |
|---|---|
| RTR template (single req) | 30 days |
| Agency candidate-ownership standard | 6 months |
| Contingency protection window | 6 to 12 months |
| Legal-recruiting resume shelf life | 6 months |
| Practitioner red-flag threshold | over 7 days |

Read this table as two layers. The window in the RTR you sign should be short, ideally at or under a week and rarely more than the 30-day template figure. The longer windows - six months of candidate ownership, six to twelve months of contingency protection - are the agency's contract with the employer, not with you, but they set how long your name stays "attached" to that agency at that client in the eyes of the fee.

The six-month figure recurs in places that have nothing to do with each other: agency candidate-ownership standards, legal-recruiting resume shelf life, and even public-sector applicant-pool reuse. That recurrence is the useful signal. Even where no contract binds you, a submission's practical cooldown clusters near six months. Your log needs a six-month horizon on every row so you can see, at a glance, when a client and requisition is genuinely clear again.

#### Deciding whether to sign an RTR

Horizontal axis runs from Broad scope (any opening) to Narrow scope (one req). Vertical axis runs from Unverified agency to Verified approved supplier.

| Quadrant | What it means |
| --- | --- |
| Unverified and broad | Walk. This is the fake-role and mailshot zone. |
| Unverified but narrow | Verify the supplier relationship first, then reconsider. |
| Verified but broad | Amend to a single req and expiry before signing. |
| Verified and narrow | Sign, then log the row before submission. |

*Scope and verifiability are the two axes that decide whether an RTR is safe to sign.*

## The fields that stop a duplicate before it starts

To prevent a duplicate submission you need a dedupe key: the combination of fields that uniquely identifies one submission, so a second one is visible before it happens. The load-bearing key is client or company, plus requisition number, plus role, plus date, plus submitting recruiter.

Practitioner call scripts confirm what a good recruiter collects and agrees before submitting: client name, job title, and pay rate, plus a check on whether you have been submitted for that role before. Applicant-tracking templates add the unique requisition number as the field that actually distinguishes two near-identical roles at one company. Miss the req number and two openings at the same client collapse into one line, hiding exactly the duplicate you were trying to catch.

Capture these columns per submission:

| Field | What it does |
|---|---|
| Company and requisition number | The dedupe key; two agencies to the same req is the failure |
| Role title and pay rate | Distinguishes near-identical postings and flags rate conflicts |
| Submitting recruiter and agency | Names who is authorized at this client |
| Consent timestamp and proof | Proves you approved, and that the submission occurred |

The reason to log the consent timestamp and the proof separately is that they are different events. Consent is what you granted. Proof is confirmation the recruiter actually sent it. A row with consent but no proof is a submission you cannot rely on.

> **Watch out:** Proof of submission is opt-in
>
> Some recruiters confirm submission only if asked, and never copy candidates on submissions. An unrequested submission is invisible to you, which is the exact condition that produces silent duplicates. Always ask for dated written confirmation, and treat no confirmation as not submitted.

## The procedure, from intake call to a logged submission

Run this order for every recruiter and every role. It moves from vetting the recruiter, to stating your rule, to consenting per role, to holding the window, to closing it out. Each step has a clear "done" condition.

#### Controlled submission, one role at a time

1. **Run the intake call and vet the recruiter** - Confirm the recruiter is real and the role exists before agreeing to anything. Never agree to be put forward unless they name the end client, and ask whether they are an approved supplier and when they last placed there. Done when you have client name, role, and confirmation of a genuine client relationship.
2. **State your consent rule in writing** - Send one line: submit me only with my written approval per role. Make consent-first explicit because some agencies spec candidates to market before asking. Done when the recruiter has acknowledged the rule in writing.
3. **Run the duplicate check before consenting** - Cross-check the client plus requisition number against your submission log on the same call, and have the recruiter check whether you have been submitted for the same role before. Done when no prior submission to that client and req exists.
4. **Review and scope the right-to-represent** - Confirm the document names one role, one requisition number, one company, and a short stated expiry, then amend any broad language before signing. Done when you hold a single-role RTR with an expiry, from a verified agency.
5. **Grant per-role consent and log it** - Record client, req number, role, pay rate, recruiter, date, and consent timestamp in your log before the submission happens. Done when a complete log row exists ahead of submission.
6. **Obtain proof of submission** - Request written confirmation that the submission actually occurred, by email, text, or message, because confirmation is often opt-in. Done when a dated confirmation is stored against the log row.
7. **Enforce the exclusivity window, then release** - Hold other agencies off that specific client and requisition only for the agreed window, and log the expiry date. Done when the window is tracked and no other agency can submit you to that one requisition.
8. **Remediate an unauthorized submission** - If a recruiter submits you without consent, tell the firm the recruiter does not represent you for this role, tell the recruiter to withdraw, and log the incident. Done when the firm is notified, the recruiter has withdrawn, and no fee attaches.

The consent-first rule in step two is worth defending explicitly, because there is genuine disagreement in the trade. It is common for a recruiter to "spec" a candidate, meaning float your profile to a client to gauge interest before asking you. Good agencies get permission first. Since a spec submission that surfaces later is untracked, and untracked is exactly how silent duplicates happen, you make consent-first non-negotiable and get it acknowledged in writing.

**Consent rule and proof request, one message**

```
Thanks for the call. Two things I need in writing before we go further.

1) Consent per role. Please submit me to a client only with my written approval for that specific requisition. No speculative or blanket submissions.

2) Proof each time. When you submit me, please confirm in writing that it was sent, with the date, the client, and the requisition number.

For this role: client [CLIENT], requisition [REQ NUMBER], title [ROLE]. I approve submission to this one requisition only, with an exclusivity window of [DAYS] days from today. Please confirm you agree to the above.
```

*Send after the intake call, before any RTR. Paste the client and req details in where shown.*

## How this goes wrong, and the check that catches each

Every failure below has a false positive that makes it look fine. The check is what separates the real signal from the lie. Give this section the most attention, because these are the ways careful candidates still lose the job.

### Blanket RTR disguised as single-role

It looks "standard," which is the trap. The check: confirm the document names one requisition number and one company only. Reject it if it grants representation for "any suitable opening." A single-role RTR that omits the req number is not single-role.

### Verbal-only submission with no proof

The recruiter says "you're in," and it feels done. The check: demand written confirmation that the submission was actually sent. No dated confirmation means you treat the role as not submitted, so you neither hold a window for it nor count it against your log.

### Spec or mailshot without consent

The recruiter frames it as normal market activity, and it can even breach data rules when done in bulk. The check is your consent-first rule from step two. The tell that it happened anyway is an untracked submission surfacing later at a client you never approved.

### Duplicate that costs you the offer

Two agencies both claim you, and you assume "first wins." It does not reliably win, because disputes turn on effective cause, and the client may retract the offer to dodge the double fee. The check: one submission per client and requisition in your log, enforced by the duplicate check before you ever consent.

### Exclusivity with undefined submission

You think the window protects a real submission, but "submission" was never defined. The check: define submission as documented consent you gave, in writing, so the window protects an event that actually exists.

### Stale log at volume

The sheet looks complete, so you trust it. The check: tracking degrades past a threshold. It is manageable to about five applications, strains around fifteen, and is genuinely hard at thirty without a system. Reconcile recruiter confirmations against your log rows weekly.

### Unverifiable recruiter or fake role

The role sounds real and specific. The check: the recruiter names the end client and their approved-supplier status. If they will not, refuse to sign and do not send your resume.

> Your log's job is not to prove you were first. It is to prove no second submission ever happened.

## Your leverage depends on how thick the market is

How easily you can walk from a bad RTR depends on recruiter supply where you are. In a thick market you have real exit; in a thin one, the cost of signing something bad is higher because your alternatives are fewer.

| Segment | Count |
|---|---|
| US agency and technical recruiters | 21,727 |
| US staffing-industry recruiters | 27,562 |
| UK technical recruiters | 680 |
| US to UK technical recruiter ratio | about 32:1 |
| UK as share of US technical supply | about 3.1% |

In Refolk's index of professional profiles, US technical-recruiter supply stands at 21,727 against the UK's 680, a roughly 32-to-1 gap. A US candidate can decline a blanket RTR and find another agency working the same client without much friction. A UK technical candidate is in a far thinner market, so a single bad signing removes a larger share of the available agencies. Adjust your firmness to the market: in a thick one, walking is cheap and you should walk from anything unverifiable; in a thin one, spend the extra time amending rather than abandoning.

Knowing which agencies actually place at your target client is the friction here, and it is the friction [Refolk](/candidates) removes. Rather than cold-calling firms and hoping they are approved suppliers, you can find the recruiters who already work the accounts you care about, then run the vetting call from step one with a name and a track record in hand.

Ask me this: `Recruiting managers at US IT staffing agencies who handle Workday-based submissions.` - [run the search](https://www.refolk.ai/start?q=Recruiting%20managers%20at%20US%20IT%20staffing%20agencies%20who%20handle%20Workday-based%20submissions.).

*Returns named recruiters at agencies that submit through employer ATS pipelines, so you can vet supplier relationships before you sign anything.*

## Keep the log current, and the proof reconciled

The log is only worth what it can prove, and it decays the moment a recruiter confirmation goes unrecorded. Reconcile it weekly and it stays evidence; leave it and it becomes a story you tell yourself.

The average job seeker submits 100 to 200 applications over a three-to-six-month search, and with several agency recruiters in play, the number of submissions you did not personally file climbs fast. That is precisely where a stale log bites. Set a weekly reconciliation: match every recruiter confirmation against a log row, chase any consent row that has no proof yet, and clear any window whose expiry has passed so other agencies are released for that requisition.

Refolk can carry part of this load by tailoring your resume to each posting and scoring how well you actually fit before you consent to a submission, so the version a recruiter sends is the one you approved rather than a generic file you have lost track of. But the consent log and the proof trail stay yours to keep; no tool should own the record of who was authorized to submit you where.

#### Before you call any submission done

- [ ] The RTR names one requisition number and one company, with a stated expiry.
- [ ] The exclusivity window is defined against documented consent, not a casual introduction.
- [ ] A log row exists with client, req number, role, pay rate, recruiter, and consent timestamp.
- [ ] You hold dated written confirmation that the submission was actually sent.
- [ ] The duplicate check shows no other agency submitted you to this client and req.
- [ ] The exclusivity window expiry is recorded, so you know when other agencies are released.
- [ ] Any unauthorized submission has been remediated the same day and logged as an incident.

Run this loop for every recruiter and every role, and the outcome you are protecting against - a client who quietly drops you to avoid a two-agency fee fight - stops being something that happens to you and becomes something you can prove never should have.

## Frequently asked questions

### Should I sign a right to represent?

Yes, but only a scoped one. A safe right-to-represent names one specific job number, one description, and one company, with a short stated expiry. Refuse any blanket version that grants exclusivity for every position or lets the agency submit you without per-submission consent. Watch for exclusivity windows longer than seven days and buried non-compete language, and never sign one from an agency you cannot verify as an approved supplier.

### What happens if two agencies submit me to the same job?

You are rarely banned outright. The documented risk is that the client retracts the offer to avoid paying two agency fees. The fee dispute itself can turn on which agency was the effective cause of the hire, not simply who submitted first. That is why single submission per client and requisition, proven in your log, matters more than trying to be first.

### A recruiter submitted my resume without permission. What do I do?

Act the same day. Tell the firm directly that the recruiter has nothing to do with your candidacy and does not represent you for this opportunity. Then tell the recruiter to withdraw any interest, reminding them you gave no permission for this specific job. If they argue, say you will explain to the firm that they involved themselves without your consent. Log the incident with timestamps.

### How long does an agency own me after a submission?

It is contract-specific, not statutory. A common RTR template runs 30 days for one requisition, while the agency-employer candidate-ownership standard is six months from the date of submission, and contingency protection windows commonly extend six to twelve months after introduction. Because the six-month figure recurs across unrelated systems, treat six months as the practical cooldown horizon in your log even where no contract binds you.

### How do I track which recruiter submitted me where?

Keep one row per submission keyed on company plus requisition number plus role plus date plus submitting recruiter. Capture pay rate, consent timestamp, and proof of submission against each row. Tracking stays manageable to about five applications, strains around fifteen, and gets genuinely hard past thirty without a system, so reconcile recruiter confirmations against your log weekly.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/agency-recruiter-controlled-submissions*