Sample report. Every name and number is invented.
Report
What each seat holder caught and missed on the assessments you set, by CWE and by language, with the settings each assessment ran under. Personal training never appears here.
- Organisation
- Fernbrook Systems
- Period
- Q1 20251 Jan 2025 to 31 Mar 2025 inclusive
- Produced
- 31 Aug 2026, 09:14 UTCPeriod boundaries are cut in UTC.
- Named detail
- Open. This document names people.
No assessed work in this period
Set an assessment for your seat holders and their graded results appear here, along with the export you hand an auditor. Nobody's own training is counted.
Nobody sat an assessment in this period, so there is nothing to set against a model. Choose a period with assessed work in it.
Nobody sat an assessment in this period, so there are no results to show with names off. The seat figures and the export are on their own tabs.
Seat integrity
An auditor reads these figures together. If more people held a seat than were bought, a seat was passed between people, and the results above cover more people than there are seats.
- Seats purchased, as things stand today
- 50
- Assigned right now
- 48
- Distinct people who held a seat in this period
- 44
The first two figures are the position today. The last covers the period, so where seats were bought or given up part way through, the comparison is across two dates. A seat can move to someone else once a calendar month. The count of people who held a seat comes from the seat assignments and releases in your audit log, and it appears on the export.
Export
The PDF is the document you hand over. It is the whole report: the period it covers, how the exercises were built and marked, what each seat holder caught and missed, the settings each assessment ran under, the seat figures, and the clauses in PCI DSS, DORA, ISO 27001 and the EU AI Act that this record answers.
The CSV is the same figures as rows. It opens in a spreadsheet, so someone checking the report can add the numbers up themselves, and it is the copy to keep if you want to compare this period with the next one.
Both cover the period selected above. Each of the other tabs also exports its own table on its own.
Both are produced here for real, by the same code that produces a customer's, over the invented rows on this page. Every page of the PDF is watermarked, the file names say sample, and the document says inside itself that it is not evidence. The four per-section spreadsheets on the other tabs are not produced here, because each one is recorded against an organisation and there is none behind this page.
What this record does not establish
What this record establishes: that the account named against each result was signed in, submitted those findings in the window shown, and was marked on our server against a prepared answer the browser never receives. The exercise is never published, so it cannot be practised beforehand. Hints are off unless an administrator switched them on, which is stated on each row. No assessment shows a walkthrough or a video, whatever its switches say.
What it does not establish: who was at the keyboard. The sitting is not invigilated. Nothing here shows whether the named person worked alone, whether someone was helping, or whether the diff was pasted into another tool. We only see what the product offered and what was submitted to it.
Read a result as evidence of work done under this account, in this window, under the stated settings. Where a role needs more than that, run the sitting under your own supervision and record that alongside this document.
Who is in this document: everybody who was assigned an assessment in the period and held a seat when they sat it. That is not necessarily everybody who writes code here. This record cannot say how many engineers the organisation has or how the people assigned were chosen. An auditor who needs that should ask for it.
These paragraphs are in the exported document as well, so a reader who is handed the file reads the same thing.
Every export is recorded against this team, with the period it covers and who produced it. That record is in the audit log.