Joiner-mover-leaver redesign: the role-change decisions identity consultants can help a company keep

Short answer

Often only partly. A disabled account looks the same whether the person left or changed roles, so the distinction lives in HR status changes, service desk tickets and approved access exceptions, not in the identity platform's log alone. Before a joiner-mover-leaver redesign, identity management consultants can ask the company's authorized owner: can the owner distinguish role transfers from employee departures? If the records can show it, and the company wants to explore licensing, introduce its decision-maker to SourceX.

Visual briefFull-size diagram
A decision tree from one account change event: still employed leads to a mover record with access modified and an exception approved, not employed leads to a leaver record with access removed, and a warning branch shows a bare 'account disabled' log entry that cannot tell the two apart.
Illustrative decision path for one account change. Audit log retention depends on the company's platform and license.

Can the owner distinguish role transfers from employee departures?

Put the question to the owner of the identity process, then ask how they would prove it for a case from three years ago. That second step separates a process that works from records that can explain it.

The distinction is built into the standard model. Microsoft's lifecycle workflow documentation defines a mover as someone who moves between boundaries within an organization and might need more access, and a leaver as someone who leaves the scope of needing access, for example by retiring or being terminated. NIST SP 800-53 sets the matching expectation for controls: access authorizations should be modified to match changed operational need after a transfer, and account management should be aligned with termination and transfer processes. In practice, most of the interesting records come from the cases that did not fit neatly: a transfer with temporary access to the old team's systems, a leaver kept active for a handover, a contractor converted to staff.

Those role-change exception decisions are the substance. Each one pairs a situation, a policy, a decision and an approver, which is the shape of record useful for AI training and evaluation of access-governance judgment. The guide on exception handling data explains why exception records matter in general; this page focuses on the identity redesign moment.

Decision map: five account changes and where each decision lives

Illustrative. A 420-person regional engineering firm is redesigning its JML process around a new identity governance tool. Five changes from the old process:

EventHR statusClassificationException decisionWhere the decision is recorded
Project engineer moves to estimatingActive, new departmentMoverKept read access to old project folders for a set handover period, approved by both managersService desk ticket plus access request approval
Office manager resignsTerminatedLeaverMailbox delegated to successor before account disabledHR offboarding form plus mailbox change log
Contractor hired as employeeActive, new worker typeMover with new identity recordOld contractor account merged, not deletedIdentity admin note in a ticket
Field technician on extended leaveActive, on leaveNeitherAccess suspended, not removedHR leave record plus a group change
Bulk disablement after a reorganizationMixedUnclearNone recordedIdentity platform log only

The last row is the warning case: the platform recorded "account disabled" with no link to the HR reason or approval. If most history looks like that row, the honest answer to the question is "no", and that is worth knowing before anyone spends time on an introduction.

Why are role-change exception decisions easy to overlook?

Because a JML redesign is about the future flow. The project defines new triggers from the HR system, birthright access by role, automated provisioning and cleaner offboarding. Its success measure is fewer orphaned accounts and faster joiners, not a readable history of past decisions.

The history is also scattered. The authoritative mover or leaver status sits in the HR system. The reason for an exception sits in a service desk ticket. The approval sits in an access request tool or an email. The identity platform holds the action itself, often with a short default retention: Microsoft Entra keeps audit logs for 7 days on Entra ID Free and 30 days on P1 and P2, and longer retention means routing logs to storage through Azure Monitor. Each team sees one piece and assumes another team keeps the whole.

Finally, redesigns retire the logic that explains old cases. Provisioning scripts, legacy workflows and spreadsheet trackers are replaced, and with them goes the rule that decided whether a given change counted as a transfer or a departure. Nobody needs that rule after go-live, so nobody asks to keep it.

Four metadata questions for the owner

Stay at metadata level: what exists, how much, how long, which system and who owns it.

  1. Where is the classification? Does each account change link to an HR status that says transfer, departure or leave, or does the identity log stand alone?
  2. Are exceptions recorded with reasons? When a mover keeps old access or a leaver stays active for a handover, is the approval and reason written down, and where?
  3. How far back, and where kept? How many years of tickets, access request approvals and review sign-offs exist, and are platform logs routed to long-term storage?
  4. Who owns and authorizes? Who owns HR and access records, which privacy obligations apply, and who could authorize a licensing discussion?

Never ask for user lists, access exports or HR files, and do not open an access review to check an answer. Many identity programs include employee personal data, so expect the owner to want counsel involved; that is the right instinct, not an obstacle. The MSP client offboarding checklist and the guide to internal access controls for a sensitive data project cover adjacent questions about access and records.

How do you disclose the reward and get the owner's permission?

Ask before you raise SourceX, and disclose in the same breath. For example: "Those decision records may have value outside the company. May I mention one option? I am a SourceX referral partner, so I may receive a reward if it goes ahead."

If the owner agrees, explain that SourceX licenses approved business data directly from companies for AI training and evaluation and pays the company, and that any reward to you is funded separately under its terms and never deducted from the company's payout. If the owner declines, the redesign carries on unchanged.

State the reward exactly. The default on a company's first qualifying transaction is 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%, and the USD 50,000 floor applies once per referred company. Illustrative reference only: a company paid $400,000 for a qualifying completed handoff would mean a $70,000 default reward (USD 50,000 plus 5% of the payout, which is more than 15%). A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. The rewards page explains each condition.

Does the company qualify, and who can authorize a licensing discussion?

Check fit before you raise it. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

QuestionWhat an identity consultant can usually confirmUnknown until SourceX reviews
Which records exist?Access requests, exception approvals, review sign-offs, HR status changesWhether buyers need that record type
Who owns them?The company, subject to employee privacy obligationsThe rights review result
Who can authorize?CEO, often the owner, usually with counselDataset scope and de-identification
How much and how long?Rough event counts and years coveredThe company's offer and any reward

Sign the Channel Partner Agreement before you submit an introduction. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, and one partner is credited per company. The management consultants page, the fractional CIO page and the partner hub show how this fits other advisory roles.

Go deeper on joiner-mover-leaver redesign records

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.

If the owner can show transfers apart from departures in the records and wants to explore licensing, register as a partner, check who qualifies, and read the program terms before you make the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Why does the mover-versus-leaver distinction matter for licensing?

Because the decisions around a transfer, such as which access to keep, for how long and who approved it, are judgment calls made against a policy. Records that show those calls, with the reason, are far more informative than a list of disabled accounts.

Are identity audit logs enough on their own?

Often not. Platform audit logs can have short default retention, so the longer record usually sits in HR systems, service desk tickets and access review sign-offs. Ask where each part is kept.

Can I share an access review export with SourceX to show the opportunity?

No. Access data is sensitive, and partners never handle client records. Describe what exists, how much and where, and let the authorized contact decide whether to talk to SourceX.

Sources

  1. refer.sourcex.si/terms
  2. learn.microsoft.com/en-us/entra/id-governance/what-are-lifecycle…
  3. learn.microsoft.com/en-us/entra/identity/monitoring-health/refer…
  4. nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment