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.
[01]What changedViya Constructions
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 crew of ten on a labor-heavy site and on a material-heavy one build different value. One company-wide rate judges both alike.
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.
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.
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
A guided job in Bleno. The project manager types the crew. ProjectSignal and fixed logic supply the rest.
The project manager types "/" and picks the labor plan. A card opens on the current planning week, Sunday to Saturday.
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.
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.
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.
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.
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.
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.
[04]Connected to ProjectSignalViya Constructions
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.
[05]The next morningViya Constructions
This part runs in ProjectSignal, from updates site engineers already post in their Telegram groups.
India time. The 09:00 note covers turnkey sites, where the company executes the work end to end.
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.
Morning work update. Total labor: 9.
Site B had 14 people planned today, but your update reports 9. Why didn't the other 5 come to site?
Shuttering team moved to Site F for slab casting, back tomorrow.
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.
1. Two carpenters from Site D tomorrow, extra shift Saturday.
[06]Who decides whatViya Constructions
Usually the AI reads, fixed logic calculates, a person confirms. Here there is no document to read.
[07]More detailViya Constructions
A shortfall is raised with the site that morning, and at 11:30 with the manager where the escalation is on.
ProjectSignal works it out per site and per manager. Site engineers keep posting the update they already post.
One calculation shared by card and save, and no AI model in the path that produces a number.
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.
[08]Where this fitsViya Constructions
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.