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.
[01]What changesViya Constructions
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.
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
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.
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.
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.
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
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.
Purchase opens the queue of approved requests, grouped by material and site. An unapproved request is not in it.
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.
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.
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?
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.
The order gets its number and a PDF in the company's current purchase order format, built from the confirmed values.
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.
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.
Purchase sees each result on the order itself. Pass all three and it is created. Fail any and it waits for a named approver.
[04]Connected to ProjectSignalViya Constructions
ProjectSignal already numbers every request and adds up every load. The order is designed as a record of the platform itself.
Designed. Stage budgets come from Viya Estimator, which is in build.
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.
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
[06]More detailViya Constructions
Six are Viya's, as written. The format and cancel rules come from the design work. The last five run in ProjectSignal today.
What the design gives each reader once it runs.
An order over budget, or outside it, carries the name of the person who approved it, and why.
Approved requests arrive grouped by material and site, and the order goes out in your own format.
A vendor's invoice can be matched to an order with a rate and to loads counted on site.
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.
Orders raised against an approved request, orders shared from the system, and over-budget orders that carry an approval.
[07]Where this fitsViya Constructions
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.