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.
[01]What changedViya Constructions
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
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.
Steel arrives in two loads, blocks in three. A record that only knows ordered and delivered leaves site and office disagreeing.
Approved on a phone call, ordered by message. Nobody can say later who approved what, or at what rate.
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
The live part uses no AI: the message has a fixed first line, so plain logic reads it.
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.
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.
The purchase team marks the order placed, with supplier and expected date, then in transit. A request open past its expected date shows overdue.
The site posts a DELIVERY NOTE with the request number, quantity and vehicle number. A short load leaves the request partly delivered.
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.
PURCHASE REQUEST
SITE NAME: Site E
MATERIAL NAME: Solid block 6 inch
MATERIAL QUANTITY: 1,500 nos
REQUIRED DATE: Friday
Logged as PR-1482. Site E. Solid block 6 inch.
DELIVERY NOTE
PR NUMBER: PR-1482
MATERIAL QUANTITY: 900 nos
VEHICLE NUMBER: given
PR-1482 partly delivered. 900 of 1,500 received.
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.
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.
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.
Per material: budget quantity for the stage, already requested, already ordered, balance. Balance is budget minus open and approved requests.
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.
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.
The decision is posted in the site group. Approved requests go to purchase for a purchase order, and live tracking takes over.
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".
[04]The budget behind itViya Constructions
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.
[05]Connected to ProjectSignalViya Constructions
The design, in build. Today the bot writes only the numbered request and delivery receipts.
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.
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.
[06]Who decides whatViya Constructions
Material outside the estimate always goes to the project lead.
[07]More detailViya Constructions
Seven rules run today. Five are the design.
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.
[08]Where this fitsViya Constructions
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.