# Access review remediation referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/customer-access-review-remediation-referral-brief-template
Last updated: 2026-11-04

A company introduction about customer access review remediation is a one-page brief that the security operations head can correct and forward to the CEO unchanged. It describes the records without containing any: who the company is, what the reviews cover, which tools hold decisions, findings and tickets, how many cycles they span, rough counts, any dated deadline, the single open question, and who can authorize a licensing discussion. Exports, screenshots, account names and customer names stay out. Copy the blank form below, then check your draft against the completed Illustrative brief.

This template is part of the [customer access review remediation guide](/guides/workflow-customer-access-review-remediation). Fill it in after one conversation with whoever runs the reviews, and write only what someone at the company will stand behind.

## The blank brief: nine fields

Paste the first two columns into a message and answer every field in a line or two. Writing "unknown" beats guessing.

| Field | What to write | Usually answered by |
|---|---|---|
| Company | Sector, country, full-time headcount at peak | CFO or HR lead |
| Review task | Who and what gets certified, how often, since which year | Security operations head |
| Record classes | Certification decisions with reasons, findings with owner responses, removal tickets, staff departure dates | Security operations head |
| Systems | Governance module, compliance tracker, ticketing, log store, HR system | Identity administrator |
| Coverage | Cycles held per tool, and any stretch where a record class was not kept | Identity administrator |
| Volume | Findings per cycle, removals per year, service accounts in scope, each with its source | Compliance lead |
| Access event | A dated event only: consolidation, license end, admin cut-off | Program lead or procurement |
| Open question | The one thing nobody yet knows about completeness or rights | Security operations head |
| Sponsor and signer | Day-to-day owner; the CEO, who can approve a licensing discussion | Security operations head, then the CEO |

Use the company's own words. When the identity administrator says "we only kept campaign reports from the second year", the brief repeats that sentence.

## Answering each field from menus and counts

Nobody should open a certification decision to complete this form. Settings screens, report menus and dashboard counts are enough.

- **Certification reasons.** Ask whether reviewers were required to give a reason, and whether each cycle's campaign report was saved. Okta Identity Governance, for instance, has a Past Campaign Details report that carries the reviewer's justification beside each decision, with separate level 1 and level 2 fields where a campaign has two levels of review. "Reports saved every cycle since 2022" is a strong line; "the tool can produce reports" is not.
- **Saved history.** Microsoft Entra review history reports can be fetched for only 30 days after each is generated, so the brief should say whether past reports were actually kept, and where.
- **Proof of removal.** Write the earliest date from which sign-in and change events are held in a separate log store, if anyone knows it. The parent guide explains why that date matters; the brief needs only the date itself.
- **Findings and tickets.** One yes or no: do findings quote ticket keys? It tells a reviewer at once whether the remediation trail joins up. The [records across systems map](/guides/customer-access-review-remediation-records-across-systems) explains each join.
- **Counts as ranges.** "Roughly 30 to 60 items a quarter, from the compliance dashboard" is honest and sufficient.

## Completed brief (Illustrative)

A fictional company, invented for this page. The figures are placeholders, not anyone's real data, and this is not a completed deal.

| Field | Illustrative entry |
|---|---|
| Company | U.S. B2B payments SaaS provider, about 260 full-time staff at peak |
| Review task | Quarterly review of employee and service-account access to customer tenants, with tracked remediation since 2021 |
| Record classes | Certification decisions with reasons, tracked items with owner responses, a change ticket per removal, audit events, HR departure dates |
| Systems | Single sign-on platform with governance module, compliance tracker, ticketing, log store, HR system |
| Coverage | About 20 review cycles; tracked items in one tool throughout; audit events kept in the log store since 2023 only |
| Volume | 30 to 60 items a cycle; about 400 service accounts in scope, from the compliance dashboard |
| Access event | Admin cut-off for the acquired company's identity tool, dated in the integration plan |
| Open question | Service-account exceptions, such as a departed approver still owning an account, are well documented, but some findings name customers |
| Sponsor and signer | Security operations head sponsors; the CEO decides |

That is enough for a first review. It shows the company likely meets the size threshold, where each record class lives, which years the independent evidence covers, the real deadline and who signs.

## Writing the open question: the departed approver

The open question is the most useful line in the brief, because it tells SourceX where the rights review starts. In access review remediation, the strongest cases are often the awkward ones: an approver leaves the company, a service account they owned keeps its access to customer tenants, the next review flags it, ownership is reassigned and the access is cut back. A company that can follow that chain, from the HR departure date to the tracked item, the ticket and the audit event, holds a complete decision record.

Write the question as a fact plus an uncertainty, in one sentence. Good: "Departed-owner exceptions are tracked as findings with tickets, but findings sometimes name customers." Weak: "We have great exception data." The first lets a reviewer plan de-identification and contract checks; the second says nothing. Do not add an example finding to prove the point.

## What stays out of the brief, and who receives it

Leave out exports, screenshots, account names, customer names, log lines and anything copied from the systems. If the company had a security incident in the review period, say only that counsel should be involved; the page on [whether a company with a data breach can license data](/questions/can-a-company-with-a-data-breach-license-data) covers that situation. Auditor workpapers are not the company's records, so they stay out too; the [management letter remediation page](/data-types/management-letter-comments-remediation) explains the difference.

Send the draft to the security operations head first and ask them to correct it. They then forward it to the CEO with a covering note; the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner) has wording for that note, and the [client opportunity brief generator](/tools/client-opportunity-brief-generator) produces a similar summary for other workflows. The [who-can-license answer](/questions/who-can-license-customer-access-review-remediation-records) explains the roles in more detail.

The introduced company needs 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. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Buyer interest, the rights result, de-identification needs and any offer stay unknown until SourceX reviews the opportunity with the company.

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

Once the security operations head has corrected the brief and the CEO, who can approve it, expects it, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you send it.

## Sources

- https://refer.sourcex.si/terms
- https://help.okta.com/en-us/content/topics/identity-governance/columns-campaign-details.htm
- https://learn.microsoft.com/en-us/entra/id-governance/access-reviews-downloadable-review-history
