Case Study: Automating the OneDrive → Excel → PDF → Email Pipeline
How a mid-sized consulting firm transformed their weekly client reporting from a 4-hour manual process to a 15-minute automated workflow with AI agents.
Every Friday afternoon, Sarah dreaded the same ritual. As operations manager at a 35-person consulting firm, she spent four hours pulling Excel files from OneDrive, consolidating client data, generating PDF reports, and emailing them to stakeholders. The process was critical—clients expected their weekly updates—but it consumed her entire Friday afternoon.
This is the story of how her firm deployed AI agents to handle the workflow end-to-end.
The Original Process
Before automation, the weekly reporting workflow looked like this:
- Retrieve files — Download 12 Excel workbooks from various OneDrive folders, each containing client project data
- Consolidate data — Copy relevant data from each workbook into a master reporting template
- Run calculations — Update formulas, check for errors, verify totals
- Generate PDFs — Export each client's report section as a branded PDF
- Compose emails — Write personalized cover messages for each client
- Send and log — Email reports to the right contacts, log completion
Total time: 4 hours, every Friday, without fail.
The hidden costs went beyond Sarah's time. Reports occasionally went to wrong recipients. Data entry errors crept in. And if Sarah was sick or on vacation, the entire process either stopped or fell to someone unfamiliar with the nuances.
Mapping the Automation Opportunity
When the firm decided to automate, they started by documenting exactly what happened at each step. The analysis revealed something important: most of the process was mechanical.
| Step | Human Judgment Required? |
|---|---|
| Download files from OneDrive | No |
| Identify correct files by date/name | Minimal |
| Copy data to template | No |
| Run standard calculations | No |
| Flag anomalies for review | Yes |
| Generate PDF reports | No |
| Compose standard email text | No |
| Personalize for exceptions | Yes |
| Send to correct recipients | No |
| Log completion | No |
Only two steps genuinely required human judgment: reviewing anomalies and handling exceptions. Everything else followed predictable patterns.
The Automated Workflow
The new workflow operates in three phases:
Phase 1: Intelligent Data Collection
Every Friday at 2 PM, the automation:
- Connects to OneDrive and Google Drive (different teams used different platforms)
- Locates the correct Excel files using naming conventions and modification dates
- Downloads and validates each file against expected schemas
- Flags any missing files or unexpected formats immediately
What previously took 45 minutes now happens in seconds—and catches problems Sarah used to discover mid-process.
Phase 2: Processing and Generation
With validated data in hand, the system:
- Consolidates data into the master template using predefined mapping rules
- Executes all calculations and cross-references
- Runs validation checks: Do totals match? Are variances within expected ranges?
- Generates branded PDF reports for each client
- Composes email drafts with standard messaging
For routine weeks (no anomalies, all data within normal ranges), this phase completes without human intervention.
Phase 3: Human Review and Delivery
Here's where the human-in-the-loop design becomes critical. The system doesn't blindly send reports. Instead:
- Sarah receives a summary dashboard showing all reports ready for delivery
- Anomalies are flagged with context: "Client X shows 47% variance in billable hours vs. prior week"
- She can approve all standard reports with one click
- Exception reports require individual review and optional message customization
- Once approved, emails are sent and logged automatically
Sarah went from 4 hours of manual work to 15 minutes of focused review.
Technical Implementation
The firm's setup wasn't exotic. They used:
- Cloud storage: OneDrive for most teams, Google Drive for two departments
- Data format: Standard Excel workbooks with consistent (mostly) naming
- Email: Microsoft 365
- No existing automation: They'd never used Power Automate or similar tools
The agentic orchestration layer connected these systems through OAuth integrations. The AI agent was configured as a modular "skill" — a self-contained package of instructions, rules, and context that captured how their team actually ran the reporting process.
The agent handles:
- File retrieval across both OneDrive and Google Drive
- Excel processing — data consolidation, formula execution, validation
- Anomaly flagging based on variance thresholds the team defined
- PDF generation with brand templates
- Email composition and delivery orchestration
No changes were required to the team's existing tools or habits. The agent adapted to their workflow, not the other way around. Files stayed in OneDrive. Reporting templates stayed in Excel. The agent simply orchestrated the process that Sarah used to do manually.
Results After Three Months
The quantitative improvements were immediate:
| Metric | Before | After |
|---|---|---|
| Time spent weekly | 4 hours | 15 minutes |
| Data entry errors | 2-3 per month | 0 |
| Missed/late reports | 1-2 per quarter | 0 |
| Wrong recipient incidents | ~1 per quarter | 0 |
But the qualitative changes mattered more. Sarah now spends Friday afternoons on strategic work. The team has confidence that reports go out correctly every week, regardless of who's in the office. And when anomalies occur, they're surfaced prominently rather than buried in spreadsheets.
Lessons Learned
Start with documentation
The firm spent two weeks documenting their existing process before attempting automation. This investment paid off immediately—they discovered three variations of "the process" that different team members used, and standardized before automating.
Design for exceptions, not just the happy path
The initial design assumed all weeks would be routine. Reality: about 30% of weeks have at least one anomaly requiring human attention. The approval workflow became the most important part of the system.
Validate early, not late
Early versions processed all files before checking for problems. Now, validation happens immediately on download. Catching a missing file at 2:01 PM is far better than discovering it at 5:30 PM.
Keep humans in meaningful positions
The agent handles mechanics. Sarah handles judgment. This division respects both the efficiency gains of automation and the irreplaceable value of human oversight for client-facing communications. Every action the agent takes is logged in a full audit trail—what files were accessed, what rules were applied, what was produced.
Applicability to Your Organization
This pattern—cloud storage to data processing to document generation to communication—appears across industries:
- Accounting firms: Monthly client financial summaries
- Property management: Tenant communication and reporting
- Healthcare: Patient status updates to referring physicians
- Professional services: Project status reports to clients
- Sales teams: Pipeline reports to leadership
If your workflow involves pulling data from files, processing it in spreadsheets, generating documents, and sending them to people—automation can likely help.
Getting Started
If you recognize your own Friday afternoon in Sarah's story:
- Document one cycle completely. Write down every click, every file, every decision.
- Identify the mechanical steps. What happens the same way every time?
- Find your judgment points. Where do you actually need to think, not just execute?
- Define your approval comfort level. What must you review before it goes to clients?
The goal isn't to remove yourself from the process—it's to ensure your time goes to the parts that actually need you. Describe the outcome you want, and let AI agents handle the clicks.
reflexion