Operational Context
In field-heavy industries like construction or onsite inspections, capturing real-time progress relies on capturing data where it happens. This workflow applies to production environments where onsite staff need a friction-free way to archive documentation directly into a centralized document management system (SharePoint) without manual office-side intervention.
The Problem
Resistance to new apps is the primary point of failure for field documentation. Superintendent and onsite contractors often bypass formal systems in favor of text messages or local storage, leading to "data silos" where critical project photos die in individual inboxes or personal galleries. The challenge is capturing this data without adding cognitive load to the field team.
Investigation Approach
To solve this, I designed a "No-App" architecture that leverages the existing behavior of sending emails with attachments. The system is built on a standard enterprise stack:
- Trigger: Monitoring a dedicated Outlook inbox.
- Logic: Power Automate for parsing subject lines and routing.
- Storage: SharePoint Online project libraries for long-term archiving.
Resolution
I implemented a 4-step automated pipeline that stabilizes this ingestion process:
- Inbox Monitoring: A cloud flow triggers on new emails with attachments to
photos@company.com. - Dynamic Routing: The flow uses
split()expressions to parse the Project ID from the subject line (e.g.,101 - Description). - Smart Renaming: To prevent collisions, files are renamed using
utcNow()and metadata from the sender. - Automated Filing: Files are dynamically routed to the corresponding project folder in SharePoint, creating a "hands-off" filing system.
System Considerations
- Access Control Implications: Ensure the service account running the flow has "Contribute" access to all project libraries while onsite staff only need "Send As" or "Send to" permissions.
- Performance Impact: Large batches of high-res photos can hit Power Automate concurrency limits. I implemented "Apply to each" loops with sequential processing to ensure stability.
- Automation Opportunities: This ingestion layer serves as a foundation for downstream AI extraction or automated client progress reporting.
Want to build this?
I have packaged the exact Setup Checklist and Flow Diagram for this system. You can get it for free in my Automation Vault.
Cover image credit: Microsoft Support - All about approval workflows
