Back to platform
Recruitment automation

Rules that route and notify — with people in the loop.

Hiring Policy is an event-driven rule engine for recruiters. Define if-this-then-that rules that act on candidates automatically as assessment milestones occur — routing them forward and sending notifications — while the decisions that affect a candidate stay strictly with a person.

Rule Engine Structure

Anatomy of a rule

A hiring-policy rule is a small, readable piece of automation. You decide what it applies to, what starts it, what must be true, and what it does — in that exact order.

Stage 01

Scope

Which jobs, pipelines, or candidate pools the rule applies to. Avoid global side-effects by targeting precise requisitions.

eg. role == "Senior ML"
Stage 02

Trigger

The event that initiates rule evaluation — such as a completed assessment, verified identity telemetry, or submission deadline.

eg. event.graded_at != null
Stage 03

Conditions

The empirical checks that must hold before execution. Combines normalized score percentiles, skill matches, and test validity metrics.

eg. score >= 78 && integrity == 100
Stage 04

Actions

What happens next, run sequentially in the prioritized chain you designate — routing, reviewer queues, and templated emails.

eg. dispatch(stage_2, notify_lead)

Action Capabilities

What a rule can do today

Three primary actions are live today — funnel routing and automated communications. Each runs automatically the millisecond a rule matches, in the explicit priority order you set.

Route to an assessment

Automatically send the candidate the next assessment in your evaluation funnel the moment the trigger fires. No waiting for manual recruiter queue sweeps.

Route to a reviewer

Assign the candidate directly to a specific team member, domain peer, or rotating hiring committee panel so the right expert picks up the deep qualitative review immediately.

Send an automated email

Dispatch a templated, branded message to the candidate or internal hiring team — a status nudge, next-step preparation guide, schedule request, or transparent progress confirmation.

Ethical & Safe Architecture

Built for human oversight over automated decisions

Automation is only safe if consequential outcomes stay firmly with a person. Hiring Policy is architected from the bare metal around that conviction — routing and notifications execute smoothly on their own, but any decision affecting a candidate’s status is permanently held for an affirmative human judgment.

Consequential actions are held

Candidate-affecting actions (rejection, hiring offer, salary qualification) are physically suppressed in code until a recruiter or hiring manager records a rationale. They can never auto-execute.

Fully logged execution trace

Every rule trigger match, condition outcome, and dispatched webhook is serialized to an append-only ledger. When compliance officers inspect outcomes, every step is mathematically reviewable.

Hardened for absolute reliability

Actions are strictly idempotent and claimed atomically in transaction before runtime execution. Network retries, timeout recoveries, or concurrency spikes cannot trigger a duplicate action.

Firm Ethical Boundary

Where we draw the line

We are unapologetically deliberate about what software should and should never do. Hiring Policy routes and notifies — it never decides who gets hired or rejected.

System Design Rule: Any action classified as “Adverse Impact Potential” immediately enters a hard hold state requiring dual cryptographic token authorization.

Explicitly Prohibited Capabilities (Engine Level)

Auto-hire, auto-reject, or auto-eliminate candidates

No algorithm or threshold is ever permitted to terminate a candidacy without affirmative human confirmation.

Silently mutate a candidate’s lifecycle status

Status changes require signed actor attribution in the applicant tracking audit log.

One-click bulk discard of held actions

We deliberately prevent high-volume “blind rubber-stamping” that circumvents human evaluation.

Escalation or penalty SLA timers on pending evaluations

Candidates are never timed out or dropped due to reviewer scheduling backlogs.

What it does do:

Run the routine, repetitive routing, invitations, and messaging instantly. Keep a human reviewer on every consequential fork, and log the entire chain immutably.

Assessments provide the signal — Hiring Policy acts, carefully.

// Onboarding first teams

Automate the busywork. Keep the judgment.

Bring a hiring funnel, and we will demonstrate how Hiring Policy eliminates days of candidate latency while safeguarding fairness and institutional review where it matters most.