# Role change access completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/role-change-to-access-completeness-checklist
Last updated: 2026-11-04

A role-change-to-access trail breaks when a person moves jobs and the new access is granted on request while the old access is removed by nobody in particular. Terminations are usually one automated event; transfers are a grant plus a removal, and only the grant is somebody's job. Six checks, each scored pass, partial or fail from a conversation with the identity owner, show whether a company's Workday, Okta and ServiceNow records hold that removal step, its timing and its proof.

This scorecard belongs to the [role-change-to-access records guide](/guides/chain-role-change-to-access). If you want to see what a single export loses before scoring anything, the [before-and-after page](/guides/role-change-to-access-missing-context) walks one transfer through.

## Scoring rules: 2, 1 or 0 per check

Each check scores 2 for pass, 1 for partial and 0 for fail; six checks make 12. Pass means the identity owner or HR operations lead says the condition holds for the whole period they describe. Partial means it holds for some years, some applications or some business units, and they can say which. Fail means it does not hold or nobody knows. Write "unknown" beside a zero that comes from not knowing, because a reviewer reads those differently from a known no.

Ask for estimates, never examples. "Roughly what share of applications are granted through groups?" is the right question. "Can you show me a user who moved?" is not. Your notes hold counts, years and system names only: no user names, no group names, no log lines.

## Six checks on the transfer trail

| Check | Ask at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Coverage overlap | "Since when have the HR system, the identity platform and the ticketing tool all been in place?" | Three or more years with all three running | Under three years of overlap | One of the three replaced without its history |
| 2. Shared employee key | "Does the HR employee ID appear in the identity profile and on access tickets?" | On all three, mapped from the HR feed | On two of the three | Matching only by name or email |
| 3. Event timing | "Is a job change recorded with its effective date, and how soon does the identity platform see it?" | Effective date kept; identity change within a day or two | Effective date kept; changes wait for a batch or are keyed late | Job changes overwrite the old record |
| 4. Old access removal | "When someone moves, how is access the old role no longer needs taken away?" | Group rules plus a step for direct assignments | Group rules only; direct assignments left | No defined step for movers |
| 5. Removal evidence | "Where is a removal recorded, and how long is that record kept?" | Removal logged and kept beyond the platform default | Logged, kept only for the platform default | Not recorded, or record aged out |
| 6. Transfer review | "Does anyone confirm what a mover still needs, and is that review recorded?" | Recorded review for transfers, with outcome | Periodic access review that also catches movers | No review |

Check 2 decides whether the systems join without guesswork. If the identity profile carries the employee ID from the HR feed, each access change lines up with its HR event. If matching is by name, it works for most people and fails for exactly the ones who changed names, roles or both. The companion page on [linking HR, identity and ticket records](/guides/role-change-to-access-record-linkage) goes through those keys step by step.

Check 3 matters because the gap a buyer would learn from is measured in days. A job change keyed weeks after the person moved makes the mismatch look shorter than it was.

## Why checks 4 and 5 carry the score

They test the mover's removal step, which is often where companies are weakest. Okta's documentation says group rules can move a user from one group to another automatically when a profile attribute such as department changes. Access granted through a group follows the person. Access assigned to the individual directly does not, and neither does anything outside the identity layer. Okta's Workday provisioning page gives a concrete case of the same pattern: moving a worker to a different provisioning group changes Okta group membership, but the Active Directory organizational unit stays the same, because Okta sets it only when the user is created.

Check 5 then asks whether any of that left a record. Okta keeps System Log events for 90 days; older events exist only if the company exported the log or streamed it to a SIEM. A company that removes direct assignments diligently but keeps no record beyond 90 days scores pass on check 4 and partial on check 5, and that split is worth stating plainly.

Check 6 is the one auditors look for. NIST SP 800-53 control PS-5 asks organizations to review and confirm ongoing operational need for access when individuals are reassigned or transferred, and to modify authorizations to match. Whether the company's records show that review happening, or not happening, is part of the history either way.

## Illustrative: a 340-person distributor scores 7 of 12

Illustrative. A fictional 340-person industrial parts distributor answered the checks in one call with its identity administrator and a short follow-up with HR operations.

| Check | Mark | Points | What they said |
|---|---|---|---|
| 1. Coverage overlap | Pass | 2 | HR system since 2019, identity platform since 2020, ticketing since 2018 |
| 2. Shared employee key | Pass | 2 | Employee ID mapped into the identity profile and the ticket requester field |
| 3. Event timing | Partial | 1 | Effective dates kept; transfers often keyed a week or more late |
| 4. Old access removal | Fail | 0 | Group rules for departments; no step for direct assignments |
| 5. Removal evidence | Partial | 1 | Group removals logged; identity log kept for the default period only |
| 6. Transfer review | Partial | 1 | Twice-yearly access review, recorded in a spreadsheet |
| Total | 7 of 12 | 7 | Moves are traceable; removals for movers are not |

In one sentence for the sponsor: the company can show when each person moved and what they were granted, but not what the old role kept or when it went, beyond the last 90 days. That is a fair, useful description. About 60 transfers a year, the figure they gave, belongs in the notes as well.

The same metadata-only discipline applies to other systems; the [metadata-only Salesforce inventory template](/resources/a-metadata-only-salesforce-inventory-template-for-company-introductions) shows it for CRM records, and [audit logging for MCP connectors](/resources/mcp/mcp-audit-logging) covers a newer kind of access record.

## Who answers each check, and what the score leaves open

The identity administrator answers checks 2, 4 and 5. HR operations answers check 3. Check 1 and check 6 usually need the IT or security lead. None of them can authorize a licensing discussion: identity records touch HR, security and IT, so the CIO or CISO may sponsor the introduction, but the CEO (in an owner-run company, usually the owner) is the one who can authorize it.

Confirm the baseline before introducing: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license, 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. Sign the Channel Partner Agreement before submitting.

The score does not say whether the rights cover these records, whether employee data can be de-identified to a buyer's standard, whether any buyer wants them, or what they would be worth. Those stay unknown until SourceX reviews the company under its own agreement. If SourceX later asks a follow-up question, [how to understand a request for more information](/guides/how-to-understand-a-request-for-more-information) explains what it usually means. Naming Okta, Workday and ServiceNow describes where these records commonly sit, not a SourceX connector. More record locations are listed under [systems](/systems).

## 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 a company you advise has scored all six checks, fails included, and an executive who speaks for HR, identity and IT will take the call, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you submit.

## Sources

- https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf
- https://help.okta.com/en-us/content/topics/users-groups-profiles/usgp-about-group-rules.htm
- https://help.okta.com/en-us/content/topics/provisioning/workday/workday-provisioning.htm
- https://support.okta.com/help/s/article/Exporting-Okta-Log-Data?language=en_US
- https://refer.sourcex.si/terms
