Confirm what the person wants referred, who may receive it and which contact route or details are appropriate to share. Send only the context needed to assess the request, and distinguish a referral from an endorsement or an agreed engagement. Use the information-handling requirements relevant to the organisations and people involved.
Define the referral purpose and the recipient’s task
Clarify what the referral should help the recipient decide. A request for a short conversation, a service enquiry and a job application need different information. Describe the relevant problem or contribution without attaching an entire private history. The recipient should understand why the referral may be useful and what action, if any, is being requested.
Check the limits of your own knowledge. You may be able to confirm that someone asked for an introduction without being able to verify every professional claim they make. State the basis of the referral accurately. Avoid language implying that you have assessed suitability, authority or availability when you have only identified a potentially relevant connection.
Confirm the information and route before sharing
Ask the person which details they want passed on and whether they are comfortable with the proposed recipient and purpose. An approved public profile or professional contact page may be enough. Do not assume that information shared with you privately is intended for onward distribution. If another organisation’s material is involved, follow the applicable permission and information-handling process.
Use a shareable brief when it can replace a forwarded message chain. Remove unrelated conversation, private addresses, customer details and attachments unnecessary for the recipient’s decision. The aim is a useful minimum, not an empty referral that forces the person to repeat everything. Include sufficient relevant context while avoiding information kept merely because it was easy to copy.
Keep the handoff and expectation clear
Explain who will take the next step and what the referral does not yet establish. The recipient may need to assess fit, capacity or engagement terms before continuing. A warm introduction does not automatically create an appointment, commercial agreement or obligation to recommend the person further. Let the participants make those decisions through their own appropriate process.
If the request changes, check whether the original sharing arrangement still fits. Someone who agreed to an introduction for an informational conversation may not expect their details to be distributed across a sales team. Keep distribution limited to the agreed purpose and use authorised routes for any necessary change rather than treating the first referral as open-ended permission.
Maintain only the coordination record you need
Record the practical status of the referral where appropriate: requested, permission checked, introduction sent or no further action. Keep sensitive explanations separate from a general relationship log. Follow the retention and access rules relevant to your work and review whether the record still serves a clear purpose. A referral process should not become an uncontrolled collection of private profiles.
If information was shared incorrectly, use the relevant organisational process to correct the situation and inform the appropriate owners. Improve the workflow so the same unnecessary material is not copied again. These are practical information-handling steps; requirements for particular personal data and jurisdictions should be assessed through the appropriate qualified or institutional route.
A fictional referral uses a public brief instead of a private email chain
A fictional scenario to explain the method, not a customer result or a market benchmark.
A fictional business adviser receives a request from a founder seeking help with service onboarding. The founder’s original email includes a customer dispute and personal contact information that are unnecessary for an introductory discussion. The adviser asks for a short shareable version describing the business problem and the kind of expertise sought.
The founder approves that brief and a professional contact page for one named recipient. The adviser introduces the purpose and leaves the participants to decide whether a conversation is useful. The private email chain is not forwarded. This invented example demonstrates purpose-limited sharing; it does not provide a legal assessment of a particular referral or claim that permission alone resolves every applicable information requirement.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Define the recipient’s decision and the reason for the referral.
- Confirm the person’s intended recipient, purpose and contact route.
- Use a shareable brief instead of unnecessary private correspondence.
- Distinguish introduction from endorsement or engagement.
- Keep a proportionate coordination record and appropriate access.
Common questions.
Can I forward an entire email chain if it saves time?
Check whether all of its information is relevant and appropriately shareable. A short approved brief often preserves the useful context while removing unrelated private comments and attachments. Convenience alone does not establish that every detail should be passed on.
Is a public profile always enough for a referral?
Sometimes it provides a suitable starting point, but the recipient still needs a clear purpose and requested next step. The person may prefer a particular contact route or limit the proposed introduction, so confirm expectations rather than assuming the public page settles them.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse AccelerateLink.
Found an error or a missing qualification? Send an editorial correction.
Find my next move.
Use a practical tool to turn this idea into a clearer starting point.
Find my next move