Spreadsheets, generic project management platforms, and ad-hoc SharePoint lists solve coordination problems. Utility capital programs have a structurally different problem — and it compounds every year you let it slide.
When a project manager leaves, their cost tracking, change order log, and RFI history leave with them. The next person starts from scratch.
No single source of truth for executed vs. pending change orders means your board sees a number that doesn't match what your PM tracks.
Operations inherits assets with no warranty dates, no O&M references, and equipment records that don't match what was actually installed.
Federal funding audits require documentation trails that spreadsheets and shared drives can't produce on demand. Disallowed costs are real.
Three people spend two days pulling numbers from five different places to produce a report that's already outdated by presentation time.
Without structured cost event tracking, potential claims accumulate in informal notes until they surface during or after construction.
| Capability | Spreadsheets & Generic Tools | AMP Essentials Purpose-Built |
|---|---|---|
| RFI tracking tied to contract documents | ✕ Manual log, no document traceability | ✓ Structured RFI log linked to drawing revisions and responsible parties |
| Change order workflow with approval chain | ✕ Email routing, no audit trail | ✓ Configurable approval chain matching your agency's authority matrix |
| Pending change order cost exposure | ✕ Not tracked until executed | ✓ Real-time pending exposure visible alongside approved contract value |
| Submittal register with review tracking | ~ File folders, no workflow | ✓ Submittal register with scheduled vs. actual review dates and aging alerts |
| Cost event logging (differing site conditions) | ✕ No structured capture before disputes form | ✓ Cost events documented at occurrence with supporting records attached |
| Portfolio-level CIP dashboard | ✕ Manual assembly from multiple spreadsheets | ✓ Real-time roll-up across all active projects — board-ready on demand |
| Structured closeout process | ✕ Checklist in email, no enforcement | ✓ Closeout workflow required before project closure; CMMS-ready data output |
| CMMS asset handoff data | ✕ PDFs in a zip file, manually re-entered | ✓ Structured asset records pre-populated from project data, ready for import |
| Federal funding documentation (IIJA / SRF) | ✕ Ad-hoc file organization, fails audit | ✓ Funding source attribution and documentation trail per reimbursement requirement |
| Role-based access (contractor / engineer / owner) | ~ Folder permissions only | ✓ Granular role-based access — contractors see their data, owners see everything |
| Alternative delivery support (GCCM / PDB / DBB) | ✕ Generic templates require full rebuild per delivery method | ✓ Delivery method-specific workflows built in — no customization required |
| Board-reportable audit trail | ✕ No automatic logging of changes | ✓ Every action logged with user, timestamp, and before/after state |
| Built by utility capital program practitioners | ✕ Built for general project management | ✓ Designed by practitioners with 20+ years of owner-side utility experience |
| Runs in your existing M365 environment | ~ Requires separate system and integration | ✓ SharePoint Online or Cloud SaaS — integrates with your M365 stack natively |
Patterns from utilities that reached out after their current approach failed them
A mid-size water utility ran its entire GCCM program in a shared Excel workbook. When the senior PM left, the file had 47 versions across three SharePoint folders. No one knew which was current. Change order exposure was understated by $1.2M at the board presentation.
A utility received DWSRF funding for a water main replacement program. During the reimbursement audit, they couldn't produce Davis-Bacon compliance records for 34 contracts. The documentation existed — scattered across email, PDFs, and three shared drives — but not in a format the auditor could verify. $800K temporarily disallowed.
A wastewater treatment plant expansion closed out with 200+ equipment items. The contractor delivered O&M manuals in a ZIP file and as-builts on a hard drive. Two years later, operations staff were manually searching PDFs for warranty information on equipment that had failed — warranty dates had never been recorded in the CMMS.
Not just software. Built by people who managed these programs from the owner's side for 20 years.
Public utilities answer to ratepayers, boards, and regulators — not shareholders. Every workflow in AMP Essentials is designed to produce documentation that holds up in a board meeting, a state audit, or a legal dispute.
AMP Essentials runs on SharePoint Online inside your existing Microsoft 365 environment, or as a cloud SaaS. No new login for your team. No IT procurement process. Your M365 investment already pays for the infrastructure.
GCCM, Progressive Design-Build, and Design-Bid-Build have fundamentally different contract structures and documentation requirements. AMP Essentials has distinct workflows for each — not a generic template your team has to bend into shape.
AMP Essentials captures CMMS-ready asset data throughout the project — equipment data from approved submittals, warranty dates from substantial completion, O&M references from the document library. Operations receives a complete asset, not a ZIP file.
The team configuring your AMP Essentials deployment has managed utility capital programs from the owner's side. They know what a capital programs director needs at 6 AM before a board meeting — because they've been that person.
AMP is an Oregon and Washington MBE certified firm. For utilities with diversity and equity program requirements in their capital programs, AMP brings certified expertise — not a workaround.
Book 30 minutes with our team. Show us how you're currently tracking your capital program — we'll show you exactly what changes and what doesn't.