Fig. 2 — coverage-gap-flow
TAY Coverage Gap Flow
This automation scanned a shared calendar and surfaced the visits that had no staff assigned. It was built as an independent workflow automation on top of Microsoft 365, and it targeted a high-volume scheduling problem in a live research environment with thousands of visit records annually, where coverage gaps had previously been found by manual review.
Facts
Role: Independent workflow automation build
Type: Operations automation / scheduling support
Stack: Power Automate, Outlook calendar logic, Microsoft 365
No public link
What I built
- Built a Power Automate flow to scan a shared calendar for unassigned visits.
- Applied logic for identifying scheduling gaps across high-volume research operations.
- Used Microsoft 365 ecosystem tools to support team workflow visibility.
- Reduced the need for manual calendar review.
Why it mattered
- Helped staff catch unassigned visits earlier.
- Reduced manual auditing work.
- Improved coverage reliability for high-volume visit operations.
- Made scheduling risks more visible.
Relevant skills
- Power Automate
- Scheduling automation
- Microsoft 365
- Operations analysis
- Workflow design