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

Each site's labor is planned for the week, day by day. Each morning, the site's headcount is checked against that plan.

Each project manager at Viya Constructions plans how many workers each of their sites needs each day of the week. That plan could be entered only on ProjectSignal's own screens or kept in spreadsheets, and the daily labor report was compiled by hand at one flat rate. We built a workflow that puts the week on one card in chat, values each day from that site's own labor share of its budget, and records a reason for every revision. It is live and handed over, and it writes planned labor only.

Client
Viya Constructions
Department
Project management
Starts from
The week's dates. No file to attach
Gives you
Planned labor per site per day in ProjectSignal, valued in money
Connected to
ProjectSignal, as the signed-in project manager
Status
Live. Live and handed over.

[01]What changedViya Constructions

The week's labor plan goes in on one card, with a reason for every revision. Each morning's headcount is checked against it.

Before

One flat rate, one hand-built report.

  • A daily labor report compiled by hand at one flat rate
  • Correcting a filed figure risked counting labor twice
  • Project managers read every site group to piece the day together
Now

One card for the week, checked every morning.

  • Each day valued at its own site's labor share of budget
  • A saved day can be revised, with the reason on record
  • Silent sites named at 09:00, short sites at 11:30
  • 92 days
    at most between the first and last date of one run
  • 85%
    of planned labor is the line between on track and behind
  • 0
    actual headcounts the workflow reads or changes

From the rules in the workflow and in ProjectSignal.

With more than 40 sites live, a labor shortfall is the earliest sign that a stage is slipping. Viya values each day's planned labor in rupees and calls the figure work product, so a labor-heavy site and a material-heavy one read on one scale.

The morning side runs in ProjectSignal: reading site updates and tracking planned against actual labor are in use, and the 09:00 note and 11:30 escalation are live, the escalation switched on site by site.

[02]Why this is hardViya Constructions

A headcount is easy to collect and hard to trust. The rate, the plan and the week all move.

  1. 01

    Ten workers are not the same amount of house

    A crew of ten on a labor-heavy site and on a material-heavy one build different value. One company-wide rate judges both alike.

  2. 02

    A plan typed beside the turnout is not a plan

    Ask for planned and actual together and the plan bends toward the number beside it. It must be fixed before anyone knows who will turn up.

  3. 03

    The week changes shape after it is planned

    A week planned as an ordinary week gains a milestone, or the reverse. Labor entered earlier can drop out of view, and retyping it would count it twice.

  4. 04

    A short crew is rarely reported

    A site that plans 14 workers and gets 9 says nothing. Three short days later the slab date moves, and nobody can say when it started.

[03]How it worksViya Constructions

One card for the week. Only the changed days are saved.

A guided job in Bleno. The project manager types the crew. ProjectSignal and fixed logic supply the rest.

  1. 01Project manager

    Pick the weeks

    The project manager types "/" and picks the labor plan. A card opens on the current planning week, Sunday to Saturday.

  2. 02The workflow

    Load the manager's own sites

    The workflow reads every project this manager owns that is linked to a site. A project with no site link is left out and named.

  3. 03The workflow

    Lay out each week as the site runs it

    With a milestone due, labor is planned on that milestone up to its due date, and later days on the week's plan. A week ProjectSignal marks read-only stays read-only, with its reason.

  4. 04Project manager

    Type the crew for each day

    One whole number per day, Sunday optional. A saved day shows what it was. Changing it, even from zero, needs a reason, kept with who changed it and when.

  5. 05Fixed logic

    Value every day

    Each day's labor is multiplied by that site's labor-day value, which comes from the labor share of its budget. The smaller labor's share of the budget, the more each labor-day is worth. One site's rate never prices another.

  6. 06Project manager confirms

    Save only what changed

    The card lists the days to save and sends only those, in one request. It reopens with the saved figures until the manager presses Done.

The card shows what each day is worth before it is saved.

Each site carries its own rate label, so the manager sees whose budget a figure is priced at. A site with no budget runs on the company default, and is labeled so.

Plan labor · Site B · Sun 8 to Sat 14 Nov
Milestone weekPlinth beam due Wed 11 Nov · ₹3,000 a labor-day
Mon 9 Nov12 workers · ₹36,000New
Tue 10 Nov14 workers · ₹42,000Was 12
Thu 12 Nov8 workers · ₹24,000 · on the week's planNew
ReasonTwo more carpenters for beam shuttering
Days to save3 days · 34 labor-days · ₹1,02,000
Illustrative. Made-up site, crew and rupee figures, in Indian digit grouping.

[04]Connected to ProjectSignalViya Constructions

The plan is saved where the morning headcount lands. ProjectSignal compares the two itself.

  1. Reads

    From ProjectSignal

    • Projects this manager owns, each with its site
    • Open milestones and due dates
    • Each site's labor share and labor-day value
    • Saved labor, its revisions, and which days are open
  2. Does

    What happens in between

    • Lays out each week by milestone
    • Values each day at its site's rate
    • Lists exactly the days that changed
    • Waits for Save
  3. Writes

    To ProjectSignal

    • Planned labor per day, on the milestone or the week's plan
    • A revision record: who, when, old and new, why
    • Earlier labor in another place, moved, not duplicated

It never reads or writes actual labor. That comes only from the site's morning update.

Planned labor is read and saved through the project manager's own ProjectSignal sign-in, under that person's permissions. A manager plans only the projects they own. ProjectSignal marks each day open or locked, and the workflow never widens that.

There is no separate dry run. The card is the preview: its list of days and the save request come from the same logic, so what is sent is what was shown. ProjectSignal validates the save. If it refuses, the card returns with the typed numbers and the reason.

ProjectSignal then compares the plan each day with the headcount from site, per site, per project manager and for the company, in labor and in rupees.

  1. Site budget
  2. Milestone plan
  3. Readiness by role
  4. Weekly labor plan
  5. Morning headcount check

[05]The next morningViya Constructions

By 09:00 the silent sites are named. By 11:30, the short ones. With the site's reason and the manager's commitment.

This part runs in ProjectSignal, from updates site engineers already post in their Telegram groups.

WhenWhat happens
Evening before, by 18:00The site engineer posts tomorrow's crew and work in the site group.
By 09:00The morning update is posted. ProjectSignal reads the headcount and records one number per site per day, whichever channel filed it.
09:00Each project manager gets a private note in the app: how many of their sites have filed and which have not. It is sent even when all have, so silence is never ambiguous. That leaves two and a half hours to chase.
When the update landsIf fewer came than planned, the site group is asked why. The reply is recorded as the site's reason.
11:30Where the escalation is on, one message per project manager goes to the escalation group, which leadership reads: short sites numbered with planned, came and the site's reason, silent sites listed. The manager replies with one commitment per site: how it recovers the week, not an excuse for the day.

India time. The 09:00 note covers turnkey sites, where the company executes the work end to end.

Which plan counts.

The shortfall check uses labor planned on the milestone, else on the week's plan, else the figure the site engineer posted the evening before. A site whose week was never planned is still checked.

A short morning at Site B
Site engineer

Morning work update. Total labor: 9.

ProjectSignal

Site B had 14 people planned today, but your update reports 9. Why didn't the other 5 come to site?

Site engineer

Shuttering team moved to Site F for slab casting, back tomorrow.

ProjectSignal · 11:30

1. Site B: planned 14, came 9. Reason from site: shuttering team moved to Site F. No update by 11:30: Site H. Project manager, reply with the site number and your plan to make it up this week.

Project manager

1. Two carpenters from Site D tomorrow, extra shift Saturday.

Illustrative. Made-up sites and figures. Three messages in the site group, two in the escalation group.

[06]Who decides whatViya Constructions

In this workflow no AI plans the labor, values it or counts it. It writes one summary at the end.

StepDone by
How many workers each day, and why a figure changedThe project manager
Each day's value, every total, which days are sentFixed logic, the same on the card and in the save
Today's headcountFixed pattern rules reading the site engineer's message. No AI model
Why fewer came, and what to do about itThe site engineer gives the reason. The project manager gives the commitment
The closing summary of what was savedThe AI, from the saved values only, told never to recompute them

Usually the AI reads, fixed logic calculates, a person confirms. Here there is no document to read.

[07]More detailViya Constructions

The rules it follows

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

RuleWhat it does
Actual laborNever read or written here. Planned labor is never described as actual.
Linked sites onlyOnly projects ProjectSignal reports as linked to a site. The same name is not a link. If links cannot be read, it says so and never shows an empty list.
Whole numbers0 to 100,000 per day. Blank means not planned. A blank Sunday with nothing saved is saved as 0 when another day in its week changed.
Only changes are sentA day is sent only if it differs from the record. Locked days never. At most 300 days per save.
A revision needs a reasonUp to 1,000 characters, one per save. ProjectSignal refuses a revision without one.
Rounding and totalsEach day is rounded once to whole rupees at its own site's rate. Totals add those days.
On track or behindLabor achieved against labor planned to date. 85% or more is on track. Judged in labor, never rupees, so a budget correction cannot flip it.
Unplanned daysLabor on a day with nothing planned counts as achieved and is flagged, so a week can read above 100%.
Reading the headcountA stated total wins. Otherwise one count per trade line is added, leaving out engineer, supervisor and manager lines. A range such as 2-3 counts as 3.
11:30 cut-offAn update after 11:30 is not escalated that day. A commitment is final once given. The escalation is switched on per site by an administrator and starts off.
What it means for you

Three readers, three answers.

  1. For owners

    A slip shows on the day it starts

    A shortfall is raised with the site that morning, and at 11:30 with the manager where the escalation is on.

  2. For operations heads

    The weekly review starts from planned against actual

    ProjectSignal works it out per site and per manager. Site engineers keep posting the update they already post.

  3. For your technical person

    Writes go through the platform, as the person

    One calculation shared by card and save, and no AI model in the path that produces a number.

Is this your problem too?

Four signs, and what we need to start.

  • Project managers start the day reading every site group
  • The week's labor plan lives in a spreadsheet, or in someone's head
  • Every site is measured at one rate, whatever its budget split
  • You learn a site was short when the milestone date moves

To start we need a week of your labor plan and of site updates as they exist, each site's labor and total budget, and one owner with thirty minutes a week.

When a site gets nine workers instead of fourteen, who finds out, and on which day?

Send us a week of your labor plan and a week of site updates, as they exist. We will show you how the two could be compared each morning. Start with one workflow. You only pay if it works.