Sample report
The complete report, published.
Every section a paying customer receives, from a tenant built for the purpose. No form, no email address, nothing redacted. Thirty pages, typeset as a document rather than a printed web page. Look for the grey evidence rows under each finding.
Kirkwell Industries Ltd is not a real company. The tenant, the staff and the findings are invented, and deliberately mid-range rather than a disaster — because that is what most real ones look like.
What the document contains
In the order it arrives in.
The score, and what it means
One number out of 100 with the band it falls in, then six area scores — identity, email, data, licensing, workplace and Copilot — so a low score names the area that owns the problem rather than passing one verdict on everything.
Severity as a schedule
Critical, high and everything else, each with a timeframe against it: this week, this month, this quarter. A count on its own is inert. A count with a date is something that goes in a diary.
Evidence tables
Every domain against SPF, DKIM and DMARC. Every third-party application and what it can reach. Who can complete a multi-factor prompt. The narrative explains; the tables are what somebody works through.
A Copilot verdict
Ready, or not yet, with the blockers named. The sample says not yet and lists what would have to change first — considerably cheaper to establish before the licences are bought than after.
Every finding, in full
Grouped by area and ordered by severity within each, so the document can be worked through one area at a time or forwarded to whoever owns that area.
What was not scanned
How many sites were examined out of how many exist, and which checks did not run. Anything unassessed is excluded from the score rather than counted as a pass — a report that omits what it could not see is the one to distrust.
The same document, about your tenant
What you have just read is what arrives, with your own findings in it. Reports are delivered within three working days of access being approved.