Module 01
Project Control Center
The screen the PM opens first. What's open, what needs you, every meeting, every document, the project in chat, all in one place, shown by role. The dashboard for the job: not a report about the project, the project.
The System
The complete project system.
Every piece of information on the job, including every selection, approval, decision, change, question and conversation, is collected, stored and managed in one place. Not the financials; those stay in your accounting system. Everything else, here.
Module 02
CC it on everything, and the inbox stops being the filing system. Every email on the job is read as it lands: what it says, who it's from, what it changes. It's filed to the project, handed to whoever it belongs to. When a reply is owed, it's drafted; you send it.
Module 03
Capture
The project is in the room. Invite it to meetings. It attends. Start Teams calls with the Clarity button. It hears them. Record on site from your phone. It files the walk. What was said is what's recorded. Three habits, nothing else to learn.
Module 04
The Ball
Every open item on the job: who has the ball, what they owe, since when. Nothing waits on someone remembering. Every morning the project opens the day with the three things that matter and what's been sitting too long. The ball is never dropped, because it's never only on a person.
Module 05
The Item
Every conversation on a project is about a physical thing: a tile, a faucet, a window, a slab. So the record is built around the item. The item schedule, the plans, the selections: what was chosen, by whom, where it goes, what it costs, what changed and why. One record per item. The system of record for what's being built.
Module 06
Site
On your phone. Who's on site, the punch items, the safety incident, what the framer said about Thursday, all recorded, sorted and filed into the daily log, the punch list, the safety report, before you're back in the trailer.
Module 07
Decisions
Every decision on the job, caught as it's made, in the call, in the email, on the walk, with who made it, when and why. The decisions still owed, and what's waiting on them. When someone says "I never agreed to that," the project already knows.
Module 08
Changes
Design changes happen; on a high end job, every week. The request, the revised drawing, the price, the approval, the sub who has to know. Each step is held until the next one's done.
Module 09
RFIs
The question asked on the walk becomes a drafted RFI: the drawing, the spec section, who asked, what they said. Every RFI on the job and where it really stands, from what the architect actually said back.
Module 10
Reporting
The owner's report. The weekly client update. "How are we doing on the schedule?" It's answered from the record, not from memory. Written by the project from what actually happened, reviewed by you, sent by you.
Module 11
Documents
Your company already has a project folder. Your team already works out of it. The project files what arrives on the job into your folder, in your structure, automatically. It reads and it adds. It never changes a document and never removes one. We fall into your filing. We don't replace it.
Integrations, including Procore, 365, SharePoint and the rest, have their own page.