scheduler agent sent interview invites for the wrong office - it used the hiring manager's old location from a stale...

TL;DR: Read the interview location from the job requisition in the ATS, not from the hiring manager's calendar profile. The profile describes the person and goes stale when they move; the requisition describes the job and is what the candidate is actually interviewing for. Verify the location before every send.

scheduler agent sent interview invites for the wrong office  -  it used the hiring manager's old location from a stale calendar profile

1. Fetch the requisition from the ATS for the job and read its office or location field.

Expected: the req names the correct office where the role sits.

1. Compare it against the location the agent pulled from the manager's calendar profile.

Expected: the profile shows the manager's previous office, confirming the stale source.

1. Change the scheduler's location source: requisition first, with an explicit fallback chain (req, then interview-specific override, never the person's profile).

Expected: a dry-run invite for the same job now shows the req's office.

1. Re-send corrected invites to affected candidates with the right office and an apology for the confusion.

Expected: candidates confirm the corrected location.

1. Add a mismatch check: if the manager's calendar profile location differs from the req, flag the recruiter instead of silently picking one.

Expected: the flag fires in a test where the two disagree.

Use this when

• Invites carry the wrong office, building, or city.
• The agent sources location from a person attribute (calendar profile, HRIS record) rather than the job.
• Hiring managers recently moved offices or work across multiple sites.

Not for this skill when

• The requisition itself has the wrong office (fix the req data, not the agent).
• The role is fully remote and the location field is irrelevant.
• The wrong location came from a candidate-facing careers page, not the scheduler.

Variant phrasings

• interview invite had the wrong office address
• agent used stale location from the hiring manager's profile
• candidates sent to the wrong building for onsite interviews
• scheduler pulled office from calendar instead of the job req

Why it happens

People attributes and job attributes live in different systems with different freshness. A calendar profile is updated rarely and reflects where a person sits; the requisition is maintained by recruiting and reflects where the role sits. The agent grabbed the nearest location field it could find, which happened to describe the person, and never questioned whether it described the job.

Edge cases

• Hybrid roles legitimately spanning two offices: the req may list one while the panel sits in the other. Confirm per-interview, not per-job.
• Managers who split time across sites: the profile location is sometimes right. The mismatch flag exists for exactly this case.
• Candidates flying in: the invite may need travel details the req does not carry. Handle travel as a separate field, not by overriding location.
• Office moves mid-loop: a req updated after early interviews means early candidates got one office and later ones another. Reconcile before the onsite round.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst1t1tnkHSY-k4lA919RRoQ