TGH Tech
Case study · Workflow 04 of 20 · Win the work · Live

One scope of work goes in. Both contracts come out on the approved, locked templates.

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.

Client
Viya Constructions
Department
Sales and contracts
Starts from
One scope of work (Word document) and the client details
Gives you
Two contract PDFs: labor construction and material supply
Connected to
Documents only today. The ProjectSignal handover is designed.
Status
Live. Handed over 5 October 2026. Documents only; no ProjectSignal write.

[01]What changedViya Constructions

Two contracts, filled from one confirmed set of details. The approved wording is never retyped.

Before

Fill two long contracts by hand.

  • Owner, property, prices and payment stages placed by hand in two long templates
  • Scope, electrical points and material rates retyped from the scope of work
  • Owner and land details entered once for each contract
  • Every hand-filled line a chance for a copy error
Now

One scope of work in. Two checked contracts out.

  • Client details typed once, checked on a review card, used in both contracts
  • Scope, electrical points and material rates copied as written
  • Nothing built until both prices are confirmed and the stages total 100 percent
  • Approved wording, drawings and layout kept as signed off
  • 2
    contracts from one scope of work and one review
  • 48 + 18
    pages of approved wording and layout, kept as signed off
  • 6
    review steps confirmed before either contract is built
  • 11
    standard payment stages, editable, that must total 100 percent

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

Two contracts per project, and both have to say the same thing.

  1. 01

    Two contracts, one project

    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.

  2. 02

    Long documents, filled by hand

    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.

  3. 03

    Three schedules, word for word

    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.

  4. 04

    The payment schedule is the collection plan

    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

Six review steps stand between a scope of work and a contract.

The person preparing the contracts starts the job in Bleno by typing "/" and picking Construction agreements.

  1. 01Contracts staff

    Attach the scope of work, type the client details

    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.

  2. 02The workflow

    Read the three schedules as written

    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.

  3. 03Fixed logic

    Prepare the review card

    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.

  4. 04Contracts staff confirm

    Check the owner and the land

    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.

  5. 05Contracts staff confirm

    Confirm both prices and the payment stages

    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.

  6. 06Contracts staff confirm

    Review scope, electrical points and material rates

    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.

  7. 07Fixed logic

    Validate again, then build both contracts

    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 contract text is never generated.

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.

  • A file fingerprint and a page count are checked before each template is used
  • A schedule that does not fit stops the run. No schedule row is dropped
  • A change asked for in chat goes back through the same checks
Step 3 of 6 · Date, prices and payment stages
Agreement date3 November 2026Default: today
Labor contract price32,40,000 in whole rupeesFrom chat
Material contract priceNot enteredRequired
Contract period14 monthsEdited
Payment stages11 stages, total 98 percentMust total 100
Illustrative. Made-up project and figures. The card stays blocked until the price is entered and the stages total 100 percent.

[04]Connected to ProjectSignalViya Constructions

Today it produces documents. The handover into ProjectSignal is designed, not built.

  1. Reads

    From ProjectSignal today

    • Nothing. Owner, land and price details are typed in chat and confirmed on the card.
  2. Does

    What happens in between

    • Reads the scope of work document
    • Checks the identity, land and price fields
    • Holds the payment stages to 100 percent
    • Builds both contracts on the approved templates
  3. Writes

    To ProjectSignal today

    • Nothing. Both contracts are PDF documents in Bleno.

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.

  1. Estimate check and quotation
  2. Construction agreements
  3. Quotation summary
  4. Critical path schedule

[05]Who decides whatViya Constructions

The AI reads. Fixed logic calculates. A person confirms. The templates do the legal wording.

StepDone by
Reading scope rows, electrical points, material rates and exclusionsThe AI, copying each row as written
Carrying details typed in chat onto the review cardThe AI. Every value is shown back for confirmation
Defaults, required fields, ID number length, whole-rupee prices, stage total, amounts in words, contract-style dates, page numbersFixed logic
Whether owner and land details, both prices, the stages and every schedule row are rightThe person preparing the contracts, on the review card
Contract wording, drawings and page layoutViya's approved templates. Never generated or reworded
Placing confirmed values on the templates and flowing the schedulesFixed logic, after each template passes its check

The AI is never asked to write a contract.

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

The rules it follows

What it refuses, what it checks, what it never does.

RuleWhat it does
Template checkBoth template files are checked against a stored fingerprint and their page counts, 48 and 18. A file that fails is refused.
Set places onlyValues go into the execution sentence, owner block, price clause, contract period clause, property table, schedules and page footers.
Nothing added to the scopeThe AI copies rows from the scope of work. Its instruction is never to add a standard item, rate, brand, quantity or project fact. Every row is shown for review.
The document is dataText inside the scope of work is treated as content to copy, not as an instruction.
Warnings from the documentIf a heading is missing or a value cannot be read, the AI reports it on the first review step. Its instruction is not to invent warnings.
Owner and landOwner name, parent or spouse name, address, email and all six land details are required. The email must be valid. The Aadhaar number, India's national identity number, must have exactly 12 digits.
Prices and stagesBoth prices are required, each a positive whole-rupee amount. The contract period is a whole number of months. There must be at least one payment stage, and the stages must total 100 percent.
SchedulesAt least one scope row and one material rate row. Electrical points are optional.
Dates and amountsA date typed day-first is converted; one that is not a real date is refused. Dates print in contract style, such as "3rd day of November 2026". Prices print with Indian digit grouping and again in words. Stages print as percentages only, not rupee amounts.
A schedule that does not fitThe run stops with an error. No schedule row is dropped.
An unreadable fileA Word file with no readable text stops the run, which asks for the original file, not a scan.
Checked twiceEvery rule runs when the card is confirmed and again before the contracts are built. If one fails, neither contract is produced.
Changes afterwardA change asked for in chat edits the confirmed inputs, re-runs the checks and produces a new version. Standard terms and template text cannot be changed.
What goes in, what comes out

One Word document and one message in. Two PDFs out.

ItemFormatWhat it carries
In: scope of workWord document, the original fileScope rows, electrical points by room, material specifications with rates, exclusions
In: owner and property detailsTyped in chat, confirmed on the cardSix owner fields and six land fields
In: commercial detailsTyped in chat, confirmed on the cardAgreement date, place of execution, both prices, contract period, payment stages
Out: labor construction agreementPDF, approved 48-page templateOwner block, period and price clauses, property schedule, scope of works with exclusions, electrical points, materials and brands, payment stages
Out: material supply agreementPDF, approved 18-page templateOwner block, property schedule, materials with indicative rates, total materials price, payment stages
What it means for you

Four readers, four answers.

  1. For owners

    The contract you approved is the one that goes out

    Wording, drawings and layout come from the approved file on every run. Only this client's fields and schedules change.

  2. For sales and contracts staff

    Both contracts from one sitting

    The owner and the land are entered once and read the same in both contracts.

  3. For accounts

    The stage table adds up before anyone signs

    The stages that become your collection plan must total 100 percent, and both prices must be whole, confirmed figures.

  4. For your technical person

    No generated legal text

    The AI reads one document. Checks, formatting and placement are fixed logic, and the workflow ships with 14 automated tests.

Is this your problem too?

Signs that contract drafting is a good first workflow.

  • Every project needs more than one contract with the same client
  • Your contracts are long approved documents where only names, land, prices and schedules change
  • Scope, electrical points or material rates are retyped from a scope document into the contract
  • Nothing checks that the payment stages add up before the draft goes to the client

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.

Where it goes next

From a document to a project record.

None of these is live yet.

Next stepStatusWhat it adds
Project set-up from the signed agreementDesignedScope, contract value, built-up area and payment stages carried into the ProjectSignal project record, with a schedule the customer approves.
Scope vaultIn buildAsked for by Viya on 1 November 2026. One checked, versioned scope per site in ProjectSignal. Today the scope is read for agreements and quality checklists, then not stored.
Estimate totals on the price stepPlannedThe card shows the labor and material totals from the issued estimate and flags a typed price that differs.

Who checks that both contracts for a project say the same thing?

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.