Quarve

System / Quarve ATS

In production

Selection infrastructure for complex hiring operations.

Quarve ATS puts requisitions, evaluation pathways, permissions, evidence, approvals and decisions in one controlled system - so hiring runs as an operation, not a stack of spreadsheets and inboxes.

01 / The lifecycle

One requisition, start to finish.

Every stage of selection lives in the same system, with explicit state, ownership and history at each step.

  1. 01

    Requisition

    A role is defined, owned and approved

  2. 02

    Distribution

    The role reaches candidates through controlled channels

  3. 03

    Application

    Candidates enter the system with a complete record

  4. 04

    Evaluation

    Structured assessment against defined criteria

  5. 05

    Interview

    Scheduled, recorded and attributed

  6. 06

    Decision

    Made with evidence, by the right people

  7. 07

    Offer

    Approved, issued and tracked to acceptance

  8. 08

    Deployment

    The hire hands off cleanly into the organization

ats.quarve.app
Quarve ATS: the jobs list showing requisitions in draft, published, paused and closed states, each with department, location and openings
Product capture / 01 - Every requisition carries explicit stateIllustrative workspace data

02 / Inside the system

How Quarve ATS behaves.

Recorded and captured directly from the working product. The workspace shown is illustrative; the system is not.

ats.quarve.app
Screen recording / 01 - From requisition to pipeline to audit trailIllustrative workspace data
ats.quarve.app
Quarve ATS: the pipeline board of a requisition, with candidates arranged across Screening, Shortlisted and Interview stages
Product capture / 02 - The pipeline, stage by stageIllustrative workspace data
ats.quarve.app
Quarve ATS: a candidate record with stage, ownership, source, files and recent activity consolidated in one place
Product capture / 03 - One candidate, one recordIllustrative workspace data

03 / Capabilities

Structure the process. Preserve the judgment.

01

Requisition governance

Every requisition carries an explicit state - draft, open, on hold, closed - with defined ownership and controlled transitions. Roles are created, duplicated and retired through the system, not around it.

02

Evaluation architecture

Evaluation pathways are configured per role: stages, criteria and who evaluates at each point. Assessments are structured and attributed, so a decision can be traced to its evidence.

03

Evidence & candidate record

Applications, documents, evaluations and history consolidate into one candidate record. The system holds the evidence; people exercise the judgment.

04

Permissions & roles

Role-based permissions scope every action - who can view a pipeline, move a candidate, approve a requisition or issue an offer - within each organization's own structure.

05

Candidate communication

Candidates hear from your organization, not from a vendor: branded, templated communication managed inside the system, with custom templates and server-side preview.

06

Distribution & sourcing

Open roles are distributed to candidate channels from within the system, keeping publication, applications and pipeline state connected.

Permissions, audit history, data policy and accountability are native to the system.

Read the security architecture →

04 / Change log

The system ships continuously. Recent changes:

August 2026

Candidate communication rework

Branded candidate email shell, custom templates and server-side preview - candidates hear from your organization, not a vendor.

August 2026

Draft requisition lifecycle

Recoverable deletion and duplication for draft roles, with permissions to match.

September 2026

Requisition filtering

Multi-status filters across the jobs list and the API that backs it.

Next step

Examine Quarve.

A walkthrough covers the system itself: workflows, permissions, evidence, governance and how Quarve ATS is deployed in your organization.

Request a system walkthrough