When approval routing is enabled, Requidex evaluates the active rules in priority order. Every condition configured on a rule must match. The first matching rule selects its full approval route; if no rule matches, the default route is used.

​

From the Approval routes tab on the company Approval routing page, authorised hiring-side users can open the New route dialog to create a route, or edit, clone, activate, deactivate, and delete unused routes. The first route is activated and selected as the default automatically; routing remains paused until explicitly enabled. Cloning opens the New route dialog with the selected route's settings pre-filled so they can be reviewed before saving. For each stage, the route editor can use project approvers at a chosen minimum approval stage or automatically assign specific company users who have requisition approval permission. The route dialog also controls stage order, flexible approval, and the optional Tier 1 agency cap. Deactivating or deleting the default route clears the default and pauses routing until another active default is selected.

​

The Routing rules tab on the company Approval routing page shows every rule across all approval routes in evaluation order. Authorised hiring-side users can drag rules to reorder them, with priority 1 at the top. New rules are appended to the bottom. Creating or editing a rule opens a separate dialog where its approval route and conditions are selected; priority is controlled only by list order. A rule can apply to any trade, selected trades, or trades carrying selected tags; trade and tag targeting cannot be combined on the same rule. When the page detects an obvious overlap, it shows which earlier rule takes precedence.

Use Suppliers (Optional) to attach several specialist suppliers to one rule. Any matching supplier triggers the rule, including when other suppliers are selected. Point the rule to a three-stage route retaining the first three approver stages, and keep the standard four-stage route as the default. Other conditions and rule priority still apply.

​

Project costed or non-project costed is requested only when the first active rule that could match the selected trade uses that condition. Before submission, the approvers for the first pending stage are shown on the requisition form, after accounting for any stages the creator can approve automatically. Project approvers can be selected when the first pending stage uses Standard project approvers or an approval-stage pool; fixed company approvers are shown read-only and assigned automatically. The review screen shows the resolved route, the rule or default decision, and all required stages. The server resolves the route and validates fixed approvers again when the requisition is submitted. A company admin who is eligible to auto-approve can leave Send through the usual approval process unticked to auto-approve without routing. Routing applies automatically for users who are not offered this choice.

​

Authorised hiring-side users can open the Overview tab and use Correct cost classification while a routed requisition is awaiting approval. Requidex previews the new route, stages, and eligible approvers before applying the change. The user must select a configured reason, select at least one first-stage approver when prompted (specific-user stages assign their configured users automatically), and reselect the complete agency list. Approvers for later stages are selected as approval progresses, or assigned automatically for specific-user stages. Applying the correction resets approval progress and records the old and new routing decision in the activity history. Invalid or stale routing decisions are blocked.

​

Permitted quantity, date, rate, and shift amendments can change the estimated requisition value. While the requisition is awaiting approval, Requidex calculates the proposed value and always shows the resulting route, routing decision, stages, and amendment reason before saving. When the route, decision, approval progress, configuration, or existing selections are affected, the complete agency list must be reselected and a starting approver chosen when prompted; specific-user stages assign their configured approvers automatically. Completed stages reset. When routing is unchanged, approval has not started, and the existing selections remain valid, the user confirms the preview without reselecting approvers or agencies and the current approval state is preserved. Requisitions do not currently have a trade amendment action.

​

Approval routing controls the hiring-side approval sequence. Agencies continue to receive approved requisitions through the existing distribution process. A route may limit how many Tier 1 agencies the hiring side selects, but Tier 2 and Tier 3 timers and agency access remain unchanged.