Also written: RTR · Right to represent
Why does an RTR exist?
Because layering makes duplicate submission easy and expensive. One requirement can reach a consultant through several vendor chains at once. If two vendors submit the same person to the same end client, the client usually disqualifies the candidate outright rather than adjudicating which vendor was first.
The RTR is the paperwork that prevents it: the consultant confirms in writing, per role, which vendor is representing them.
What does an RTR actually contain?
At minimum: the consultant’s name and consent, the end client, the specific requirement or job title, the vendor being authorised, the rate agreed, and a date. Some also carry an expiry, after which the consultant is free to be represented elsewhere for that role.
How is it enforced operationally?
On a manual desk, by memory and a spreadsheet — which is why collisions happen. Enforced properly, it is a per-route lock: once a consultant has an RTR for a role through one vendor, no other route can carry them for that same role until the RTR lapses.
That is only possible if duplicate copies of the requirement are collapsed into one canonical job first. If twelve vendor blasts are twelve separate records, there is nothing for the lock to attach to.
Is an RTR a consent record?
Yes, and it should be treated as one. It is evidence that a named individual agreed to have their résumé sent to a named client at a named rate, so it belongs in an immutable audit log alongside the submission itself, not in an email thread.
Related on this site
More terms
- Vendor blast — A vendor blast is the mass distribution of one job requirement across many vendors, so the same role reaches a staffing desk repeatedly in slightly different wording.
- W2 vs C2C vs 1099 — W2, C2C, and 1099 are the three tax terms for US contract work: employee of the agency, company-to-company billing, and independent contractor paid as an individual.