Skip to content
IT staffing

RTR & Duplicate Guard

Checks, before you submit, that the consultant hasn't already gone to that end client and that a right-to-represent covers this exact requirement and rate.

Check before submit

Before a submission goes out, the Guard answers green, amber or red, with its reasons

RTR & Duplicate Guard on a wide screen, at the top of Check before submit: a dark sidebar with Check before submit, Submissions, RTR ledger, Possible duplicates, Consultants and Retention; the top bar names the fictional firm Banjara Demo Tech LLC with a Synthetic data badge and the signed-in recruiter, Anusha Reddy. Under the heading and its intro, the date and the rights to represent on file. On the left, a new submission form with a consultant, a requirement and a rate of $95.00 an hour, above the rights to represent waiting to go out. On the right, the check's answer: Green, Clear to submit, with a checklist saying a right-to-represent covers this requirement and rate and that there is no earlier submission to this end client, and a card to submit the consultant to Summit Demo Energy with the Submit button.The real screen, on synthetic data
Green: an RTR covers this exact requirement and rate, and no earlier submission to this client

Demo built on synthetic data.

1 of 5: Check before submit

The problem

A duplicate submission can cost you the placement and the vendor. So can submitting on an expired right-to-represent, or at a rate the consultant never agreed to. The evidence sits across emails, PDFs and three people's inboxes.

What it does

From: Apex Demo TalentRe: RTR for Ravi KumarValid until 30 November 2026RTR ledgerAllExpiring in 7 daysRevokedKarthik RaoSummit Demo Energy18 OctRavi KumarNorthwind Demo Bank30 Nov

It keeps a ledger of every right-to-represent — consultant, vendor, end client, requirement, rate, expiry — with the email or PDF it came from.

Right to representApex Demo Talent$68/hr on C2CFields readConsultantRavi KumarRequirementREQ-DEMO-4012Rate$68/hrEnd clientExpires30 Nov 2026Not in the email

It reads new right-to-represent emails and PDFs into the ledger and leaves a field empty when the document doesn't state it.

Possible duplicateEarlier submissionRavi KumarPhone+1-555-0142Emailravi.k@example.comSubmitted 12 SepNew résuméRavi K. KumarPhone, same+1-555-0142Email, newrk.dev@example.testSame end clientSame personDifferent people

Before each submission, it looks for an earlier submission of the same person to the same end client, including under a different email or a re-typed résumé.

Check before submitRavi Kumar for REQ-DEMO-4012GreenAmberRedRTR on file, not expiredRate matches the RTR!Same phone as SUB-DEMO-0311Possible duplicate: a person decidesSubmitOverride with a reason

It answers green, amber or red with the reasons, and a person resolves anything that isn't green.

Try to break it

On the call we'll trigger these, live:

  • The right-to-represent names a lower rate than the submission. The submission is stopped until they match.
  • The right-to-represent expired yesterday. Submission is blocked, with a renewal request ready to send.
  • A résumé comes back with a new email address. It's flagged as a possible duplicate, with both records side by side.
Right to representApex Demo Talent$62/hr on C2CValid until 30 NovCheck before submitREQ-DEMO-4012RedRates don't matchIn the RTR email$62/hrOn the submission$68/hrSubmitStopped until they match

Where it runs

An office computer or a cloud account in your name.

Who else does something like this

SAP Fieldglass is a vendor management system that large clients use to manage staffing suppliers, including duplicate candidate checks on the client side.

The Guard runs on your side, before a submission leaves your office.

The rules it respects

Candidate data is kept to what the submission needs, with a retention period you set.

What our tests measured

How we test

These figures come from test runs on Google's Gemini (gemini-3.5-flash-lite), a hosted model, on synthetic data. We'll add runs on a local model.

Green answers where a duplicate or an invalid RTR existed0
Pre-submit checks that answered the right colour100%
Planted duplicates flagged for a person100%
Flagged pairs that turned out to be the same person86.95%
RTR fields read correctly100%
Fields an RTR doesn't state, left empty100%
RTR emails delivered twice and stored twice0
Submissions that reached a vendor twice0
Median time to read one RTR2348 ms
  • Run on 13 October 2026
  • Model: gemini:gemini-3.5-flash-lite
  • 833 examples
For your engineers
Engines
Consent Spine, Extractor, Reconciler
Sealed mode
Test passed: with sealed mode on, it refuses every outbound connection except to the model you've approved.

Data flow

A bench-sales firm's documents (synthetic)RTR emails and PDFsRésumésData kept to the needno dates of birth, no SSNsStored oncesame email or contentExtractor engineeach value with its wordsRTR ledgerappend-only, source keptIdentity rulesemail, phone, profile, nameRésumé similarityCheck before submitred, amber or greenA person decidesSame person or notSubmissionsonly on a fresh greenReconciler enginesent once, held for replayVendor portalsMail serversaudit_log