← سند dashboard All docsPublished copy (redacted) of sanad/onboarding/MATCHING-RULES.md · source updated 3 Nov 2026 07:26 Riyadh · synced 4 Nov 2026 05:16
Matching and queue rules (onboarding / matching / apply queue)
Standing rule: cities (Bandar via سند Lead, 2 Nov 2026 ~6:59 PM Riyadh)
- Matching and queue building for EVERY client use ONLY the cities the client picked in their profile (profiles.json
onboarding.cities in sanad-db, mirrored in the client's profile.md "Target cities").
- Not picked = not matched, not queued. Do not add "nearby" cities and do not widen to all Saudi unless
all_saudi is true in the profile.
- Relocation answers (
relocate, relocate_cities) do not widen the list by themselves: use cities and, only if the client set it, all_saudi. If cities and relocate_cities differ, flag it to Lead.
- Rows whose city is unclear, remote, hybrid or multi-city: do not drop silently. Keep, add a CITY FLAG to the row note, and tell Lead.
- Already-submitted applications are never touched by a city clean-up: only note them.
- Before building or refreshing a queue, re-read the picked cities from the live profile (SELECT only) and compare with profile.md; report any mismatch.
- Queue files (queue-30d.csv) have no city column today: record the city (from the listing, employer page or pack folder name) in the row note or add a
city column when a queue is rebuilt.
See also: CLIENT-DATA-RUNBOOK.md (where everything a client sends gets saved).
Job-form defaults (Bandar via سند · Lead, 3 Nov 2026 7:26 AM Riyadh), all clients
- Relatives at the employer: No.
- Business travel: Yes.
- Salary figures: monthly.
- Saudi clients: no other nationality and no permanent residency elsewhere.
- Shifts: every type is fine (nights, weekends, holidays, 12-hour shifts, overtime).
- A client's own stated answer, if it differs, overrides these defaults.