A crew can look fully staffed and hard at work while producing well below what the wage bill assumes — and nothing in a typical attendance register would ever show it.
Every Indian construction site tracks attendance carefully — who showed up, for how many hours, at what wage. Almost none track the other half of the equation: how much work that attendance actually produced, measured against what the BOQ or estimate assumed a crew of that size should deliver in a day.
Productivity shortfalls trace back to the site, not the worker: material not staged in time, unclear or overlapping task assignment, waiting on a preceding trade to finish, and rework from quality issues. A mason crew standing idle for forty minutes waiting on cement to arrive is still "present and working" on the muster roll — but the day's output tells a different story.
A 25-worker crew at ₹650/day achieving 78% of planned output instead of a disciplined 95%+ effectively pays for roughly a fifth of its labour-days without corresponding progress. Across a full project, that gap is frequently larger than any single material overrun — because the wage bill keeps accruing regardless of what actually gets built.
It does not require new equipment or a big process overhaul — it requires logging actual quantity completed per crew per day against a planned rate (e.g. sqm of brickwork, cum of concrete), and reviewing any crew running consistently below 90% of plan as a trigger to investigate the cause, rather than treating it as normal variance.
The sites that catch this log actual quantity completed per crew per day against the planned rate — sqm of brickwork, cum of concrete — and treat any crew running consistently below 90% of plan as a trigger to investigate the cause, not as normal variance. Since the root cause is almost always upstream of the crew itself (staging delays, unclear sequencing, waiting on a preceding trade), the fix usually isn't a stricter supervisor — it's removing whatever is keeping a present, willing crew from being able to work.