Labor contractors on Viya Constructions' sites quote in Malayalam, Kerala's language, often by hand. The sample work orders we started from were drafted in English, put through an online translator and assembled by hand. With this workflow a site engineer photographs the quotation and the scope, confirms what was read, and issues a Malayalam work order whose payment stages add up exactly. That part is live. Work orders raised from the labor budget, with a balance in ProjectSignal, are in build, not live.
[01]What changedViya Constructions
Figures from the workflow's own rules.
Almost all the labor on Viya's sites is supplied by labor contractors: about thirty of them across more than 40 live sites. On a labor-only contract, labor is effectively the whole cost, and the work order is where it is committed.
The workflow first shipped on 1 October 2026 and is listed as handed over in the 5 October implementation record. It was reworked up to 17 October and is on its third version. It writes nothing to ProjectSignal. The next step, which Viya asked for on 1 November, is planned and in build, not live.
[02]Why this is hardViya Constructions
Contractors quote in Malayalam, often handwritten, and many quotations reach the office as phone photos. A work order the contractor cannot read is one they cannot be held to.
Some quotations price every line, others give one lump sum. Labor is paid in parts as the work is done, so the amount must be split into stages. A split that does not balance is a dispute waiting to happen.
Work orders are typed site by site, often after the contractor has started, at the contractor's quoted rates. Nothing compares a rate with what the estimate allowed.
What is still payable is rebuilt by hand from the PDF, the payment messages and the accounts books, when a contractor asks or a dispute starts. Overpayment is hard to recover. Underpayment stalls the crew.
[03]How it worksViya Constructions
A site engineer or other project staff types "/" in Bleno and picks the work order workflow. Nothing has to be attached to start.
Work order number, issue date and site details, all required.
Two slots, each a photo or a PDF. Either can be left empty and typed by hand.
The scope is read as rows of item, material specification and work, plus any notes printed under it. Each priced quotation line is read as printed. Malayalam stays Malayalam.
If either document names a contractor, the card asks: is this the contractor? Name and full postal address are required.
The AI suggests the stages, usually 6 to 12, each a distinct piece of the work in the order it is done, weighted by the labor it takes. Fixed logic scales them to exactly 100 percent and recalculates every amount.
Any line can be corrected. Read again re-reads a document. Regenerate takes an instruction such as "only 5 items, and leave out the handrail". The card will not confirm until the percentages total 100.
Start, expected duration and completion, in plain text. Required.
Every required field is checked again. The work order is built in Malayalam from the confirmed values, with the 19 fixed terms and signature lines for manager and contractor.
The AI may propose how to divide the quotation. Fixed logic decides what is printed: percentages to one decimal place, the last stage taking the remainder, every amount recalculated from the quotation total to the paisa, a hundredth of a rupee.
[04]Connected to ProjectSignalViya Constructions
This workflow does not touch ProjectSignal today. ProjectSignal holds the vendor register: which contractor holds which site, and whether the work order there is awarded, rates agreed or not awarded. It holds no value and no payments. Weekly payments are worked out from the payment sheet with no record of what the work order allowed.
On 1 November 2026 Viya asked for that to change. This part is planned and in build. None of it is live. What follows is the design. Underneath it are the work order above, the vendor register and the weekly contractor invoices.
The planning engineer or project manager selects the work, say ground floor masonry, from the site's labor budget, which comes from the estimate through Viya Estimator, also in build.
The contractor is picked by vendor code. A new contractor gets a code automatically. The type is quantity rate, square-foot rate, lump sum, or labor rate card: man-days at a daily rate per category. The budget rate or amount shows beside what is entered.
Standard clauses for that type of work attach from a clause library. Scope fills in from the agreement and the site's scope document, and can be edited.
At or below budget it goes ahead. Above budget it needs an amendment or a higher approval. Work outside the labor budget needs the project lead. It is issued in Malayalam where the contractor needs it and shared by WhatsApp or email. Its value enters the contractor's ledger for that site, and the vendor register shows the site as awarded.
Accounts records every weekly payment against the work order, with date and reference. Still payable is the value, after approved amendments, less total paid, shown per site and per contractor across sites.
In the plan, sites already running under PDF work orders are registered first, with value and payments to date. Each opening balance shows as unconfirmed until accounts confirms it against the books, so the balance covers every site, not only new awards.
It is designed to write the way the Bleno workflows that already write to ProjectSignal do: as the signed-in person, within their permissions, previewed first, through ProjectSignal's own validation.
[05]Who decides whatViya Constructions
If the quotation gives no unit, quantity or rate, the work order prints none. The AI is told never to calculate a missing figure or infer a unit.
[06]More detailViya Constructions
The same approved terms on every work order, in the contractor's language, with stages that add up. In build: each one checked against the labor budget before issue.
Site staff photograph what the contractor gave them, confirm what was read, and get the Malayalam work order back.
In build: every weekly payment recorded against its work order, and a flag before a payment goes over the value.
Percentages and amounts are fixed logic. Terms are fixed, versioned text. The workflow's 43 automated tests include scaling to 100 percent, amounts summing to the total and the terms being stored with the work order.
To start: three real work orders with their quotations, your standard terms, one owner on your side, and thirty minutes a week.
[07]Where this fitsViya Constructions
Send us three real work orders and the quotations behind them. We will show you how they would be read, balanced and issued. Start with one workflow. You only pay if it works.