Running Four Sites: Daily Reports, Labour and Material Requests

Picture a Coimbatore civil contractor building four residential projects at the same time: two independent houses, a G+3 apartment block and a G+4 commercial-cum-residential building in Tiruppur. Each site has its own engineer. The owner and an accounts person sit in a small office and visit sites when they can.

Most of what the office knows about the sites arrives as photos and voice notes in chat groups. Progress is described differently on every site. One engineer sends ten photos and no quantities; another sends a typed list once a week. When a client asks how far the slab work has reached, the owner has to call the engineer and wait.

Labour is the larger headache. About 120 workers come through three labour contractors, and attendance sits in notebooks at each site. At month-end the accounts person types those notebooks into a spreadsheet, works out overtime by hand and subtracts advances from memory and slips. Every wage cycle ends with at least one argument over days and amounts.

• No common report format. Sites cannot be compared, and old reports cannot be found.
• Attendance retyped every month. Mistakes creep in between the notebook and the wage sheet.
• Material asked for by phone. Requests are forgotten, duplicated or arrive after the work has stopped.

In this scenario the contractor does not try to change everything in one go. They start with the three things that cause the most daily friction: the site report, attendance and material requests. Everything else stays as it is for now.

One daily report format for every site

Each project is set up with its locations, such as blocks, floors and work fronts, so every entry is tied to a place. Engineers file the daily progress report from a phone browser before leaving site: each work item with quantity, unit and labour, plus photos stamped with where they were taken. The owner approves each report, or rejects it with a reason so the engineer knows what to fix.

Attendance that becomes the wage sheet

The worker register is imported from the existing spreadsheet using CSV import, with each worker’s trade, skill, daily wage and labour contractor. Shifts are set up once. Supervisors then mark labour attendance each day with check-in, check-out and overtime, and the muster roll builds itself from those entries.

• Wage sheets are generated from attendance for the period, not retyped.
• Advances already given are entered against the worker, so the sheet shows the net amount.
• Once wages are handed over, the sheet is marked paid and the record stays with the project.

Material requests instead of phone calls

When a site needs cement, steel or blocks, the engineer raises a material request with a priority and the date it is needed. The office approves it and issues stock from what is held, with every stock movement recorded against the project. The owner can see what each site has asked for and what is still pending, without ringing anyone.

With this workflow, the office sees every site’s report the same evening in the same format. The owner can answer a client’s question about progress by opening the report, and can download it as a PDF to share. Reports are searchable by project and date, so a dispute about when a slab was cast can be settled from the record.

Wage day becomes a check rather than a rebuild. The wage sheet comes from the attendance supervisors already marked, and advances sit against each worker instead of on loose slips. When a labour contractor questions a count, the muster roll shows each day.

Material requests stop living in call logs. Each one has a date, a priority and a status, so the owner can see what is waiting for approval and what has been issued to which site. That gives the office a chance to act before a site runs short, rather than after.