Parsing Location and Work Eligibility Without False Assumptions

One application can contain five different locations

Current residence, preferred working location, mailing address, past employer location, and the country where a person is authorized to work are different concepts. A remote role adds another dimension: the countries where the employer can lawfully engage the worker. A candidate may live in Berlin, be willing to move to Amsterdam, have worked in London, and possess authorization for more than one market. Reducing that story to a single location label makes search and screening less reliable.

Some applicant systems populate location from a resume, application form, social profile, or IP-derived estimate. Workable explicitly documents several of these inputs and offers a way to inspect or correct the source. Treat that as an operational lesson, not an endorsement of one platform. Every location field needs provenance: who supplied it, when it was supplied, what it describes, and whether it was inferred or confirmed.

Consider the line "London | Berlin | Remote" beneath a candidate name. London might be the location of a previous employer. Berlin might be current residence. Remote might be a preference rather than permission to work anywhere. A parser cannot safely choose one of these meanings without more context. The defensible result is an unresolved field with the original excerpt attached.

Why the same country name leads to different answers

A country mentioned in a project history is evidence about employment history, not necessarily residence. A telephone country code can reflect a long-held number. An IP address can be affected by travel or network routing. A city in a school name is not a current address. A postcode can be ambiguous or outdated. Even a field entered by the candidate can become stale after relocation.

A useful data model separates reported_current_location, location_source, source_date, preferred_work_locations, relocation_willingness, working_arrangement_preference and authorization_status. The last field should not be silently calculated from any of the first six. In the application, display the original evidence next to the normalized value, and provide a way for a reviewer to request clarification.

A practical trap: a filter called "Candidates in Germany" may contain people whose most recent CV mentions Germany, whose application form says Germany, or whose internet connection was located there. Unless the interface exposes the distinction, the recruiter can mistake a data-quality problem for a shortage of talent.

Right to work is not nationality and not geography

Work authorization is a legal and role-specific question. Living in a country does not automatically mean a person can take every job there. Living elsewhere does not automatically mean a person lacks permission to work in the target country. Nor should birthplace, nationality, name, language, education, or accent serve as a proxy for eligibility.

The official European Commission guidance explains free movement rights for EU nationals working in other member countries. The United Kingdom maintains prescribed right-to-work processes that employers must follow. The United States distinguishes employment eligibility verification from unlawful citizenship or national-origin discrimination. Canada distinguishes open work permits from employer-specific permits. These are not interchangeable systems, and recruiting teams should never compress them into a universal rule.

For ordinary hiring workflows, it is usually more useful to ask relevant, consistently worded application questions about work authorization and sponsorship than to infer answers from personal characteristics. The correct timing and wording depend on local law and the role. Do not request identity documents earlier than necessary or expose sensitive responses to everyone with access to a CV.

Remote does not mean anywhere

A fully remote vacancy may still be restricted to specific states or countries because of payroll, tax, data-access rules, regulatory exposure, working hours, or an approved employment entity. A candidate located outside the advertised region may be a genuine match for the work but not for the engagement model currently offered. That is a constraint to clarify, not a sign that the candidate is unqualified.

Write remote eligibility into the job brief in operational terms: permitted working countries or regions, whether relocation is considered, office attendance expectations, required time-zone overlap and who decides exceptions. Avoid the phrase "remote worldwide" if the employer cannot actually contract with people worldwide. These details can reduce both false exclusions and wasted interviews.

A screening review that does not invent facts

Use this sequence whenever location matters to progressing an application:

1. Define the requirement. Is it residence, time-zone overlap, ability to attend a site, permission to work, or a contractual employer restriction?
2. Inspect the source. Check whether the field came from a direct candidate answer, parsed CV line, older profile, or indirect estimate.
3. Separate explicit from inferred. Record a candidate statement as a statement. Never promote a weak inference to verified status.
4. Ask the narrowest clarification. Ask only what is needed to resolve the relevant constraint, with equal questions for comparable applicants.
5. Record what changed. Preserve a reason for correction and distinguish original source text from the later response.
6. Keep the review reversible. Unknown or conflicting fields should create a clarification task, not an automatic rejection.

The sequence is deliberately small. A large compliance questionnaire is not an improvement if it collects personal details unrelated to the role. Recruitment data should be accurate, limited to what is necessary, protected by permissions, and updated when its purpose changes.

Three failure cases worth adding to your quality checks

Case 1: The international graduate. A CV shows a university in Singapore and a current address in Manchester. A shortcut interprets Singapore as a current location. The fix is to compare field labels and dates, then use the direct application answer as the current self-reported location if appropriate. Neither the university nor the address determines work eligibility.

Case 2: The cross-border engineer. A candidate lives in one EU member country and applies for a role in another. A naive filter expects current residence in the target country. The correct next question is whether relocation or the permitted working arrangement is feasible. General EU mobility rights may be relevant, but the employer still has payroll and role-specific obligations to consider.

Case 3: The remote applicant. A person applies from a location outside the current payroll footprint. Their skills fit perfectly. A useful workflow tags the contractual constraint separately from capability fit and asks whether another engagement route is approved. It never converts the constraint into a statement about nationality or competence.

How to test your existing pipeline on 30 resumes

Choose a small, varied sample of real application formats that your organization can lawfully process. Include resumes with multiple addresses, remote projects, foreign education, relocation notes, missing addresses, and conflicting application answers. Have a reviewer label the relevant fields using the original source document and any permitted candidate answer. Record when the label is unknown.

Compare the extracted value to the reviewed label. Count field-level correct extractions, incorrect extractions, and unverified guesses separately. Also record decision impact: did an error remove a potentially suitable person from a search or queue? Ten harmless location formatting errors are not equivalent to one unjustified disqualification. Do not calculate eligibility accuracy by assuming that every field left blank means "no authorization".

An effective remediation log captures the failed example, the reason, the corrected value, whether the parser or rule was updated, and the result on a new holdout sample. Check that a correction for one address format does not silently break another.

FAQ

Can a resume parser verify permission to work?

Not from ordinary address or nationality cues. It may extract an explicit statement, but extraction is not independent verification. Appropriate official checks must follow the rules of the relevant jurisdiction and employment arrangement.

Should an application be rejected when location is unknown?

Not by default. Clarify whether location is a genuine essential constraint, then ask a targeted question. Unknown information is not evidence that a candidate fails a requirement.

What should a recruiter see before filtering by location?

At minimum, the field meaning, original source, recency, whether it was estimated and a correction option. If the field has legal significance, escalate to the appropriate authorized workflow.

Better candidate decisions start with better field meanings

The first product improvement is not another scoring algorithm. It is a trustworthy boundary between what a resume says, what a parser infers, what a candidate confirms and what an employer must formally verify. Preserve that boundary, and location becomes a useful hiring constraint rather than an invisible source of false negatives.