Approval Routes Configuration
This section provides everything you need to know to configure and manage approval routes in Weissr Capex Management. You’ll find practical guidance, best practices, and key concepts to help your organization implement a structured, policy-aligned approval process.
Approval routes play a critical role in ensuring that investment requests are reviewed and approved according to your internal governance and financial controls. A well-configured route supports transparency, accountability, and efficiency across all project types.
What’s covered in this documentation
The following sections offer step-by-step instructions to help administrators set up and manage approval routes tailored to your organization’s needs:
Create, edit, reorder, or delete routes and steps
Define permissions and approval conditions
Configure automatic routing logic for complex approval paths
Align approval workflows with your investment policies and thresholds
👉 To see how approval routes appear and function from an end-user perspective, visit: Routing and Approvals
Key components of an approval route
Routes
Define the distinct approval paths your organization uses, based on criteria like project type, business unit, or investment amount.
Steps
Specify the sequence of decision points within each route.
Statuses
Configure the status options available at each step (e.g., Approved, Rejected, Completed).
Permissions
Set who is authorized to approve each step — based on role, threshold, or other criteria.
Route Groups
Use conditions to automatically switch a request to another route if the original one no longer applies (e.g., due to a change in funding amount).
How approval routes work
Approval routes are predefined workflows that guide projects through the necessary approvals. They support a wide range of project types — from routine maintenance to large-scale investments — and ensure that each request follows the appropriate review process.
Roles involved in the approval process
Project leaders and stakeholders
Initiate requests and manage project progress through the route.
Decision-makers
Assigned to specific steps, they review requests and choose to approve, reject, or return them for changes.
Step configuration and decision logic
Each approval step can be customized using conditions to match your approval policies:
Role-based permissions – Restrict steps to users with specific roles (e.g., finance controller, department head).
Financial thresholds – Require higher-level approvals for projects exceeding set monetary limits.
Custom logic – Combine project attributes (e.g., region, category) to route approvals dynamically.
Approval route workflow
Initiation – A request is submitted and assigned a route based on its attributes (e.g., Capex amount, project type).
Sequential review – Decision-makers review the request step by step, choosing to approve, reject, or request revisions.
Criteria-based progression – Each step enforces permissions or thresholds before moving to the next.
Final approval – When all steps are completed, the request advances to execution.
What happens after approval?
Execution phase
Approved projects move into execution. Funds can be allocated, expenditures tracked, and progress monitored through integration with ERP systems or manual input. Users can compare planned versus actual outcomes throughout this phase.
Post-completion phase
Evaluate the project’s success by reviewing budget adherence, timelines, and outcomes. Document lessons learned and finalize reporting.
Completion state
Once all evaluations are done, the project is closed and archived, signifying full completion and approval.