TGH Tech
Case study · Workflow 13 of 20 · Run the sites · In build

The site asks what the scope says. In build: an answer that names the page or clause, or says "I don't know".

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.

Client
Viya Constructions
Department
Planning and site execution
Starts from
A scope document, then a question from site
Gives you
As designed: one current, checked scope per site, and answers that cite it
Connected to
ProjectSignal: the site's Scope vault, the project register, roles and site access
Status
In build. Asked for on 1 Nov 2026. Filing and the phone app are in build; answers are designed. Nothing is live.

[01]What changesViya Constructions

One current scope per site, and an answer the site can check. In build. Here is what exists and what does not.

Before

Find the PDF in the chat. Then phone a senior.

  • Scopes travel as chat attachments
  • Nobody can say which version a site is working to
  • Scope questions go to seniors by phone
  • Answers from memory drift from the document
As designed

One current scope per site. Ask it from the phone.

  • One scope per site in ProjectSignal: R0, R1, R2
  • A new version counts only once its sender confirms it
  • Site teams ask Bleno in English or Malayalam
  • Every answer names document, version and page or clause, or says "I don't know"
PartStatusWhat that means
A Scope vault for every siteExistsIn ProjectSignal, beside the schedule, work order and drawing vaults, with numbered versions. It stores PDF files and does not read them.
Bleno reading scopesLive in other workflowsAlready read for agreements, quality checklists, schedules and work orders. No route into the vault yet.
Filing a checked scope from BlenoIn buildStarts assisted, for office roles: Bleno reads, the sender checks, the file goes into the vault by hand. Then Bleno files it.
Answers with the sourceDesignedBleno already answers from ProjectSignal records. Answering from a site's documents needs confirmed scopes first.
Bleno as an app on site phonesIn buildRuns in the browser today. Installing comes first, then access by site, then offline use.

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

Scope is what site, purchase and subcontractors argue about. And nobody can say which version a site is working to.

  1. 01

    The scope sits next to the price

    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.

  2. 02

    Scopes are revised

    Viya labels versions R0, R1, R2. When each is one more chat attachment, a site can work to a scope that has been replaced.

  3. 03

    The answer is a phone call

    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 AI reads the scope. The sender confirms it. After that, every answer has to point back to it.

The design, not yet running: first filing a scope, then answering from it.

Filing a scope

  1. 01Project lead starts

    Attach the scope

    A project lead, planning engineer or project manager attaches the scope in Bleno (PDF, Word or scan) and names the site.

  2. 02The workflow

    Find the site

    Bleno identifies the site, or asks. The site must exist in the ProjectSignal project register.

  3. 03The workflow

    Read the scope

    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.

  4. 04Sender confirms

    Check what was read

    The sender corrects anything wrong on a review card. A field the sender skips is stored as unchecked, not as confirmed.

  5. 05Fixed logic

    File the next revision

    A preview, then the store: R0 first, then R1, R2. Older versions stay, read-only, with who confirmed each and when.

  6. 06Fixed logic

    Show it on the register

    The project register shows scope loaded, version and date for the site.

Nothing is filed until its sender confirms the card.

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.

Scope check · Site A · R1 (replaces R0)
InclusionsFront compound wall with gate. Page 4, clause 7.2.Confirmed
ExclusionsSide and rear compound walls. Interiors, landscaping.Corrected
BrandsBathroom tiles: provisional sum, no brand named. Page 6.Confirmed
Special conditionsNo work on SundaysUnchecked
Contract value, ratesPages 2 and 14. Stored.Hidden from site
Illustrative. A made-up site and scope.

Answering from it

  1. 01Site engineer asks

    Ask in plain words

    Anyone with access to the site asks Bleno, in English or Malayalam.

  2. 02The workflow

    Find the site, check access

    The site comes from the question or the person's assigned sites. If unclear, Bleno asks.

  3. 03The workflow

    Search that site only

    That site's documents and data only, in the current confirmed version unless an older one is asked for.

  4. 04The workflow

    Answer with the source, or say so

    Document, version, page or clause. A partial answer says what is missing. With no passage to cite, the reply is "I don't know".

  5. 05Project lead reviews

    Log it against the site

    Question, reply, sources, language and time. The project lead reviews unanswered questions every week.

[04]The answer ruleViya Constructions

With the source, or "I don't know". A partial answer says which part is missing.

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.

Bleno · Site A
Site engineer

Is the compound wall in our scope?

Bleno

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.

Project manager

Which tile brand did the client choose for the master bathroom?

Bleno

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.

Illustrative. A made-up site and scope. The second reply is a partial answer.

[05]On site phonesViya Constructions

The answer has to be on the phone in the engineer's hand. The installable app is in build. Today Bleno runs in the browser.

Asked on site. Sent when the signal comes back.

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:

  • On the Android or iPhone home screen. No app store release.
  • Sign-in with the ProjectSignal account, so role and site access carry over
  • Text, voice note, photo, PDF, Word or Excel, up to 100 MB
  • Recent chats open offline. Queued messages send when signal returns.
Bleno · Site A · Offline
Yesterday 18:40Photo: first floor slab shutteringSent
Today 07:55Voice note, 0:42Queued
Today 07:56Is the compound wall in our scope?Queued
Illustrative. A made-up site. Two messages wait for signal.

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

The vault belongs to ProjectSignal. Bleno is the way in, and the way to ask.

  1. Reads

    From ProjectSignal

    • The project register: the site must exist
    • The person's role and assigned sites
    • The site's current confirmed scope
    • Later: milestones, purchase requests, purchase orders
  2. Does

    What happens in between

    • Reads the scope, shows every field for checking
    • Keeps contract value and rates from site roles
    • Answers from one site, with version and page
    • Says "I don't know" when the documents do not say
  3. Writes

    To ProjectSignal

    • The scope file as the next revision
    • The checked details, with who confirmed them and when
    • Scope loaded, version and date on the register
    • Every question and reply, against the site

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.

  1. Construction agreement
  2. Scope vault and site answers
  3. Contractor work orders
  4. Milestone readiness

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

The AI reads and finds the passage. People decide what the scope is.

StepDone by
Reading the scope documentThe AI, only the fields listed
Whether what was read is rightThe sender, field by field, on the review card
Which version is currentThe project lead
Version numbers, old versions, who may see which siteProjectSignal's own records and roles, not the AI
Finding the passage and wording the answerThe AI, held to one rule: cite a passage or say "I don't know"
Whether the answers are rightThe reader, who is shown the page, and the project lead's weekly sample

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 it follows

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

The rules the build has to meet. Viya wrote most of them.

RuleWhat it does
One document, one siteBleno never mixes sites in an answer.
The site must existBleno files only to a site on the project register. It does not create sites.
Nothing counts until confirmedA new version is used only after its sender confirms it.
Old versions stayKept read-only. Answers use the current version unless an older one is asked for.
Commercial sectionsContract value and rates are hidden from site roles and not used in answers to them. Budgets and margins stay hidden from roles that cannot see them in ProjectSignal.
Assigned sites onlyA person gets answers only about their assigned sites. Management sees all.
No passage, no answerThe answer step cites a passage or returns "I don't know". A partial answer says what is missing.
LanguageReplies come in the language of the question, English or Malayalam.
Everything is loggedEvery question and reply against the site. Views and downloads of vault documents too.
What we settled before building

Three decisions made on paper.

  1. 01

    The vault was already there

    ProjectSignal already had a Scope vault per site with numbered versions. What was missing was a reader and a road into it.

  2. 02

    Test the refusals first

    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.

  3. 03

    Answers start narrow

    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.

What it means for you

Three readers, three answers.

  1. For owners

    One document to settle it

    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.

  2. For operations heads

    The lookup stops being a phone call

    Project managers and planning engineers stop being the only place a scope can be looked up.

  3. For your technical person

    Access stays in one place

    Roles and site assignments come from the platform, checked on every request. Search is limited to one site and its current confirmed version.

Is this your problem too?

Four signs, and what we would need to start.

  • The current scope for a site is whichever PDF was forwarded last
  • When a scope is revised, you cannot say which sites have the new version
  • Project managers answer the same scope questions by phone every week
  • Work gets done on site that nobody priced, because someone said yes

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.

Who gets the call when one of your sites asks "is that in our scope?"

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.