Hey {{first_name | default: "there"}},
You already have a version of this system. It's just spread across six files, two email threads, a whiteboard photo, and a log your superintendent built three jobs ago that nobody fully understands.
The RFI log doesn't talk to the CO log. The CO log doesn't talk to the pay app. When an owner asks what the current projected contract value is, you're opening three spreadsheets and doing math in your head.
That's not a technology problem. It's a design problem.
THE LESSON
I've watched good PMs lose disputes they should have won because their documentation was a collection of logs instead of a system.
The RFI was real. The time impact was real. But when it came time to show that RFI-017 is why CO-004 happened, which is why the pay app shows a $40K variance — that thread didn't exist anywhere. Every piece was in a different place. Nobody had connected them.
The PM who has a system where RFI-017 already cross-references CO-004, where the CO log already shows the updated contract value, where the pay app already flags the affected SOV line — that PM wins that conversation in five minutes. The PM rebuilding the story from memory loses it.
Here's how I think about the design question: every piece of information on a project touches at least two other pieces. An RFI touches a schedule activity and potentially a CO. A CO touches the contract value and the pay app. A submittal touches a long-lead item and a schedule activity. When you're setting up your tracking system, the question to ask is: when this piece of information changes, what else has to update? That's the connection that needs to be built in.
AI is genuinely useful at this layer — not for building the spreadsheet, but for thinking through the connections before you build it. Describe your project structure to Claude and ask it to map what data points need to talk to each other. You'll surface connections you hadn't thought of. Then build them in from the start, when it costs nothing, instead of discovering them mid-project when you need them and they don't exist.
THE TOOL
The PM Edge Project Tracker — an Excel workbook from project setup to closeout. 14 work tabs plus an auto-populating Dashboard and a How-to-Use guide. The connections are already built in.
The RFI log has a CO cross-reference column. The CO log has a running contract value that updates when COs get approved. The pay app tracks lien waivers by sub and flags when a check is going out without one. The risk register has a pre-filtered owner report view. These took multiple projects to get right. You get them on day one.
14 work tabs: Project Directory & Roles / RACI Matrix / Master Schedule / 3-Week Look-Ahead / Submittal Register / RFI Log / Change Order Log / Pay Application Tracker / Risk Register / Planning Tasklist / Safety Log / Punch List / Meeting Minutes Log / Closeout Checklist
Plus: A live Dashboard that recalculates every overdue flag and days-open count the moment you update the as-of date — and a How-to-Use guide that explains the system so a junior PM can run it on day one.
Every tab comes pre-loaded with sample data from a fictional mid-project commercial building. You can see how the connections work before you touch it.
No Smartsheet subscription. No Procore license. Just Excel.
$49. One-time. Lifetime updates.
Already have the Toolkit? Bundle both for $69.
INDUSTRY PULSE
On my radar:
• Construction software consolidation is accelerating — The major platforms are buying point solutions and bundling them into subscriptions. If your workflow depends on a standalone tool, the odds are rising it gets acquired and repriced within 18 months. Owning your data in a format you control is worth something.
• Excel isn't going anywhere — Despite years of "spreadsheets are dead" predictions, Excel remains the most-used project management tool in construction by a wide margin. The PMs winning with it have built systems. The ones losing with it are still on disconnected logs.
• The $9/month tool becomes a $90/month tool — Procore, Autodesk, and Smartsheet have all followed the same arc: launch low, raise prices after the user base is locked in. A one-time purchase is a different economic model entirely.
Forward this to a PM who's been meaning to fix their tracking system for the last three jobs.
— Jesse
The PM Edge | pmedge.io