TGH Tech
Case study · Workflow 16 of 20 · Buy and build · Live

A photographed quotation goes in. A complete work order comes out, in the language the contractor reads.

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.

Client
Viya Constructions
Department
Site execution, project management
Starts from
A photo or PDF of the contractor's quotation and the scope of work
Gives you
A complete work order PDF in Malayalam
Connected to
Documents only today. ProjectSignal record and balance in build, not live.
Status
Live. Document workflow live and handed over. Budget check, record and balance in build, not live.

[01]What changedViya Constructions

The work order is written in Malayalam, from the contractor's own quotation. Its payment stages total the quoted amount, exactly.

Before

Draft in English, translate, assemble by hand.

  • Drafted in English, then put through an online translator
  • Contractor details and quotation typed in from a phone photo
  • Payment schedule assembled by hand
  • After issue: a PDF, with no record of value or payments
Now

Photograph it, confirm it, issue it.

  • Malayalam stays Malayalam. The terms are fixed Malayalam text
  • Contractor, quotation and scope read from the photos, confirmed on a card
  • Payment stages total exactly 100 percent and the quoted amount
  • In build: a record in ProjectSignal with value, payments and balance
  • 6 to 12
    payment stages usually suggested, in the order the work is done
  • 100.0
    percent: what the stages always total
  • 19
    fixed Malayalam terms, word for word on every work order

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

The work order is the commitment behind every weekly payment. Today it is a PDF with no balance.

  1. 01

    Quotations arrive in Malayalam, on paper

    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.

  2. 02

    One total has to become stages

    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.

  3. 03

    Rates come from the quotation, not the budget

    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.

  4. 04

    A PDF has no balance

    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

Two photos, four confirmations, one work order.

A site engineer or other project staff types "/" in Bleno and picks the work order workflow. Nothing has to be attached to start.

  1. 01Site engineer confirms

    Enter the site details

    Work order number, issue date and site details, all required.

  2. 02Site engineer

    Photograph the scope and the quotation

    Two slots, each a photo or a PDF. Either can be left empty and typed by hand.

  3. 03The workflow

    Read both documents together

    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.

  4. 04Site engineer confirms

    Confirm the contractor

    If either document names a contractor, the card asks: is this the contractor? Name and full postal address are required.

  5. 05Fixed logic

    Split the quotation into payment stages

    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.

  6. 06Site engineer confirms

    Review quotation, scope and split

    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.

  7. 07Site engineer confirms

    Add the work schedule

    Start, expected duration and completion, in plain text. Required.

  8. 08Fixed logic

    Build the work order

    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 split is a suggestion. The total is not.

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.

  • No usable suggestion: shares are estimated per scope item. If that fails too, the split is equal
  • The card says which of the three it used
  • Change a percentage and the amount follows. The amount cannot be typed
Payment split · Site B · painting labor
1 · Ceiling, primer coat8.0 · 14,400
2 · Ceiling, two coats12.0 · 21,600
3 · Walls, putty, primer22.0 · 39,600Edited
4 · Walls, two coats24.0 · 43,200
5 · External, all coats28.0 · 50,400
6 · Handrail and touch-up6.0 · 10,800Takes the remainder
Total100.0 percent · 1,80,000 rupeesAdds up
Illustrative. Made-up site and figures: percent of the quotation, then rupees.
What the contractor receives
സൈറ്റ് വിവരങ്ങൾSite details
കരാറുകാരന്റെ വിവരങ്ങൾContractor: name, address, contact
ജോലിയുടെ ക്വട്ടേഷൻQuotation of work, with total
ജോലിയുടെ വ്യാപ്തിScope: item, material specification, work
പേയ്മെന്റ് ഷെഡ്യൂൾPayment schedule, with totalsBalanced
വർക്ക് ഷെഡ്യൂൾWork schedule
നിബന്ധനകളും വ്യവസ്ഥകളുംTerms and conditions: 19 clausesFixed text
മാനേജർ · കോൺട്രാക്ടർSignatures: manager, contractor
Illustrative. The work order's section headings as printed, with their meaning in English.

[04]Connected to ProjectSignalViya Constructions

Today the work order is a document. The record, the budget check and the balance are in build.

  1. Reads

    From ProjectSignal today

    • Nothing. Site and contractor details are typed or read from the photos.
  2. Does

    What happens in between

    • Reads the scope and the quotation
    • Balances the payment stages
    • Prints the fixed terms
    • Builds the PDF
  3. Writes

    To ProjectSignal today

    • Nothing. The work order is a PDF in Bleno.

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.

In build: the work order starts from the labor budget.

  1. 01Planning engineer or PM

    Pick the work from the labor budget

    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.

  2. 02Planning engineer or PM

    Pick the contractor and the type

    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.

  3. 03Planning engineer or PM

    Attach clauses and scope

    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.

  4. 04Approver confirms

    Approve, issue, register

    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.

  5. 05Accounts confirms

    Record each weekly payment

    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.

Contractor ledger · Site BIn build
Painting laborValue 1,80,000 · paid 1,08,000 · payable 72,000Within value
Tiling laborValue 2,40,000 · paid 2,52,000 · over by 12,000Over value
Illustrative. Made-up figures, in rupees. This view is in build, not live.

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.

The chain, once built.

  1. Estimate and labor budget
  2. Contractor work order
  3. Contractor invoices
  4. Vendor ledger

[05]Who decides whatViya Constructions

The AI reads. Fixed logic calculates. A person confirms. The terms are nobody's to reword.

StepDone by
Reading the scope and the quotationThe AI, only the fields asked for, in the language as written
Suggesting the payment stagesThe AI. A suggestion only
Percentages to 100, every amount, required fieldsFixed logic
Whether the contractor, each line and each percentage are rightSite or project staff, on the card
Terms and conditionsViya's approved Malayalam text, fixed and versioned. Never generated
In build: budget check and balanceFixed logic. Approvals and payment entries stay with people

A blank stays blank.

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 rules it follows

What it refuses, what it balances, what it never rewrites.

RuleWhat it does
Only what is printedThe AI is told never to fill a field with a plausible guess, and to split the quotation only into work the documents name.
PercentagesThree equal stages come out as 33.3, 33.3 and 33.4. A split that does not total 100 is refused, on the card and again after it.
AmountsRecalculated from the quotation total on confirmation. On 1,00,000 rupees those stages print as 33,300, 33,300 and 33,400.
Lump sumOne total becomes one line with a label of at most eight words. The work list stays in the scope.
Nothing readableThe card names the file and asks for that part to be typed. Regenerate will not run on a total of zero.
Read againOn the quotation: new lines, the reviewer's percentages kept. On the scope: a fresh split.
Terms19 clauses, with a version mark stored on every work order. No one can reword them, in a run or by asking in chat.
A later changeAsked for in chat, it changes the confirmed values. Every check runs again and a new version is built. The terms stay out of reach.
In build: budget lineWork orders on one line cannot add up to more than the line without an amendment. Amendments are approved again, and earlier revisions kept.
In build: payment over valueFlagged. It needs a remark and a named approver. It is never blocked silently.
What it means for you

Four readers, four answers.

  1. For owners

    Contractors held to terms they can read

    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.

  2. For operations heads

    A work order without retyping the quotation

    Site staff photograph what the contractor gave them, confirm what was read, and get the Malayalam work order back.

  3. For accounts

    Still payable, per work order

    In build: every weekly payment recorded against its work order, and a flag before a payment goes over the value.

  4. For your technical person

    Arithmetic and legal text sit outside the AI

    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.

Is this your problem too?

Four signs, and what we need to start.

  • Contractors quote in one language and work orders are written in another
  • Work orders are typed after the contractor has started
  • Nobody compares a work order rate with the estimate
  • Nobody can say what is still payable without opening the PDF and the payment sheet

To start: three real work orders with their quotations, your standard terms, one owner on your side, and thirty minutes a week.

Can you say today what is still payable on each work order?

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.