Job Changes at Target Accounts: Separate Internal Promotions From New Employers

To distinguish an internal promotion from a move to a new employer, compare the person's previous and current company identities before interpreting the title change. Preserve dated evidence for both employment records. If the company is unchanged, classify the role update separately; if the company differs, verify the move before choosing an outreach play.

A changed title alone cannot establish either event. It may reflect expanded responsibility, a lateral move, a corrected profile, or a different naming convention. Even a more senior title does not prove that the person now controls budget or has started a buying process.

The workflow below is a proposed classification method for revenue teams. It separates documented Unify signal capabilities from the review rules your team must define. It does not assume that Unify automatically detects or classifies internal promotions.

Classify the employment change before choosing a campaign

Use an event record that preserves what changed rather than replacing the old title with the newest value. A current contact profile answers “what do we know now?” An employment event must also explain what the earlier record said and which evidence supports a transition.

Separate classification from qualification. Classification describes the employment change. Qualification asks whether the person and account fit your sales process and whether follow-up is appropriate. A confirmed move can be irrelevant; an internal promotion can matter without creating a new account.

1. Establish what the source actually says changed

Read the underlying evidence instead of relying only on an alert label. Record the source URL or approved internal reference, when it was checked, the title shown, the employer shown, and any stated start or end date. Preserve the wording needed to support the classification.

A source can establish a current role without establishing a promotion. It can also announce an appointment without proving that the person has already started. Keep those distinctions visible. Where only a month is given, retain month-level precision rather than inventing a day.

Separate the time the team discovered the change from the time the employment change occurred. Detection time is useful for operational routing; employment time is useful for interpreting the person's situation. Neither should silently replace the other when a workflow asks how recent an event is.

Do not infer increased responsibility solely from title normalization. Seniority labels can help organize a review queue, but the classification should rest on evidence of the actual change. If the source says only that a title changed, that is the claim the event should retain.

2. Confirm company identity before declaring a new employer

Compare the prior and current employer using the account identifiers and supporting evidence available to your team. Names alone are insufficient because companies can share similar names or operate under multiple brands. Domains help with research, but a changed domain by itself is not proof of a new employment relationship.

Check whether the apparent difference reflects a rebrand, an acquisition, a parent-subsidiary relationship, or a separate company. Record the relationship instead of forcing every difference into a binary move/no-move field. The operational account receiving the contact and the employer named in the evidence may require separate treatment.

When identity remains ambiguous, send the event to the account-data owner. Ask for a decision with a supporting reference, not just a corrected display name. Keep the person out of an employer-change sequence until that decision is available.

Also verify that the previous and current records describe the same person. A name match alone is a weak basis for merging employment histories. Use the approved identity evidence in your systems, and retain uncertainty when records cannot be reconciled.

3. Preserve employment history in a reviewable event record

Use the following blank field structure as an operating template. These are proposed review fields, not a claim that every field exists natively in Unify or your CRM. Implement only the information needed for the decision and permitted by your data policies.

Retain unknown values as unknown. An empty end date does not necessarily mean the old role continues, and a newly observed profile entry does not establish its exact start date. If sources disagree, preserve the disagreement with the review decision rather than silently discarding an inconvenient record.

Consider overlapping roles explicitly. Employment, advisory positions, board appointments, and consulting relationships can coexist. A new affiliation may be relevant, but it should not automatically replace the person's primary employment or trigger outreach written for a full-time hire.

Keep the underlying event separate from the current contact fields. That lets the team update contact details while retaining the rationale for an earlier routing decision. It also makes later corrections possible without reconstructing the history from a sent message.

4. Use the appropriate Unify signal family

Unify's Champion Tracking documentation describes following customers, former buyers, and advocates as they move to new companies. It checks selected people every 30 days and shows detected moves with the new company and role. Recent moves may appear in a later cycle as information becomes available.

The same documentation describes excluding old job records after a detected move and using job-change conditions or a champions trigger for follow-up. Review those workflow settings before activating outreach; a detected move still needs an appropriate account and relationship decision.

Unify's New Hire Tracking documentation describes daily searches for people who recently joined target companies. Teams select companies and personas and set a daily limit. Found hires can feed audience filters and plays for research, account-owner notifications, or qualified sequence enrollment.

Those documented families support different starting points: a known relationship moving elsewhere, or relevant hires discovered at target accounts. Neither establishes a native internal-promotion classifier. Treat the same-employer review rules in this article as a separate operating method unless your team verifies additional functionality.

For the discovery setup, see how to track job changes at target accounts. Use the classification here before selecting the campaigns described in the guide to turning new-hire and job-change signals into outbound plays.

5. Match the sales hypothesis to the verified event

An internal promotion supports a question about changed responsibility at the same organization. Review the existing account owner, active conversations, and customer relationship first. The relevant action may be an internal handoff or account-plan update rather than a new outbound sequence.

An employer change supports a different question: does a prior relationship create a relevant reason to reconnect at the new organization? Recheck account fit and the person's current role. Familiarity with your product does not establish authority at the new company, and the previous company's commercial circumstances do not transfer with the person.

A newly discovered hire supports research into the role and account, without implying that your team already knows the person. Do not borrow the language of a warm champion relationship when no such relationship exists.

For any event type, separate the observed fact from the proposed business relevance. The fact may establish a new role; the relevance remains a hypothesis about responsibilities or priorities. Draft messaging that can stand on the verified fact without asserting an unobserved budget, project, or mandate.

Keep outreach proportionate. A public role announcement is not an invitation to disclose private CRM history or details from a previous employer. Have the relationship owner decide what context is appropriate to reuse and what should remain internal.

6. Hold ambiguous updates and control repeat actions

Create a review queue for missing company identity, conflicting dates, uncertain person matches, and unclear role types. Give each item a specific unanswered question and an owner. “Needs research” is less useful than identifying the exact fact that would change the classification.

Set a review interval that reflects the team's capacity and the source's likely update pattern. If the missing evidence never appears, keep the event unresolved or close it without outreach. A queue should not turn uncertainty into certainty merely because an item has been waiting.

Before an approved event starts a workflow, check existing conversations, contact preferences, account ownership, and suppression rules. Confirm the intended contact route for the current role. Avoid continuing a sequence against an old employment record simply because its address remains stored.

Define what counts as the same event across repeated observations. A later source confirmation should enrich the existing review record when it describes the same transition. It should not automatically create another congratulatory message or a second owner assignment.

Evaluate classification quality before expanding automation

Review a sample of actual events and ask whether another reviewer can reproduce the classification from the retained evidence. Track disagreements by cause: company identity, dates, person identity, or role interpretation. Use those findings to refine the instructions and source requirements.

Evaluate detection, classification, and outreach separately. Finding a change does not prove that it was classified correctly; correct classification does not prove that a message was relevant. Avoid treating sequence volume as evidence that employment data is accurate.

Start with a reviewed queue and allow only well-supported event types into automated routing. In Unify, connect the documented signal family to an appropriate research or owner-review step before increasing outreach volume. Keep the review record available when a rep needs to explain why the person entered the workflow.

Glossary

• Internal promotion: an evidenced advancement within the same employer.
• Internal role update: a same-employer change that does not necessarily establish promotion.
• Employer change: a verified transition to a different employing organization.
• Employment date: when a role started or ended, with the precision supported by its source.
• Observation time: when your team or system discovered evidence of the change.
• Event classification: the reviewed interpretation of an employment change, separate from sales qualification.

Frequently asked questions

Does a more senior title prove that someone was promoted?

No. A title can change without evidence of greater responsibility or an internal promotion. Compare the employer and inspect the underlying source. When the evidence supports only a title change, retain that narrower classification and avoid claiming a promotion in outreach.

Does Unify automatically distinguish promotions from employer changes?

The documentation reviewed describes Champion Tracking and New Hire Tracking, not an automatic internal-promotion classifier. Use the proposed evidence review in this article to distinguish same-employer changes from verified moves. Confirm any additional product capability before relying on it in an automated workflow.

Can a company rebrand look like a job change?

A changed company name or domain can create an apparent difference between records. Review the organizational relationship before deciding that the employer changed. Preserve a rebrand or account-identity correction separately from an employment transition when the evidence supports that distinction.

Which date should determine whether a job change is recent?

Keep both the supported employment date and the observation time. Choose the date that matches the workflow's purpose and document that choice. Do not substitute detection time for a missing start date or invent a precise day from a source that gives only a month.

When should a job-change alert be held instead of triggering outreach?

Hold it when person identity, employer identity, dates, or role type remain materially uncertain. Also check account ownership, active conversations, and contact restrictions before routing. A verified employment event is a research input; it does not remove the need to qualify the next action.