TGH Tech
Case study · Workflow 15 of 20 · Buy and build · Designed

No purchase order without an approved request. A design for Viya: every order budget-checked.

At Viya Constructions an order to a vendor is a phone call or a message. ProjectSignal holds a status set by hand and a vendor name typed in: no document, no rate, no vendor record behind it. On 1 November 2026 Viya asked for a real purchase order. This page sets out that design, not built yet, and what it stands on. Approved requests go in. Fixed logic checks the order against the stage budget, the planning engineer approves anything over, and the vendor gets a numbered PDF.

Client
Viya Constructions
Department
Purchase, with planning for approvals
Starts from
Approved purchase requests, grouped by material and site
Gives you
A numbered purchase order PDF in the company's own format, with a send log
Connected to
ProjectSignal, where the order is raised. Bleno's part, reading quotes and status, is planned
Status
Designed. Requested by Viya on 1 November 2026. Specified in writing, not built. Request tracking under it is in use.

[01]What changesViya Constructions

Today the order is a status someone sets. The design makes it a document with a number, a vendor and a rate.

This is a design, written from the requirements Viya sent on 1 November 2026. Left: how ordering runs today. Right: what the purchase order adds.

Before

An order nobody can point to.

  • Placed by phone or message, then marked "PO sent" by hand
  • No rate on record to hold against the budget or the bill
  • Overspend found when the stage's bills are added up
As designed

A numbered order, checked before it is sent.

  • Raised only from approved requests, never for more than was asked
  • Rate, quantity and unbudgeted material checked against the stage budget
  • A PDF in the company's own format, shared in one click, every send logged
  • 3
    checks on every order: rate, stage quantity, and material that is not in the budget
  • 9
    states an order can be in, from Draft to Closed
  • 7
    statuses a request already moves through in ProjectSignal today

From the design's own rules and the request tracking in use.

Material is the largest share of cost and the most common reason a planned crew stands idle. A numbered order with a rate is what every later check stands on.

We traced Viya's eight requirements for this workflow against the running platform. Two are partly there: the vendor register holds a phone and email, and delivery states exist on the request. Six are new.

It is planned in two steps. First the order itself: raised from approved requests, capped at the requested quantity, numbered, shared as a PDF, moved along by deliveries. Then the three budget checks, on pilot sites. Request approvals come first, because without them there is no queue to order from.

[02]Why this is hardViya Constructions

A phone order leaves nothing to check the bill against. And nothing to match the truck to when it arrives.

  1. 01

    The rate lives in a phone call

    Rates are agreed by phone and compared with nothing. A high rate on one site is never seen beside what another site paid last week, or what the estimate assumed.

  2. 02

    Material arrives in parts

    Steel comes in two loads, blocks in three. If the record knows only ordered and delivered, site and office disagree about what is there. With no order, a load can only be matched to the request.

  3. 03

    The bill has nothing to stand on

    Accounts are meant to match order, receipt and invoice before paying. With no order document and no rate on record, nothing ties a vendor's bill to an approved need.

  4. 04

    Over budget is found at the end

    Overspend on material usually shows when a stage's bills are added up, after the money is spent. The check belongs before the order goes out, on rate as well as quantity.

[03]How it worksViya Constructions

From an approved request to the vendor's phone. Eight steps, each with a name against it.

The design, step by step. Six of the eight steps are Viya's, as written. Quote comparison builds on one line of its request. The receipt step is our reading of its states. Only request tracking and receipts run today.

  1. 01Purchase

    Open the approved queue

    Purchase opens the queue of approved requests, grouped by material and site. An unapproved request is not in it.

  2. 02The AI reads

    Compare quotes when it matters

    Supplier quotes, PDF or photo, are read into one card: rate, tax, delivery and credit. Quotes that differ on grade, brand or delivery terms are flagged. Purchase records the choice and the reason. Planned after the first version.

  3. 03Purchase

    Build the order

    Purchase selects the requests, picks the vendor from the vendor database and enters rate, GST (India's goods and services tax), delivery site and date, and payment terms.

  4. 04Fixed logic

    Check against the stage budget

    Is the rate above the budget rate? Does the total ordered for the stage exceed the budget quantity? Is the material in the stage budget at all?

  5. 05Planning engineer confirms

    Approve what is over

    Within budget on all three, the order is created directly. Otherwise the planning engineer approves, rejects or sends it back with a comment. Unbudgeted material also needs the project lead.

  6. 06Fixed logic

    Number it and produce the PDF

    The order gets its number and a PDF in the company's current purchase order format, built from the confirmed values.

  7. 07Purchase confirms

    Share in one click

    WhatsApp opens a chat with the vendor holding the order message and a PDF link. Email sends the PDF attached. Each send is logged, and the order becomes Sent.

  8. 08Site engineer records

    Receive against the order

    Placing an order is not the same as material arriving. The site engineer or storekeeper records each load, and receipts move the order to Partly delivered, then Delivered. Purchase closes it.

Three checks run before the order has a number.

Purchase sees each result on the order itself. Pass all three and it is created. Fail any and it waits for a named approver.

Purchase order draft · Site A
Cement · rateAt or under the budget rateWithin
Cement · stage quantity380 bags ordered + 50 = 430 of 640 budgetedWithin
M-sand (manufactured sand)2 loads asked, 1 load left in the budgetOver
Waterproofing compoundNot in the stage budgetUnbudgeted
Next stepPlanning engineer and project leadPending approval
Illustrative. Made-up site, materials and quantities. The designed screen, not a live one.

[04]Connected to ProjectSignalViya Constructions

The request and the delivery are already records. The order between them is the new one.

ProjectSignal already numbers every request and adds up every load. The order is designed as a record of the platform itself.

  1. Reads

    From ProjectSignal

    • Approved purchase requests, with site, stage and quantity
    • The stage budget: quantity, unit, rate and amount per material
    • The vendor database: code, phone, email
  2. Does

    What happens in between

    • Groups approved requests by material and site
    • Runs the three budget checks and routes anything over
    • Numbers the order, builds the PDF, logs the share
  3. Writes

    To ProjectSignal

    • The purchase order: lines, revisions, state
    • The approval and its comment, the send log
    • Ordered and received quantities on each request, which becomes Partly ordered or Ordered

Designed. Stage budgets come from Viya Estimator, which is in build.

Part of the jobIn ProjectSignal todayNew with the purchase order
The requestNumbered from a site group message, tracked through seven statuses. In use.Approval states and a stage. See purchase requests against budget.
The orderA "PO sent" status and date on the request, set by hand.A record with a number, lines, revisions and nine states: Draft, Pending approval, Approved, Sent, Partly delivered, Delivered, Closed, Rejected, Canceled.
The vendor and rateFree text on the request. No price.A vendor from one database, with rate, GST and payment terms. See vendor ledger.
The deliveryDelivery notes from the site group, part loads added up, a calendar of what lands where. Live.Receipts linked to order lines, so Partly delivered and Delivered are worked out, not typed.
The documentNone. In Bleno, a rate-inquiry sheet built from a BOQ is live.A PDF in the company's own format, a one-click share and a send log.

Middle column: running at Viya now. Right column: the design.

In the first version purchase raises the order on ProjectSignal's own screens, so every rule here is the platform's own. One budget check serves requests and orders, and it reads the budget itself, never a copy.

What is ordered counts against the stage budget. Viya's request includes a view per project and stage: budget quantity, requested, ordered, balance and percent used.

Bleno's part in the design is reading: supplier quotes into the comparison card, and order status answered in chat, so a project manager need not phone purchase. Drafting an order from Bleno comes later, as the signed-in person, previewed first, through the platform's own validation.

Site roles see quantities and balances. Rates are shown only to roles that can see budgets.

  1. Estimate and budget
  2. Purchase request
  3. Purchase order
  4. Delivery and stock
  5. Vendor ledger

Later, planned.

A rate check on each order line: the budget rate, recent rates for that material near the site and the vendor's last rate. It needs about three months of order rates first.

[05]Who decides whatViya Constructions

The AI reads. Fixed logic calculates. A person confirms. Nobody approves an order they raised.

StepDone by
Reading supplier quotes into one comparison (planned later)The AI: rate, tax, delivery and credit only. It flags quotes that are not like for like
Choosing the vendor, rate and terms, and sending the orderPurchase. Each send is logged
The three budget checks and the order numberFixed logic
Approving an order over budgetThe planning engineer, and the project lead when the material is unbudgeted
The purchase order PDFBuilt from confirmed values in the company's format. Standard terms are fixed text, never written by the AI
Recording what arrivedThe site engineer or storekeeper. Fixed logic adds up the loads

[06]More detailViya Constructions

The rules it follows

Viya's rules as written, and the ones receipts already enforce.

Six are Viya's, as written. The format and cancel rules come from the design work. The last five run in ProjectSignal today.

RuleWhat it doesStatus
No order without a requestRaised only from an approved request, and never for more than it askedDesigned
Rate checkOver budget when the order rate is above the budget rateDesigned
Quantity checkOver budget when the total ordered for the stage exceeds the budget quantityDesigned
Unbudgeted materialMaterial not in the stage budget needs the planning engineer and the project leadDesigned
Change after approvalA new rate or quantity makes a new revision and repeats the checkDesigned
No contact, no sendSharing needs the vendor's phone or email on file. Every send is logged: channel, time and userDesigned
The format is the company'sThe layout changes only with the company's approvalDesigned
Cancel releasesCanceling before delivery releases the quantity back to the requestDesigned
Receipts cannot exceed the orderLoads are added up exactly. A total above the ordered quantity is refusedLive
Units are never converted50 bags is never turned into kilogramsLive
Frozen after the first loadMaterial, specification, quantity and unit cannot be edited once a receipt existsLive
No double countA delivery note that reaches the system twice is counted onceLive
One change at a timeA status moves only from the status the person saw. If someone moved it meanwhile, the change is refusedIn use
What it means for you

Three readers, three answers.

What the design gives each reader once it runs.

  1. For owners

    Every order has an approved request behind it

    An order over budget, or outside it, carries the name of the person who approved it, and why.

  2. For purchase heads

    One queue, not a chat to scroll

    Approved requests arrive grouped by material and site, and the order goes out in your own format.

  3. For accounts

    A bill you can check

    A vendor's invoice can be matched to an order with a rate and to loads counted on site.

Is this your problem too?

Four signs that ordering is running on memory.

  • Orders go to vendors by phone or chat, at whatever rate was agreed on the call
  • A truck arrives and nobody can say which order it belongs to
  • A vendor's bill is checked against memory, not against an order and a receipt
  • You learn a stage went over on material after its bills are added up

To start we would need one recent purchase order, your number series and standard terms, your rule for who approves what, and your vendor list with phone numbers. Then one owner in purchase and thirty minutes a week.

What will be counted once it runs.

Orders raised against an approved request, orders shared from the system, and over-budget orders that carry an approval.

Could you match last month's vendor bills to an order, a rate and a delivery?

Send us one recent purchase order and your rule for who approves what. We will show you how ordering runs today and what a first version would look like. Start with one workflow. You only pay if it works.