# JML redesign introduction email, annotated | SourceX

Canonical: https://refer.sourcex.si/resources/joiner-mover-leaver-redesign-introduction-email
Last updated: 2026-11-05

Send a short, plain email to the executive who can authorize a licensing discussion. Name the record types the owner described (HR status changes, approved access exceptions and the tickets that explain them), say whether transfers and departures can be told apart in that history, disclose your referral interest, and ask for a single call about metadata. Never include user names, access lists, ticket text or an estimate of value. The draft and its annotation follow.

This email is part of the [joiner-mover-leaver redesign guide](/guides/moment-joiner-mover-leaver-redesign-identity-management-consultants). It is the last step of the conversation, not the first: send it after the [JML meeting agenda](/resources/joiner-mover-leaver-redesign-meeting-agenda) ends with a yes.

## When the email is ready to send

The draft only works if four things are already settled. If any is missing, fix that first and write later.

- **The owner opted in.** They agreed to an introduction after hearing that you are a SourceX referral partner. Agreement to "think about it" is not agreement to be introduced.
- **The answer to the core question is known.** You asked whether the owner can distinguish role transfers from employee departures, and you have their word for it: yes, partly or no. A "no" means there is nothing to introduce yet.
- **The recipient is named.** It must be the person who can authorize a licensing discussion about HR and access records, by name and title. In identity work that is rarely the person who ran the workshop.
- **Your partner agreement is signed.** The Channel Partner Agreement comes before any introduction is submitted.

Identity records carry employee personal data, so assume the recipient will forward the email to counsel. Write it so that forwarding helps you.

## The draft: subject line, three paragraphs, one ask

Illustrative. Replace everything in brackets with what the owner told you, and delete any sentence you cannot support.

> **Subject:** Introduction: [Company] and SourceX, access decision history
>
> Hi [Executive name],
>
> While [Company] redesigns its joiner-mover-leaver process, [Owner name] and I discussed the history the old process leaves behind. As the team described it, HR status changes record whether each account change was a transfer, a departure or a leave, and approved access exceptions are kept in [service desk system] with reasons, going back about [number] years.
>
> You are the person who can decide whether that history is worth discussing with SourceX. SourceX licenses approved business data directly from companies for AI training and evaluation and handles the agreement, rights review, data preparation, delivery and payout. I have not seen, exported or kept any HR, ticket or access records.
>
> For transparency, I am a SourceX referral partner. If a qualifying license completes, SourceX may pay me a reward from its own funds; it never reduces what [Company] receives. Would a 20-minute call with SourceX about record types, years and systems, and nothing more, be useful?
>
> [Your name]

Three paragraphs, roughly 150 words. If yours runs past 200, something from the "never" column below has probably crept in.

## Why each line is there, and what stays out of it

Read the table row by row against your own draft. The last column is where most edits go wrong.

| Line | Why it is there | Never put in it |
|---|---|---|
| Subject: "access decision history" | Says what the email concerns in neutral words both parties can forward | "Opportunity", "monetize", a dollar figure, or the word "breach" |
| "While [Company] redesigns its joiner-mover-leaver process..." | Places the email inside a project the executive already sponsors | Project problems, audit findings or orphaned-account counts |
| "HR status changes record whether each account change was a transfer, a departure or a leave" | Answers the core question at metadata level: the classification exists and where | Any employee name, department move, termination reason or HR file detail |
| "approved access exceptions are kept in [service desk system] with reasons" | Names the record type that carries the judgment: situation, policy, decision, approver | Text from a ticket, a quoted approval, or an example of a specific exception |
| "going back about [number] years" | Gives the time span that makes a history useful | A figure the owner did not give; leave it out instead |
| "You are the person who can decide..." | Confirms authority and hands the choice to the right person | Deadlines, "before the old system goes", or pressure of any kind |
| "SourceX licenses approved business data directly from companies..." | One accurate sentence on what SourceX does and handles | Buyer names, prices, or claims the records "will sell" |
| "I have not seen, exported or kept any HR, ticket or access records." | Tells counsel at once that nothing personal has left the company | Any hint that you hold a sample, screenshot or user list |
| "For transparency, I am a SourceX referral partner..." | Discloses your interest and that the reward is funded separately | The reward amount, or wording that suggests the company pays it |
| "A 20-minute call... record types, years and systems" | A small, metadata-only ask that is easy to accept or decline | A request for exports, admin access, sample tickets or logs |

### Why the second paragraph points to HR and ticket records

The executive reading this email needs to know where the evidence sits, and a counsel reading it over their shoulder needs to know how long it lasts. Three sourced points shape that sentence:

| Point the draft relies on | What the source says | How it changes the wording |
|---|---|---|
| The classification may not be in the identity platform | Microsoft's lifecycle workflow model treats a mover (crossing boundaries inside the organization, perhaps needing more access) and a leaver (no longer needing access) as different events | Because a disabled account can look the same either way, the draft cites HR status changes as the place that says "transfer" or "departure" |
| Good practice expects linking records | NIST SP 800-53 asks for access to be modified after a transfer and for account management to follow termination and transfer processes | The draft can mention exception approvals as a normal, expected record type, not a special favor |
| Platform history is short by default | Microsoft Entra holds audit logs 7 days on Entra ID Free and 30 days on P1 and P2, longer only when routed to storage through Azure Monitor | The draft gives the time span from tickets and HR history, not from sign-in or audit logs, unless the owner confirmed long-term routing |

If the owner told you their platform logs are routed to long-term storage, you may add "and archived platform logs" to the list of record types. If they were unsure, leave it out; an unsure claim in an introduction becomes a correction later.

## Words that turn a JML email into a records leak

Most problems come from helpful additions. These are the ones to cut on sight.

| Tempting addition | Why it feels useful | What it really does |
|---|---|---|
| "For example, when a payroll analyst moved to treasury last spring..." | Makes the record type concrete | Describes a real person's transfer outside the company |
| A redacted access review attached | Shows the format | Moves employee records out without authority, redacted or not |
| "Roughly 12,000 account changes" when nobody counted | Sounds precise | Creates a number the company never stood behind |
| Copying the HR and IT teams | Keeps everyone aligned | Widens a commercial conversation the executive has not approved |
| "This should qualify" | Sounds encouraging | Prejudges a review only SourceX can make |

The [introduction email builder](/tools/introduction-email-builder) offers other openings, the [wealth advisor introduction email](/resources/wealth-advisor-business-owner-client-introduction-email) shows the same disclosure in a different relationship, and the [email preparation worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation) helps collect facts before you draft. Keep the disclosure and the metadata-only ask in every version.

## Facts to confirm about the company before it goes

Spend two minutes on these before you press send.

- **Size and history.** 50+ full-time employees at peak (contractors excluded) and a documented operating history. A JML redesign often signals enough headcount, but check rather than assume.
- **Location and language.** 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.
- **Rights.** The company must have rights to license the records. HR and access records involve employee privacy obligations, so expect counsel to shape what can be offered.
- **Attribution.** The first valid introduction within the 90-day window is credited when the company submits a verified application, with one partner per company.
- **Reward.** Illustrative only: if the company were paid USD 100,000 for a qualifying completed handoff, the default reward on a first qualifying transaction would be USD 55,000 (the greater of USD 50,000 plus 5% and 15%). Nothing is payable for the email, a meeting or a signature on its own; the [rewards page](/rewards) lists each condition.

What stays unknown until SourceX reviews the application: buyer need for access decision records, the rights review result, de-identification scope and any offer. If the [archive context checklist](/resources/joiner-mover-leaver-redesign-archive-context-checklist) left an item open, keep it out of the email. The [management consultants page](/for/management-consultants) shows how other advisory roles handle the same step.

## 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 confirmed that transfers and departures can be told apart and agreed to the introduction, [register as a partner](/register), check [who qualifies](/who-qualifies), and keep the [program terms](/terms) open while you adapt the draft.

## 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
