Candidates & Sessions
Candidates
A candidate is a person being evaluated. Candidates are identified by email and scoped to your organization. The same person can take multiple assessments, and each attempt creates a separate session. Candidates are not admin users - they don’t log into the admin portal. Instead, they receive a unique link that drops them directly into the assessment workspace.Sessions
A session represents one candidate’s attempt at one assessment. It tracks everything: when they started, what they configured, every message they exchanged with the AI, and the final deliverable they submitted.Session lifecycle
The
setup status is a legacy name for the Explore phase described below. It is a fixed, ungraded orientation window, not an admin-configurable step.The phase model
Every assessment runs on a fixed three-phase model. Gradient sets the shape; the admin only edits the Task phase.1
Explore (fixed 5 minutes, ungraded)
A short orientation window. The candidate gets oriented, reads the brief, browses the available data, and (where the assessment permits it) sets up their AI workspace by adding skills, memory, or their agents.md configuration. Nothing here is scored.
2
Task (admin-set time, graded)
The only admin-editable phase. The candidate works with the AI assistant to complete the task brief: chatting, running tool calls (like creating slides), searching connected data sources, and iterating on the deliverable. A countdown timer is visible, and this is the phase Gradient scores.
3
Reflection (optional, fixed 10 minutes)
When enabled, a short reflection on the work just completed. The prompt is locked and identical for every candidate, so reflections are comparable across candidates and assessments. Reflection Quality feeds the rubric.