Screening a candidate who has lived in four countries

Criminal record checks are not universally available and are not universally permissible. Some countries make them available only to the individual, some restrict them by role, and some prohibit an employer from considering them at all outside defined categories. Education verification depends on whether the awarding institution still exists and responds. Employment verification depends on whether the former employer is required to confirm anything.

This is why a cross-border screening order is a judgement rather than a checkbox. The provider will tell you what is possible in each jurisdiction; your counsel will tell you what is permissible for the role you are filling. A CRM that offered a single order-a-global-check button would be encouraging a mistake.

A multi-country screening order is assembled from where the candidate has lived, and that history is usually reconstructed from a resume by someone reading between the lines. It gets recorded as a note, if at all, and then re-derived from scratch the next time the same candidate is submitted somewhere else.

Holding structured location history on the candidate record makes the order assemblable and makes it repeatable. It also makes the gap visible: if the last seven years contain an eighteen-month period with no country recorded, that gap is the thing that will delay the check, and it is better found at screening kickoff than three weeks later.

Candidates are usually willing to supply the missing detail. Nobody asks them, because nobody realised there was a gap. A structured field turns an implicit reconstruction into an explicit question, and asking it at the point of offer rather than at the point of screening compresses the timeline by however long the provider would otherwise have spent waiting for an answer.

Surhires does not run background checks and is not a consumer reporting agency. Ordering lawfully in each jurisdiction, obtaining consent in the form that jurisdiction requires, running whatever adverse-action or equivalent process applies where you are hiring, and handling a dispute about report content are all yours, with HireRight.

Where a candidate is in the EU or the UK, the product supports consent capture on candidate records, configurable retention windows, data export and erasure workflows, and you remain the controller for the candidate data you hold. Screening documents fall inside that. A CRM holding a copy of a report does not become the party accountable for it.

Order in HireRight's own portal against your own account, with the country components the placement needs. When results return, file them against the candidate record in Surhires: which components were run, which country each covered, the completion date, the ordering user, and the outcome you acted on.

Also file the consent you collected and the form it took, because on a cross-border placement that record is more likely to be asked for than the report itself. Document capture and expiry reminders already sit against the candidate record; the verification itself is a workflow you run, not a certification we hold.

Teams routinely conflate the two, and they are different obligations with different timing. A background check tells you about a candidate's history. A right-to-work or working-rights check tells you whether they may lawfully be employed in the country of the placement, and it usually has to be completed before a start rather than before an offer.

The product handles this side with document capture and expiry reminders against the candidate record, plus working-rights checks against visa class where an Australian placement requires it and right-to-work capture for the UK. The verification itself remains a workflow you run.

Sequencing matters as well. A right-to-work check completed before an offer can create its own problems in some jurisdictions, and one completed after a start date creates a different problem entirely. Where in your process it belongs is a decision to take with counsel for each country you place into, and then to encode as a required-at-stage rule rather than as a habit.