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

A milestone plan goes in, scanned or typed. Checked milestones land in ProjectSignal, each with a registered owner.

At Viya Constructions, each site's next milestone, with its date, owner and collection amount, sat in a plan document that had to be retyped into the system. Now a project coordinator attaches the plan. Owners and sites are matched to what ProjectSignal already holds, likely repeats are questioned, and nothing is saved until the coordinator has seen exactly what will be created.

Client
Viya Constructions
Department
Planning and project coordination
Starts from
A milestone plan: PDF, scan or spreadsheet
Gives you
Project plans and milestones in ProjectSignal
Connected to
ProjectSignal, read and write
Status
Live. Recorded in use at Viya on 5 October 2026. Reads from and writes to ProjectSignal today.

[01]What changedViya Constructions

A coordinator loads the plan instead of retyping it. Nothing is created until ProjectSignal has been asked.

In home construction a milestone is also money: each stage the client signs off releases a payment.

Before

Retype it and hope the names match.

  • Every milestone retyped from a PDF, scan or sheet
  • Owners written as the name is spoken, not as registered
  • A site name spelled slightly differently reads as a new project
Now

Read it, ask the platform, then save once.

  • Six columns read; a missing owner stays empty
  • Unknown owners and near-miss sites get a "did you mean"
  • A dry run before the save, and a fresh one right before it
  • 6
    columns read from every plan, plus its printed total
  • 100
    rows at most per run, saved as one transaction
  • 2 to 4
    review cards per run; two on a clean plan
  • 0
    records created while any row is blocked

Figures are the workflow's own rules.

Without a complete milestone calendar, readiness checks and labor planning have nothing to hang off. Typing it by hand across 40 sites is slow and error-prone. Loading it in bulk with no checks creates duplicates. This workflow loads it in bulk and asks ProjectSignal about every row first.

[02]Why this is hardViya Constructions

Matching names is harder than it looks. A system that matches by name will create a duplicate without complaint.

  1. 01

    Plans arrive as documents

    A plan for 40 sites is a table in a PDF or sheet, often scanned. A bad scan runs the site name into the next cell, and GF slab (ground floor) looks like FF slab (first floor).

  2. 02

    People are written the way they are called

    The plan carries the name as people say it. The staff register carries the registered one. The system blocks every row under a name it does not know.

  3. 03

    Sister sites differ by one digit

    Villa 01 and Villa 02 are separate jobs. Matching loose enough to forgive a typo will offer one villa for the other, unless numbers must match exactly.

  4. 04

    One milestone, two wordings

    "Completion of internal plastering" may already be in the system as "Internal plastering". Exact matching sees two milestones. Loose matching would merge GF slab and FF slab.

What we learned early.

A project system that recognizes a project by its name and owner will create a duplicate when a name is spelled slightly differently. So the import suggests the registered person and the existing site first, and the coordinator decides.

[03]How it worksViya Constructions

One run, with up to four stops for a person. A clean plan needs only two.

The coordinator types "/" in Bleno, picks Import a milestone plan and attaches the file. Their own ProjectSignal account must be connected first.

  1. 01The workflow

    Read the plan

    Six columns per row: the plan's milestone number, site, project owner, next milestone, date and collection amount. Scans are turned into text first. A missing owner stays empty. Where a scan runs a printed milestone such as Plinth beam into the site cell, only that phrase is split out. The totals row is kept as the printed total, not read as a milestone.

  2. 02Fixed logic

    Validate every row

    Each row needs a site, an owner, a milestone, a real date and a valid amount. A site listed under two owners is flagged. Rows are summed in paise (hundredths of a rupee) and compared with the printed total.

  3. 03Coordinator confirms

    Correct the rows

    The coordinator fixes, adds or removes rows in a table that shows each row's issues. Nothing goes to ProjectSignal while an issue remains.

  4. 04Fixed logic

    Dry run in ProjectSignal

    ProjectSignal answers row by row, without saving: create a project plan and milestone, add a milestone to an existing plan, skip an exact repeat, or block.

  5. 05Coordinator confirms

    Ask about names

    Only when needed. A site that would become a new project but is close to an existing one gets a "did you mean". So does an owner ProjectSignal cannot find. Then the dry run is repeated.

  6. 06Coordinator confirms

    Ask about similar milestones

    Only when needed. Each new milestone is compared with those already on its plan and with the other rows. A close match becomes a question: same milestone, or a different one.

  7. 07Coordinator confirms

    Confirm the exact changes

    One card: projects and milestones to create, rows skipped, rows blocked, the collection total, and the action for every row. It cannot be confirmed while a row is blocked.

  8. 08The workflow

    Save, then report

    A fresh dry run is taken right before the save. If anything is now blocked, nothing is created. Otherwise everything is created in one transaction, and a result card maps each plan row to its new milestone number.

Questions, one at a time
Bleno

ProjectSignal has no staff member called "Er. Sajan K" (4 rows). Did you mean one of these? Sajan Kuriakose. Sajana K. V. Skip to leave those rows out.

Project coordinator

Sajan Kuriakose

Bleno

ProjectSignal has no project plan called "Site B Vila 02" (3 rows). Did you mean "Site B Villa 02"? Or: No, create "Site B Vila 02" as a new project.

Project coordinator

Site B Villa 02

Bleno

"Site A" already has "Internal plastering", due 3 Oct 2026. Is "Completion of internal plastering", due 10 Oct 2026, the same milestone?

Project coordinator

Same milestone, don't add it again

Illustrative. Made-up sites, names and dates. Name questions come first.

The last card shows the save before it happens.

Every row appears with the owner as the plan wrote it, the registered owner it will get, and the action ProjectSignal will take. With a row blocked, as here, it cannot be confirmed.

Confirm the exact changes
Site A · Plinth beamAdd to the existing planAdd
Site B Villa 02 · GF slabNew project plan and milestoneCreate
Site E · HandoverExact repeat, already on the planSkip
Site D · Roof slabTyped owner is still not on the staff listBlocked
Illustrative. Made-up sites.

[04]Connected to ProjectSignalViya Constructions

ProjectSignal decides what is created. The workflow asks it first, every time.

It reads from ProjectSignal and writes to it. Both are live today.

  1. Reads

    From ProjectSignal

    • Its own dry run of the import, row by row
    • Active registered staff, for owner suggestions
    • Existing project plans and site names
    • Milestones already on each target plan
  2. Does

    What happens in between

    • Reads six columns and the printed total
    • Validates every row, then asks about near-miss names and similar milestones
    • Shows the exact changes and waits
  3. Writes

    To ProjectSignal

    • A new project plan for each site that has none yet
    • Milestones: name, target date, collection amount, assigned owner
    • Nothing else. No file is produced

ProjectSignal is Viya's system of record, so the workflow never decides by itself what gets created. Every proposed change goes through the platform's own import preview, and the platform answers for each row. A picked name is still only a suggestion: ProjectSignal is asked again. The save runs as the signed-in person, under that person's own ProjectSignal permissions and through the platform's own validation. Someone not allowed to import plans there cannot save one from Bleno.

ProjectSignal keeps one project plan per site, owned by a project manager. Once saved, the plan for each site in the file holds every imported milestone with a named owner, a target date and the collection amount it releases. From there ProjectSignal flags a milestone that is due within three days or overdue, and Milestone readiness and the weekly labor plan read the same records. Collection amounts are shown to leadership and administrator roles only; everyone else sees the due date.

  1. Plan file
  2. Milestone plan import
  3. ProjectSignal
  4. Milestone readiness
  5. Weekly labor plan

[05]Who decides whatViya Constructions

The AI reads. Fixed logic calculates. A person confirms.

StepDone by
Reading a scanned or typed planThe AI, once per run. It is told to leave a missing owner empty, and it never sees the staff register.
Dates, amounts, conflicting owners, the totalFixed logic. Money is added in whole paise.
What a near-miss name might meanFixed logic suggests. The coordinator picks, types the right name, or skips.
Whether two similar milestones are the same workThe coordinator. Fixed logic only decides when to ask.
What would be created, skipped or blockedProjectSignal, in a dry run
The saveThe signed-in person, from a preview with nothing blocked. ProjectSignal decides who may save.

[06]More detailViya Constructions

The rules it follows

What it checks, what it refuses, what it never assumes.

For the person who will ask how it decides.

RuleWhat it does
Row capAt most 100 rows per run, saved as one transaction. Extra rows are dropped with a warning.
Dates and amountsDay-first and year-first dates are read. 31 February is rejected. Amounts cannot be negative and carry at most two decimals.
Printed totalIf the rows do not add up to the plan's own total, a missing, extra or misread row is reported. No printed total, no check.
Repeated plan numbersWarned, not blocked. The plan's number is only a reference.
Unreadable scanIf no text can be read, the workflow says so and asks for a retry or the original spreadsheet.
Owner suggestionsAt most three, from active registered staff only. Titles such as Mr, Dr or Er (engineer) are ignored. A name is offered only when its similarity score (Jaro-Winkler) reaches 0.82.
Site suggestionsSame scoring, and numbers and short codes must be equal. Villa 01 is never offered for Villa 02.
Answers to name questionsA confirmed name is noted on the next preview: Owner "X" is read as "Y" (4 rows), as you confirmed. A declined site stays a new project. A declined owner's rows are left out; if none remain, the run stops. With nothing to suggest, the card asks for the exact staff name or work email.
Similar milestonesFiller words such as "completion of" and "work" are ignored. Asked when every remaining word matches, or when the match is at least 0.75 and the dates are within 60 days. GF slab against FF slab scores 0.5 and is not asked. Nor is 11th pile against 12th pile. A skipped question imports the row. Up to 40 project plans are checked per run.
Blocked rowsChecked at confirmation, before the save, and on the fresh dry run. One blocked row means nothing is created.
What goes in, what comes out

One plan in. Records out, no new file to keep.

ItemFormatNotes
In: milestone planPDF, scan or spreadsheetSix columns, plus a printed totals row if the plan has one.
Already in placeRecords in ProjectSignalSites exist. Each owner is active staff and resolves to an active project manager.
Out: project plans and milestonesRecords in ProjectSignalEach milestone has a name, target date, collection amount, assigned owner and its own number.
Out: result cardIn the chatCounts created, skipped and blocked, the collection total, and each plan row's new milestone number.
What it means for you

Four readers, four answers.

  1. For owners

    Every milestone has a name against it

    Each milestone that reaches the system has a registered owner, a date and the collection it releases.

  2. For operations heads

    Plans are loaded, not retyped

    One sitting takes up to 100 milestones. The coordinator answers only the questions the plan raises.

  3. For accounts

    The collection total is checked

    Where the plan prints a total, the rows are added in paise and compared with it before the save.

  4. For your technical person

    Writes go through your platform's rules

    Dry run, then save, as the signed-in person, in one transaction. 58 automated tests cover the workflow and its ProjectSignal connection.

Is this your problem too?

Four signs, and what we would need to start.

  • Your milestone or payment-stage plan lives in a PDF or spreadsheet, and someone retypes it
  • The same person appears under two spellings in your records
  • You have found the same site, or the same milestone, entered twice
  • Your sites include sister units that differ by a number or a letter

To start we need one real plan (the scan, not a cleaned-up sample), your staff and site lists, one coordinator who owns the job, and thirty minutes a week to review live use.

Which plan does your team retype at the start of every job?

Send us one real plan, scan and all. 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.