Viya's quality manual holds 24 checklists and 599 checks. For each new project, someone read the scope of work and decided by hand which sheets applied. Now a QA manager or site engineer can attach the scope and review a proposed selection. Out comes an Excel workbook: the sheets that apply, word for word, a reason for every sheet in or out, and the scope no checklist covers. It is live and handed over. It produces a document and does not write to ProjectSignal today.
[01]What changedViya Constructions
Figures from the workflow's own library and rules.
A checklist rewritten for each project drifts. A fixed library, selected by rule, is how every site gets checked against the same written standard.
It first shipped on 15 September 2026, and the implementation record of 5 October lists it as handed over. A person starts it; nothing triggers it when a project is created.
[02]Why this is hardViya Constructions
A project manager at Viya carries up to ten sites. Nobody can stand on every slab before it is poured.
A house with an underground water tank needs the 41-check sheet for RCC work on underground tanks. Granite floors need a different sheet from vitrified tile. Excluding open terrace plastering drops the roof top plastering sheet. Internal plastering stays.
The scope says "PCC below column footing". The sheet is titled "PCC below foundation". A line that says only "Plastering" does not say which of four plastering sheets it means.
On a sample agreement, seven trades in the scope had no checklist: electrical, plumbing, sanitary fittings, carpentry, windows, tanks and a fabricated staircase.
[03]How it worksViya Constructions
The flow runs in a straight line on purpose. No sheet exists until a person has reviewed every proposed inclusion and rejection.
A QA manager or site engineer types "/", picks the job and attaches the scope of work PDF.
The AI reads project name, client and location, then scope headings and trade words, a few words each, never whole specification paragraphs. Exclusions are copied word for word with their location: "open terrace plastering", not just "plastering". Anything not stated stays empty.
Each checklist has its own trade phrases and word pairs. Fixed rules compare them with the scope wording, ignoring capitals and punctuation. The AI has no part in the choice.
Site clearing is always in. A checklist the scope supports is in, quoting the wording that selected it. One touched only by an exclusion is out, quoting the exclusion. The rest are out: no scope wording supports them.
Any scope item that matches no checklist is listed, once per trade, and shown first. That work will go uncovered unless a checklist is written for it.
The card shows the project details and any warnings, then all 24 checklists with code, activity, number of checks and reason. The reviewer can tick or untick Include. Rows cannot be added or removed, and no check can be reworded.
An index tab and one tab per included checklist, in Viya's printed layout, every check pulled from the fixed library. The closing message states how many sheets were produced and names each checklist left out.
A reviewer who disagrees with a line can see which words in the scope decided it. The card's own instruction: "Confirm every proposed inclusion and rejection before generating the site workbook."
[04]Connected to ProjectSignalViya Constructions
Bleno workflows cannot read or write ProjectSignal's quality records today.
ProjectSignal records quality stage by stage. Each check on a site is pending, in progress, completed, failed or skipped. A per-site setting fits the stage list to the house, because a single-story home has no first-floor lintel. Setbacks carry the hard-gate flag because nothing above the foundation can fix a house built on the wrong setback.
The workbook is the other half: the detailed sheet for the activity itself. Nothing joins the two today. The workbook does not create stage checks in ProjectSignal, and its 24 checklists and ProjectSignal's stage list are separate lists. Reconciling them is a decision for Viya's quality owner.
Writing the confirmed selection into each project's stage checks at project start is proposed, not in build. None of the eight workflows Viya asked for first is a quality workflow, and on 2 November 2026 this one moved down the list behind them. It needs a reviewed way to write into the quality module, and is to be revisited once the scope vault, now in build, holds every live site's scope. If built, it will write as every Bleno workflow that writes to ProjectSignal does: as the signed-in person, previewed first, through the platform's own validation.
Only the first arrow is this workflow. The second is not built. Stage checks and signed reports are made by people in ProjectSignal, against its own stage list.
[05]Who decides whatViya Constructions
The same split as every Bleno workflow: the AI reads, fixed logic calculates, a person confirms.
The AI is used twice: reading the scope, and writing the closing summary, which may only repeat the result.
[06]More detailViya Constructions
For the quality head who will ask how a sheet got in or stayed out.
24 sheets, 599 checks. The grouping is ours and titles are shortened; the counts are the library's. RCC is reinforced concrete, PCC plain concrete, DPC the damp proof course.
Every house starts from the same controlled wording. One page per project shows which sheets were issued, which were not and why, and which trades your manual does not cover.
Whoever starts a project reviews a proposed selection with reasons. They cannot reword a check, and site engineers get the layout they already know.
The AI extracts text and writes the closing summary. Selection is phrase and word rules, held by 14 automated tests. A run cannot change the library.
To start we need your checklist set as printed today, three real scopes of work and one owner for the library. Then thirty minutes a week to review what real runs show.
[07]Where this fitsViya Constructions
Send us your checklist set and one real scope of work. We will show you which sheets fixed rules would select, which they would leave out and why, and what no checklist covers. Start with one workflow. You only pay if it works.