- A Job Change Is a Relationship-Transfer Test, Not a Green Light
- Confirm the Move Before Treating It as a New-Company Opening
- Rebuild the New-Role Context Before You Contact the Person
- Choose the Relationship Path the New Context Allows
- Keep the Old Account and New Company as Separate Records
- Frequently asked questions
Act on a job-change signal by treating it as a relationship-transfer validation, not an immediate pitch. Before choosing a message or recipient path, re-establish the person's remit, start timing, authority, relevance, and permission to contact.
A Job Change Is a Relationship-Transfer Test, Not a Green Light
The alert lands while you still remember the last account. That memory can make the next step feel obvious, send a note and call it a warm opening. Pause there. A job change tells you that the old relationship may need to be re-examined. It does not tell you that the person's authority, priorities, or reason to hear from you survived the move. The useful question is narrower: has this relationship actually transferred to the new company?
What the Alert Confirms, and What It Does Not
A profile change is not a complete account fact. LinkedIn's help documentation, checked September 2026, notes that some profile edits do not generate network notifications even when profile-update sharing is enabled. Read the alert as a prompt to inspect the record, not as proof that every visible detail is current. The signal can start your check. It cannot finish it for you.
Why a Prior Champion Does Not Automatically Carry Authority
The old account and the new company now have different questions attached to them. LinkedIn Sales Navigator Data Validation documentation, checked September 2026, says it can identify when a CRM contact no longer works for the account linked to that contact record. That is a useful separation, not a handoff of influence. Keep the former champion's history as context, while treating the new role as an untested relationship with its own authority and relevance.
Confirm the Move Before Treating It as a New-Company Opening
Before you decide what the old relationship means, confirm what changed. LinkedIn Sales Navigator's alert guidance, checked September 2026, distinguishes a saved lead moving to a new company from a saved lead changing roles at the same company. Those are different operating situations. One can prompt research into a separate company. The other may only require you to reconsider the person's remit at the existing account.
Separate a Company Move from a Role Edit
If the person moved to a new company, create a new-company research question rather than assuming an inherited opening. If the person changed roles at the same company, revisit their remit before changing the account path. When the record does not make the event clear, keep the action in research or wait status instead of choosing a message.
- New company: investigate the new context before choosing outreach.
- Same company, new role: reassess remit and authority at the existing account.
- Unclear event: preserve uncertainty and do not select a message yet.
Check Whether the New Start Date Is Certain Enough to Act
An alert can arrive before the role has settled into a useful working context. Confirm the move from the information available to you, then ask whether you can name a current remit and a reasonable reason to engage now. In OKKI Go, preserve the uncertainty as part of the contact record rather than converting it into an outreach task. The boundary is deliberate: a confirmed move is not yet a confirmed opening.
Rebuild the New-Role Context Before You Contact the Person
You are deciding whether the relationship can cross a company boundary. Use a simple threshold: do not reconnect until you can state what the new role is responsible for, what authority the person appears to hold, and why your offer belongs in that context. If any answer is only borrowed from the old account, the signal has not earned an outreach decision. It has earned more research.
Map the New Remit and Actual Authority
Start with the work, not the title alone. Ask what the person can influence in the new role and whether that scope touches the problem you once helped solve. A familiar seniority label can hide a different mandate. Until the remit is clear, do not let an old champion label stand in for current authority.
Test Inherited Priorities Against Your Old Relationship
Your prior work may explain why the relationship matters to you, but it does not establish the new company's priorities. Separate the two. Note what the person valued before, then look for a present reason that fits the new role. If you cannot make that connection without retelling the old deal, you do not yet have a basis for a reconnection.
Check Whether Your Offer Is Relevant in This Company
Relevance is a present-tense test. It asks whether the new company, role, and timing make a conversation sensible now. It does not ask whether you would like the old relationship to continue. An OKKI Go workflow can keep these checks visible as notes for the next reviewer, but the notes should record uncertainty honestly. They should not manufacture a fit from a familiar name.
Choose the Relationship Path the New Context Allows
Imagine the moment after a former champion's move appears in your queue. Assume the only confirmed inputs are the previous relationship and an apparent new employer. Your constraint is that you cannot assume the new remit, priority, or permission. Change the mechanism from automatic outreach to validation. The observable result is a choice among reconnect, research, route, or wait. The consequence is proportionate action, not a promised response. This applies only while the new-company context remains uncertain.
Reconnect Only When Relevance and Permission Survive the Move
Reconnect when your check gives you a current reason to speak with this person in this role. Keep the message scoped to that reason. The old relationship can make the contact less cold, but it should not be used as permission to skip the new context. If the new remit cannot support the conversation, choose another path.
Research Further When the Role Is Real but the Fit Is Unclear
Research is the right result when the move appears real but the role does not yet explain relevance. Keep the old relationship as a lead, not a conclusion. Clarify the remit, the new company's situation, and whether a useful reason to engage exists before choosing a recipient or writing copy.
Route the Old Account When the Champion Has Departed
Do not abandon the old account merely because the person left. Route it as its own coverage question: who now owns the relevant work, and what needs to be rechecked there? This protects both records from a common mistake, treating one departure as a reason to move all attention to the new company.
Wait When the New Role Has Not Settled
Wait when the record still cannot support a clear reading of timing, remit, or relevance. Waiting is not a lost action. It prevents you from making the old relationship do work that the new context has not earned. Set a reason to revisit rather than disguising uncertainty as a warm opportunity.
Keep the Old Account and New Company as Separate Records
The decision becomes easier to review when the old account and the new company remain separate records. One describes a departed relationship and a replacement path. The other describes a possible new relationship that still needs validation. Keeping them distinct lets you explain why the next action is reconnect, route, research, or wait without claiming that a job change settled the question for you.
Record Why the Next Action Is Reconnect, Route, Research, or Wait
Reconnect when the new role, present relevance, and a reason to engage are clear enough to contact the person. Research when the move appears real but remit, authority, or relevance remains unresolved. Route when the old account needs a replacement-contact path. Wait when the available information does not yet support a reliable reading of timing or role context.
Common Questions About Acting on Unclear Job Changes
The point of the record is not to create a larger signal program. It is to make one current choice legible. When another person opens the contact record, they should be able to see what the alert suggested, what remained unconfirmed, and why the selected path was proportionate. That is enough to hand the decision back to the person who will act next.
Treat the alert as a reason to look again, not a reason to assume. When you can explain the new role, present relevance, and next action, the relationship may be ready to transfer. Until then, preserve the uncertainty and let it guide the decision.
Frequently asked questions
What do job-change signals describe in an existing relationship?
They describe a possible change in the contact's company or role. They do not prove that the old relationship, authority, or relevance transferred to the new setting.
What evidence should remain attached to a job-change decision?
Keep the alert category, what you confirmed about the move, the current remit or unknowns, the old-account replacement path, and the reason for reconnecting, researching, routing, or waiting.
What boundary limits a job-change signal?
It stops before message writing, tool selection, and a general signal-selling program. Its purpose is only to decide whether one former champion relationship is ready to transfer.
When should a job-change signal change the next action?
Change the next action only after the available context supports a present-tense reading of role, authority, timing, relevance, and permission. If it does not, research or wait is the more accurate result.
