Write the decision sentence
“Our board needs to know whether former contractors can still reach client files before the next supplier review” gives an assessor more direction than “check our security.” Bring the deadline and the person who will act on the answer. If the objective is broad assurance, name the business processes that cannot be interrupted.
Sketch the estate
List the production tenant, recently acquired tenants and any directory synchronisation. Identify who operates identity, mail, collaboration and devices. Where an MSP controls settings, name the relationship owner who can arrange evidence. A rough map with honest unknowns is more useful than a polished but incomplete diagram.

Summarise licence coverage
A subscription invoice does not show who benefits from a particular control. Bring a summary of licence families, populations and exceptions. Ask the assessor to distinguish missing entitlement from incomplete deployment; those situations lead to different investments.

Choose examples safely
Describe one sensitive workflow, such as a supplier sharing a contract with finance. Explain who should have access and when it should expire. For initial scoping, a fictional document name and role descriptions are enough. Leave real files, recipient lists and screenshots for a secure evidence channel.

Agree access options
Ask the provider to propose the minimum collection method for each workload. If you cannot grant a role, discuss a supervised session or a customer-run export. Record the limitations rather than assuming a restricted view proves a control is absent.

Plan around change
Tell the assessor about migrations, policy pilots and planned administrator changes. Pick a collection time and agree which high-impact changes require a fresh sample. Otherwise the final report may accurately describe a configuration that was retired halfway through fieldwork.

Leave with a written boundary
After the call, expect a short list of included workloads, excluded actions, required evidence and decisions you still owe. Give every unresolved dependency an owner. A proposal can then explain what will be tested without relying on a vague promise to review everything.

A brief you can send without exposing the tenant
Imagine a finance director who wants confidence in payment approvals before year end. The first useful document is a short summary of the process and who operates it. There is no need to send a password, an unredacted mailbox export or a list of privileged users. The assessor can identify secure collection requirements after the boundary is agreed.
| Brief field | Illustrative answer | Question to resolve |
|---|---|---|
| Business process | Supplier payment changes by email | Who approves changes out of band? |
| Operating model | Internal IT plus an outsourced service desk | Who administers identity policy? |
| Expected output | Leadership summary and prioritised engineering work | Who accepts the report and when? |
Published by Atlant Security. Sources, editorial policy and corrections.

