Start with one known target. Separate direct paths from routes through another person, then check each leg’s state, source, date and missing context before a human proposes whom to ask.
Replace the group-chat ask and loose mutual count with a route record that one person owns. The page does not choose an introducer or send a request.
Route semantics first
A direct path has one visible viewer-to-target leg. An indirect path has a named intermediary and two legs. The counts below describe this sample’s records and people, not usable introductions.
Jordan Lee
Operating Partner · Meridian Capital
Person profile · Local sample
3
visible path records
1
direct path · via is null
2
indirect paths
2
distinct intermediary people
Route 01
Direct – one leg
No intermediary and no implied introduction request.
Leg 1 · You Jordan Lee
Route 02
Indirect – two legs
One possible path through one intermediary person.
Leg 1 · You Maya Chen
Leg 2 · Maya Chen Jordan Lee
Route 03
Indirect – two legs
The second leg stays Unknown until more context appears.
Leg 1 · You Owen Reed
Leg 2 · Owen Reed Jordan Lee
Unknownvia: null) and a non-contact strength state. Each indirect sample has a named via person and two supported leg fields. The intermediary count is the number of distinct via people in this sample; a direct target is not counted again as indirect. Neither count says that a route is usable.Read the evidence within its limits
Keep relationship state, contact metadata and access source separate. Each answers a different review question.
Assessed, estimated and Unknown are evidence states, not people judgements.
Assessed uses a person’s current relationship assessment. Estimated uses the available product estimate. Unknown means the visible record cannot support a strength label. None means fit, authority, willingness, interest, endorsement, consent or likely response.
Data and access boundary
Source rights and account access decide what appears and who can view it. Default Google and Microsoft access covers basic email metadata and read-only calendar events, not email bodies. Available records depend on source rights and account setup.
Visibility does not mean fit, authority, willingness, interest or consent. The buyer sets the approved purpose, consent to use the record, consent to an introduction, viewers, retention, offboarding and deletion terms.
Sample review access
From route review to owned work
Carry Jordan and all three route options into one review record. ‘Proposed route – check with Maya’ is a human check, not an action, approval or claim that Maya will help.
Introduction review
Phone record
Introduction review
Table record · Local sample
| Target | Visible routes | Proposed route | Decision | Owner | Next step | Comments | Buyer contact system |
|---|---|---|---|---|---|---|---|
| Jordan Lee · Operating Partner · Meridian Capital | Direct · Via Maya Chen · Via Owen Reed | Proposed route – check with Maya | Needs human check | Nina Patel | Ask Maya to review the request and missing context | 2 review comments | Record and hand-off method to agree |
Graph One holds
Jordan Lee, the Direct, Via Maya Chen and Via Owen Reed route records, evidence notes, missing context, proposed or hold state, owner, comments and next review.
The buyer’s agreed contact system owns
The request, colleague response, target contact, consent and outcome in the CRM, ATS, deal, talent, advisory or programme process chosen by the buyer.
This hand-off states the fields that must survive. It does not claim a live integration, export, write-back, notification or automated workflow; the method forms part of the agreed scope.
Where route review fits
Relationship review is a shared step after the relevant job has chosen the target. Each job needs a different prior human decision.
Choose the account and relevant buying role first.
Check account fit, buying authority, interest and permission before asking.
Review the capability gap and eligible partner set first.
Check compatibility, partner interest, authority and agreement separately.
Review the firm, stage, mandate and target person before the route.
Check investment fit, appetite, allocation and interest beyond proximity.
Give the person the same evidence review as the rest of the slate first.
Network strength must not rank merit, fit, availability or consent.
Review the mandate and evidence gaps first.
Check independence, standing, conflicts and willingness before approach.
Approve the member or programme request and standing check first.
Check membership, representation, safeguarding and consent separately.
Exact first meeting test
Bring the team members who may hold relevant records, the current source setup and the CRM, ATS, deal, talent, advisory or programme system that owns the next contact.