How assessment works

Requirements come first

An assessment is only ever run against an explicit requirement set. YoHe can propose requirements from a pasted job description, but the proposal is a draft: nothing is assessed until a person has reviewed and saved the set.

Each requirement carries a weight and a short description of what evidence would satisfy it. Requirements are versioned, and each assessment records the version it ran against.

What a finding contains

• The requirement it answers.
• A verdict: evidenced, or not evidenced.
• For an evidenced finding, the supporting passage with its source document and location.
• For an unevidenced finding, a suggested question that would resolve it.

There is deliberately no third verdict. A requirement is either supported by something in the documents or it is not; a partial-credit band would reintroduce exactly the unarguable middle ground that scores create.

Banding, not ranking

Applicants are grouped by how much of the requirement set has evidence behind it. Bands tell you where to start reading. They are not a ranking, and the system does not produce a single ordered list of candidates from best to worst.

Overrides

Any finding can be overridden by a person. The original finding is retained alongside the override, with the author and timestamp, so the record shows both what the model concluded and what the team decided.