Job Requisition Approval Workflow

What happens if HR rejects the requisition?

The workflow routes the requisition back to the manager with the specific reason for the return, so there's no ambiguity about what needs fixing. The status updates to reflect the return, and the manager can revise and resubmit through the same workflow instance. Nothing gets lost in email threads — the history stays attached to the requisition record.

Can this handle a rejection at the budget/management approval stage too?

Yes. If budget or management approval declines the requisition, the workflow captures the rejection reason and notifies the manager directly. The manager can then revise details — like headcount justification or salary band — and restart the approval cycle without creating a duplicate record.

What if we need more than one approver at the budget stage?

You can customise the approval step inside assess.one to add multiple approvers, sequential sign-off, or parallel review depending on your governance needs. Roles and notification recipients are configurable directly in the platform, so you're not locked into a single-approver structure.

Who needs access to this workflow?

Typically hiring managers, HR reviewers, budget/management approvers, and recruitment need access, each scoped to their step in the process. You control permissions and visibility per role inside assess.one, so managers only see their own requisitions and approvers only see items awaiting their decision.

How long does it take to get this workflow live?

Minutes. Since this is a ready-to-use template, you publish it and your team can start submitting requisitions immediately — there's no implementation project or software install required. You can adjust steps, statuses, or notification rules before or after go-live without downtime.

Can we customise the statuses or add extra steps, like a legal review?

Yes, every step, status label, and approval rule is editable inside assess.one. You can insert an additional review stage — legal, finance, or diversity compliance, for example — anywhere in the sequence without rebuilding the workflow from scratch.

What happens if a manager submits a replacement role instead of a new headcount?

The same requisition record and workflow path handle both new and replacement roles — the initial capture step includes a field to distinguish them. HR review and approval logic can be configured to apply different rules or fast-track replacement roles if your policy allows it.

How do approvers and managers get notified at each stage?

Notifications are configured inside assess.one and fire automatically at each key decision point — submission, HR return, approval, and rejection. You can set these to email, Slack, or in-platform alerts depending on how your teams work, with no third-party integration setup needed.

What if recruitment needs to send the requisition back for clarification after approval?

While the standard flow moves approved requisitions straight to recruitment, you can add a return path from the recruitment handoff step back to the manager or HR for clarification. This is configured directly in the workflow builder as an additional routing rule.

Is there an audit trail for compliance or budget reporting?

Yes, every status change, approval, rejection reason, and notification is logged against the requisition record automatically. This gives HR and finance a complete, timestamped history for compliance reviews or headcount budget audits without manual tracking.