At Viya the scope of each site travels as a chat attachment, and "is the compound wall in our scope?" (the boundary wall around the plot) costs a phone call to a senior. On 1 November 2026 Viya asked for three things: each scope read, checked and stored as a numbered version in ProjectSignal, answers that cite it or say "I don't know", and Bleno as an app on site phones. None of this is live. The vault exists, filing and the app are in build, and answers are designed.
[01]What changesViya Constructions
Status as recorded on 2 November 2026.
Before designing anything, we checked the request against what ProjectSignal and Bleno already do. The table is the result.
A wrong yes is work nobody priced. Viya's platform requirements say no extra work without an approved change order. That only holds if the person on site can find out where the scope ends.
[02]Why this is hardViya Constructions
A scope document can carry contract value and rates beside the scope of work, and Viya's rule is that site roles do not see them. The labor agreement that carries the scope runs to about 48 pages.
Viya labels versions R0, R1, R2. When each is one more chat attachment, a site can work to a scope that has been replaced.
The same scope and specification questions reach project managers and planning engineers many times a week. An answer from memory drifts from the document.
[03]How it worksViya Constructions
The design, not yet running: first filing a scope, then answering from it.
A project lead, planning engineer or project manager attaches the scope in Bleno (PDF, Word or scan) and names the site.
Bleno identifies the site, or asks. The site must exist in the ProjectSignal project register.
Five groups of details: client, location, plot and building; scope by stage; specifications and brands; inclusions and exclusions; milestones and special conditions. Each keeps its page. Contract value and rates are marked as commercial.
The sender corrects anything wrong on a review card. A field the sender skips is stored as unchecked, not as confirmed.
A preview, then the store: R0 first, then R1, R2. Older versions stay, read-only, with who confirmed each and when.
The project register shows scope loaded, version and date for the site.
A scan does not read as cleanly as a typed document, so the card shows every field that was read. The sender can save, correct a field or flag the wrong site.
Anyone with access to the site asks Bleno, in English or Malayalam.
The site comes from the question or the person's assigned sites. If unclear, Bleno asks.
That site's documents and data only, in the current confirmed version unless an older one is asked for.
Document, version, page or clause. A partial answer says what is missing. With no passage to cite, the reply is "I don't know".
Question, reply, sources, language and time. The project lead reviews unanswered questions every week.
[04]The answer ruleViya Constructions
The risk in any assistant that answers scope questions is a confident wrong answer. On site, a wrong "yes" gets built. So the design allows an answer only when there is a passage to point to: document, version and page or clause, so the person asking can check it in seconds. If the documents cover part of the question, the reply gives that part and says what it does not know. If they cover none of it, the reply is "I don't know".
Viya asked for it this way: "I don't know" over a guess, and no separate process for unanswered questions. Every question and reply is logged against the site, the project lead reviews a sample each week, and the log shows where a scope is unclear.
Is the compound wall in our scope?
Yes, the front compound wall with gate is included. The side and rear walls are not. Source: Scope R1, page 4, clause 7.2, External works.
Which tile brand did the client choose for the master bathroom?
I don't know. Scope R1 lists bathroom tiles as a provisional sum (page 6) but names no brand, and no selection is recorded for this site.
[05]On site phonesViya Constructions
Site teams live on their phones, on patchy 4G. A chat in a browser tab is not where a site engineer asks about a compound wall. What Viya asked for:
Bleno's chat already takes documents, photos and audio. The build order: install on the home screen, access by site and role, offline use and the 100 MB limit, then the ProjectSignal account as the only sign-in. The target is a load under 2 seconds on 4G, timed on site phones.
[06]Connected to ProjectSignalViya Constructions
This is the design. Nothing is written to ProjectSignal today: the vault exists, and the route from Bleno into it is in build.
The writes are designed to follow the rule of every Bleno workflow at Viya: as the signed-in person, within their permissions, through the platform's own validation, previewed first.
Access is not copied into the assistant. ProjectSignal already limits project managers and site engineers to their assigned sites and hides budget amounts by role. The design applies the same limits to documents.
None of these links is live. Agreements and work orders are live and produce documents. Reading the stored scope into work order text and readiness checks is the design.
[07]Who decides whatViya Constructions
As designed. The usual pattern: the AI reads, fixed logic calculates, a person confirms. Here nothing is calculated, so the fixed part is the rules.
[08]More detailViya Constructions
The rules the build has to meet. Viya wrote most of them.
ProjectSignal already had a Scope vault per site with numbered versions. What was missing was a reader and a road into it.
The test plan: real questions with known answers and known unknowns, 30 per scope document, each with its expected answer and page. Today's chat runs on the same set first, as a baseline.
Pilot roles first, from a site's confirmed scope only. Then every role on the phone app, with other site records added as sources later.
When site, purchase and a subcontractor disagree about what is included, there is one current version, a record of who confirmed it, and a log of what the site asked.
Project managers and planning engineers stop being the only place a scope can be looked up.
Roles and site assignments come from the platform, checked on every request. Search is limited to one site and its current confirmed version.
To start we would need two real scope documents from live sites, one person who can check what was read from them, and thirty minutes a week to review the answers.
[09]Where this fitsViya Constructions
Send us two real scope documents. We will show you what a first version would look like. Start with one workflow. You only pay if it works.