Three people can do the job. Everyone else waits for them.
In a construction company, a few people hold the work that makes or loses money on every project. None of it is written down in a way anyone else can use.
One person reads the agreement and knows what the company has actually promised. One person builds the schedule and knows which task controls the finish date. One person turns the weekly payment sheet into invoices. When they’re busy, everything waits. When they leave, the method leaves with them.
More software doesn’t fix this, because the software has nowhere to read the method from.
Start where the work waits longest. Write the method down. Then build it.
Project management first
The longest queues were in planning: schedules, milestone plans and readiness checks. So that’s where we started, before moving into billing, contracts, quality and site work.
The method, not just the output
We sat with the people who do each job best and wrote down exactly how they do it: the steps, the rules, the templates, and what a correct result looks like.
Connected, not bolted on
Workflows read and write through the company’s own project management system, using its own validation. Nothing works around it.
Every result is confirmed
Each workflow stops for a person to check and correct the details before a document is produced or a record changes.
What each one takes in, and what comes out.
Each workflow is started by typing “/” and its name. Some update the project management system directly. Others produce documents and change nothing in it.
Project management
| Workflow | Takes in | Gives you |
|---|---|---|
| Critical path schedule | A signed construction agreement | A provisional schedule: work breakdown, activity network, critical path and total working days, as PDF and Excel, plus a list of missing information |
| Import a milestone plan | A milestone plan (PDF or spreadsheet) | New project plans and milestones in the project management system, previewed row by row before anything is created |
| Milestone readiness | A project plan and one milestone | The readiness checklist answered one question at a time, each answer with a reason, saved as a new revision |
| My projects | Your name and a date range | Your milestones due in that range, with daily labor counts you can update |
Billing
| Workflow | Takes in | Gives you |
|---|---|---|
| Create invoices | The weekly payment sheet | Numbered invoices, one page each, with deductions and amount due, as PDF and Excel |
| Design phase invoice | Client, project and amount | The company’s approved one-page design invoice |
Contracts and quotations
| Workflow | Takes in | Gives you |
|---|---|---|
| Quotation summary | The labor agreement, and optionally the material supply agreement | One quotation summary: client, payment stages, scope, elevation, electrical points and material rates |
| Construction agreements | One scope of work document and the client details | Both contracts for the project, built from the company’s approved templates |
Quality and site
| Workflow | Takes in | Gives you |
|---|---|---|
| QA checklist workbook | A scope of work | A controlled quality checklist workbook for that project, with a reason recorded for every checklist included or left out |
| Contractor work order | Site and contractor details, and the contractor’s quotation | A complete work order, built step by step, in the language the contractor works in |
The AI reads. Fixed logic calculates. A person confirms.
Every workflow follows the same rules. That’s what lets a site engineer or an accounts assistant trust the result.
- It reads, and doesn’t guessOnly the fields it’s asked forThe milestone import reads six columns: milestone, site, owner, next milestone, date and amount. If a value is missing, the cell stays empty.
- Fixed logic does the mathNever the AIInvoice amounts, deductions, schedule dates and payment stages are calculated by fixed logic. The quotation summary checks that payment stages add up to 100 percent.
- A person checks firstReview cardsBefore an invoice is made or a milestone is created, the details appear on an editable card. Nothing continues until someone confirms it.
- It previews before it writesNo surprises in the systemThe milestone import does a dry run first: row by row, what would be created, skipped or blocked. If an owner’s name doesn’t match a registered person, it suggests the closest match before anything is saved.
Documents are built from the confirmed values, never written freehand by the AI. Every figure on an invoice or schedule is a figure someone reviewed.
A signed agreement goes in. A provisional schedule comes out.
This is the workflow that used to wait for one planner. It never adds work the agreement doesn’t contain, and it always calls the result provisional, not an approved baseline.
- Read the agreementProject details and the scope headings exactly as the agreement writes them, including exclusions.01
- Map scope to activitiesPick the activities the agreement supports from a reference library, repeat the structural cycle for each floor, and build a work breakdown to the ISO 21511 standard.02
- ReviewThe project details, work breakdown and activity data appear for checking. Everything is editable.03
- Check and calculateLook for broken links, loops and missing durations. Then work out the earliest and latest dates for every task, and the slack each one has.04
- ProduceA schedule PDF and an Excel workbook, with total duration in working days, the critical chain of tasks and the near-critical work.05
- ReportOnly the calculated values, plus a list of information that’s still missing.06
Owners know the critical path by instinct. What they usually can’t get is a current answer, on a Tuesday, for a live project, without asking the one person who keeps the schedule. Now anyone in the role can produce it.
14 workflows, across several departments, mostly in project management.
Project management came first because that’s where the work waited longest. Billing, contracts, quality and site operations followed, and each new department builds on the same rules and the same connection to the company’s system.
One thing we learned early: matching names is harder than it looks. A project system that recognizes a project by its name and owner will happily create a duplicate when a name is spelled slightly differently. So the import now suggests the right registered person before anything is created. Details like this are most of the difference between a demo and a workflow a company can rely on.
Their rules are theirs. The shape of the work is the same everywhere.
Every contractor has its own templates, rates, suppliers and payment stages. None of that carries over, and it shouldn’t.
What does carry over is the shape of the work. A signed agreement that has to become a schedule. A payment sheet that has to become invoices. A scope that has to become contracts and quality checklists. These are the same jobs in every construction company, done by two or three people who are always busy.
Specific AI holds the method, whoever’s method it is.