# JML redesign meeting agenda (20 min) | SourceX

Canonical: https://refer.sourcex.si/resources/joiner-mover-leaver-redesign-meeting-agenda
Last updated: 2026-11-04

Use 20 minutes with the access lead, the HR systems owner and the person who can authorize a licensing discussion. Block two puts the question directly: can the owner distinguish role transfers from employee departures in the records, not only in today's process? The next blocks find where exception approvals and reasons are written and how long logs and tickets are kept. The meeting ends with a recorded decision: introduce, revisit after go-live, or stop. Nobody opens a user list.

It is part of the [joiner-mover-leaver redesign guide for identity management consultants](/guides/moment-joiner-mover-leaver-redesign-identity-management-consultants), which explains why role-change exception decisions matter. This page is the meeting: seats, timed blocks, how to read the answers, and the close.

## Seats and timing for a short identity meeting

Book it at the end of a design session, after the new HR-driven triggers are agreed and before legacy automation and workflows are retired. People can still explain how the old process told a job change from an exit.

| Seat | Reason to invite | Blocks |
|---|---|---|
| Access lead | Owns account automation, the directory and its logs | 1, 2 and 4 |
| HR systems (HRIS) owner | Knows which worker status changes mean transfer, leave or termination | 2 |
| Service desk or access request owner | Knows where exceptions and their approvals are recorded | 3 and 4 |
| CIO, CISO or owner, with counsel if wanted | Owns the records and can authorize a licensing discussion | 4 and 5 |

The invite line: "20 minutes on how the old process recorded transfers, departures and exceptions. Description only; no user data." That sentence tells HR and IT nobody will ask for an extract.

## Running a tight 20 minutes

Twenty minutes leaves no slack, so set the ground rules in the first breath.

- **Timekeeper.** Hand the clock to the access lead and ask them to call each boundary. You stay free to listen and take notes.
- **No live examples.** If someone starts describing a named colleague's move, stop politely and ask for the pattern instead. Personal details never belong in these notes.
- **Parking lot.** Design questions about default role bundles or approval chains go to the workshop backlog, not this slot.
- **Notes template.** Four columns: block, answer (yes, partial, no, unknown), who answered, follow-up owner. Read them back at minute 17.
- **Hard stop.** Finish on time even with an open item; a named follow-up beats losing the decision maker to the next meeting.

## The 20-minute run sheet

Illustrative. A 380-person specialty insurance broker is rebuilding its account lifecycle around HR-triggered automation. The consultant runs this agenda at the close of the second design workshop.

| Minutes | Question | Answered by | A good answer sounds like |
|---|---|---|---|
| 0-3 | What changes in the redesign, and when do the new triggers go live? | Access lead | "HR events will drive provisioning from go-live; the old scripts retire after." |
| 3-8 | For a change three years ago, could you show whether the person transferred or left? | HRIS owner and access lead | "Yes for most: every account change has an HR status code, transfer or termination." |
| 8-13 | When a mover kept old access or a leaver stayed active, is the reason and approver written down? | Access request owner | "Yes; exceptions go through a ticket with the manager's approval and an end date." |
| 13-17 | How long are identity logs, workflow history and tickets kept, and who owns them? | Access lead and CIO | "Audit logs are routed to storage; tickets go back to 2018; HR owns status history." |
| 17-20 | Would the company like to hear how licensing of approved records works, and who would lead it? | CIO or owner | "Yes, with counsel; our CISO is the contact." |

### Facilitator notes for blocks two and four

These two blocks carry the meeting. The notes below are what to say if the room stalls, with the source behind each prompt.

**Block two, minute 3.** Start from the vocabulary the new tool will use. Microsoft's lifecycle workflows name two separate events: someone crossing a boundary inside the organization who may need more access, and someone who no longer needs access at all. Then ask the HRIS owner: "Before this redesign, which field told IT which of those two happened?" NIST SP 800-53 expects a transfer to change access and account handling to follow the termination and transfer processes, so many teams will say a process exists. The three-year test asks whether the record of it exists too. A company can run a sound process today and still hold no trace of which category a 2022 change fell into.

**Block four, minute 13.** Ask the access lead which Entra license the company holds before asking about years. Entra's default audit retention is 7 days on Entra ID Free and 30 days on P1 and P2; anything older survives only if someone routed it to storage through Azure Monitor. If the answer is "we never set that up", turn straight to the service desk owner and the HRIS owner, because their tickets and status history become the long record. Write the license tier and the routing answer as two separate notes.

## Interpreting what you hear

| Answer | What it usually means | What to note |
|---|---|---|
| "The platform just shows 'disabled'." | Transfers and departures look the same in the identity log | Ask whether HR status history can be matched by date; note "partial" |
| "Exceptions are approved by email." | Decisions exist but outside a system of record | Note "email" and roughly how many years |
| "We merged contractor and employee accounts by hand." | Identity records changed with notes in tickets | Note the ticket queue type, not cases |
| "Logs were never exported." | Platform history is short | Note it for the [archive context checklist](/resources/joiner-mover-leaver-redesign-archive-context-checklist) |
| "HR will not let anyone touch status history." | Ownership and privacy need the owner and counsel | Pause at block four; do not push |

"Transfers mostly distinguishable, exceptions in tickets since 2018, logs short, CISO to decide with counsel" is a complete answer. The [exception handling data guide](/guides/exception-handling-ai-agents-data) explains why the exception rows matter most.

## Saying the three things before block five

**What SourceX does.** SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. Nothing leaves the company because of this meeting.

**Your interest.** You are a SourceX referral partner. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward under the [terms](/terms). It is funded separately and never deducted from the company's payout. Illustrative only: a $250,000 payout to the company would mean a $62,500 default reward.

**Fit.** 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.

Unknown until SourceX reviews it: demand for access-governance decision records, the rights and privacy review, the de-identification required for employee data, any offer and any reward. Partners never ask for or handle user lists, access reviews or HR files. The guide to [internal access controls for a sensitive data project](/guides/internal-access-controls-sensitive-data-project) shows how companies protect such records.

## Recording the outcome

| Outcome | When it fits | Recorded by | Next action |
|---|---|---|---|
| Introduce now | Block two is yes or partial, the company owns the records, the owner opted in | Consultant | Send the [introduction email](/resources/joiner-mover-leaver-redesign-introduction-email) to the named contact, copying counsel if asked |
| Revisit after go-live | Answers depend on HR or log checks still to be done | Access lead | Set a date tied to the documented go-live |
| Stop | The owner declines, or privacy constraints rule it out | Consultant | Note the reason; the redesign continues unchanged |

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. The [cybersecurity due diligence resource](/resources/cybersecurity-due-diligence-m) covers related identity questions in a deal setting, and the [first board meeting agenda](/resources/first-board-meeting-after-private-equity-investment) shows another tightly timed meeting format.

## 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 meeting closed on "introduce now" and the owner named a contact, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before making the introduction.

## Sources

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