TGH Tech
Case study · Workflow 07 of 20 · Plan the job · Live

A scope of work goes in. The quality checklists for that exact house come out, each with a reason.

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.

Client
Viya Constructions
Department
Quality
Starts from
A scope of work PDF
Gives you
An Excel workbook: an index and one tab per checklist that applies
Connected to
Nothing yet. It sits beside quality control in ProjectSignal
Status
Live. Produces a workbook. Not linked to ProjectSignal quality records.

[01]What changedViya Constructions

Which checklists apply is now a rule, not one person's reading. And every choice has its reason written down.

Before

Read the scope, pick the sheets by hand.

  • 24 checklists as separate spreadsheet files in a folder
  • Someone reads each scope and picks the sheets by hand
  • Slow, and easy to get wrong
  • Printed sheets drift from the controlled wording
Now

Attach the scope, review, print the workbook.

  • One workbook per project: an index and a tab per checklist that applies
  • Fixed rules pick the sheets: the same scope always gives the same selection
  • Every checklist, in or out, carries a written reason
  • Scope with no checklist is named
  • 24
    controlled checklists in the fixed library
  • 599
    checks, reproduced word for word
  • 41
    checks on the RCC for superstructure sheet: 29 before the pour, 10 during, 2 after

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

Quality on site depends on which checklist the engineer happens to have. And every house needs a different set.

A project manager at Viya carries up to ten sites. Nobody can stand on every slab before it is poured.

  1. 01

    No two houses need the same sheets

    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.

  2. 02

    Scopes are written in the contract's words

    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.

  3. 03

    A folder cannot show what is missing from it

    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 AI reads the scope. Fixed rules choose the sheets. A person confirms every one, in or out.

The flow runs in a straight line on purpose. No sheet exists until a person has reviewed every proposed inclusion and rejection.

  1. 01QA manager starts

    Attach the scope of work

    A QA manager or site engineer types "/", picks the job and attaches the scope of work PDF.

  2. 02The workflow

    Read the scope

    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.

  3. 03Fixed logic

    Match against all 24 checklists

    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.

  4. 04Fixed logic

    Decide, and write down why

    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.

  5. 05Fixed logic

    Name the scope with no checklist

    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.

  6. 06QA manager confirms

    Review the selection

    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.

  7. 07Fixed logic

    Build the workbook

    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.

The review card shows the reason, not just the answer.

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."

Review QA checklist selection · Site A
No checklist existsElectrical, Plumbing. That work will go uncovered unless a checklist is written for it.Not covered
1.1 Clearing of siteAlways selected: every project begins with site clearing.Include
7 PCC below foundationSelected by scope: "PCC below column footing".Include
18 Plastering for internal wallsSelected by scope: "Plastering". The exclusion "Open terrace plastering" may narrow where it applies.Include
20 Roof top plasteringExcluded by scope: "Open terrace plastering".Left out
25 Flooring using graniteNo scope wording supports this activity.Left out
Illustrative. A made-up scope for Site A, run through the real rules. Open terrace plastering is excluded. Seven of 24 checklists are selected.

[04]Connected to ProjectSignalViya Constructions

Today it produces a workbook. ProjectSignal holds the quality records. The two are not linked yet.

  1. Reads

    From ProjectSignal

    • Nothing today. The person starting the job attaches the scope.
  2. Does

    What happens in between

    • Reads headings, trade words and exclusions
    • Matches them to 24 checklists by fixed rules
    • Records a reason for every checklist
    • Waits for a person to confirm
  3. Writes

    To ProjectSignal

    • Nothing today. The workbook is downloaded as Excel.

Bleno workflows cannot read or write ProjectSignal's quality records today.

Question on a live siteWhere the answer lives
Which checklists apply to this house, and whyThe workbook's index tab
What to check before, during and after each activityThe workbook's checklist tabs
Has this stage been checked on this siteProjectSignal stage checks, every change of status logged
Which check carries the gateProjectSignal: one check flagged as a hard gate, setbacks marked and confirmed on site
Who stands behind a completed checkProjectSignal: the project manager's signed quality report, with site observations and a reference number
What the homeowner can show a bank or valuerProjectSignal's owner portal: a stage certificate. One cannot be issued while a check on the stage is pending

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.

  1. Scope of work
  2. QA checklist workbook
  3. Stage checks in ProjectSignal
  4. Signed quality report

Read the arrows carefully.

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 AI reads. Fixed logic selects. A person confirms.

The same split as every Bleno workflow: the AI reads, fixed logic calculates, a person confirms.

StepDone by
Reading project details, scope headings, trade words and exclusionsThe AI, only those fields. A missing value stays empty and is flagged
Choosing the checklists, writing each reason, listing uncovered scopeFixed rules. Never the AI
Including or leaving out a checklistThe QA manager or site engineer, on the review card
The wording of every checkViya's controlled library. Neither the AI nor the reviewer can change it
Signing off a stage checkThe project manager, in ProjectSignal. Outside this workflow

The AI is used twice: reading the scope, and writing the closing summary, which may only repeat the result.

[06]More detailViya Constructions

The rules it follows

Every rule, written down.

For the quality head who will ask how a sheet got in or stayed out.

RuleWhat it does
Fixed library24 checklists, 599 checks, one version, word for word with the original spelling
Site clearingAlways included. If the scope seems to exclude it, a note says it remains mandatory
Scope matchIn, with "Selected by scope" and the matching wording quoted
Scope beats exclusionA checklist touched by both the scope and an exclusion stays in, with a note that the exclusion may narrow where it applies
Exclusion onlyOut, with "Excluded by scope" and the exclusion quoted
No supportOut, with "No scope wording supports this activity"
Bare trade headings"Plastering" or "Painting" alone selects the internal walls sheet, and "Tiling" alone the vitrified tile sheet. The other sheets in the family need their own wording, or the reviewer's tick
Uncovered scopeReported first and written into the index, one entry per trade
Empty selectionRefused. Nothing ticked, no workbook
No scope wording foundThe card says so and asks for every checklist to be reviewed
Missing project detailsThe card says which of project name, client or location was not found in the scope
What goes in, what comes out

One scope of work in. One workbook out.

ItemWhat it holds
Scope of work, PDFProject, client, location, scope headings, trade words, exclusions
Index tabProject, client, location and generation date, library name, how many of 24 were selected, included checklists with item counts, those left out with reasons, scope with no checklist
Checklist tabsThe company's title block, a note to tick the box or enter readings, YES, NO, NA and remarks columns, checks in before, during and after bands numbered straight through, Checked by and Approved by with sign, name and date

What is in the library

GroupSheets (checks)
SiteClearing of site (18), Surface preparation (17)
FoundationRandom rubble masonry (17), PCC below foundation (26), RCC for foundation (41), RCC work for underground tanks (41), Block work below foundation (24), DPC below floor level (41), Earth filling for basement (9)
SuperstructureRCC (41), Block work (24)
Floors and tilingPCC for flooring (26), Vitrified tiles (21), Ceramic tiles (21), Dadoing (21), Granite (23)
PlasteringCeiling, Internal walls, External walls, Roof top (33 each)
Painting and puttyExternal walls, Internal walls, Ceiling, Putty work (14 each)

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.

What it means for you

Three readers, three answers.

  1. For owners

    One written standard on every site

    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.

  2. For quality heads

    A review, not a reading exercise

    Whoever starts a project reviews a proposed selection with reasons. They cannot reword a check, and site engineers get the layout they already know.

  3. For your technical person

    No AI in the selection

    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.

Is this your problem too?

Four signs, and what we need to start.

  • Your checklists live as separate files in a shared folder.
  • One person knows which sheets apply to which kind of job.
  • Sheets on site no longer match the wording your quality head approved.
  • Nobody has listed which trades in your contracts have no checklist.

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.

Who decides which checklists your next house starts with?

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.