Whether next week's slab can be cast depends on the drawing, the shuttering (formwork) team, the steel delivery and the client. Each answer sits with a different person, and it used to be settled by phone. Now the questionnaire lives in ProjectSignal, and a guided job walks each role through its own questions, across every site with a milestone due that week. A site with no milestone gets a weekly labor, material and work-plan check instead.
[01]What changedViya Constructions
Viya's weekly rhythm asks each role to confirm readiness before the week starts.
Counts as documented at the end of October 2026; Viya can edit the questions.
In home construction a milestone is also money: each stage the client signs off releases a payment. A milestone that starts unready finishes late, and the payment moves with it.
Both checklists run in ProjectSignal today, and the milestone questionnaire is in real use. The chat job shipped for one milestone on 24 September 2026 and was handed over. The weekly check followed on 8 October and the all-sites run on 27 October.
[02]Why this is hardViya Constructions
A drawing the client has not confirmed in writing. A labor contractor who was never told the revised scope. A material delivery with an unresolved dependency.
A slab is cast late because the shuttering material was never ordered. The drawing, the shuttering team, the steel delivery and the client's payment each sit in a different head.
A labor contractor's "yes, we will come" decays fast. Without a date on it, nobody can tell a fresh commitment from a stale one.
Scope and drawing problems cannot be solved by adding people. They have to be cleared before a date is worth committing.
With no payment stage to chase, labor and material slip unnoticed until the next milestone is already late.
[03]How it worksViya Constructions
The person types "/" and picks readiness. Nothing is attached: milestones, questions and roles are already in ProjectSignal. One coordinator typically serves many sites, so the run answers once and marks the exceptions.
It opens on the next planning week, Sunday to Saturday. Any dates up to 92 days work.
Every open milestone due in those dates that this person can reach, on plans linked to a site, with its answered count. Open ones start ticked.
With its section, role and help text. Yes or No in one tap, N/A only where allowed. Another role's questions are never asked.
One answer covers every ticked milestone, and a site that differs gets its own. Typing works too: "yes for all, M/6 no" and the reason.
Asked only where the question's rules require them. Follow-ups appear only when an answer opens them.
Questions down, milestones across. It lists exactly what will be sent.
Only complete, changed answers go, against the questionnaire version it loaded. One site's refusal never undoes another's.
A result card per project and milestone, and a short summary of what was saved and what was not.
A purchase manager answers the material question for the week in one pass, then overrides the one site that is short.
Six questions. Is labor at site, confirmed in the past two days? Is anything stopping it? Has the contractor been told the planned work and confirmed the completion date?
Five questions. Is material at site? Is the delivery plan confirmed? Can anything delay it? The delivery date is asked only after a No.
Planned labor for each of seven days, then actual labor daily, with a reason and an action for any gap. A week planned at zero needs a pause reason.
The weekly check is started on its own, one site and one whole week at a time. ProjectSignal works out the week's status on every read: blocked, at risk, awaiting update, planned pause or ready. Blocked means labor is not available, something is stopping it, or material is not at site. Nobody types the status, because a status somebody can set by hand will be set by hand. After any save, and at 18:05 India time daily, ProjectSignal notifies each role holder of their own open gaps. The project manager sees them all.
[04]Connected to ProjectSignalViya Constructions
No question is written into the workflow. Questions, rules and permissions all come from ProjectSignal, so a new questionnaire needs no rebuild.
Reads and writes happen as the signed-in person, inside their ProjectSignal permissions.
ProjectSignal marks each question as this person's to edit or not, and the workflow never widens that. A project manager can read every section and change only the questions assigned to them.
Readiness has no separate dry run. The confirmed review is the preview, and the save sends exactly the rows it listed. ProjectSignal checks the questionnaire version again and writes an audit row for every change.
ProjectSignal scores each milestone: clarity, the share of applicable questions with a valid Yes, and completion, the share answered at all. There is no pass line. Its milestone list sorts each one into not answered, needs attention or everything else. The same questions can also be answered on ProjectSignal's own screens.
[05]Who decides whatViya Constructions
Usually the AI reads, fixed logic calculates, a person confirms. Here there is no document to read, so the AI writes one short summary.
What each role is asked before a milestone.
[06]More detailViya Constructions
For every milestone due next week: who has answered, what is not ready, and what is being done about it.
In a milestone week, coordinators and purchase managers answer once and mark the site that differs. Every gap has an owner, with the reason and action its question asks for.
Each save names the questionnaire version and carries a key that identifies a repeat. ProjectSignal enforces permissions, not the chat. About 330 automated tests cover the six ProjectSignal workflows this one belongs to.
To start we need your current checklist, who holds each role on each site, and one owner with thirty minutes a week.
[07]Where this fitsViya Constructions
Send us the readiness checklist you use now, even a paper one. We will show you what a first version would look like. Start with one workflow. You only pay if it works.