HUBSPOT ROUTING TEST LAB REF-ROUTE-001 / Policy 1.0.0 / Synthetic reference PURPOSE Inspect the routing decision before implementing a CRM handoff. Every eligible record should have a proposed owner or a specific exception reason. An excluded record should stop before assignment. WHAT THIS LAB DOES The browser runs a deterministic local function on six fictional inputs. It checks eligibility, supplied identity matches, existing ownership, territory and configured owner availability in that order. It displays the proposed action and the visited rules. It sends no record values and makes no CRM requests. WHAT WAS VERIFIED LOCALLY The six baseline terminal states were executed against the local engine. Tests also exercise priority conflicts, inactive owners, ambiguous matches, missing territory, multiple owner candidates, corrected exceptions, malformed inputs and replay determinism without mutating inputs or policy. WHAT WAS NOT VERIFIED No real CRM search, association, subscription, paid seat, owner assignment, task creation, API write, workflow enrollment or production replay was executed. ASSIGNED means an owner was proposed locally. It is not proof that HubSpot owns the record, and it is not a completed sales handoff. SIX BASELINE RECORDS 01 net-new: propose Sales EU 01 and a new contact. 02 existing-customer: preserve Account team 02; reuse SYN-CONTACT-020. 03 duplicate: preserve Sales EU 01; reuse SYN-CONTACT-030, no new contact. 04 missing-owner: hold; APAC's configured owner is inactive. 05 conflicting-territory: hold; EU and NA signals disagree. 06 ineligible: exclude; company type is outside the target criteria. IMPLEMENTATION ACCEPTANCE CHECKS 1. Define authoritative IDs and matching. Verify existing contacts before proposing creation. A unique match can be reused; multiple matches need review. 2. Define which relationship is authoritative for customers. HubSpot contact and company owners are independent by default. Test your chosen property, primary company association and optional owner synchronization. 3. Review active users, applicable paid seats and subscription requirements in the real portal. The sample active flags are fictional, not license checks. 4. Verify one authoritative territory. Keep a review queue for conflicting or missing data rather than assigning an arbitrary owner. 5. Inspect the destination contact, ID, owner property and associations after the CRM action. A local proposal is not a successful write receipt. 6. Replay the same submission. Verify no extra contact or downstream task is created. Define event keys, retry behavior and action guards as appropriate to your chosen integration. This lab does not implement a persistent ledger. 7. Test enrollment and re-enrollment separately. HubSpot can rerun workflow actions when a record re-enrolls. Local function determinism is not sufficient. 8. Store visible exception reasons and assign responsibility for resolving them. Rerun only after correcting the source data or approved routing policy. SCOPE LIMITS The policy is illustrative and uses explicit named territory owners. It does not model round robin, workload balancing, concurrent assignments, real account qualification, permissions, retention, consent or communication eligibility. The eligibility input is an agreed targeting flag, not permission to send email. No messages are composed or sent, and no marketing enrollment is proposed. SOURCE FILES hubspot-routing-rules.txt: JSON policy and synthetic owner registry. hubspot-routing-fixtures.txt: JSON inputs and independently specified outcomes. hubspot-routing-test-matrix.csv: baseline acceptance expectations and boundaries. OFFICIAL REFERENCES, REVIEWED 2026-09-28 https://knowledge.hubspot.com/records/deduplication-of-records https://knowledge.hubspot.com/object-settings/sync-ownership-between-contacts-and-companies https://knowledge.hubspot.com/workflows/assign-and-rotate-record-owners-using-workflows https://knowledge.hubspot.com/workflows/add-re-enrollment-triggers-to-a-workflow EVIDENCE LABEL Synthetic reference. Tested locally, no live CRM execution and no client performance or revenue result claimed.