TGH Tech
Case study · Workflow 09 of 20 · Run the sites · Live

Before a milestone starts, each role answers for its part. Each gap goes on record, with a name against it.

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.

Client
Viya Constructions
Department
Planning, project management, coordination, purchase
Starts from
The coming week's milestones in ProjectSignal
Gives you
Each role's answers with reasons and evidence, saved as a new revision
Connected to
ProjectSignal, as the signed-in person
Status
Live. Live and handed over.

[01]What changedViya Constructions

A round of phone calls became a written checklist. Each answer has an owner, a date and a record.

Viya's weekly rhythm asks each role to confirm readiness before the week starts.

Before

Call around, and hope it holds.

  • Settled by phone, or on a paper form with a section per role
  • "If No, what is the reason?" on the form, with nothing to enforce it
  • No record of who answered what, against which version
  • A site with no milestone could sit idle unnoticed
Now

Ask each role, in writing, before the week begins.

  • Each role answers only its own questions, in chat
  • An answer missing a required reason, action or file stays open
  • Every save names the questionnaire version and adds a revision
  • Every live site is under one of two checklists each week
  • 26
    questions before a milestone: 17 on scope, drawings, labor and material, 9 on the client
  • 4
    named responsibilities on every project, one person each
  • 11
    questions on the weekly check, plus a seven-day labor plan
  • 2 days
    after which a labor confirmation counts as stale

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

Most delays are decided before the work begins. Each precondition sits with a different person.

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.

  1. 01

    Everyone knew something different

    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.

  2. 02

    A Monday yes is still quoted on Thursday

    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.

  3. 03

    More labor does not fix a missing drawing

    Scope and drawing problems cannot be solved by adding people. They have to be cleared before a date is worth committing.

  4. 04

    Quiet weeks hide the slip

    With no payment stage to chase, labor and material slip unnoticed until the next milestone is already late.

[03]How it worksViya Constructions

One week, every site, your own questions only.

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.

  1. 01The person chooses

    Pick the week

    It opens on the next planning week, Sunday to Saturday. Any dates up to 92 days work.

  2. 02The workflow

    List what is due

    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.

  3. 03Each role answers

    Ask one question at a time

    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.

  4. 04Each role answers

    Answer once, mark the exception

    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.

  5. 05Each role answers

    Reason, action, evidence

    Asked only where the question's rules require them. Follow-ups appear only when an answer opens them.

  6. 06Each role confirms

    Review the grid

    Questions down, milestones across. It lists exactly what will be sent.

  7. 07Fixed logic

    Save one project at a time

    Only complete, changed answers go, against the questionnaire version it loaded. One site's refusal never undoes another's.

  8. 08The workflow

    Report counts, not a verdict

    A result card per project and milestone, and a short summary of what was saved and what was not.

Answer once. Mark the site that differs.

A purchase manager answers the material question for the week in one pass, then overrides the one site that is short.

Material availability · Sun 15 to Sat 21 Nov
All 3 milestonesMaterial on the purchase request delivered to site?Yes
Site A · Plinth beamSame as allYes
Site B · Ground floor slabShuttering plywood short. Second supplier delivers Thursday. Photo attached.No
Site C · LintelSame as allYes
Illustrative. Made-up sites and answers.

A week with no milestone still gets asked.

  1. Labor

    Project coordinator

    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?

  2. Material

    Purchase manager

    Five questions. Is material at site? Is the delivery plan confirmed? Can anything delay it? The delivery date is asked only after a No.

  3. Week plan

    Project manager

    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

ProjectSignal owns the questions. The workflow owns the conversation and the exact save.

No question is written into the workflow. Questions, rules and permissions all come from ProjectSignal, so a new questionnaire needs no rebuild.

  1. Reads

    From ProjectSignal

    • The published questionnaire and each question's rules
    • Open milestones due that week
    • Who is assigned each question
    • Answers already saved, by every role
  2. Does

    What happens in between

    • Asks only this person's questions
    • Applies the reason, action and evidence rules
    • Shows what will be saved
    • Saves one project at a time
  3. Writes

    To ProjectSignal

    • Yes, No or N/A, with reason, action and evidence
    • A new readiness revision per project
    • With no milestone: the week's answers and seven-day plan

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.

  1. Milestone plan import
  2. Readiness by role
  3. Weekly labor plan
  4. Purchase requests

[05]Who decides whatViya Constructions

No AI decides whether a site is ready. Each role answers for its own part.

StepDone by
Which questions exist, who answers each, which sites are dueProjectSignal, from Viya's questionnaire and the roles on each project
Whether an answer is completeFixed logic, the same rules on the card and the server
Each answer, and what is savedThe role that owns the question, from the review grid
Clarity, completion and weekly statusProjectSignal, computed on every read
The closing summaryThe AI, from saved values only, told not to infer pass or fail
Whether the milestone goes aheadPeople. Readiness informs the decision and never blocks a milestone from being marked complete

Usually the AI reads, fixed logic calculates, a person confirms. Here there is no document to read, so the AI writes one short summary.

RoleAnswers forAsked, for example
Planning engineerScope (5 questions), drawings (4), client planning (6)Has the client confirmed the scope in writing? The drawing? Is the client aligned with the payment schedule?
Project coordinatorLabor (6)Is labor ready, confirmed in the past two days? Has the contractor been given the revised scope?
Purchase managerMaterial (2)Is the material on the purchase request delivered to site? Is anything holding it up?
Project managerThe client (3)Is the client satisfied? Was last week's planned work achieved? If not, was a call taken?

What each role is asked before a milestone.

[06]More detailViya Constructions

The rules it follows

What it refuses, what it caps, what it never does.

RuleWhat it does
Linked plans onlyFor milestone readiness a plan counts only if it is explicitly linked to its site; a matching name is not a link. If links cannot be read, the run says so and stops.
Text and filesReasons and actions up to 5,000 characters. Up to 5 files per answer, 25 MB each: Excel, PDF, photo or Word, linked only when the reviewed answers are saved.
Follow-up questionsAsked only when the answer above opens them, at most three levels deep. If work will not continue after the milestone, the question about telling the client appears.
Partial progressIn a milestone week an unanswered question is not sent, so a half-finished review never blanks a saved answer. The weekly check has to be answered in full.
Questions changed mid-reviewProjectSignal refuses that project's save. The run reloads the questions and shows the review once more, keeping each milestone draft whose question is unchanged. There is one retry, not a loop.
Weekly check answersAn adverse answer needs a reason and the action that will be taken; N/A always needs a reason. A Yes on the labor confirmation needs the date it was confirmed, never a future one.
The week planExactly seven days. Blank means unknown, 0 means none. No actual for a day still to come.
One checklist per weekA site with a milestone due that week is turned away from the weekly check, with the milestone named. A past week opens read-only.
What it means for you

Three readers, three answers.

  1. For owners

    A gap is named before it costs a date

    For every milestone due next week: who has answered, what is not ready, and what is being done about it.

  2. For operations heads

    One pass covers a role's milestones for the week

    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.

  3. For your technical person

    Versioned, permissioned, repeat-safe

    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.

Is this your problem too?

Four signs, and what we would need to start.

  • A milestone started late because a drawing, a labor team or a delivery was assumed
  • "Material is arranged" is an answer you hear in review meetings
  • One coordinator or purchase manager is asked the same thing on every site
  • Sites go quiet in weeks when no payment stage is due

To start we need your current checklist, who holds each role on each site, and one owner with thirty minutes a week.

Who in your company knows, today, whether next week's pour can happen?

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.