The Report That Shows Its Work

A hiring report is read by someone deciding whether to spend an hour of their week on an interview. If the first thing they see is three paragraphs of methodology, the report has already used up the attention it needed for the second thing.

What changed

The report now opens with a score and a skills breakdown instead of a page of caveats. Every skill links straight into the recording of the moment it was demonstrated, so a reviewer is never taking a number on faith. Explanatory text that used to sit on the page moved into a hover instead, there when you want it and out of the way when you do not.

The candidates table that lists everyone who has taken an assessment got the same treatment: it is now dense enough to scan the way a real hiring pipeline needs to be scanned, status, score, AI workflow, and a recommendation, all visible at once instead of spread across a wider, sparser layout. A separate "Integrity" tab, which used to sit apart from everything else on the report, was folded into the same evidence view instead, itemized per question rather than summarized as one number for the whole session.

We also found, and fixed, a real inconsistency: the same score could read one label in one part of the report and a different label two cards down, because the different cards on a report had quietly grown their own separate scales over time, one card using a five-way split, another using a three-way split, neither matching the scale the report's own headline number used. Now there is one scale, used everywhere on the page: Weak, Promising, Solid, or Strong. The same number means the same word no matter which card you are reading, which matters more than it sounds like it should, because a recruiter comparing two cards on the same page has no reason to expect the scale under them to be different.

Why it matters

A recruiter without a technical background is trusting the report to do the judgment work for them. A report that contradicts itself, even in a small way, is a report that has to be double-checked, which defeats the purpose of writing one in the first place. Consistency is not polish here. It is the thing that makes the report usable by someone who cannot independently verify it against the raw session.

The same logic applies to quoting a candidate's own weakest prompts directly under their communication score, instead of only showing the number. A score alone asks a recruiter to trust an evaluation they cannot see the reasoning behind. Reading the actual prompt lets them form their own view of whether the number is fair, which is a different and stronger kind of trust than being asked to accept it.

That instinct, show the specific moment rather than only the summary of it, is the same one behind linking every skill straight into its place in the recording. A summary can always be argued with in the abstract. A specific recorded moment mostly speaks for itself, and a recruiter who disagrees with a score after watching the moment behind it is disagreeing with something concrete rather than with an opaque number.

Where it points

The report's next job is making the connection between a skill score and the specific behavior behind it even shorter to find, fewer clicks between "here is the number" and "here is exactly why," and extending the same evidence-first instinct to the parts of the report that still lean on summary text instead of a direct pointer into the recording.