Coordinator Hours Returned Annually
Twenty hours per week of manual status work disappeared - 1,040 hours per year redirected to engineering and client delivery.
Case study
1,040 Hours Back on Engineering Work: An EPCM Proposal Hub in Microsoft Access
A Texas EPCM practice running as Alliance Engineers was losing a full workweek every month to proposal admin. We built an Access control center that routes bids from Outlook, tracks delivery live, and cut approval cycles from days to hours.
Delivery Metrics at a Glance
Proposal Routing Speed
Request-to-approval dropped from a 3-5 day cycle to same-day handling - roughly 75% faster bid movement through the pipeline.
Front-End Version Conflicts
Automated application updates removed every instance of staff running outdated Access files against current project data.
Database File Size After Attachment Move
External file storage shrank the .accdb from 1.8 GB to 720 MB - a 60% reduction that restored save and query speed.
Status-Chase Email Volume
Partners and PMs stopped rebuilding weekly status packs - follow-up email traffic around project state fell by 80%.
First-Year Return on Build Cost
Lower admin overhead plus stronger proposal throughput produced 180% ROI in the opening year.
The Firm and the Friction
Alliance Engineers runs EPCM work across Texas - engineering, procurement, and construction management for industrial clients. Proposals drive revenue; active projects drive delivery.
Both sides of the business ran on fragmented tools. Bid requests landed in Outlook. Status lived in spreadsheets. Attachments clogged a growing Access file. Managers stitched KPIs together by hand every Friday.
The firm did not lack data. It lacked one place where a partner could answer: Which proposals are pending? Which jobs are behind? What did we win this quarter? - without calling three people.
Four Bottlenecks Holding Up Proposals and Projects
These were the failure points we mapped in discovery - each one costing billable hours:
1. Inbox-to-Spreadsheet Proposal Handoffs
Business development emailed new bid requests, then coordinators re-keyed details into tracking sheets. Approvals wandered for 3-5 days because nobody owned the next step in a shared system.
2. A Database File Swollen With Attachments
Storing proposal drawings and PDFs inside the Access backend pushed the file toward 2 GB. Saves slowed. Warnings appeared. Staff hesitated to add new records because the system felt like it was running out of room.
3. Stale Front-Ends on Active Projects
Distributing updated Access front-end files by email failed as headcount grew. Engineers opened old versions, wrote to mismatched schemas, and created reconciliation work nobody budgeted for.
4. Friday Report Assembly Marathons
Leadership needed pipeline metrics, completion percentages, and weekly delivery summaries. Coordinators spent 20+ hours each week copying numbers out of disconnected sources.
Building the Delivery Control Center
We built a single Microsoft Access application that sits at the center of proposal intake, project tracking, and management reporting for this EPCM team.
Outlook remains the front door - a bid email creates a proposal record automatically and kicks off the approval path. Delivery PMs update job status in the same database partners use to review the pipeline.
Attachments live on shared storage with pointers in Access, not blobs in the tables. The front-end checks for updates on launch so every user runs the same version. Dashboards and Excel exports pull from one dataset - not a folder of half-synced workbooks.
Access + Outlook: How the Pieces Connect
EPCM workflows are email-native. Fighting that habit fails. We wired VBA so qualifying Outlook messages spawn structured proposal rows - client, scope, due date, and owner - without a coordinator retyping the thread.
Status transitions fire Outlook notifications to the next approver or project lead. The inbox becomes an audit trail; the database becomes the authority on current state.
SQL Server recordsets back the heavier queries - pipeline totals, completion rollups, and multi-year bid history - while Access forms stay the daily interface for coordinators who already know the environment.
Microsoft Forms integration (shown in the screenshots) captures field inputs from staff who do not live inside Access daily - site walk data, checklist responses - and lands those submissions in tables the dashboards already read.
Modules in Production
Outlook-Triggered Bid Intake
Qualifying emails create proposal records and start approval routing without manual re-entry from the inbox.
External Attachment Store
Files live on shared paths; Access holds links only. The database stays lean while staff open documents from the proposal screen.
Self-Updating Front-End
Launch-time version checks deploy the current Access UI automatically - no email attachments to install.
Role-Based Outlook Alerts
Approvals, kickoffs, and status changes notify the right mailbox so teams stop forwarding threads for context.
Live Pipeline and Delivery Boards
Submitted, won, lost, and kicked-off counts plus project completion percentages on one management view.
Scheduled Excel Workbooks
Sales forecast and manpower planning exports regenerate from live data - leadership stops waiting on Friday manual compiles.
Screens From the Live System
The carousel below shows the production database this EPCM firm runs today - main tracking forms, Microsoft Forms tie-in, and the automated notification panel coordinators use to push status updates.
The primary form set is where PMs maintain active jobs and proposal coordinators move bids through approval. The Microsoft Forms screen connects external field input into the same tables. The notification module is what sends Outlook alerts when a record changes state - won, lost, delayed, or ready for kickoff.
MS Access Project Tracking Main Forms
Microsoft Forms Integration
Automated Notification System
Twelve Months Later
Proposal routing now finishes the same day a qualified request hits the system. Coordinators stopped rebuilding pipeline spreadsheets because partners read live dashboards instead.
The database file dropped below a gigabyte after attachments moved out - saves are instant again. Every user launches the current front-end; version mismatch tickets disappeared entirely.
Engineering staff got roughly 1,040 hours back in year one. Business development reported faster bid turnaround and better win rates once proposals stopped aging in email limbo.
“We used to burn days chasing proposal status in email threads. Now bids land in the database from Outlook, approvals fire the same day, and I open one dashboard before my morning standup. The hours we got back paid for the build - winning more work was the upside we did not model.
Stack and Integrations
Microsoft Access - proposal and project UI, dashboards, and coordinator workflows
VBA - Outlook automation, approval logic, version checks, and export routines
SQL Server recordsets - pipeline aggregations and multi-year project history queries
Microsoft Outlook - bid intake triggers and role-based status notifications
Excel automation - forecast and manpower workbooks generated from live tables
Should Your Firm Build Something Similar?
An Access-based delivery control center fits EPCM and professional services teams where email, Excel, and legacy Access files already overlap:
EPCM and A&E firms with Outlook-driven proposal intake
If bids start as email and end up in spreadsheets, you are paying coordinators to be human APIs.
Multi-discipline shops tracking both pipeline and active delivery
Partners need won/lost metrics and field progress in one place - not two reporting cycles.
Growing teams hitting Access file-size or version-drift limits
Past 1 GB with embedded attachments, or past 15 users on emailed front-ends, the architecture needs redesign - not more reminders to save locally.
Leadership spending 15+ hours weekly on status compilation
If Friday reporting is a manual export festival, automating from one database pays back fast.
If proposal tracking alone costs more than one full day per week, you are already funding a custom hub.
Questions We Hear From EPCM Teams
Why would an EPCM firm use Microsoft Access instead of a commercial PM platform?
Commercial platforms force EPCM workflows into generic project templates. This Texas firm needed proposal intake from Outlook, custom approval chains, KPI dashboards tuned to their bid pipeline, and Excel exports formatted for manpower planning - none of which mapped cleanly to off-the-shelf tools. Access let us build forms around how their business development and delivery teams already worked, with VBA handling the Outlook and Excel hooks.
How did moving proposal attachments out of the Access file help?
Embedding PDFs and drawings inside an .accdb ballooned the file toward the 2 GB ceiling - performance degraded and save operations slowed. We stored files on a shared network path and kept only the file reference in Access. Database size dropped from 1.8 GB to 720 MB, a 60% reduction, while staff still opened attachments from the same proposal record with one click.
What does the auto-update mechanism for the Access front end do?
As more engineers joined, emailing updated front-end files failed - people ran stale versions and wrote conflicting data. The application now checks a version table on launch and pulls the current front-end automatically. Version mismatch incidents went to zero because nobody depends on remembering to install an emailed update.
How fast can a firm like this expect payback on a custom Access build?
This client recovered 20 hours of coordinator labor every week - 1,040 hours in the first year - and shortened proposal routing from multi-day cycles to same-day turnaround. Combined with higher bid throughput, they reported 180% ROI in year one. Payback timing depends on how many hours your team currently spends chasing proposal status and rebuilding weekly reports.
Next step
Want similar results in your operations?
Book an Automation Opportunity Assessment. We map workflows and scope a practical build plan.
- No Onsite Visit Required
- No Technical Specification Required
- Assessment Before Commitment
- Clear Scope Before Work Begins
Questions before you book? Speak with our team at +1 385 386 3860
