IMPLEMENTATION GUIDE

From agreement
to accepted workflow.

A controlled Valases rollout aligns region, privacy, users, roles, assessment design, evidence rules, and operational ownership before candidate activity begins.

01
PHASE ONE

Discovery and control decisions

Confirm the customer's legal entity, operating region, primary administrators, hiring volume, job families, retention requirements, candidate notice, accessibility process, and first integration priority.

OUTPUTS FROM THIS PHASE

  • Approved region and assignment source
  • Named implementation owners
  • Data and retention requirements
  • Pilot scope and success criteria
⊙
Region selection

Confirm legal entity, data residency, and regional cloud assignment before provisioning begins.

◈
Ownership mapping

Identify named administrators, privacy owners, and implementation sign-off authority.

◻
Pilot scoping

Define the job families, candidate volume, and acceptance criteria for the pilot phase.

02
PHASE TWO

Organization provisioning

Create the organization, owner, initial administrators, plan metadata, and regional assignment. Validate access through the intended production domain before inviting wider teams.

Organization created

Legal entity, subdomain, and regional assignment confirmed and recorded.

Owner and admins provisioned

Named owner account and initial administrator seats activated with role-appropriate permissions.

Domain access validated

All initial users confirm access via the production domain before broader invitation.

SSO and provisioning scope

Identity provider integration confirmed and attribute mapping validated before wider rollout.

03
PHASE THREE

Hiring workflow design

Define role templates, required evidence, pipeline stages, transition authority, interviewer responsibilities, decision reasons, compliance checks, and offer release permissions.

WORKFLOW DECISIONS

  • Role templates and pipeline stages
  • Evidence requirements per stage
  • Transition and decision authority
  • Offer release and approval gates
  • Compliance check configuration
  • Interviewer responsibility mapping
▦
Stage design

Map each pipeline stage to required actions, responsible parties, and transition criteria.

◎
Decision controls

Configure who can move, hold, or reject a candidate at each stage and what evidence is required.

⊞
Offer workflow

Set approval chains, offer generation rules, and communication triggers before go-live.

04
PHASE FOUR

Assessment design and validation

Select the work environment, duration, timing mode, proctoring expectations, scoring keys or checkpoints, reviewer rules, and candidate instructions. Preview the complete journey before publishing.

◑
Environment selection

Choose the work format: coding, spreadsheet, accounting, tax, MCQ, or case. Each requires a specific delivery environment.

◷
Timing and proctoring

Set duration, timing mode, consent-led proctoring controls, and candidate communication expectations.

◈
Scoring and review

Define scoring keys or qualitative checkpoints, reviewer assignment rules, and AI-assist thresholds.

◻
Preview and sign-off

Run through the full candidate journey end-to-end before publishing to live roles.

05
PHASE FIVE

Customer acceptance

Named administrators run an end-to-end test covering role creation, candidate delivery, consent, assessment recovery, reviewer evidence, interview scorecards, decision controls, offer preparation, permissions, and support escalation.

ACCEPTANCE CHECKLIST

  • Role creation and pipeline staging
  • Candidate invitation and consent flow
  • Assessment delivery and recovery
  • Reviewer evidence and scoring
  • Interview scorecards and notes
  • Decision controls and audit trail
  • Offer preparation and approvals
  • Support escalation path tested
06
PHASE SIX

Controlled launch

Begin with the approved pilot roles and monitor delivery failures, latency, candidate support, reviewer consistency, proctoring false positives, and workflow exceptions before expanding volume.

Pilot roles live

Activate only the agreed pilot job families and candidate volume at launch.

Monitoring window

Track delivery failures, assessment latency, reviewer response times, and support volume for an agreed period.

Volume expansion

Expand to additional roles and regions only after pilot metrics meet acceptance criteria.

Self-service onboarding can be added later without weakening these controls. The product should automate the same decisions — not bypass them.

Ready to plan
your rollout?

Book a 30-minute briefing and we'll scope the implementation against your region, governance requirements, and rollout priorities.

Book a briefing ↗