The variation hiding in paragraph six
Scope does not usually change in a document titled “scope change”. It changes inside a consultant’s answer to a question about something else, and whether you get paid for it depends on somebody noticing that afternoon.
One RFI, followed through
A real shape of event, with what happens now beside what happens with the reading automated.
The response lands
The structural engineer replies to RFI-138 about a penetration through a beam. Nine paragraphs, two marked-up sketches attached. Paragraph six says the additional trimming steel is to be supplied and installed by the builder.
How it goes now
It goes in the RFI register as "answered". Somebody reads it properly on Thursday, or does not.
With the reading automated
The response is read on arrival, compared against the contract scope and the last issued drawing revision, and flagged: this answer changes what you are building. Sits at the top of the CA's list, not the bottom.
A draft variation exists
Not submitted. Drafted, with the RFI number, the clause it hangs off, the drawing revision, the paragraph quoted, and a placeholder for cost and time.
How it goes now
Nothing exists. If it is remembered at all it gets written up next week from memory.
With the reading automated
The CA opens a draft that is already 80% complete and either kills it or prices it. Two minutes instead of forty, and it happens the same day.
The trail is assembled
Every document that touches this change: the original RFI, the response, the superseded drawing, the site instruction, the meeting minute where it was mentioned in passing.
How it goes now
Assembled in month seven, under time pressure, when the variation is disputed.
With the reading automated
Assembled while it is happening, when everyone still remembers what was said and the emails are three clicks away.
Nothing is left behind
Every approved variation is reconciled against what actually appears in the progress claim.
How it goes now
Two of eleven get missed. It happens on most jobs and it is nobody's fault in particular.
With the reading automated
A short list: approved, not yet claimed. Cleared before the claim goes in.
Why this one is worth doing first
Unregistered variations are the clearest money on the table. The work gets built either way — the only question is whether it was captured in time to be claimable. That makes the value easy to measure: count the variations raised in the first three months against the same period on a comparable job.
It is also the least disruptive place to start. Nothing about how your team works has to change. The RFI still goes out the same way, the response still lands in the same inbox, and the register is still the register. What changes is that something reads the response the moment it arrives instead of on Thursday.
The CA still decides everything. They just decide it on day zero with the clause already in front of them.
What it needs from you
- Read access to the RFI correspondence. Wherever it lives — the platform, a shared mailbox, both.
- The contract and the current drawing set. Without the scope baseline there is nothing to compare an answer against.
- One CA who will use it on one job. Not the whole business. One person, one project, and a comparison at the end.