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.
[01]What changedViya Constructions
In home construction a milestone is also money: each stage the client signs off releases a payment.
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
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).
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.
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.
"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.
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
The coordinator types "/" in Bleno, picks Import a milestone plan and attaches the file. Their own ProjectSignal account must be connected first.
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.
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.
The coordinator fixes, adds or removes rows in a table that shows each row's issues. Nothing goes to ProjectSignal while an issue remains.
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.
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.
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.
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.
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.
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.
Sajan Kuriakose
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.
Site B Villa 02
"Site A" already has "Internal plastering", due 3 Oct 2026. Is "Completion of internal plastering", due 10 Oct 2026, the same milestone?
Same milestone, don't add it again
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.
[04]Connected to ProjectSignalViya Constructions
It reads from ProjectSignal and writes to it. Both are live today.
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.
[05]Who decides whatViya Constructions
[06]More detailViya Constructions
For the person who will ask how it decides.
Each milestone that reaches the system has a registered owner, a date and the collection it releases.
One sitting takes up to 100 milestones. The coordinator answers only the questions the plan raises.
Where the plan prints a total, the rows are added in paise and compared with it before the save.
Dry run, then save, as the signed-in person, in one transaction. 58 automated tests cover the workflow and its ProjectSignal connection.
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.
[07]Where this fitsViya Constructions
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.