Changing the CRM owner does not complete a handover
A colleague takes over a client and the owner field changes. Two days later, the client is still waiting for a promised answer. The new colleague saw the project plan, but the latest commitment remained in an old email.
Complete the transfer when the receiving person understands the current state, can open the evidence, and accepts the next action. Until then, the previous owner remains responsible. Use this rule for a lasting change of account contact or project responsibility.
Download the handover record and client introduction and completed fictional example.
Summarize what the next person needs to decide
The new colleague does not need a chronological transcript of every email. They need the agreement, unresolved questions, and the first action. Provide a brief summary with links to the original records.
Include the client contact, current scope, latest confirmed commitment, open decisions, and nearest due date. Identify any dependency that could change that date. A confirmed Wednesday delivery and a working estimate dependent on Monday’s photographs are different commitments.
In the fictional example, Morgan transfers a website project to Casey. The first task is to confirm by Tuesday whether the supplied photographs are sufficient for the design, rather than a vague instruction to review the account.
Test access as the receiving person
Link to the existing CRM, files, and conversation. Casey opens them with their own account and locates the exact proposal and latest message. If a shared link fails, the transfer remains open.
Do not paste passwords into the handover document. Use your established account administration or sharing process. Give client-file access to people who need it for their work. Check application ownership separately: software ownership and client responsibility may be controlled in different places.
Ask for an explicit acceptance
The receiving colleague confirms that they opened the evidence, understand the unresolved items, and will own the stated next action from the agreed time. A short retained reply can be sufficient operationally:
I have taken over the client from October 5. I can open the project records. By Tuesday I will check the photographs and confirm the next step with the client. Morgan is still resolving access to analytics.
Assign a person and date to each missing item. If an item blocks progress, postpone acceptance. A created task or delivered notification does not establish that the recipient accepted responsibility.
Introduce the confirmed change to the client
Send the introduction after the internal acceptance. Name the new contact, the effective date, and the nearest next step. The client should not need to retell the project. Keep internal notes and unconfirmed estimates out of the message.
From Monday, Casey will coordinate the next steps. I have copied them here and handed over our existing records and agreement. On Tuesday they will confirm whether the photographs are sufficient for the design. You can continue replying in this thread.
These are example dates; use your actual agreement. If the recipient is unavailable or declines the handover, the previous owner proposes an alternative and retains responsibility.
Close the transfer after its first action
During a short follow-up review, check that the introduction was sent, the new owner performed the first action, and remaining items have named owners. Then mark the transfer complete. Keep the original history.
Automation can prepare tasks and reminders. Acceptance of responsibility and interpretation of commitments remain human decisions. For the initial inquiry route, see one new inquiry. For the transition before delivery starts, see agreement to start.
The case and procedure are illustrative. Try one test handover in your environment, including an inaccessible link and an unavailable recipient.
When the transfer does not pass
If Casey cannot open proposal v2, keep “waiting for access.” Morgan retains the client relationship and checks the repair by October 5 at 10 a.m. Do not send the ownership-change introduction yet. If Casey can open the records but lacks capacity for Tuesday’s check, Morgan arranges another receiver or confirms a revised next step with the client; reading the record is not acceptance. Analytics does not block the photograph check in this model, so it can retain its own open task after the main responsibility transfers.
Use an internal reminder for the agreed next action. It tracks work; it does not accept responsibility or automatically introduce the new owner to the client.