# JML redesign archive context checklist | SourceX

Canonical: https://refer.sourcex.si/resources/joiner-mover-leaver-redesign-archive-context-checklist
Last updated: 2026-11-05

Check three stations in order: before the redesign is announced, before the new HR-triggered automation goes live, and before legacy rules, workflows and trackers are switched off. At each, confirm whether the records will still show who transferred, who left and why an exception was granted, name the owner, and note what is lost if it is skipped. Station dates come from the company's own plan, never from your estimate.

The checklist belongs to the [redesign guide for access-management advisors](/guides/moment-joiner-mover-leaver-redesign-identity-management-consultants). The questions are first raised in the [20-minute meeting agenda](/resources/joiner-mover-leaver-redesign-meeting-agenda); this page carries them through to switch-off.

## Setting the clock for an access-process redesign

| Station | Where the date usually comes from | If no date exists |
|---|---|---|
| Announcement | The access governance project charter or an audit finding that triggered it | Treat station one as an early, unhurried inventory |
| Go-live | The cutover plan for HR-triggered access automation | Record who owns the go-live decision |
| Legacy switch-off | Retirement of old automation rules, a legacy IGA tool contract end or a ticket queue migration | Leave it open; the item is "who decides" |

Every item gets one state: **confirmed** by an owner, **unknown** with a named person to find out, or **at risk** because the plan drops it. Record configuration, counts and owners. Never record names, user IDs or HR details, even as examples.

## Station one: before the redesign is announced

| Confirm | Owner | If skipped |
|---|---|---|
| Whether each past account change can be matched to an HR status: transfer, leave or termination | HR records owner and access lead | Transfers and departures become indistinguishable in history |
| Where exceptions are approved: access request tool, service desk or email | Access request owner | The reasons behind kept access or delayed disablement scatter |
| Whether platform audit logs are routed to long-term storage | Access lead | History older than the platform default is already gone |
| Who owns HR and access records, and which privacy obligations apply | CIO or owner, with counsel | Rights and privacy issues surface after an introduction |

The control expectation is clear: NIST SP 800-53 expects access to change when someone changes jobs, and account handling to follow HR exits and moves. Whether the records show that it happened, case by case, is what this station finds out.

## Station two: before the new workflows go live

| Confirm | Owner | If skipped |
|---|---|---|
| Whether legacy workflow and automation run history will be exported before the switch | Access lead | Portal history ages out after go-live |
| Whether the classification logic in old automation rules is documented | Access engineer | Nobody can explain later why a change counted as a transfer |
| Whether exception tickets keep their link to the HR event that triggered them | Service desk owner | Decisions survive without the situation they answered |
| How many years and roughly how many role changes per year exist | HR records owner | The archive cannot be described when it matters |

Retention is short by default on some platforms. Microsoft Entra keeps audit logs for 7 days on Entra ID Free and 30 days on P1 and P2, and lifecycle workflow history in the admin center can be filtered for up to 30 days; Microsoft's guidance is to save that history as a CSV report, up to 100,000 records per download, or use the reporting API for more. Whether to do any of this is the company's call.

## Station three: before legacy workflows are switched off

| Confirm | Owner | If skipped |
|---|---|---|
| Whether old trackers and spreadsheets of exceptions are archived or deleted | Access lead | The only record of some handover decisions disappears |
| Whether the legacy IGA tool or ticket queue keeps a read-only period, and who reviews its end | CIO | History is removed at contract end without a decision |
| Who signs off the final retention decision for access and HR history | CIO or CISO, with HR | No one is accountable for what was dropped |
| Whether the owner wants to hear about licensing before switch-off | Owner | The question is never asked while the history exists |

Bulk disablements after a reorganization are the case to watch. If the platform logged "account disabled" with no HR reason or approval attached, that slice of history cannot answer the transfer-versus-departure question, and the checklist should say so honestly.

## When the checklist is done: fit, disclosure and what stays unknown

The checklist describes the records; it does not decide eligibility. Before raising SourceX, check: 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.

| What the checklist establishes | What only SourceX review establishes |
|---|---|
| Whether transfers, departures and exceptions are distinguishable, and for how many years | Current demand for access-governance decision records |
| Who owns HR and access history, and which privacy rules apply | The rights and privacy review, including de-identification |
| Documented go-live and switch-off dates | Any offer to the company |
| That the reward was disclosed | Whether any referral reward becomes payable |

Ask permission before mentioning SourceX, and disclose your interest in the same breath. SourceX licenses approved business data directly from companies for AI training and evaluation and pays any eligible reward separately under its [terms](/terms), never from the company's payout. Illustrative only: a $400,000 payout to the company would mean a $70,000 default reward. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. When the owner opts in, use the [introduction email](/resources/joiner-mover-leaver-redesign-introduction-email). The [exception handling data guide](/guides/exception-handling-ai-agents-data), the [email archive migration guide](/guides/email-archive-migration), the [Microsoft 365 Business Premium user limit page](/systems/microsoft-365-business-premium-300-user-limit) and the [MSP client offboarding checklist](/resources/msp-client-offboarding-checklist) cover neighboring records and moments.

## 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 legacy workflows are still running and the owner wants to talk before they retire, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) first.

## Sources

- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-reports-data-retention
- https://learn.microsoft.com/en-us/entra/id-governance/download-workflow-history
- https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf
