Home/Resources/Implementation Centre
Run an assessment project without losing the thread.
A practical operating guide for agency teams moving from client setup and role evidence to candidate invitations, comparable results, protected client review, and project closeout.
For recruitment agencies and staffing firms. Product boundary reviewed 27 August 2026.
- Set upAgency account and client record01
- PlanProject, role, and evidence scope02
- InviteSingle or CSV candidate batch03
- MonitorDelivery and completion states04
- ReviewComparison and interview focus05
- HandoffProtected client decision06
Check the operating conditions before the first invite.
A clean launch is mostly decided before the candidate receives an email. These 4 checks reduce rework without turning the project into a long implementation programme.
- Client & project
- The correct client record, project, role name, and project owner are clear.
- Evidence plan
- Every assessment answers a material role question; overlap has been removed.
- Candidate batch
- Names, email addresses, instructions, deadline, and support route are checked.
- Decision handoff
- The team knows what will be compared, verified in interview, and shared with the client.
The agency implementation sequence.
Complete the steps in order for a new project. Return to the relevant step when a delivery, access, evidence, or client-response exception appears.
- 01Business-email signup, Google OAuth, deferred password, and onboarding are available.
Create the agency account
Use a business email or Google sign-in, complete onboarding, and confirm the person who will own candidate and client follow-up.
- 02Real agency-owned client records and projects are available.
Create the client and project
Keep the client, role, candidate cohort, and recruiter responsibility together so the shortlist and analytics remain attributable to the right agency engagement.
- 03Role templates and assessment assignment are available. Use the selection guide.
Choose a focused assessment plan
Start from the role outcomes, select only material evidence, and use the same role-relevant process for candidates being compared.
- 04Single and CSV bulk invitations use a durable queue.
Prepare and send invitations
Invite one candidate or check the CSV batch before upload. Make the purpose, timing, candidate support route, and next step clear.
- 05Invitation delivery health and project funnel visibility are available.
Monitor delivery and completion
Separate sent and failed invitation states from invited, started, and completed candidate stages. Follow up on the operational condition you can see.
- 06Results, comparison, ranking, and interview questions are available.
Review comparable evidence
Read individual results before using comparison and ranking. Carry strengths, risks, trade-offs, and uncertainty into structured interview questions.
- 07Verified email plus a one-time code protects the expiring or revocable link.
Share the client-ready brief
Check the immutable PDF and protected review link, send it to the intended client email, and ask for interview, hold, or decline with context.
- 08Agency analytics populate from existing workflow records.
Close the project from actual activity
Review funnel movement, delivery health, shortlist views, response time, and client decisions. Record what the next project should improve.
Route the exception—do not turn it into a candidate judgment.
Operational status and assessment evidence answer different questions. Keep them separate.
| Visible condition | Check first | Next action | Do not infer |
|---|---|---|---|
| Invitation failed | Address and candidate record | Correct, resend, and record the owner | Candidate disengagement |
| Invited, not started | Delivery, timing, and instructions | Confirm receipt and the support route | Low motivation or capability |
| Started, not completed | Access, interruption, and support needs | Record material context before interpretation | A comparable completed result |
| Mixed evidence | The role outcome behind each signal | Ask one structured verification question | One score decides the shortlist |
| Client has not responded | Whether the protected brief was viewed | Request one explicit client decision | Silence means decline |
Finish with a client action, not a report attachment.
The current handoff keeps the shortlist brief protected and gives the client a narrow decision surface. The recruiter can see the resulting activity without pretending the link is a persistent client account.
- Server-generated immutable PDF.
- Opaque expiring or revocable review link.
- Verified client email plus one-time code.
- Evidence review, comment, interview, hold, or decline.
- Recruiter activity summary and agency analytics.
Use the product that exists—not the roadmap in disguise.
The implementation guide separates current operating controls from planned capabilities.
Account creation and onboarding, agency-owned client records, projects, role templates, assessment assignment, single and CSV bulk invitations, delivery health, funnel visibility, results and comparison, ranking, interview questions, immutable PDF output, protected client review, client responses, and agency analytics.
ATS/API/webhook or SMS integrations, persistent client accounts, per-client white-label branding, advanced team roles, SSO/SCIM, per-link permission scopes, automated hiring decisions, candidate passports or cross-client evidence reuse, full audit events, consent grants, and assessment-version lineage.
Take the operating sequence into the next client project.
The ungated checklist covers setup, assessment planning, invitations, exception handling, evidence review, protected handoff, closeout, and the current product boundary.
Implementation questions, answered plainly.
Use the platform-status page when you need the latest live-versus-planned boundary.
Review Platform StatusWhat should we set up before inviting candidates?
Create or select the client, create the project, define the role evidence needs, choose a focused assessment plan, check candidate records, and confirm instructions, deadline, and candidate support ownership.
Can we invite a candidate batch from a CSV?
Yes. The current product supports individual and CSV bulk invitations through a durable queue. Review sent and failed delivery states before treating non-completion as a candidate follow-up issue.
How does a client review the shortlist?
The recruiter shares an opaque expiring or revocable link. The intended client uses a verified email and one-time code, reviews evidence, comments, and records interview, hold, or decline. This is not a persistent client account.
Where should we look when candidates do not complete?
Separate the condition first: failed delivery, invited but not started, or started but not completed. Check address, delivery, timing, instructions, access, interruption, support, and material context before interpreting candidate evidence.
Does CandidatesAssessment integrate with an ATS today?
Not yet. ATS, API, webhook, automation, and SMS integrations remain planned. The current operating route for a candidate batch is CSV invitation.
Start one client project on a clearer operating path.
Create the agency account, define the role evidence plan, invite candidates, monitor progress, review the shortlist, and give the client one protected next-decision surface.