Executive search
Executive search relationship history: record context without inventing closeness
A practical relationship-history record for search firms: origin, dated interactions, ownership, uncertainty and the next permitted step, with a fictional worked example.
A partner opens a contact record before discussing a new assignment. It contains an old introduction, several messages and a colleague's note saying “strong relationship.” What can the partner safely conclude?
They can establish that particular interactions occurred, if the underlying records support them. They still need to check who participated, what was discussed and whether any restriction affects the next step. A busy history does not tell the whole story of a professional relationship.
An executive search relationship-history template should make that distinction useful. Its purpose is to help a consultant prepare an appropriate conversation, find the right colleague and avoid asking someone to reconstruct the same context. It should preserve uncertainty rather than turn scattered activity into an invented claim of closeness.
TL;DR
- Record how the connection began and what the dated evidence establishes.
- Separate an interaction, a colleague's account and your interpretation of the relationship.
- Identify the appropriate relationship contact without treating that person as the owner of another person's choices.
- Before the next action, review confidentiality, relevance and any restriction carried by the source.
Copyable relationship-history record
Use this as a working structure in a system you already maintain. Include only information appropriate to the purpose and intended audience.
| Field | Useful entry |
|---|---|
| Person and context | The correct identity and why this history matters to the assignment |
| Connection origin | How the people became connected, with a source or an explicit unknown |
| Dated interactions | Event date, participants, subject and a pointer to the permitted record |
| Relationship contact | The colleague best placed to clarify context, including the basis for that suggestion |
| Attributed account | Who described the relationship and when they made that assessment |
| Limits and restrictions | What the evidence does not establish; any relevant sharing or contact boundary |
| Next question | The specific clarification needed before action |
| Review owner | Who will check the record and maintain the working account |
This is a narrative aid, not a person score. A short history with a clear source can be more useful than a long timeline whose meaning no one has checked.
Start with the question you need to answer
Decide why you are opening the history. Preparing for a previously arranged conversation requires different context from asking a colleague about a possible introduction. An old search assignment may be relevant to one question and inappropriate to reuse for another.
Write the immediate purpose at the top of the record. For example: “Establish whether our colleague can explain the origin of this connection before we consider asking for an introduction.” That question does not presume the colleague will agree, the other person will welcome contact or the introduction is suitable.
Check the assignment context against the mandate kickoff record. A relationship should not become a reason to expand the brief informally. If the next step would change the assignment, resolve that change through the agreed client process. Verify the person's identity before attaching the history to that question; a similar name or employer is insufficient.
Avoid importing an entire mailbox or historical project simply because it is available. Select records needed for this question and keep their original context accessible to the reviewer.
Separate the event from its interpretation
A useful history distinguishes three kinds of statement. First, a source-backed event: named people attended a meeting on a recorded date. Second, an attributed account: a colleague says the meeting began a continuing working relationship. Third, an interpretation: the consultant thinks that colleague is a sensible person to ask about an introduction.
Keep the source attached to the first statement, the speaker attached to the second and the uncertainty attached to the third. Combining them into “warm route to candidate” loses the differences that matter before anyone acts.
Relationship intelligence is a product category with differing implementations. 4Degrees describes relationship intelligence around professional connections and interaction context. That vendor description helps explain the category; it does not establish the accuracy of a particular record or a person's willingness to participate.
Use the research-note structure for evidence that belongs in the assessment of a search question. Keep relationship context distinct from judgments about suitability, motivation or availability.
Read activity signals without turning them into permission
Some systems use activity to help users navigate a network. Affinity's relationship-intelligence page describes relationship signals based on factors including interaction recency and frequency. Those are Affinity's product claims, not Laisy capabilities or independent proof of relationship quality.
A frequent exchange can have many meanings. It could concern an operational problem, a transaction or a short period of intense collaboration. An infrequent exchange might follow a long professional association. The record should explain what is actually known instead of making the number of interactions carry all that meaning.
If your existing system supplies a score, retain its provenance and treat it as a prompt to investigate. Ask the relevant colleague whether the context is accurate and appropriate to use. Do not rewrite the score as a confirmed personal endorsement.
In particular, relationship activity is not permission to disclose a person's interest in a role, circulate a private conversation or approach a referee. Those actions need their own review against the actual circumstances and applicable requirements.
Distinguish record maintenance from contact
A recently edited contact can look current even when the relationship has not been reviewed. Someone may have corrected an address, merged a duplicate or changed a job title. Those operations say little about when a meaningful conversation last occurred.
Google Contacts' editing guidance notes that some older contacts may lack addition or edit history. Even where history exists, a record edit and a professional interaction are different events. An absent timestamp is an evidence gap, not proof that nobody spoke.
Where the source allows it, record both the event date and the date the account was entered. Label a recollection as a recollection. If the speaker cannot place the event precisely, use an honest range or “date unconfirmed” rather than an invented day.
When duplicate records disagree, preserve the conflict while someone resolves identity and context. Do not merge histories solely because names match. The question is whether the records concern the same person and whether combining them is appropriate.
Fictional example: the introduction that needs a question first
This example is synthetic. Its dates, counts and people are invented to demonstrate the record, not to describe customer results or a relationship-strength benchmark.
A fictional search firm is considering whether to ask a partner about an introduction. The selected record shows two meetings and one follow-up message in the previous year. A researcher initially writes “established relationship” because all three interactions involve the partner.
On review, the meetings concerned the same project and the follow-up was administrative. The partner may know the person well, but these records do not establish that. The researcher replaces the label with a source-backed account and a question.
| Record element | Reviewed entry |
|---|---|
| Origin | Introduction during a fictional industry project; original introducing party unconfirmed |
| Evidence | Two project meetings and one administrative follow-up, with permitted source pointers |
| Interpretation | Partner appears to be the relevant colleague to ask about context |
| Uncertainty | Present relationship and suitability of an introduction have not been confirmed |
| Next step | Ask the partner to review the account before considering any external request |
The revision does not downgrade the person or the relationship. It narrows the claim to what is known. The next action is an internal clarification, not an automated introduction or an assumption that the other party wants to hear about a role.
Carry confidentiality with the history
Some of the most useful relationship context is also the least appropriate to copy broadly. A consultant may know why a previous conversation was confidential, while a colleague sees only that the conversation happened.
For AESC member firms, the Candidate Bill of Rights addresses confidentiality around candidate interest and the search process. This is a member standard, not a statement that every firm has the same engagement terms or that Laisy certifies compliance.
Record a practical boundary where it is relevant: who may review the original account, what should remain internal and what needs clarification before reuse. Link to the appropriate source rather than reproducing sensitive detail in a broadly visible summary.
If the boundary is unclear, assign the question to the person responsible for resolving it. A history is useful when it helps someone make that check. It is not useful when it silently removes the restriction that made the original conversation possible.
Maintain the account when colleagues change
Relationship context often lives with an individual consultant. A transition becomes fragile when the record contains only their name and an unexplained adjective.
Include the source-backed context in an appropriate consultant handover. Ask the departing or changing contact to identify what remains uncertain and which next step has already been discussed. A new colleague should know whether an introduction was merely considered, requested, accepted or completed.
Do not backfill a smooth story when the person who knew the context is unavailable. Preserve the evidence you have and record the gap. Where necessary, change the proposed action so it does not depend on an unverified assumption.
Review the history when something material changes: a corrected identity, a new confidentiality instruction or a colleague's clarification. Keep that correction traceable so an old exported summary does not continue to circulate as the current account.
The Government Data Quality Framework guidance recommends communicating known data limitations. Applied here, a relationship account should expose missing dates, uncertain identity and unverified recollections to its reviewer.
Where the account lives in a shared document, Google Docs’ version-history guidance explains how to inspect earlier changes. That can help locate a correction, but an edit timestamp still does not establish when a professional interaction occurred.
Test whether the record helps a real preparation task
Choose a suitable task in which a consultant currently has to reconstruct relationship context. Agree the selected permitted inputs, the reviewer and what a useful record must establish. Include the time spent checking and correcting the draft when evaluating the result.
A one-assignment pilot can define that test alongside existing tools. In a Laisy discussion, agree the reviewed output and a clear point to continue or stop. This guide does not promise automatic relationship discovery, inbox access or a particular saving.
The useful outcome is a consultant who can explain the next step and its basis. A larger contact graph or a more confident label does not demonstrate that the preparation improved.
Frequently asked questions
Should every relationship have a strength score?
Only use a score where its purpose, source and limitations are understood. A narrative record can be enough for the immediate task. Keep activity signals distinct from permission, endorsement and candidate suitability.
What if the relationship exists only in a consultant's memory?
Record their account with attribution and a review date. Ask which parts they can substantiate and which remain recollections. Do not invent supporting interactions or imply independent verification.
Does an old conversation justify contacting someone about a new role?
Review the present purpose, context and any relevant boundary before acting. The existence of the old conversation does not settle whether a particular approach or disclosure is appropriate now.
Can AI fill gaps in the relationship history?
A draft can organize selected records, but missing evidence should remain visible. Have a person verify identity, dates and interpretations. Do not let plausible wording become an invented meeting, endorsement or promise of access.