Recruiterflow detects a potential off-platform hire by tracking the relationship between a candidate entering a job pipeline, a client rejection, and a subsequent hire of that same candidate, all within a defined time window.
The three conditions
A flag only appears when all three are true simultaneously:
A candidate in your database changes jobs: someone you've worked with joins a new company.
Their new employer is one of your clients: a company you actively recruit for in Recruiterflow.
The hire didn't come through you: there is no placement recorded in Recruiterflow, and the candidate is not in your hired pipeline for that client.
When all three are true, Recruiterflow surfaces a Possible Off-Platform Hire tag on that candidate's entry in the Job Candidate Activity (JCA) page. It looks back approximately 12 months.
A concrete example
Your recruiter submits Sarah Chen to Acme Corp for a VP of Sales role on March 1st. Acme Corp rejects Sarah on April 15th - "not the right fit at this time." On October 10th, Recruiterflow detects that Sarah has joined Acme Corp. That's 7 months after submission, well within the 12-month window. The Off-Platform Hire tag appears on Sarah's JCA entry for that role.
Your team now has grounds to review your contract with Acme Corp and investigate whether a fee is owed.
Important things to know
The tag is a signal, not a verdict. It tells you to investigate. The contractual determination of whether a breach occurred, and what fee applies is between your firm and your client.
The detection window is approximately 12 months from the candidate's original job pipeline addition date.
The tag does not auto-alert anyone. It appears visually on the JCA page. Your team needs to check it or have a review process in place.
The fee amount and contract terms are yours to define. Recruiterflow flags the event; enforcement is entirely in your hands.