This checklist is for the partner operations lead at a firm that signed the SourceX Channel Partner Agreement as an entity and is moving live referrals between two managers who both stay: a book rebalanced, a sector desk created, a promotion. If the outgoing manager is leaving the firm or moving to a client, use the continuity protocol for staff changes. If the person signed the agreement personally, it is an offboarding, not a reassignment. A temporary absence has its own leave handoff.
Five parts of the record a reassignment cannot touch
- The partner of record. The agreement's signing record identifies the party, its authorized signatory, the document version and the date. A firm that signed remains the partner however its staff are arranged.
- The introduction evidence. The sample agreement says every introduction record identifies the company, domain, partner, opportunity, method and timestamps, and that a dispute must not erase original evidence. The record is never re-created under the new manager's name.
- The attribution window. Credit requires a verified application within 90 days of the recorded introduction, and the terms say the window does not extend. A transfer neither pauses it nor starts it again.
- The scope of the CEO's permission. What the CEO agreed to, on which date and in which message, travels unchanged. The new manager inherits that scope and nothing wider.
- The reward basis. the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, paid to the partner of record under the payment and tax details on its account. One cap covers a parent and its subsidiaries.
One line sits outside your firm entirely: SourceX may communicate directly with a referred company, and a partner need not join every call or email. After an application, the company's working contact is SourceX, not your manager.
What the transfer entry moves, and what stays behind
A transfer entry has five parts: the reference, the outgoing and receiving manager, the date the receiver takes over, the end of the overlap and the operations lead's initials. Everything else moves as pointers to records your firm already holds.
| Moves to the receiving manager | Stays where it is |
|---|---|
| Open next steps, due dates and their owners | The outgoing manager's personal notes and impressions |
| Pointers to the CEO's written permissions | Copies of email threads pasted into the CRM; keep the pointer |
| The introduction reference and its date | Anything learned in paid client work, which belongs to the engagement file |
| Do-not-raise flags and quiet periods the CEO asked for | The outgoing manager's inbox and calendar, until forwarding is set |
| Status labels read from the dashboard, with dates | Reward amounts, which the referral record never holds as forecasts |
The receiving manager is an employee who needs the information for the referral, which is the kind of recipient the agreement's confidentiality clause allows, and the firm answers for its staff's compliance. So share the referral, not the client relationship around it.
Check what the CRM actually did. Salesforce's help article on changing a record's owner says, in our paraphrase, that the previous owner's open activities move with the account while closed activities stay behind, and that open opportunities owned by other users move only if the person making the change selects that option. In practice, steps assigned to a third colleague stay with that colleague, reminders in a personal calendar do not move at all, and the history of completed steps keeps the outgoing manager's name. That history is evidence; leave it alone.
SalesforceThe manager transfer checklist, by stage
Find the stage the referral has reached, then work its row.
| Stage at transfer | What moves | The receiving manager never | Who hears, and when |
|---|---|---|---|
| A. Not yet raised with the CEO | The row, its relationship owner and any fit answers in the CEO's own words | Makes the first ask without the relationship owner's agreement | Nobody outside the firm |
| B. CEO asked, no reply yet | The single ask, its date and the channel used | Sends a second ask, or a "just following up" note | Nobody; the outgoing manager forwards any reply the same day |
| C. CEO said yes, not yet submitted | The dated written yes, the facts allowed to travel and the answer about earlier contact with SourceX | Asks the CEO to confirm the yes again | The CEO, in one line, only if the outgoing manager had promised to send the introduction personally |
| D. Submitted, no verified application yet | The submission reference, the introduction date and the day-90 date | Submits the company a second time | The CEO only if the CEO asked your firm for a reminder |
| E. Application in SourceX's process | The dashboard stage, read and dated | Carries questions between SourceX and the company | Usually nobody; SourceX deals with the company directly |
| F. Reward status shown | The status label, Estimated, Eligible, Approved, Processing or Paid, with the date read | Edits the account's payment or tax details | Your finance contact, if the outgoing manager was SourceX's day-to-day contact |
| G. Closed: declined, lapsed, not credited or no deal | The ending code and any do-not-raise flag | Reopens the row because the new desk likes the company | Nobody |
Stage C carries the most risk, so close it before the switch when you can: if the CEO's yes is in writing, the earlier-contact question is answered and your agreement is signed, the outgoing manager submits before handing over. A yes left waiting for a new owner is a yes the CEO may be asked for twice.
The read-back before the switch
Before the operations lead dates the transfer, the receiving manager states six things back to the outgoing manager, from memory first and then against the record:
- The entity, and the CEO who decides for it.
- What the CEO agreed to, on which date and in which message.
- The introduction date and the day-90 date, if the company was introduced.
- Which facts may travel to SourceX, and which may not.
- The one open next step, its owner and its date.
- Anything the firm must not do: a do-not-raise flag, a quiet period, a person the CEO asked you not to copy.
Any wrong answer is corrected in the record, not just in conversation, and the read-back is repeated. During the overlap, both names sit on the record, but only the receiving manager writes to the company. The outgoing manager stays reachable for questions and silent toward the CEO.
Who owns each step during the move
- The operations lead dates the transfer, runs the post-move check and holds escalation. For a bulk move, the same check runs on every record, however the reassignment was made.
- The outgoing manager completes the read-back, sets inbox forwarding and forwards any company message within one working day until the overlap ends.
- The receiving manager owns every open step from the transfer date and reads the dashboard on the cadence the record sets.
Escalate to the operations lead when a CEO objects to the new contact (the outgoing manager may remain the voice while the administration moves), when the receiving manager has a paid engagement with the company (referral notes stay out of that work) or when SourceX's notices for your firm still go to the outgoing manager's address. The agreement sends notices to the addresses in its signature block "as updated by written notice", so a change there takes a written notice, not a profile edit.
A rebalanced book of five referrals (Illustrative)
Illustrative: invented companies, days and outcomes. Manager A moves to a new sector desk; Manager B takes five referrals on day 41, with an overlap to day 46.
| Ref | Stage on day 41 | What the checklist did |
|---|---|---|
| R-31 | B: CEO asked on day 30, no reply | The CEO replied to Manager A on day 44; A forwarded it that day and B answered. No second ask was sent |
| R-32 | C: written yes on day 38 | A submitted on day 40, before the switch; B inherited a submitted record and the CEO heard nothing new |
| R-33 | D: introduced on day 6 | B copied the day-96 window end into the record and sent nothing; no message was owed |
| R-34 | E: in SourceX's process | B read the dashboard stage, dated it and left the company to SourceX |
| R-35 | G: CEO declined in the spring | The do-not-raise flag moved with the row and blocked B's new desk from listing the company as a target |
Thirty days later, the reconciliation found one stray reminder in Manager A's calendar for R-31, now closed, and nothing else.
Reconcile after thirty days
- Every moved record shows one owner, one open step and a due date.
- No company shows a second submission, and no CEO received two messages about the same step.
- The count of open referrals on the dashboard matches the CRM, stage by stage; the status reconciliation guide maps labels to fields.
- The transfer entry stays on the record permanently, as part of the evidence chain.
The fit facts do not change in a reassignment either: 50 or more full-time employees at peak, contractors left out; years of records the company created itself; rights to license them, never previously licensed for AI training; and a CEO who wants the conversation. What remains for SourceX's review also stays the same: whether the records match a current program, what customer contracts permit and what a license would cover.
When a reassignment is the wrong tool
- The CEO's trust is personal. A relationship cannot be reassigned. Keep the outgoing manager as relationship owner and move only the administrative steps.
- Capacity is the real problem. If referrals keep moving because one manager is overloaded, fix the intake. The first partner manager hire sets out caps worth borrowing.
- The record is already messy. Moving an unclear record to a new person makes it less clear. Repair it first, using the three-object referral CRM schema, then move it.
Nobody has published how often handoffs cause repeat asks or duplicate submissions, so count both for two quarters if you want to know, and browse the guides library for the neighboring operations playbooks.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
Before your next book rebalance, make sure the firm itself is the party that registered and signed, keep who qualifies beside the read-back and check the program terms for the window and notice rules each transfer must leave untouched.