Decide What a Partner Needs to Know About a Prospect
Share a minimal referral packet with verified purpose, recipient, contents and permission boundaries instead of forwarding full CRM notes.
10/24/20263 min read
A partner usually needs enough context to assess a referral, not every note your team has ever stored about the prospect. Full CRM histories can contain irrelevant personal commentary, confidential commercial details and restrictions that are easy to misread outside their original context.
Prepare a minimal referral packet with a sharing gate. The packet should answer the partner's specific decision while making clear what the prospect has agreed may be shared. A useful handoff is selective by design, not merely a large export with a confidentiality label.
Name the receiving decision
Ask what the partner needs to decide now: whether the task fits, whether a conversation is appropriate or whether a defined implementation step is feasible. Do not share detailed project data for an initial fit check if an anonymous description would suffice.
Separate company context from information identifying individuals. Both can be confidential, and personal business information can still carry privacy obligations. The relevant law, contractual terms and recipient permissions require their own review; this article is not legal advice.
Build the smallest useful packet
Include the requested task, relevant operating context, confirmed constraints, the agreed contact route and material unknowns. Add the source of the sharing authorization and its scope in a controlled internal reference. The receiving partner needs the handling instructions, not necessarily the full evidence of every permission discussion.
Exclude unrelated deal notes, subjective personality labels, private explanations for delays, confidential pricing from other providers and personal details that do not affect fit. Do not send credentials, access codes or production datasets as part of a routine referral.
Prepare an illustrative handoff
Fictional Fern Advisory wants to introduce a customer to fictional Ash Training for a supervisor workshop. The customer agrees to share a short description of the training task and a business contact route. It has not authorized sharing internal performance reviews.
The packet states that the team needs practice using an already defined shift-handover checklist; delivery format and dates remain open; one nominated coordinator may be contacted through the agreed introduction. It notes that the partner should assess fit before proposing a workshop.
The packet omits employee performance comments and a private account note about a budget discussion. Those details are not necessary for the immediate decision. The example is fictional and does not establish that a particular disclosure is lawful in every setting.
Use a sharing approval gate
Before sending, verify the recipient, purpose, exact contents and permitted onward use. Check that the partner still needs the information and that the prospect's latest instructions have not changed. A standing collaboration does not authorize arbitrary disclosure.
NIST's voluntary privacy framework offers a way to think about data actions, purposes and participants. Use that inventory approach to describe the handoff, while recognizing that it supplies neither consent nor contractual rights. Where uncertainty remains, hold the data and ask the appropriate owner to resolve it.
Give the recipient a correction route
The packet should identify what is confirmed and what is a hypothesis. If the partner finds a mismatch, it should return the narrow correction rather than creating a new profile or contacting additional people. Decide how the original team updates its record without spreading the incorrect information further.
Use a secure, approved channel proportionate to the information. Restrict access to the necessary recipient and avoid public links for private context. Ask about retention or removal when the referral is declined or no longer needed, following the applicable agreement and policy.
The handoff is complete when the partner can make the intended next decision and understands the limits on contact and reuse. If additional information is genuinely required later, review that request separately. A small packet that preserves meaning and boundaries is more useful than an exhaustive record that leaves the recipient to guess what they are allowed to use.
Sources and scope
The worksheet and fictional example are original editorial proposals. References support only the stated research, data or product context, not endorsement or proof of results. Verify any product capability against the actual subscription.
NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0