Every new project at Viya Constructions needs two contracts: a labor construction agreement and a material supply agreement. Filling two long approved documents by hand invites copy errors. Now one scope of work and the client details produce both, with identity and price fields checked and payment stages that must total 100 percent. It produces documents only and writes nothing to ProjectSignal today.
[01]What changedViya Constructions
Figures from the workflow's own rules and templates.
Viya contracts directly with the homeowner by negotiated agreement, not by tender. One scope document drives both contracts so the two cannot drift apart, and balanced payment stages keep collections in step with the work. The stages a client signs become the collection plan and the milestone sequence for the job.
It first shipped on 24 September 2026 and was handed over to Viya's team on 5 October 2026.
[02]Why this is hardViya Constructions
Each project has a labor construction agreement covering labor, workmanship and supervision, and a material supply agreement with a separate supply company. Owner, land, material rates and payment stages must read the same in both.
The approved templates run to 48 and 18 pages. Owner details, the property schedule, payment stages, the scope list, room-by-room electrical points and the material rate card are each placed by hand, and each is a chance for a copy error in a legal document.
The scope of work, the room-by-room electrical points and the material specifications with rates must reach the contract as agreed, with brands, dimensions and quantities intact.
Stages are tied to physical progress, from agreement sign-off through plinth beam and each roof slab to key handover. If they do not total 100 percent, the contract and the collection plan disagree from day one.
[03]How it worksViya Constructions
The person preparing the contracts starts the job in Bleno by typing "/" and picking Construction agreements.
The scope of work goes in as the original Word document. The owner, the land and the two prices are typed in the same message.
The AI reads the scope rows (item, description, specification), the electrical points for each room, the material specifications with rates, and every exclusion. Rows keep the document's order and are not summarized. Its instruction is to add nothing the document does not print.
Empty rows are dropped. Defaults are filled: today's date, the standard contract period and the 11 standard payment stages. If no scope rows or no material rates were read, a warning says so.
Owner name, relationship (son of, daughter of or wife of), parent or spouse name, address, ID number and email. Then district, taluk (sub-district), village, local body, survey number and extent (plot area). Entered once and used in both contracts. The card asks the person to check them against the client's identity records.
The labor price and the material price belong to separate contracts, and both must be confirmed. Stage rows can be edited, added or removed. The card will not move on until they total 100 percent.
Three more steps show the scope rows, the electrical points by room and the material rates that were read, with exclusions kept apart from the scope rows. Nothing reaches a contract until the card is confirmed.
Every field is checked again and each template is verified as the approved file. Confirmed values go into set places, schedules flow across the template's schedule pages, unused schedule pages are removed and the pages are renumbered. Two PDFs appear in the chat.
The 48-page labor agreement and the 18-page material supply agreement are the background of every run. Fixed logic writes confirmed values into set places on those pages and nowhere else.
[04]Connected to ProjectSignalViya Constructions
This workflow does not touch ProjectSignal today. The scope, contract value and payment stages sit in the two PDFs, and the project team re-keys what it needs into ProjectSignal after signing.
The next connection is designed, and none of it is built. When a client signs, the scope, contract value, built-up area and payment stages would be carried into the project record, linked to the site and the client, with a detailed schedule for the customer to approve. ProjectSignal needs new fields first. The design holds two rules: the stages balance to 100 percent, and the customer approves the schedule before it becomes the baseline.
That write would be confirmed on a review card and made the way Bleno workflows at Viya write: as the signed-in person, within their permissions, previewed first, through the platform's own validation.
The documents already feed the next jobs. The quotation summary reads the labor agreement and, if attached, the material supply agreement. The critical path schedule reads the construction agreement. The milestone plan import is where the project's milestones reach ProjectSignal.
[05]Who decides whatViya Constructions
The AI reads the scope of work, carries the typed details onto the card, and writes a closing message that states the owner and the two confirmed prices.
[06]More detailViya Constructions
Wording, drawings and layout come from the approved file on every run. Only this client's fields and schedules change.
The owner and the land are entered once and read the same in both contracts.
The stages that become your collection plan must total 100 percent, and both prices must be whole, confirmed figures.
The AI reads one document. Checks, formatting and placement are fixed logic, and the workflow ships with 14 automated tests.
To start we need your approved contract templates, one real scope of work, and one person on your side who prepares contracts today. Then thirty minutes a week to review what real use shows.
None of these is live yet.
[07]Where this fitsViya Constructions
Send us your approved template and one real scope of work. 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.