TGH Tech
Case study · Workflow 14 of 20 · Buy and build · In build

Material asked for in the site group is tracked to the last load. The check against its stage budget is in build.

Material is requested in a chat message, approved by phone and ordered with no rate on record. An over-budget stage is usually found when the bills are added up. At Viya Constructions the tracking is live: a request posted in the site group in a fixed format becomes a numbered request in ProjectSignal, tracked through order, transit and part deliveries. The budget check is in build: each request shown against the stage budget from the estimate, then approved by name.

Client
Viya Constructions
Department
Site execution, purchase, planning
Starts from
A purchase request posted in the site's Telegram group
Gives you
Live: a numbered request tracked to delivery. In build: the budget balance beside it
Connected to
ProjectSignal today. The estimator's stage budget, in build
Status
In build. Request tracking is live in ProjectSignal. The budget check and approvals are in build.

[01]What changedViya Constructions

Every request has a number and a status today. The budget beside it is what we are building now.

Before

Asked in chat, copied into a list.

  • Purchase staff copied requests out of the site groups
  • A request buried under photos became a delay on site
  • Nobody could see what had arrived, or how long it took
  • Site stock was whatever someone remembered
As designed

Numbered, tracked, counted on arrival.

  • The bot numbers the message in the group
  • Status moves from pending order to PO sent, in transit, delivered
  • Part loads are counted against the ordered quantity
  • A calendar shows what lands on which site, which day
Before

Tracked, but not checked.

  • A request names a material, not a stage
  • No budget figure sits beside it
  • Approval is a phone call with no record
  • The order goes out with no rate on the request
As designed

Checked before anyone approves.

  • Every request is tied to a stage or work item
  • Budget, requested, ordered and balance, per material
  • Over the balance needs a reason
  • The project manager approves by name

Material is the largest share of cost and the most common reason a planned crew stands idle. Request tracking is in use at Viya. The check needs a budget per stage, so it follows the estimator.

The plan measures requests tied to a stage, over-balance requests with a reason, and time to approval.

[02]Why this is hardViya Constructions

A request is one sentence typed on site. The budget it belongs to sits in an estimate workbook.

  1. 01

    Requests come from everywhere

    More than 40 sites, several engineers each, all asking in chat: typed, spoken, or a photo of a handwritten list. M-sand (manufactured sand) and msand must count as one material.

  2. 02

    Loads rarely arrive whole

    Steel arrives in two loads, blocks in three. A record that only knows ordered and delivered leaves site and office disagreeing.

  3. 03

    Approval leaves no trace

    Approved on a phone call, ordered by message. Nobody can say later who approved what, or at what rate.

  4. 04

    The budget is checked too late

    The estimate knows how much cement the first floor slab should take. Nobody sees that figure when the request is made, so overspend usually surfaces with the stage's bills.

[03]How it worksViya Constructions

Five steps run today. Six more are in build, between the request and the order.

The live part uses no AI: the message has a fixed first line, so plain logic reads it.

Live today: from message to material on site

  1. 01Site engineer

    Post the request

    The site engineer posts a message whose first line is PURCHASE REQUEST, then material, specification, quantity, required date, the work it is for, and scope or extra work.

  2. 02Fixed logic

    Number it

    The bot ignores everything else in the group. It takes the site from the group, numbers the request and replies with the number. If the site name is unclear, the request is still logged and the sender is asked.

  3. 03Purchase team

    Order and dispatch

    The purchase team marks the order placed, with supplier and expected date, then in transit. A request open past its expected date shows overdue.

  4. 04Site engineer

    Receive, in part or in full

    The site posts a DELIVERY NOTE with the request number, quantity and vehicle number. A short load leaves the request partly delivered.

  5. 05Fixed logic

    Stock and calendar

    Receipts add up to what each site has received. The calendar shows what lands where, what is overdue and what has no date. The purchase manager also sees days to deliver, split between days before the order and days with the supplier.

In the site group
Site engineer

PURCHASE REQUEST
SITE NAME: Site E
MATERIAL NAME: Solid block 6 inch
MATERIAL QUANTITY: 1,500 nos
REQUIRED DATE: Friday

Purchase bot

Logged as PR-1482. Site E. Solid block 6 inch.

Site engineer

DELIVERY NOTE
PR NUMBER: PR-1482
MATERIAL QUANTITY: 900 nos
VEHICLE NUMBER: given

Purchase bot

PR-1482 partly delivered. 900 of 1,500 received.

Illustrative. Made-up site, quantities and request number.

In build: the check before approval

Viya asked for this check on 1 November 2026. It is designed in full and planned in stages: a draft reply first, then the request created once the sender confirms, then approvals, then the balance and comparison view on sites with approved budgets.

The plan for the following week was a trial on ten real request messages in a test group, with nothing written. No live site group had changed. What follows is the design.

  1. 01Site engineer

    Ask in plain words

    The engineer types it as said on site: 50 bags cement and 2 loads M-sand for first floor slab by Thursday. A voice note or photo of a handwritten list also works. The fixed format keeps working beside it.

  2. 02The workflow

    Read the request

    The AI reads materials, quantities, stage and required date. The site comes from the group. If the stage is missing, the bot asks. If a material name matches nothing in the budget, the engineer picks from that stage's budgeted materials and the answer is remembered.

  3. 03Fixed logic

    Work out the balance

    Per material: budget quantity for the stage, already requested, already ordered, balance. Balance is budget minus open and approved requests.

  4. 04Site engineer confirms

    Confirm, with a reason if over

    The engineer confirms or corrects the draft. Above the balance, a reason is required before the request is created. Material not in the estimate is marked non-budgeted.

  5. 05Project manager confirms

    Approve by name

    The project manager approves, sends back or rejects, in the chat or in ProjectSignal. The planning engineer or project lead follows, per Viya's approval matrix. Nobody approves their own request.

  6. 06The workflow

    Post back and pass on

    The decision is posted in the site group. Approved requests go to purchase for a purchase order, and live tracking takes over.

Four figures beside every material, before the request exists.

Quantities only: rates and amounts never appear in the site group. Where a site has no approved budget, the planned reply says "no stage budget yet".

Request draft · Site A · First floor slab
Cement · 50 bagsBudget 640, requested 380, ordered 330, balance 260Within
M-sand · 2 loadsBudget 18, requested 17, ordered 15, balance 1Over by 1
Waterproofing · 20 kgNot in the estimate for this stageNon-budgeted
Illustrative. The reply as designed, with made-up quantities.

[04]The budget behind itViya Constructions

A request can only be checked against a budget that exists per stage. That budget comes from the estimate, and it is in build.

Today ProjectSignal holds three budget figures per site: total, labor and material. A request for 50 bags of cement has nothing to be checked against.

Viya Estimator reads the estimate and BOQ (bill of quantities) and turns each line into budget. It is in build: in early November 2026 it was proven on one sample estimate, not on a live site. Checking requests against that budget is a later phase of the same build.

What the estimator is built to doWhat the purchase check gets
Reads every line and standardizes its unitOne unit per material on both sides
Maps each line to a stage and work item, and flags what it cannot mapA stage to hold each request against
Totals material by stage: cement in bags, steel in kg by bar diameter, sand, aggregate, blocksThe budget quantity in the reply
Locks the estimate budget once the estimation head approves. The execution budget changes only with approvalA figure nobody on site can quietly move

[05]Connected to ProjectSignalViya Constructions

The request, its status and every delivery already live in ProjectSignal. The check adds a stage, a budget and an approver to that record.

  1. Reads

    From ProjectSignal and the budget

    • The site, from the group
    • Budget quantity for the stage
    • Open and approved requests on it
    • Quantities already ordered
  2. Does

    What happens in between

    • Reads plain words, voice notes, photos
    • Works out the balance per material
    • Shows the draft to the sender
    • Waits for the approvers
  3. Writes

    To ProjectSignal

    • The numbered request, with stage and comparison
    • The reason, when over the balance
    • Each approval: who and when
    • The decision, back to the group

The design, in build. Today the bot writes only the numbered request and delivery receipts.

Budget, requested and ordered, side by side for every stage.

The same figures feed a comparison view for planning and purchase, designed and last in the build. Near budget is marked at 90 percent used, over above 100. Material outside the estimate gets its own row.

Site A · Superstructure
Cement, bagsBudget 640, requested 430, ordered 38067% used
Steel 12 mm, kgBudget 4,880, requested 4,600, ordered 4,60094% Near
M-sand, loadsBudget 18, requested 19, ordered 17106% Over
Illustrative. The comparison view as designed, with made-up quantities.

Controlled today. In the site group, requests and delivery notes enter only through the bot. The six purchase screens only read. A status changes only from the status the person saw, so two updates cannot both win.

Added by the design. The bot's write is reviewed: a dry run, the sender confirms, then the request is created. Chat accounts are matched to ProjectSignal users, so an approval by reply comes from the right person. Approval gets its own statuses, so the delivery statuses in use do not change.

Where Bleno stands. In early November 2026 Bleno could not read or write purchase requests; read access was the first planned step. By default the design extends the bot already in the groups, with Bleno's reading of plain words, Malayalam voice notes and photos behind it. Sites keep one bot and one number series.

  1. Stage budget
  2. Purchase request
  3. Approval
  4. Purchase order
  5. Delivery

[06]Who decides whatViya Constructions

Fixed logic numbers and counts. The AI will only read. People order, confirm and approve.

StepDone byStatus
Spotting a request or delivery note, numbering, receipts, stockFixed logicLive
Order, supplier, expected date, statusThe purchase teamLive
Reading plain words, voice notes, handwritten listsThe AI, only the fields a request needsIn build
Budget, requested, ordered, balance, percent usedFixed logic, from the approved stage budgetIn build
Whether the draft is right, and why it is overThe site engineerIn build
Approving, sending back, rejectingProject manager, then planning engineer or project leadIn build

Material outside the estimate always goes to the project lead.

[07]More detailViya Constructions

The rules it follows

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

Seven rules run today. Five are the design.

RuleWhat it doesStatus
First line decidesOnly messages starting PURCHASE REQUEST or DELIVERY NOTE are readLive
UnitsSpellings are matched, bags to bag. Units are never converted: 50 bags never becomes kilogramsLive
ReceiptsReceipts together cannot exceed the ordered quantityLive
MatchingA delivery note must match its request's site, material, specification and unitLive
FreezeAfter the first receipt, material, specification, quantity and unit cannot be editedLive
Repeat messageA delivery note that arrives twice is counted onceLive
Mixed unitsWhen units differ, the calendar shows unknown, not a wrong totalLive
Sent backA corrected request runs the budget check againIn build
CanceledA canceled request releases its quantity back to the balanceIn build
Site rolesQuantities and balances only, never rates or amountsIn build
Same checks everywhereA request raised in ProjectSignal or in Bleno gets the same checksIn build
Several materialsBy default, each material in one message becomes its own request under a shared group numberIn build
Is this your problem too?

Four signs, and what we would need to start.

  • Purchase keeps its own list of what the sites asked for
  • Office and site disagree about how much of an order has arrived
  • Nobody can say later who approved a request
  • Material overspend is found when the stage's bills are added up

To start we need a week of real request messages from your site groups, one estimate with its BOQ, one owner in purchase, thirty minutes a week, and a clear rule for who approves what.

How much of this stage's cement has your site already asked for?

Send us a week of request messages from one site group and the estimate for that house. We will show you how it runs today and what a first version would look like. Start with one workflow. You only pay if it works.