assess.one – AI-powered business operations platform

Workflow Template

Capital Expenditure Approval Workflow

Captures capex requests including item, business case, cost estimate and expected benefit; finance reviews budget availability; request is routed for approval based on delegated authority thresholds tied to cost; approved requests are handed off to procurement and the requester notified; rejected requests are returned to the requester with the reason.

Organisations managing capital expenditure must demonstrate rigorous financial governance, ensuring every request is validated against available budget and approved by the appropriate level of delegated authority before funds are committed. The Capital Expenditure (Capex) Approval Workflow captures the business case, cost estimate, and expected benefit for each request, then routes it through finance review and tiered approval — manager, director, or executive — based on cost thresholds. Finance, budget owners, department managers, directors, executives, and procurement teams all operate within a single auditable workflow inside assess.one, eliminating fragmented email chains and manual sign-off tracking.

Business Outcomes

  • Reduce capex approval cycle time by routing requests automatically to the correct authority level
  • Eliminate budget overcommitment through mandatory finance review before approval routing
  • Achieve full audit trail of every approval decision tied to delegated authority thresholds
  • Cut manual escalation errors by enforcing cost-based routing rules (manager, director, executive)
  • Improve requester experience with automatic status updates and clear rejection reasons

Workflow Steps

Steps

  1. 1
    Create Capex Request Recordcreate record

    Registers the submitted capex request as a record.

  2. 2
    Set Status to Submittedupdate record

    Marks the request as submitted.

  3. 3
    Finance Review of Request & Budgetcreate task

    Finance reviews the business case, cost estimate and checks budget availability.

  4. 4
    Update Status - Under Finance Reviewupdate record

    Persists finance review outcome and updates status.

  5. 5
    Route on Budget Availability

    If no budget is available, reject the request; otherwise proceed to threshold-based approval routing.

    budget_available: "No"Set Status to Rejected (No Budget)
    budget_available: "Yes"Route Approval by Delegated Cost Threshold
    DefaultRoute Approval by Delegated Cost Threshold
  6. 6
    Set Status to Rejected (No Budget)update record

    Marks the request rejected due to lack of budget.

  7. 7
    Notify Requester - No Budgetsend email

    Informs the requester that the request was rejected due to lack of budget.

  8. 8
    Route Approval by Delegated Cost Threshold

    Routes the request to the appropriate approval level based on the cost estimate.

    cost_estimate: "10000"Set Status - Pending Manager Approval
    cost_estimate: "100000"Set Status - Pending Director Approval
    DefaultSet Status - Pending Executive Approval
  9. 9
    Manager Approval (Under $10,000)request approvalrequires approval

    Requests manager sign-off for low-value capex.

  10. 10
    Route Manager Approval Outcome

    Branches based on the manager's approval decision.

    approval_status: "approved"Set Status to Approved
    approval_status: "rejected"Set Status to Rejected
    DefaultEnd
  11. 11
    Director Approval ($10,000 - $99,999)request approvalrequires approval

    Requests director sign-off for mid-value capex.

  12. 12
    Route Director Approval Outcome

    Branches based on the director's approval decision.

    approval_status: "approved"Set Status to Approved
    approval_status: "rejected"Set Status to Rejected
    DefaultEnd
  13. 13
    Executive Approval ($100,000+)request approvalrequires approval

    Requests executive sign-off for high-value capex.

  14. 14
    Route Executive Approval Outcome

    Branches based on the executive's approval decision.

    approval_status: "approved"Set Status to Approved
    approval_status: "rejected"Set Status to Rejected
    DefaultEnd
  15. 15
    Set Status to Approvedupdate record

    Marks the capex request as approved.

  16. 16
    Hand Off to Procurementassign user

    Assigns the approved capex request to procurement for purchasing action.

  17. 17
    Notify Requester - Approvedsend email

    Informs the requester that the capex request was approved and handed to procurement.

  18. 18
    Set Status to Rejectedupdate record

    Marks the capex request as rejected and records the reason.

  19. 19
    Notify Requester - Rejectedsend email

    Returns the request to the requester with the rejection reason.

  20. 20
    Set Status - Pending Manager Approvalupdate record

    Marks the request as pending manager approval before requesting sign-off.

  21. 21
    Set Status - Pending Director Approvalupdate record

    Marks the request as pending director approval before requesting sign-off.

  22. 22
    Set Status - Pending Executive Approvalupdate record

    Marks the request as pending executive approval before requesting sign-off.

Fields

  • Requester Name*
  • Requester Email*
  • Department*
  • Item / Asset Description*
  • Business Case*
  • Cost Estimate*
  • +6 more fields

Forms

Capital Expenditure Request

8 fields

Data Views

All Capex Requests

capex_request_ref, item_description, department, cost_estimate +2 more

Dashboard Widgets

Capex Approval PipelineCapex Request SummaryCapex Requests by Status

Recommended integrations

Setup the following integrations to extend workflow capability.

  • Send email in the workflow

    AWS SES logoAWS SES
capital expenditurecapex approvalcapital requestinvestment approvalbudget

Similar Workflows

Similar Categories

FAQs

How is this workflow audited for compliance purposes?

Every capex request generates a timestamped record within assess.one, capturing status changes from submission through finance review, approval routing, and final disposition. Approval decisions, budget review outcomes, and rejection reasons are all logged against the delegated authority threshold applied, giving finance and internal audit teams a complete, exportable trail without needing to reconstruct approvals from email or spreadsheets.

Who has access to capex request data at each stage?

Access is role-based and configured directly in assess.one, so requesters, finance reviewers, managers, directors, and executives only see the information and actions relevant to their role. Procurement teams gain visibility only once a request reaches approved status, ensuring sensitive budget and business case detail isn't exposed until the appropriate stage.

How does this integrate with existing finance and procurement systems?

Notifications and handoffs — such as alerting the requester or passing approved requests to procurement — are configured inside assess.one using its built-in email and Slack integrations, requiring no external development work. Procurement teams receive approved capex requests directly within the workflow, ready for downstream action in their own systems.

Can the delegated authority thresholds be customised?

Yes, the cost thresholds that trigger manager, director, or executive approval are fully configurable within assess.one's routing logic. Organisations can adjust dollar thresholds, add additional approval tiers, or modify approver roles at any time without disrupting requests already in progress.

What happens when a request is rejected at the budget review stage?

If finance determines there is insufficient budget, the request status is automatically set to 'Rejected (No Budget)' and the requester is notified with the specific reason. The request record remains in the system for audit and future resubmission, rather than being lost in email threads.

Who needs to be granted access to use this workflow effectively?

At minimum, requesters, a finance reviewer, and approvers at each delegated authority tier (manager, director, executive) need access, along with a procurement contact for handoff. Access can be scoped by role directly within assess.one, so organisations can add or remove participants as approval structures change.

How does the workflow handle approvals at different cost thresholds?

Once finance confirms budget availability, the workflow automatically routes the request based on its cost estimate — under $10,000 to a manager, $10,000–$99,999 to a director, and $100,000 or above to an executive. Each approval outcome is captured and routed onward, either to the next status update if approved or to rejection and requester notification if declined.

How long does it take to implement this workflow?

There is no implementation project required. The template publishes in minutes inside assess.one, and once live, your finance, management, and procurement teams can begin submitting and processing real capex requests immediately.

Can approval logic and notification rules be changed after go-live?

Yes, all steps, roles, thresholds, and notification rules remain fully editable within assess.one at any time. Changes take effect immediately for new requests, so the workflow can evolve alongside organisational policy without downtime or redevelopment.

Ready to use this workflow?

Create a free account and customise this workflow for your business.

Capital Expenditure (Capex) Approval Workflow | assess.one