Real reporting problems. Sanitized implementation samples.
These examples reflect work Durell personally completed and observed. Public files use
invented names and records and disclose no person, employer, facility, vendor,
proprietary code, or confidential information.
Monthly reports18 vendors
Capacity recovered14-32 hrs/mo
Annual estimate168-384 hrs
Problem
Approximately 18 vendor compliance reports had to be prepared within a five-day
monthly reporting window. Each report required one to two hours of manual
preparation, creating a concentrated workload and repeated opportunities for
formatting, mapping, and data-entry errors.
Implemented workflow
Collection
ERP export generatedAttachment delivered through OutlookPower Automate routes and names filesControlled source folder receives files
Reporting
Power Query standardizes recordsVendor reports are preparedExceptions are surfacedHuman reviewer approves distribution
Recreated Excel QA summary using fictional vendor records. The downloadable workbook
includes raw data, mappings, standardized output, a vendor report, QA controls, and
an implementation workplan.
Controls demonstrated in the public sample
Source row counts recorded before transformation
Vendor names standardized through a controlled map
Missing and late submissions identified
Quantity exceptions added to a review queue
Vendor-ready output kept separate from raw data
Final human approval retained before distribution
Observed result
Total monthly preparation fell to approximately four hours. The workflow remained in
use for more than one year. The result represents an estimated 14 to 32 hours of
staff capacity recovered each month while preserving a final compliance review.
Time reduction78%-89%
Operating period1+ year
Human controlFinal review retained
Capacity recovered is not a guarantee of payroll reduction or cash savings. The
downloadable workbook demonstrates representative architecture and controls; it does
not contain the original files, proprietary queries, or a deployable Power Automate
flow.
In a pro bono project for an event coordinator working in a public-sector operating
environment, a weekly system export required nearly an entire shift of manual
adjustments before it matched an established template.
Durell created an Excel macro that standardized the export and applied the required
formatting. The user learned the workflow in approximately 10 minutes and required no
additional developer adjustments during the initial observed weeks.
Before
One eight-hour shift every Wednesday.
8 hours per cycle
After
Automated formatting with a short final review.
Approximately 15 minutes
Have a recurring workflow with the same pattern?
Submit the basic context for an asynchronous free fit check. It determines whether a
paid diagnostic, Automation Assessment, or implementation project is appropriate. No
payment or confidential files are required.
