Human approval at consequential gates
HireFlow is opinionated about where humans stay in control: approval before sourcing, before outreach, and before final submission or closeout.
Kempian HireFlow
The governed workflow layer for every hiring handoff.
HireFlow keeps role creation, publishing, prioritisation, and human approval in one visible system so hiring teams can move faster without losing operational control.
app.kempian.ai/hireflow
HireFlow2 items awaiting approval
Job workflow and governance
Nothing candidate-facing ships without sign-off - audit trail retained per tenant
Release train
Approval queue
Gate 3 - Outreach package
Channel: verified SES domain Template v3 - legal footer on
Subject: Travel RNA - Austin (13 wk) - intro from Kempian
Body preview: personalized opener + JD bullets + single CTA to book screening...
Approver identity, timestamp, and payload hash are written to the activity log. EU AI Act Art. 14 human oversight applies before consequential outreach.
Lifecycle story
Every state, gate, and next action stays visible.
HireFlow is designed for teams that need to understand where a role is, which handoff is active, and what must happen before the workflow can legally or operationally move forward.
HireFlow lifecycle map
Select a stage to inspect ownership, gates, and audit logic.
Human gate
Agent handoff
Audit preserved
Shortlisted
Gate 2Recruiters review ranked candidates before outreach can start.
Gate 2 is where the shortlist becomes a governed decision. Recruiters can approve, hold, or reject candidates with visible reasoning and missing-signal awareness before any outbound step is unlocked.
Operator action is required to leave this stage.
HireFlow will not auto-progress this state until the responsible human owner records the approval that unlocks the next handoff.
Next valid transition
Current ownership
Recruiter
This is the accountable owner for the next valid movement out of the selected state.
Audit posture
Immutable transition context
Shortlist approval and rejection reasons stay visible alongside the candidate record and requisition state.
Why this matters
The stage model is not decorative. It is the operating contract that keeps requisitions reviewable, explainable, and safe to hand off across humans and agents.
Operational cockpit
The requisition view is where control becomes operational.
HireFlow does not just store role data. It turns the role into a governed operating object with queue priority, publishing readiness, channel visibility, and explicit handoff accountability.
app.kempian.ai/requisitions
HireFlow queue
Active requisitions
5 roles visible | sorted by governed priority
AllHigh priority
Senior Site Reliability Engineer
DEM-A1B2C3Acme Cloud | $210k-$255k | Remote | US | Apr 22
VMShigh priorityOpen
Director of Clinical Operations
DEM-D4E5F6Globex Healthcare | $180k-$220k | Boston, MA | Apr 21
Emailhigh priorityOpen
ICU Travel Nurse - 13 week
DEM-G7H8J9Initech Medical | Hourly | TBC | Phoenix, AZ | Apr 20
VMSmedium priorityOpen
Lead AI/ML Engineer - Pipelines
DEM-K0L1M2Hooli AI | $240k-$290k | San Francisco, CA | Apr 19
Manualhigh priorityFilled
Home Health Aide
DEM-N3P4Q5Stark Care Group | Hourly | TBC | Austin, TX | Apr 18
Manualmedium priorityIncomplete
Publish control
Select governed channels for REQ-1042.
Channels only activate when their connector and publish rules are configured.
Kempian Talent Hub
Internal talent pool
LinkedIn Jobs
Connector required
Indeed
Connector required
Glassdoor
Connector required
External publish remains blocked until connectors and approval rules are ready.
Governance architecture
Workflow governance is the product, not a side note.
HireFlow is built to make approval logic, ownership, and evidence visible enough for recruiters, operations leaders, compliance stakeholders, and procurement teams to inspect the same workflow with confidence.
Legible handoff ownership
Teams can see whether the next action belongs to demand capture, sourcing, outreach, scheduling, submission, or a recruiter, which keeps automation from becoming ambiguous.
Immutable transition records
Reviewer identity, timing, reason fields, and state changes stay attached to the same requisition trail for audit and operational review.
Advisory prioritisation boundaries
Urgency and queue signals can guide recruiters and ops teams, but they never bypass approval logic or override documented process controls.
Approval rail
The core gates are explicit by design.
Each gate has a different operational meaning, but they all share the same principle: a role does not advance into a higher-risk or more external action unless the responsible reviewer signs off.
Gate 1
Approve role
Budget, rationale, and completeness confirmed before sourcing starts.
Gate 2
Approve shortlist
Recruiter reviews AI-backed ranking before any candidate-facing action.
Gate 3
Approve outreach
Outbound sequences only run after recruiter confirmation.
Gate 4
Approve submission
Final submission, offer, or closeout action is reviewed before release.
Exception and handoff control
When the workflow hits uncertainty, HireFlow slows down on purpose.
Important hiring workflows need more than a happy-path automation story. HireFlow keeps blocked records visible, preserves who owns the next correction, and prevents downstream agents from acting on incomplete context.
Incomplete requisitions stay in view
Missing fields, unclear budget, or unresolved owner data keep the role visible in a controlled incomplete state instead of pushing bad data downstream.
Escalations have an explicit route
Blocked approvals, missing recruiter review, or policy exceptions surface as owned work, not silent system failures.
Handoffs pause when the workflow loses confidence
If evidence is missing or approval is absent, the next agent does not continue. The workflow waits for a human action and records why.
Platform fit
HireFlow works best as the connective layer across the platform.
Workflow governance becomes more valuable when it connects the AI system upstream and the post-hire operating stack downstream.
Live walkthrough
See HireFlow applied to your real job workflow.
We will walk through role intake, governed state transitions, publish controls, prioritisation boundaries, and human approval gates using the workflow patterns your team actually runs.