Skip to main content

Off-Platform Hire FAQ

Answers to the most common questions about Off-Platform Hire detection.

Written by Amogh Balikai

Is this feature available on my plan?

Off-Platform Hire detection is available on the AIRA Plan for accounts that have access to the Job Candidate Activity (JCA) page. If you can see JCA on your account, the tag will appear automatically when a detection is made. No setup required.

How does Recruiterflow know a candidate was hired off-platform?

AIRA monitors job changes for candidates in your database. When a candidate changes jobs and joins a company you actively recruit for, and there's no placement recorded in Recruiterflow for that hire, the system flags it as a potential off-platform hire. The detection is automatic; it does not require you or the client to report anything manually.

Does the 12-month window start from submission or rejection?

The detection window starts from the date when the candidate was added to a job pipeline for that client and role. It runs approximately 12 months from that point.

What if my contract has a different protection period, say, 6 months or 18 months?

Recruiterflow's detection window is approximately 12 months. If your contract specifies a shorter period (e.g., 6 months), the tag may appear after your contractual protection window has already closed. Meaning, you may not have a claim even though Recruiterflow flagged it. Always check your contract dates against the Recruiterflow detection timestamp. If your contract specifies a longer period (e.g., 18 months), you'll need to monitor independently for hires in that extended window.

The candidate was hired for a different role than the one I submitted them for. Does that count?

That depends on your contract, not on Recruiterflow. Some agreements protect your submissions broadly - any hire at the company, regardless of role. Others are role-specific. Recruiterflow flags the detection regardless. Your contract and legal advisor are the deciding factors here.

Can I dispute the tag? What if Recruiterflow got it wrong?

The tag is a detection signal, not a confirmed breach. If you investigate and find the candidate was not actually hired by the client (or was hired through a different agency's process), no action is needed. There's currently no way to dismiss or archive the tag inside Recruiterflow. Note your findings on the candidate's profile instead.

Will the client be notified that I've seen this tag?

No. The Off-Platform Hire tag is internal to your Recruiterflow workspace. The client has no visibility into what's flagged in your system.

How is this different from AIRA Job Change Alerts?

AIRA Job Change Alerts notify you when a candidate in your database changes jobs. Useful for sourcing and relationship-building across your whole database.

Off-Platform Hire detection is specifically about protecting your fee. It looks for cases where a candidate you submitted to a specific client was rejected, then hired by that same client within the detection window. The trigger, the context, and the purpose are all different.

Can I export a list of all off-platform hires detected?

Currently, off-platform hire detections are visible on the JCA page. There is no bulk export or workspace-wide report. Add a note on affected candidates' profiles for your own record-keeping.

Did this answer your question?