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

A 48-page agreement goes in. A six-section summary comes out. It refuses rather than guesses.

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.

Client
Viya Constructions
Department
Sales and accounts
Starts from
The signed labor agreement, and the supply agreement if there is one
Gives you
One summary PDF, with sources and warnings
Connected to
Nothing yet. Documents only
Status
Live. Handed over 5 October 2026. Produces a PDF; writes nothing to ProjectSignal.

[01]What changedViya Constructions

The agreement gets read once, properly. The summary says where every figure came from.

Before

Read 48 pages. Retype what matters.

  • Someone reads the agreement and retypes the facts by hand
  • Two contracts for one house, and neither refers to the other
  • A payment table that can run across a page break, copied by hand
Now

Read, matched, checked, then confirmed.

  • Each fact is taken from the schedule named for it, nowhere else
  • The two contracts are matched on survey number and owner name
  • Stages must total 100 percent, or no summary is produced
  • 48 + 18
    pages in Viya's labor and material supply agreement templates
  • 6
    sections in the summary, A to F
  • 10
    conditions that stop a run before a document exists
  • 78
    automated tests, six on readings of real sample agreements

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

A long agreement is full of near misses. Each one looks like the right answer.

  1. 01

    The facts sit pages apart

    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.

  2. 02

    Two contracts, no cross-reference

    Labor and material supply are separate agreements. Neither refers to the other. Only the property schedule shows they are for the same house.

  3. 03

    Values that look alike

    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.

  4. 04

    A table split by a page break

    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

Two readings, one comparison, six things to confirm.

The AI reads. Fixed logic matches, adds and splits. A person types the one figure no document contains.

  1. 01The person preparing it

    Attach the agreements

    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.

  2. 02The workflow

    Read the labor agreement

    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.

  3. 03The workflow

    Read the supply agreement

    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.

  4. 04Fixed logic

    Match the two contracts

    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.

  5. 05Fixed logic

    Add up the stages

    If the percentages do not come to 100, the run stops and reports the total it found. Nothing is adjusted to balance.

  6. 06The reviewer confirms

    Confirm on the review card

    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.

  7. 07Fixed logic

    Build the summary

    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.

The amount is typed, never pre-filled.

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.

  • Zero is refused
  • The agreement's own price prints only as a reference line
  • The summary records that the amount was typed, not read
Confirm the quotation summary
1 · Client and propertyOwner, survey number, extentRead
Quoted amount (INR)Not in either agreementType it
2 · Payment stages9 stages, total 100Balanced
3 · Scope of works14 headings, editableCheck
4 · Scope of elevation5 rowsRead
5 · Electrical points11 roomsRead
6 · Material ratesNo supply agreement attachedStated
Illustrative. A made-up house, Site A, with made-up counts.
When the stages do not add up
Bleno

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.

Illustrative. The same made-up house, one stage lost. Wording follows the workflow's own message.

[04]Connected to ProjectSignalViya Constructions

Today it produces a document. The link into ProjectSignal is designed, not built.

  1. Reads

    From ProjectSignal

    • Nothing. It works from the agreement PDFs alone.
  2. Does

    What happens in between

    • Reads both agreements and matches them on survey number and owner name
    • Checks the stages to 100 percent
    • Waits for a person to type the amount and confirm
    • Builds one PDF from the confirmed values
  3. Writes

    To ProjectSignal

    • Nothing today. The summary is a PDF in the conversation.

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.

  1. Customer 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.

StepDone by
Reading names, property, stages, scope and rates from the PDFsThe AI, copying as written, only the fields asked for
Matching the two agreements, adding the percentages, splitting the amountFixed logic, in whole rupees
The amount being quotedA person types it. Never read, never defaulted
Fixing a misread name, a misfiled scope heading or a dropped payment stageThe reviewer, on the card
Laying out the PDFFixed logic, from the confirmed values
Sending it to the clientA person. The workflow has no send step

The same split holds in every workflow we build.

An edit after the PDF exists goes back through the checks.

The change is applied to the confirmed inputs, validation runs again, and the PDF gets a new version.

[06]More detailViya Constructions

The rules it follows

Every refusal, written down.

Ten conditions stop the run. Six more raise a warning that prints on the summary.

RuleWhat it does
What stops a runNo labor agreement found. A readable PDF that yields nothing. No owner name. No payment stages. Stages not at 100. Agreements that contradict each other about one property. An attached supply agreement that yields nothing. On confirm: no amount, a cleared client name, an emptied stage table.
What only warnsPlot extent not stated. No scope rows read. No exclusions found. A supply agreement for another property. Differing stage schedules, where the labor agreement's are used. Anything flagged during the reading.
Stage totalMust be 100, within 0.01. Checked on reading and again after the reviewer's edits. A stage with no description or no numeric percentage is dropped before the total is taken.
Stage moneyAmount times percentage, in whole rupees. The last stage takes the difference. In Indian digit grouping: 10,00,001 rupees over 33.33, 33.33 and 33.34 percent gives 3,33,300, 3,33,300 and 3,33,401.
Stage wordingCopied as the agreement writes it, abbreviations included. "GF lintel" stays "GF lintel".
Matching the two agreementsSame project means the same survey number, and owner names that agree once titles such as Mr, Mrs and Dr are set aside. A name only one agreement gives is not a disagreement. Another project: the material rates are left out. Same project but a different district, taluk (sub-district), village, local body or extent: the run stops and nothing is merged.
Plot extentCopied with its unit as written, never converted. An area inside the scope is not the plot.
Scope headingsAny text in the Item column starts a heading. Rows before the first heading are dropped, not given an invented one.
ExclusionsOnly the list at the end of the scope, qualifiers intact: "open terrace waterproofing", not "waterproofing". Warranty exclusions are not scope exclusions.
Material ratesCopied with their units and never added up. A total the supply agreement states is quoted only as the agreement's own figure.
Page furniturePage numbers and the signature block repeated on every page are stripped from the scope.
Personal dataThe owner's name only. The national ID number, home address and email are never read out.
ScansA PDF with under 400 characters of readable text is treated as a scan, not a failed reading. A scanned labor agreement stops the run.
What goes in, what comes out

Two PDFs and one typed figure in. One PDF out.

ItemDetail
In · Labor agreementPDF with readable text. Required. Read up to 120,000 characters.
In · Material supply agreementPDF. Optional. Without it, the summary says none was supplied and states no material rates.
In · Quoted amountTyped on the review card, in rupees.
Out · Sections A to DClient. Plot area as stated. Amount in figures and words. Payment stages with percentage and amount.
Out · Sections E and FScope of works by heading, scope of elevation, electrical points, exclusions. Material rates, marked indicative.
Out · Closing sectionWhere the figures come from, and the warnings raised while reading.
What it means for you

Four readers, four answers.

  1. For owners

    A summary you can stand behind

    Every figure was copied from the signed agreement or typed by your own people. The closing section says which.

  2. For sales heads

    The agreement stops being one person's knowledge

    Anyone in the role can produce the summary. The facts are read, not retyped, and the reviewer checks what was read.

  3. For accounts

    A payment schedule that adds up

    Stage amounts come from the agreement's own percentages and total the quoted amount to the rupee.

  4. For your technical person

    Rules you can test

    The AI reads named fields only. Matching, totals, validation and layout are fixed logic, covered by 78 automated tests.

Is this your problem too?

Four signs, and what we would need to start.

  • Your agreements are long, and someone retypes a short version for the client
  • Labor and materials are contracted in separate documents
  • Payment stages are copied by hand into a summary or a billing plan
  • Scope questions go to the one person who has read the agreement

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.

Who in your company has actually read the agreement?

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.