Skip to main content

Approvals & Routing

The right person decides. The work knows where to go.

Henswick reads the conditions on every request — amount, department, risk, category, who’s already reviewed it — and sends it to whoever should decide next. What doesn’t need a person keeps moving on its own.

Show us how a request should be routed

How the destination gets decided

One request, evaluated against real conditions.

Every request carries its facts — amount, department, risk, category, who’s already looked at it. Henswick checks those conditions against the routing logic you already use, then sends the request to exactly the shape it needs: continue on its own, one owner, reviewed in order, or reviewed together. Escalation and send-back stay part of the same flow.

One request evaluated against conditions, then routed to one of four shapesA request carries its facts into a set of conditions. Depending on what matches, it continues on its own, goes to one owner, is reviewed in order by two people, or is reviewed by two people at once. A separate branch escalates past a threshold. Every path ends with a decision stamp and the work resumes automatically. The diagram loops through the standard-band example: conditions read in turn, the route activates, and the request clears on its own and is stamped approved.REQUESTFacts attachedAmountDepartmentRiskCategoryPrior reviewersROUTEStandard discount bandContinues on its ownConditions already satisfiedDepartment leadOne owner decidesA single reviewer is enoughReviewer AReviewer BReviewed in orderOne reviewer, then the nextFinanceLegalReviewed togetherMore than one reviewer at onceDECISION STAMPApprovedSent backEscalatedthen work resumes automaticallypast a threshold, or no reply
One request evaluated against conditions, then routed to one of four shapesA request carries its facts into a set of conditions. Depending on what matches, it continues on its own, goes to one owner, is reviewed in order by two people, or is reviewed by two people at once, with a separate escalation past a threshold. Every path ends with a decision stamp and the work resumes automatically. The diagram loops through the standard-band example: conditions read in turn, the route activates, and the request clears on its own and is stamped approved.REQUEST · facts attachedAmountDepartmentRiskCategoryPrior reviewersROUTEContinues on its ownConditions already satisfiedStandard discount bandOne owner decidesA single reviewer is enoughDepartment leadReviewed in orderOne reviewer, then the nextReviewer AReviewer BReviewed togetherMore than one reviewer at onceFinanceLegalEscalation triggerpast a threshold, or no reply in timeDECISION STAMPApprovedSent backEscalatedthen work resumes automatically

Illustrative scenarios

The same logic, three different requests.

Different fields decide the route each time — margin, value, budget ownership. None of this is a fixed recipe; Henswick works out the conditions that match how your teams already approve things.

Illustrative scenario 1

Discount approval · Sales

Routed by margin and deal size

A rep requests an 18% discount. Inside the standard band, it clears on its own. Above it, the sales manager decides alone. Past a deeper threshold, Deal Desk and Finance review together before it moves.

Discount approval routed by margin and deal sizeA discount request is checked against the margin and the size of the deal. Inside the standard band it is auto-approved. A moderate discount goes to the Sales Manager. A deep discount goes to Deal Desk and Finance together.DiscountMarginStandard bandAuto-approvedinside the standard bandSales MgrSales Manager decidesmoderate discountDeal DeskFinanceDeal Desk + Financedeep discount, together

Illustrative scenario 2

Purchase requisition · Procurement

Routed by value and category

A department requests a purchase. Below the threshold, the department lead decides. Above it, Procurement and Finance review in sequence. Certain categories add Legal automatically.

Purchase requisition routed by value and categoryA purchase requisition is checked against its value and category. Below a threshold, the department lead alone can approve it. Above it, Procurement and Finance are added in sequence. Certain categories add Legal as well.RequisitionValueDept leadDepartment lead decidesbelow the thresholdProcure.FinanceProcurement, then Financeabove the thresholdLegalLegal is addedfor flagged categories

Illustrative scenario 3

Project request · Finance

Routed by department and budget ownership

A team requests budget for a project. Inside one department’s authority, the budget owner decides alone. Above the threshold, the owner and Finance review together. Cross-department requests bring in every owner it touches.

Project request routed by department and budget ownershipA project request is checked against its budget and how many departments it touches. A routine request goes to its own budget owner. Above a threshold, Finance is added. A request spanning departments goes to every owner at once.Project req.BudgetBudget ownerBudget owner decidessingle department, routineOwnerFinanceBudget owner + Financeabove the thresholdOwner AOwner BAll department ownersspans departments, together

Approvals & Routing

Ready to see how your approvals would route?

Bring the conditions you already check today — amount, department, risk, who’s supposed to sign off — and we’ll show you where each one lands.

Show us how a request should be routed

See how this fits with Workflow Automation, or explore the rest of Solutions.