A home construction agreement runs to dozens of pages. The facts a client wants to check, and the facts the project manager and accounts need at handover, sit in different schedules. At Viya Constructions someone read the agreement and retyped them by hand. The workflow reads the PDFs, matches the two contracts, checks the payment stages to 100 percent, and waits for a person to type the amount and confirm. Documents only: nothing is written to ProjectSignal today.
[01]What changedViya Constructions
Counts are from the workflow's own rules and tests.
In a home build, the payment stages in the agreement are the customer's own definition of value delivered. What sales agrees there becomes the collection plan and the milestone sequence. A summary that loses one stage at a page break still looks finished, which makes it worse than no summary. So this workflow is built to refuse.
Where it stands. Live, and recorded as handed over to Viya's team on 5 October 2026. This is not the priced quotation, which comes from the estimate check. It is the summary of what the agreements say.
[02]Why this is hardViya Constructions
The labor agreement runs to 48 pages. The scope of works alone covers about ten. The property sits in one schedule, the payment stages in another, the exclusions at the end of the scope.
Labor and material supply are separate agreements. Neither refers to the other. Only the property schedule shows they are for the same house.
A car porch roof area in the scope reads like the plot area. A second exclusions clause, about warranty misuse, sits twenty pages from the scope exclusions. The contractor is a named party, and is not the client.
The payment schedule can run across a page break. Lose one row and the remaining stages still read like a complete schedule.
The client wants one document they can check against the agreement. The project manager takes over the scope list and the payment stages. Accounts needs the stages and what each one collects. Usually one person has read the whole agreement, and everyone else waits for them.
[03]How it worksViya Constructions
The AI reads. Fixed logic matches, adds and splits. A person types the one figure no document contains.
Type / and pick Quotation summary. The labor agreement is required, the material supply agreement optional. Files are recognized by their wording, not by upload order. Any signed-in staff member can run it.
Owner's name, six property fields, every payment stage with its percentage, the scope rows, the scope of elevation, the room-by-room electrical points and the exclusions. Values are copied as written. What the agreement does not state stays empty.
The property schedule and the materials list: work, item and market price with its unit. It is a rate card, not a bill of quantities, so nothing is added up.
Same survey number (the plot's land record number) and same owner name: same project. If not, the material rates are left out, with a warning. Same project but a different village or extent: the run stops.
If the percentages do not come to 100, the run stops and reports the total it found. Nothing is adjusted to balance.
Six steps, from client and property to material rates. The scope step asks the reviewer to check nothing was dropped at a page break. A misfiled heading can be corrected there. On confirm, the checks run again.
One PDF. Each stage amount is the typed amount times its percentage, in whole rupees. It ends with where each figure came from and every warning raised.
Each agreement states its own contract price. The amount being quoted is in neither, so the field starts empty and no summary is produced until a person types it. A default would put a number in front of a client that nobody chose.
The payment stages read from the labor agreement add up to 90 percent, not 100. 8 stages were read; a stage was probably dropped at a page break or a percentage misread. Nothing has been adjusted to make it balance.
[04]Connected to ProjectSignalViya Constructions
As of late October 2026.
Nothing is written to ProjectSignal, so there is nothing to preview on that side. Workflows that do write, such as the milestone plan import, write as the signed-in person, through the platform's own validation, after a preview.
What is designed next. When an agreement is signed, the same kind of reading would carry scope, contract value, built-up area and payment stages into the project record in ProjectSignal, from a review card, and lead to a detailed schedule the customer approves. That is a design: it needs new fields on the project, and none of it is built. The design keeps this workflow's rule: payment stages must balance to 100 percent.
The agreements workflow produces both contracts from one scope of work. This workflow reads them for the client's summary, and the critical path schedule reads the construction agreement for the plan.
[05]Who decides whatViya Constructions
The same split holds in every workflow we build.
The change is applied to the confirmed inputs, validation runs again, and the PDF gets a new version.
[06]More detailViya Constructions
Ten conditions stop the run. Six more raise a warning that prints on the summary.
Every figure was copied from the signed agreement or typed by your own people. The closing section says which.
Anyone in the role can produce the summary. The facts are read, not retyped, and the reviewer checks what was read.
Stage amounts come from the agreement's own percentages and total the quoted amount to the rupee.
The AI reads named fields only. Matching, totals, validation and layout are fixed logic, covered by 78 automated tests.
To start we need two or three signed agreements, the summary your team made from one, one person who owns that job, and thirty minutes a week while the first version runs. Your templates will differ from Viya's. The rules get fitted to yours.
[07]Where this fitsViya Constructions
Send us one signed agreement and the summary your team made from it. We will show you how the job runs today and what a first version would look like. Start with one workflow. You only pay if it works.