---
id: mech.location_or_timezone_compliance_constraint
type: mechanism
title: "Location or Timezone Compliance Constraint"
lang: en
registry: 1.11.0
canonical: https://hoba.work/mechanisms/mech.location_or_timezone_compliance_constraint
json: https://hoba.work/api/v1/mechanisms/mech.location_or_timezone_compliance_constraint.json
---

# Location or Timezone Compliance Constraint

The company has no legal entity or provider that can issue an employment contract in the jurisdiction where the candidate resides.

> **On the canonical path** — [Terms compared before anyone spends time](https://hoba.work/process#proc.the_path_as_it_is_supposed_to_run-terms-check)
>
> Band, level, location, notice period and start date are put side by side in the first conversation, before any assessment is scheduled. Either side can stop here at no cost to the other.
>
> This entry is one of the ways that commitment stops being kept.

## At a glance

- Actor: policy
- Nature: rule
- Visibility: observable
- Agency zone: intermediary
- Evidence: proven

## What it looks like

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

**Where the constraint actually sits** — *reconstruction*

```
  offer stage Recruiter  Everything is agreed on our side. One question — you are resident where exactly?
  offer stage Candidate  Same country as in my application, no change.
> offer stage Recruiter  Then I have bad news. We have no legal entity there and our provider does not cover it, so we cannot issue a contract regardless of the role.
```

*What to notice* A hard constraint that is knowable on day one and was checked at the offer. Nothing about the candidate is being assessed here.

## From each side

The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.

### Employer policy

- **What reaches them:** The list of jurisdictions where an entity or an employment provider can issue a contract, and a candidate record showing a country outside it.
- **What it means from there:** A contract that cannot be signed, whatever the panel concluded. Adding a jurisdiction is a registration and tax decision, not a hiring one.
- **What happens next:** Holds the coverage list as written, and leaves any exception to a separate approval running on its own quarterly cycle.

### Recruiter

- **What reaches them:** A residency answer that falls outside the approved country list — a check that can happen at the screen or at the offer paperwork.
- **What it means from there:** This process ends here regardless of the panel's recommendation, and the requisition returns to sourcing while time-to-fill keeps counting.
- **What happens next:** States the constraint at the screen, where the list is at hand, or delivers it at the offer stage in the wording available for it.

### Candidate

- **What reaches them:** A posting marked remote, a process that runs normally, and a jurisdiction question arriving late — or a rejection minutes after submitting.
- **What it means from there:** Either the location was disqualifying from the start, or something about the profile was. Nothing in the message separates the two.
- **What happens next:** Records the stage at which the question was asked, and asks about entity coverage before the next remote process rather than after it.

### Public policy and industry standards

- **What reaches them:** Employment law and tax registration in each jurisdiction, and the conditions under which a cross-border employment relationship can exist at all.
- **What it means from there:** A settled boundary, working as written. Nothing in it says at which point in a hiring process the boundary has to be disclosed.
- **What happens next:** Sets the rule and the licensed intermediary arrangements that can carry an employment relationship across it, on a legislative cycle no single process can wait for.

## What this observation does NOT establish

- The jurisdictional barrier is entirely independent of the candidate's technical competence.

## Related entries

- operates at — [bar.automated_filter_parser_threshold](https://hoba.work/barriers/bar.automated_filter_parser_threshold) — Automated Filter & Parser Threshold
- operates at — [bar.recruiter_screening_call](https://hoba.work/barriers/bar.recruiter_screening_call) — Recruiter Screening Call
- emits — [obs.rejection_naming_a_jurisdiction_or_work_eligibility_ground](https://hoba.work/observations/obs.rejection_naming_a_jurisdiction_or_work_eligibility_ground) — Rejection naming a jurisdiction or work-eligibility ground
- emits — [obs.rejection_within_minutes_of_application_submission](https://hoba.work/observations/obs.rejection_within_minutes_of_application_submission) — Rejection within minutes of application submission
- emits — [obs.generic_closer_alignment_rejection_template](https://hoba.work/observations/obs.generic_closer_alignment_rejection_template) — Generic "closer alignment" rejection template

---

hoba — a public, versioned atlas of hiring obstacles. Content CC BY-SA 4.0. This document is generated from the registry; the canonical page is linked above.