Route policies

An approver needs to know why a request has reached them. Route policies give that decision a named business context, an owning business unit and an effective period. Approval Coordinator maintains the policy reference and checks how the route applies to the request. The request carries its route version so the team can distinguish the policy used for review from later configuration changes.

The route-resolution workflow checks the selected request revision and ordered approver eligibility. It records the route version and requested amount alongside operation history, then moves the request into review. That transition gives the approval team a defined starting point for its work. It is still the Approver who decides the business request.

• Policy ownership. Give each route a recognizable name and code, an owning business unit and a policy reference. Approval Coordinator keeps these aligned with the process the team actually follows.
• Effective context. Review effective dates and active state when choosing a route. Retain the version recorded on the request when explaining an earlier decision, even if current policy has changed.
• Source mapping. Define source and target fields with their types and transformation rules when information comes from a connected system. Associate the mapping with the relevant route and review its version before use.

Bring the policy that names eligible approvers and explains their order. Agree how the implementation resolves eligibility for the selected request, how it identifies a route version and who can change that configuration. Use a request from each participating business unit to check the result. Treat route setup as preparation for approval, with the actual decision made against the request.

Agree the meaning of delegation expiry and the review action when that date passes. The assigned Approver and current step should be clear before any decision is recorded. Also agree how the team sets the SLA due date and which person inspects overdue work. Date tracking becomes useful when someone owns the resulting follow-up.

A business unit updates its spending policy while a request is already in review. Approval Coordinator opens the current route and the request’s retained route version. The reviewer needs to understand which policy context belongs to that request before deciding whether the change affects it. A new policy reference alone should never become an unexplained change to an earlier business decision.

Rehearse route resolution on a submitted request with the intended amount and assigned Approver. Inspect the resulting operation record and state transition. Ask the coordinator to explain the selected step and ask the Approver to confirm their eligibility under the agreed policy. Repeat with an ineligible person and require the team to resolve that condition before approval.

If the request originates elsewhere, include a source value that needs a type conversion. Compare the mapped value with the original and the amount shown to the Approver. A mapping review should identify what changed and which version produced the value used for the decision.

• Active route policies — Inspect routes marked active and check their effective dates before use.
• Delegation expiry watch — Find requests whose recorded delegation expiry needs attention.
• My assigned approvals — Check the route version and ordered step on work awaiting your decision.

Request to review covers route resolution. Evidence to decision follows the request into human review.