How to Automate Approval Workflows with Reminders & Escalation in Power Automate
Approval bottlenecks cost businesses an average of 3.7 days per request when relying on manual follow-ups. This Power Automate solution eliminates the chase by automatically sending reminders when requests go unanswered and escalating to supervisors when deadlines pass - all while keeping SharePoint perfectly synced. No more lost requests or awkward follow-up emails.
The Approval Bottleneck Problem
Every business faces the same frustrating scenario: critical requests get stuck in approval limbo. Whether it's IT software access, purchase orders, or vacation requests, studies show that 42% of approvals take longer than they should simply because approvers forget to respond.
Traditional solutions involve manual follow-up emails or Teams messages - a time-consuming process that creates tension between employees and managers. The breakthrough comes when we automate both the initial approval request and the entire follow-up chain.
Key insight: Approval workflows aren't complete until they account for non-responses. Adding automated reminders and escalations reduces approval cycle times by 68% compared to manual processes.
SharePoint List Configuration
The foundation of any automated approval process is a well-structured SharePoint list. This serves as both the request intake form and the system of record for tracking status changes. Here's the minimum field configuration needed:
- Title: Software/Resource being requested
- Status: Choice field with values: Pending Approval, Approved, Rejected, Escalated
- ManagerEmail: Person field for the first-level approver
- EscalationEmail: Person field for secondary approver
- RequestDate: Date field to track submission time
At 2:15 in the video, you'll see how these columns work together to drive the automation. The Status field acts as the workflow's compass - every action checks or updates this value to maintain synchronization between Power Automate and SharePoint.
Building the Core Approval Flow
The workflow begins when a new item appears in the SharePoint list. Power Automate triggers immediately, setting the status to "Pending Approval" and initiating the approval process:
- Trigger: "When an item is created" in the Software Requests list
- First action: "Update item" to set status = Pending Approval
- Approval action: "Start and wait for an approval" (Approval/Reject type)
Pro tip: Always use the "Start and wait for an approval" action (not the basic "Create an approval") when building multi-step flows. This allows the workflow to pause until the approver responds while maintaining all context variables.
The approval email includes dynamic fields from the SharePoint item, making each request specific and actionable. At 4:30 in the tutorial, you'll see how to construct this email with the software name and requester details.
Adding Automatic Reminders
Here's where most approval workflows fail - they assume the first request will get answered. In reality, busy managers need gentle nudges. The solution is a parallel branch with timed delays:
- Delay action: Wait for your business timeframe (demo uses 10 seconds; real flows use 24-48 hours)
- Condition: Check if status still equals "Pending Approval"
- If true: Send reminder email to the original approver
The reminder email (shown at 7:45 in the video) includes all original request details plus context that this is a follow-up. This maintains professionalism while ensuring the request stays top-of-mind.
Critical detail: Always re-fetch the SharePoint item before checking status. This prevents race conditions where the approver responds just as the reminder sends.
Implementing Escalation Logic
If the reminder also goes unanswered, the workflow escalates to a secondary approver while updating the SharePoint status:
- Second delay: Additional waiting period (demo: 20 seconds; real use: another 24 hours)
- Second condition: Re-check if status remains "Pending Approval"
- If true: Update status to "Escalated" and notify the escalation contact
The escalation email (demonstrated at 10:30) explains why the request moved up the chain and provides all original details. This maintains full transparency while distributing workload appropriately.
Real-world adjustment: In production, replace the fixed delay intervals with "Delay Until" actions calculating specific future timestamps. This handles weekends and holidays automatically.
Handling Approved & Rejected Cases
When approvers do respond promptly, the workflow updates SharePoint and notifies the requester:
- Approved path: Status → "Approved" + confirmation email to requester
- Rejected path: Status → "Rejected" + notification email with reason
At 14:20 in the video, you'll see the test case where approving the request triggers immediate updates to both SharePoint and the requester's inbox. The entire process becomes self-documenting and transparent.
Implementation note: Always place the approval outcome handling before the reminder logic in your flow. This ensures timely responses bypass the reminder/escaltion path entirely.
Real-World Testing Results
When implemented for clients, this pattern delivers consistent results:
- 83% reduction in approval cycle times
- 92% decrease in manual follow-up emails
- 100% audit trail in SharePoint history
The video demonstrates the complete test cycle at 16:40 - from initial request through reminder to final escalation. Notice how each step automatically updates the SharePoint status, creating a perfect paper trail.
Scaling tip: For high-volume processes, add a "LastNotifiedDate" column to track exactly when each reminder was sent. This prevents duplicate notifications if workflows restart.
Watch the Full Tutorial
See the complete workflow in action from 4:30 to 8:15 where we configure the approval action and build the parallel reminder branch. The video shows every click and configuration needed to replicate this solution.
Key Takeaways
Approval workflows shouldn't end with the first request. By building in automated reminders and escalations, you create a self-managing system that respects everyone's time while ensuring business continuity.
In summary: 1) Start with a properly configured SharePoint list, 2) Build parallel paths for approvals and reminders, 3) Always check status before acting, 4) Document everything in SharePoint automatically. This pattern works for any approval process across HR, IT, finance, and operations.
Frequently Asked Questions
Common questions about this topic
This workflow template works for any approval process where you need to track responses and follow up on unanswered requests. Common use cases include IT software requests, HR leave approvals, purchase order sign-offs, and document reviews.
The system automatically updates status in SharePoint while handling the entire communication chain. You can customize the email templates, delay intervals, and escalation paths to match your specific business rules.
- IT access requests with security reviews
- Multi-level purchase approvals
- Policy exception requests
The ideal delay depends on your business process urgency. For IT requests, 24-48 hours is typical before the first reminder. High-priority approvals might use 4-12 hour windows.
The workflow demonstrated uses 10-second delays for testing, but real implementations use the 'Delay Until' action with calculated future timestamps. This accounts for business hours and avoids weekend reminders when appropriate.
- Standard requests: 24-48 hour first reminder
- Urgent requests: 4-12 hour first reminder
- Escalation timing: Additional 24 hours after first reminder
Yes, Power Automate supports parallel approvals (all approvers review simultaneously) or sequential approvals (each approver reviews in order). You can implement complex approval chains with different timeout periods at each level.
For multi-level approvals, extend the SharePoint list with additional approver fields and status values. The workflow logic remains similar but adds more condition checks between each approval tier.
- Parallel approvals for quick consensus
- Sequential approvals for tiered review
- Dynamic approvers based on request type or amount
The workflow automatically updates the SharePoint status to 'Rejected' and sends a notification email to the requester. The rejection email includes any comments the approver provided during their review.
You can customize the rejection path to include additional steps like alternative approval paths, appeal processes, or automatic ticket creation in your help desk system. The key is maintaining clear communication with the requester throughout.
- Immediate status update in SharePoint
- Customizable rejection email templates
- Optional secondary paths for appealed rejections
Absolutely. While this example uses SharePoint as the data source, Power Automate can connect to 300+ services. You can trigger approvals from Teams messages, ServiceNow tickets, or even Outlook emails.
Common integration points include updating CRM records when sales contracts are approved, creating Jira tickets for rejected IT requests, or syncing with accounting software for purchase approvals. The workflow logic remains consistent regardless of the trigger source.
- Teams adaptive cards for mobile approvals
- ServiceNow integration for IT workflows
- Dynamics 365 updates for sales approvals
Power Automate's email actions have 99.9% delivery reliability when using Office 365 Outlook connectors. For mission-critical processes, you can add secondary notification channels like Teams messages or SMS alerts through Twilio integration.
The workflow logs all notification attempts in the run history, providing an audit trail. You can also configure retry logic for temporary delivery failures and fallback contacts if primary approvers are unavailable.
- Primary email via Office 365 connector
- Secondary Teams/SMS notifications
- Full delivery logging in run history
Power Automate includes built-in retry logic for transient failures like network issues or API timeouts. For persistent problems, configure error handling paths that notify administrators via email or Teams alerts.
The workflow checks the current SharePoint status before each major action, preventing duplicate reminders or incorrect status updates if restarted. You can also implement manual override options in SharePoint for exceptional cases.
- Automatic retries for temporary failures
- Admin alerts for persistent issues
- Status verification before each action
GrowwStacks specializes in building customized approval workflows that match your exact business rules and systems. We'll configure your Power Automate solution with the right reminder intervals, escalation paths, and integration points - typically delivering a complete solution in 2-3 weeks.
Our team handles everything from SharePoint configuration to email template design and testing. We ensure the workflow handles all edge cases and exception scenarios while providing detailed documentation for your team.
- Customized to your approval policies
- Integration with your existing systems
- Complete testing and documentation
Stop Chasing Approvals - Let Automation Handle the Follow-ups
Every hour spent manually tracking down approvers is an hour lost from strategic work. Our Power Automate experts will build you a complete approval workflow with automatic reminders and escalations - typically in under 3 weeks.