Stop Chasing Approvals by Email! Move Procurement Approvals Beyond the Inbox Chase with ServiceDesk Plus
A plant supervisor needs a replacement part, and they send an email. From that moment, the request has to find its way through four people – the plant supervisor who raised it, the plant manager who signs off first, the finance head if the cost warrants it, and the procurement manager who actually places the order. Each stage adds another point where the request can be delayed, particularly when the next person is busy or misses the email.
Two problems keep coming up in this process. No one knows where a request stands without checking with someone, and the process does not move forward unless someone follows up. Across four people, those small delays quickly add up. A process that should take a few hours can easily stretch into a 2-to-3-day turnaround.
An equipment procurement approval workflow built on ServiceDesk Plus replaces this entire chain with a single configured process. This process handles routing, approval, and escalation on its own, with no custom code required.
Four Actors, Four Inboxes, Zero Accountability
The problem in this context is structural, not personal. Nobody in this chain is doing anything wrong. The process itself has no memory and no urgency built in.
- Start with the record-keeping problem. When approvals are handled through email, there is no central record showing who approved a request and when. If an audit comes up, the approval history has to be pieced together by searching through email threads.
- Then there’s the cost logic problem. Not every plant supervisor or manager knows whether a given request needs to be signed off by finance. Without a clear threshold, different people may handle similar requests with different approaches. A low-value request may end up with finance for approval when it does not need it, while a higher-value request may move ahead without the necessary financial review.
- Delays compound at every step, too. Each approver only sees the request once the person before them has acted. If that person is on leave or simply busy, the request stalls. There is no automatic fallback, so it waits.
- Finally, the requester, the person who actually needs the part, has zero visibility. Their only option is to email the concerned person and inquire what’s happening.
One Workflow, Every Approval Handled
When a workflow is properly configured, it answers each of these problems directly. It does this without adding new oversight steps of its own, and it removes the exact points where teams usually get stuck.
Firstly, the request should be initiated in the form of a structured Service Catalog. The part description, cost, plant, and business justification are captured upfront. This ensures that the system has all the information it needs to route the request correctly from the first click. This is where service catalog request automation makes the process easier, because the right information is collected before the request moves to the next stage. Procurement approval automation in IT Service Management (ITSM) starts here too, with clean, structured data captured at the point of submission.
From there, auto-routing identifies the correct plant manager based on the plant and department of the requester. There is no need for anyone to forward the request manually. A cost threshold of $2,000 determines whether finance approval is required. Every request is managed as per the same rule. Approvers gets an email or mobile notification with a link straight to the request, so they can review it and approve or reject in a couple of taps without hunting through a separate queue. Every approval, rejection, timestamp, and escalation is recorded by the workflow, which creates a complete audit trail.
What Happens at Each Stage Inside the Workflow?
Here’s what actually happens once a request is submitted, stage by stage.
1. Request submitted
The plant supervisor fills out the Service Catalog form. The required fields include a description of the part, cost, plant, and justification. The form won’t accept submission without a valid numeric cost, which prevents routing errors before they start.
2. Auto-routing
Now, the workflow engine reads the plant and department of the requester. In the process, the right plant manager is identified. The person approving it receives an email and a push notification on the mobile with the request summary. Both link straight into the Approvals screen, where they can approve or reject in a couple of taps.
3. Cost threshold check
The system checks the cost of the part against the $2,000 threshold. This is a configurable business rule integrated into the workflow settings, not something hard-coded into the platform. So, finance can change it independently without asking IT to rebuild anything.
4a. Finance approval, above $2,000
The finance approver reviews the request against budget and approves or rejects it through the quick approval flow described above.
4b. Direct to procurement, at or below $2,000
Requests that clear the plant manager without hitting the finance threshold go straight to procurement to initiate the order.
5. Notifications at every stage
Every time a stage is completed, the requester receives a status update. If there’s a rejection, a message is triggered to both the requester and the plant supervisor. Proper context, including the reason and the next steps, is also included in the message.
6. Escalation on no action
The workflow can be configured so that if the approver hasn’t acted within 24 hours, the pending approval is automatically reassigned to a predefined backup. Usually, it’s a line manager or deputy, and a 24-hour timer is restarted. Notifications are sent to both the original approver and the backup. The escalation itself remains logged.
7. Closure and audit log
Once all the required approvals are in place, the request can be sent to the procurement or ERP system through a webhook or REST call. This way, the purchase order can be created. The request is then marked as “Fulfilled”. All the details are available with the request, which includes who approved or rejected it, when they acted, and whether the request was escalated.
Why the $2,000 Rule Matters and How to Extend It
The $2,000 threshold can be changed when the approval policy of the company changes. Finance can update the amount without having to redesign the entire workflow or involve IT every time a new limit is introduced.
If the request exceeds $2,000, the request is sent to finance by the workflow before it reaches procurement. However, requests at or below $2,000 can directly go to procurement once they are approved by the plant manager.
The same setup can also handle additional approval levels. For example, requests above $10,000 could require approval from the plant director before moving ahead.
One important point has to be considered when the threshold changes. This should be configured so that requests already in progress keep following the threshold that applied when they were submitted, with the new amount applying only to requests submitted after the change. This prevents an approval from changing halfway through the process.
What Happens When an Approver Does Not Respond
A common concern with automated approvals is what happens when the person responsible for approving a request is unavailable. The SLA timer starts the moment a request lands in an approval stage, whether that’s the plant manager or finance. The default timeout is 24 hours with no recorded action. When that timer fires, the workflow can be configured to reassign the request automatically to a predefined backup and restart the clock. The original approver gets notified that their request moved on, and the whole event is logged.
The number of escalation levels can also be adjusted based on the approval structure of the company. A flat organization might set one backup approver. A larger one can build a multi-level chain that matches its actual hierarchy.
As a general rule, once an approval stage is closed it should not reopen, even if an escalation fires around the same time, this specific behavior should be confirmed against your live configuration before it’s published as a guarantee.
From 2 to 3 Days to Under 4 Hours: What Changes
The biggest change is the time saved. Once the manual approval chain is replaced with a workflow, the average approval time can fall from 2 to 3 days to under 4 hours.
The benefit is not limited to faster approvals. Every request has a record of the entire process, including approvals, rejections, escalations, and the time each action took. Finance and procurement also receive the information they need in a consistent format. They do not have to search through email threads or work with incomplete details.
As the process runs on ServiceDesk Plus workflow automation rather than a fixed script, it’s extensible. New cost tiers, extra approval stages, or additional notification triggers get added through configuration, not a rebuild from scratch. The requester, meanwhile, gets automatic status updates at every stage transition, so they do not have to ask.
Ready to Move Your Procurement Approvals Out of the Inbox?
A well-designed procurement workflow can make approvals faster, easier to track, and simpler for everyone involved. Conditional approval logic ensures that each request follows the right path based on factors like cost or department. At the same time, automated approval routing gives IT operations teams a system they can rely on to keep requests moving without constant follow-up.
When an approval is delayed, an SLA escalation workflow can move it to the right backup approver and keep the process moving. All of this can be managed through a configured ServiceDesk Plus setup, which does not require custom development.
If your team is evaluating workflow automation in ServiceDesk Plus or looking to standardize approval chains across departments, connect with our ITSM team for a workflow review. We will map your current approval process and show you how an equipment procurement approval workflow built on ServiceDesk Plus can fit into your environment.
Xponential Digital