Recruit brings your hiring rules into one page: stage rules, reply-time targets, approval steps, automation settings, candidate messages, and audit notes. This version shows fixed sample data, so leaders can review how the controls work before going live.
No live data. Fixed sample states only — no tenant or customer information.
Product screenshot
Captured Jun 16, 2026
Source: React SPA seeded workflow capture
Define visible hiring stages, allowed transitions, required exit criteria, and who can move a candidate forward or back.
Set review windows for screening, interview feedback, approvals, and offer turnaround before delays become hidden.
Route sensitive changes such as offer terms, bypasses, senior-role moves, and final decisions through the right approvers.
Switch reminders, assessment sends, feedback nudges, and candidate status messages on or off by stage.
Make candidate communication checkpoints explicit so teams know when templates, reminders, and status updates fire.
Surface audit notes, override requirements, owner roles, and evidence coverage beside each control.
Hiring leaders need to know whether their process is set up correctly before the first requisition goes live. This read-only control list shows what Recruit already has: what is configurable, what is currently on, and where the audit trail exists.
Replaces vague workflow claims with a concrete control list leaders can inspect.
Notify interviewer and recruiter when feedback is pending after 24 hours.
Require TA Head and Practice Head sign-off before release.
Hold for recruiter review when candidate reached interview stage.
Capture reason, owner, timestamp, and affected stage for every bypass.
Each control group has a clear state, owner expectation, and governance note. This version shows fixed sample data. A later version will connect to real saved settings in the admin screen.
Keep hiring stages understandable while preserving strict movement rules.
Make time pressure visible before it turns into a lost candidate.
Protect sensitive decisions without slowing every ordinary move.
Turn automation on where it saves effort, hold it where humans need to review.
Show when the candidate hears from the team and which message path is used.
Expose what will be traceable when leaders ask why a decision changed.
Each control shows a role matrix alongside a preview of what changes before you save. Leaders can tell which roles configure policy, which teams approve exceptions, who executes the day-to-day workflow, and what the audit trail will look like after the change.
Changing a toggle or reminder threshold shows you a preview of what changes before you save the setting.
The list reads like a leader checklist. Each stage shows what rules apply, SLA coverage, approval requirements, automation behaviour, candidate messages, and what gets tracked.
Workflow Controls v1 is deliberately simple: it is public, static, and contains no live data. It gives teams a clear picture of what the controls look like today, and leaves a straightforward path to connect each row to existing settings, feature flags, notification preferences, and approval workflow services in a later version.
The page shows control categories and sample states only. It does not query live jobs, candidates, users, or any private workflow configuration.
Stage policy, approvals, feature flags, notification preferences, and audit logs already exist in the product. This page organises them in one readable list.
Each rule is written in language a TA leader or IT partner can read and verify, not internal technical terms.
Bypass and approval language is explicit: owner, reason, timestamp, and affected workflow stage should be visible when a decision is reviewed.
Bring stage policy, SLAs, approvals, automations, candidate checkpoints, and what gets tracked into one page leaders can read without needing to open the technical settings underneath.