Key takeaways
- Changes are agreed out loud and by email, but most contracts pay only against a signed change order.
- Unsigned changes become disputes at the final account, and undecided changes become delays on site.
- GeniOS joins site minutes, client emails and the change log, and raises each change with its value and deadline.
- Signature requests and reminders can be drafted by an agent, and nothing goes to the client until a person approves.
The problem
No building is finished exactly as drawn. A pipe clashes with a beam and must be rerouted. The client upgrades the lobby stone. The architect revises a façade detail. Each change should become a change order: priced by the contractor, checked by the cost consultant, signed by the client, then built and billed. In practice the order is often reversed.
Picture a Monday site meeting. The client's project manager hears that the chilled water line clashes on level 3 and says "go ahead, we will sort the paperwork". He confirms it in a short email. The site team starts the reroute that week. The quantity surveyor submits change order 14 for $38,000, and it sits in the client's queue. Meanwhile change order 19, an upgraded lobby stone with a ten-week lead time, has waited twelve days for a client decision.
Three months later the client PM has moved to another project, the email is buried, and the reroute is a line in a dispute. The stone decision came late, and the lobby finished after handover.
Why it slips today
The facts about one change sit with four different people.
| Where it lives | Who sees it | How it slips |
|---|---|---|
| Site meeting minutes | Site team and client PM | A verbal go-ahead never becomes a change order |
| Client and architect email | Whoever was copied | Approval by email is not the signature the contract needs |
| Change order log sheet | The quantity surveyor | Shows "submitted", not how long it has waited or why |
| Procurement and schedule | Purchase and planning | Lead times run out while the decision waits |
A monthly commercial review lists open change orders, but it rarely asks which ones block the site this week or miss this month's valuation. Project software tracks what is entered, not the promise made in a meeting.
The solution
GeniOS reads email, meeting minutes, documents and the project tools you already use, read-only to start. When a change needs a person, it sends one piece of intelligence with the situation, what to do, why, one owner and a date.
- Work started without a signed order. Changes agreed in a meeting or email that the site has begun but the client has not signed.
- Decisions blocking the schedule. Changes waiting on the client while a lead time or a site activity runs out.
- Value missing from the valuation. Approved changes not yet in this month's payment application.
- Notice deadlines. Time and cost claims that must be notified within the contract's notice period.
It is Decision & Approval Intelligence applied to construction changes.
See it on the whiteboard
One change agreed on site, signed before the month's valuation instead of argued at the final account.
Get CO-14 signed before the 25th valuation
How: send CO-14 for signature today with the client PM's email attached.
- Your tools. A client email says go ahead, the site minutes show work started, and the change log still says pending.
- GeniOS thinks. It sees $38,000 of work under way with no signature, and the valuation cutoff close.
- Intelligence. The project director gets one note: get the change order signed before the 25th.
- Delegated. A Reply Drafter writes the signature request with the email trail attached. Nothing goes out until she approves.
- Goal moves. The client signs. GeniOS sees the signed order and the goal moves.
How GeniOS thinks and plans
GeniOS forms the project's goals from the company's own documents: the contract, the cost plan, the programme and leadership emails. A common goal for a contractor: bill every approved change in the month the work is done.
For each change it connects four pieces. What happened: the client PM approved the reroute by email, and the site began work. The pattern: approval sits in email and minutes, not on the change order form; six other changes on this project look the same. The impact: unsigned work misses this month's valuation on the 25th and weakens the final account. The owner: the project director, who holds the client relationship.
Then it picks one next step: send change order 14 for signature today, with the client's own email attached. For change order 19, where the decision itself is late, the step is a decision request with the stone's order date. Agreements made in meetings are followed the same way as in Meeting-to-Execution.
How it delegates and gets it done
The owner answers with Delegate, Done, Later or Not relevant. Delegate hands the work to a person or an AI agent: the quantity surveyor to update the pricing, a Reply Drafter to write the signature request, a Scheduler to book a decision call with the client.
Nothing goes to the client, architect or cost consultant until a person approves it. Commercial letters carry weight, so the owner reads every draft.
Each item closes only on proof: the signed change order in the documents folder, the line in the payment application, the decision email from the client. Then the goal moves. GeniOS learns from each outcome. If one client signs faster after a call than after an email, it suggests the call first. When the money is due, the work continues in Cash & Payment Obligations.
How it reaches you
Intelligence arrives on its own in the GeniOS Mac app, from the menu bar, and on the web dashboard. A project director sees the few changes that need her this week, each with a value and a date.
You no longer chase the quantity surveyor for the log, read every set of minutes for verbal instructions, or decide which of forty open changes matters most. Nobody has to tag anything or write a prompt.
A worked example
The company, names, dates and numbers in this example are made up to explain the idea.
A 450-person general contractor in Dubai is building a 16-floor office tower on a $62 million contract. Forty-one change orders have been raised so far, and seventeen are open, worth about $1.3 million.
On 9 November the client's project manager agrees in the site meeting to reroute a chilled water line on level 3, and confirms by email that afternoon. Work starts on the 11th. The quantity surveyor submits change order 14 for $38,000 on the 12th, and no reply comes. Separately, change order 19, upgraded lobby stone worth $96,000, has waited twelve days for a decision; the stone must be ordered by the 30th.
On the 17th Meera, the project director, gets one note. Change order 14 is under way and unsigned, the valuation cutoff is the 25th, and the client's email approval is attached. Six more changes, worth $210,000, were approved by email and never signed.
Meera delegates the signature request to a Reply Drafter and approves it with one line added. She asks the quantity surveyor to bundle the other six into one request. The client PM signs change order 14 on the 23rd, and it goes into the November valuation. GeniOS closes the item on the signed order. A second note, to the commercial manager, gets the stone decided by the 27th, before its order date.
How to measure it
- Days from a change being agreed to a signed change order.
- Value of work done without a signed order, at each month end.
- Share of approved changes billed in the month the work was done.
- Change decisions that arrived after the material lead time.
Where it applies
These are application areas, not current deployments: general contractors, specialist subcontractors, fit-out firms and developers managing their own construction.
- Domains: Operations, Finance, Legal & Compliance, Procurement
- Industries: Real Estate & Construction
- Roles: Executives, Managers
Questions about change order approvals
Can GeniOS approve or price change orders?
No. Pricing and approval stay with your quantity surveyor, your project director and the client. GeniOS makes sure each change reaches the right person in time.
How does it find verbal instructions?
It reads meeting minutes and the emails that follow them, alongside the change log. When work is agreed but no change order matches, it raises it.
Will the client see anything from GeniOS?
Only what your team approves and sends. Drafts are written for your owner, and nothing goes out until a person approves it.
Does it help subcontractors too?
Yes. A subcontractor chasing a main contractor for signed variations has the same problem. The approach is the same from either side of the contract.
Status
Exploring This is an application area we are exploring with early customers. If agreed changes keep turning into unpaid work, book a call and we will show how it would work on your own projects, starting read-only.