Executive search

Relationship intelligence: check the evidence behind the suggested connection

Evaluate a suggested relationship path by distinguishing recorded interactions, inferred overlap, source dates and a person's willingness to help. Includes a practical evidence review.

By LaisyPublished

A relationship-intelligence tool suggests that a colleague can reach a particular executive. The suggestion may come from recorded communication, shared work history or a manually added connection. Those sources support different conclusions.

Before acting, the team needs to understand what the path actually establishes. Evidence that two people exchanged messages is not evidence that they would welcome this request. Evidence that they worked at the same organization is not proof that they knew each other.

A useful review preserves those distinctions. It helps a consultant decide which question to ask the appropriate relationship owner without turning a score or graph edge into permission, personal familiarity or a prediction of response.

Copyable connection-evidence review

FieldWhat to establish
Proposed pathPerson seeking a connection, possible bridge and intended recipient
Path sourceRecorded interaction, manually entered relationship or inferred history
Evidence dateWhen the underlying event occurred and when the source was checked
Supplier meaningWhat the displayed score, label or connection type actually describes
Coverage limitMissing systems, historical gaps or other unobserved context
Current relationship questionWhat the proposed bridge needs to confirm
PurposeSpecific conversation or introduction being considered
Applicable boundaryRelevant restrictions and permitted disclosure
ResponseWhat the relationship owner actually says, with date
Next actionReviewed request, clarification, no approach or another defined step

The review should be small enough to use before an introduction request. It need not reconstruct someone's entire professional network. Focus on the evidence and question relevant to this proposed path.

Distinguish direct evidence from inferred history

A logged interaction, shared employer and manually added connection are not interchangeable. Each may be useful, but each needs its own interpretation.

Affinity's documentation on inferred connections explicitly describes them as leads based on shared history rather than confirmed relationships. That is a helpful source distinction: overlap can justify a question without establishing that two people know each other.

If a path rests on shared work history, check the actual overlap and its meaning. Two people at a large organization may have worked in different units or periods. Even genuine overlap does not establish the current relationship or the appropriateness of an introduction.

Keep an inferred path labeled as inferred until relevant evidence changes its status. A consultant's decision to investigate it should not silently turn it into a confirmed relationship in the next report.

Read the scale before interpreting the number

A score is meaningful only in relation to its definition. Affinity's relationship-strength documentation describes direct relationship scores ranging from 10 to 100, based on interaction recency and frequency.

That documented range is a product scale. A displayed score is not a percentage probability that someone will make an introduction, reply to a message or support an assignment. It is also not a validated assessment of trust, friendship or professional suitability.

The same supplier currently describes inferred connections differently, using labeled strength and underlying evidence rather than a displayed numerical confidence score. Do not apply the direct-interaction scale to every inferred path just because both appear inside one product.

Other suppliers may define their signals differently. Ask for the relevant current documentation and inspect the source context in the actual product. Comparing two numbers with different definitions can create an appearance of precision without a meaningful comparison.

Check what the data can and cannot observe

Recorded communications cover only the systems, periods and events available to the tool. A missing interaction can reflect an unconnected channel or incomplete history rather than a missing real-world relationship.

Likewise, a visible message may be administrative rather than a substantive professional exchange. The reviewer should not need to read unrelated private content to make this distinction. Ask the appropriate relationship owner for the context needed to assess the request through the normal authorized route.

Google Contacts' change-history guidance notes limits for some older contacts. It also illustrates why a record's edit history needs to be distinguished from actual interactions. Editing a phone number does not establish that a conversation occurred.

Write the coverage limit in the review. “No later interaction found in the reviewed source” is a supportable statement about the evidence. “They have not spoken since” is a broader claim that may not be established.

Keep record origin separate from relationship evidence

A contact can enter a system through import, integration or manual creation. The origin may explain where to look next, but it does not prove that a member of the firm knows the person.

HubSpot's Record Source property documentation describes record-creation origin. That information should not be reinterpreted as the source of every field or evidence of a personal relationship.

If a manually created contact has an asserted relationship, preserve who entered it and the basis where appropriate. Ask whether that account is current and relevant to the request. Do not infer a stronger connection from the fact that someone took the trouble to create a record.

The candidate research-note guide provides a useful structure for attributed evidence and open questions. The same discipline applies to relationship context without turning the person into a subject of speculative assessment.

Ask the bridge a contextual question

A useful question explains the proposed purpose and asks whether the path is appropriate. It leaves room for the colleague to say that the relationship is old, indirect or unsuitable for this request.

For example: “The record suggests you may have worked with this person. Is that accurate, and would it be appropriate to ask whether they would welcome a conversation about this permitted topic?” Adjust the wording to the actual evidence and disclosure boundary.

Do not ask the bridge to validate an unsupported score. They can explain their relationship and willingness; they do not need to agree that the system's label captures it perfectly.

The mandate kickoff checklist helps recover the assignment boundary. A potentially useful connection does not expand that boundary or override restrictions around contact, client identity or disclosure.

Worked example: two suggested paths

These people, records, labels and responses are fictional. They demonstrate an evidence check, not an Affinity account test or a forecast of anyone's behavior.

Suggested pathWhat the permitted record suppliesReviewer's bounded statement
Through colleague AA dated professional exchange; an illustrative direct-interaction score of 70 on the documented 10–100 scaleInteraction evidence exists. “70” is not a 70% chance of an introduction; ask A about this purpose now
Through colleague BOverlapping employment years; an illustrative inferred label of StrongA lead based on shared history. Keep the overlap and label visible; do not call it a confirmed personal relationship

The record for A reads: “A confirms the professional context and is willing to consider the specific request; recipient willingness unconfirmed.” B replies that they worked in another unit and cannot confirm knowing the target. The second record remains an unconfirmed route, with no adverse judgment about either person.

The reviewer also finds an imported contact record. Its creation origin is not a third relationship path and supplies no extra confirmation that a colleague knows the target. The output is a short evidence note, not an instruction to contact anyone.

Once a path is adequately checked and the proposed contact is otherwise appropriate, use the warm-introduction brief to prepare the separate request. Checking the evidence does not establish that an introduction was asked for, agreed or completed.

Preserve permission and willingness as separate questions

A connection can be real while a proposed approach remains inappropriate. There may be assignment restrictions, professional concerns or simple personal reluctance. The evidence review should not pressure someone to act because a system marks their relationship as strong.

Record the operational answer without inventing a motive. “Not willing to make this request” does not imply weak loyalty, a poor relationship or an adverse fact about the intended recipient.

If responsibility changes, use the handover guide to preserve the live status. The receiving colleague should know whether the bridge has merely been identified, has agreed to ask, or has actually made an introduction. Otherwise a second consultant may repeat or broaden the request unintentionally.

A person's agreement to one introduction also does not create permission for every later request. Preserve the purpose and scope that were actually discussed.

Review the output before acting on it

Whether a person or an assistant prepares the path summary, check its wording against the evidence. Watch for an inferred connection being rewritten as a friendship, a score becoming a probability or historical overlap becoming a current employment claim.

A useful output can remain modest: “Possible route through a named colleague; source shows shared employment; actual relationship unconfirmed.” That is more actionable than a confident but unsupported statement because it tells the next person what to establish.

The pilot success criteria can define one bounded review task alongside existing tools. Use selected permitted inputs and evaluate whether a responsible reviewer can trace each relationship claim and its uncertainty. Do not promise access to a network, automatic introductions or a particular response.