Attendance vs timesheets: which one do you actually need?
Two overlapping-but-distinct systems for capturing time worked. A decision framework, and why most Indian AEC practices need both — not one or the other.
Every site office in India has two clipboards. One for daily attendance — who showed up, who didn't, who came in half a day. Another for weekly timesheets — what each person billable-worked on, against which project.
The digital version of this is where most SaaS tools make a mistake: they pick one and pretend it covers both.
What attendance is for
Attendance answers the question "was this person on this site on this date?"
It matters for:
- Daily-wage contracts — labour paid by day present, not by hour billed.
- PF and ESI compliance — statutory reporting needs presence records.
- Insurance liability — site accidents are settled with attendance as evidence.
- Pay parity audits — equal work, equal pay requires presence tracking.
Attendance is binary-ish: present / absent / half-day / leave / holiday.
What timesheets are for
Timesheets answer "how did this person spend their billable hours?"
They matter for:
- Hourly billing — architecture consultancy fees, supervision contracts.
- Project profitability — how many design hours did Project A actually consume?
- Utilisation reporting — is the team 85% utilised, or are we staffing incorrectly?
- Timesheet-to-invoice conversion — turn approved billable entries into a draft invoice.
Timesheets are granular: startTime, endTime, break, activity type, project, milestone.
The overlap
At the site office, the on-site engineer is in both systems. They're present (attendance), and their 9 hours at the site are billable design-supervision hours (timesheet). One system each tracks — and you don't want to enter the data twice.
Blueprint solves this by having both first-class:
- Attendance has a unique constraint of
(user, project, date)— one record per person per project per day. - Timesheets have a unique constraint of
(user, week)— one sheet per person per ISO-week.
The mobile app lets the engineer check in once and optionally attach a time entry to the same record. The PM sees both.
When you only need one
- Desk-bound architecture studio — timesheets only. Attendance doesn't matter unless you're doing statutory payroll.
- Daily-wage-only contractor — attendance only. You don't bill by the hour.
- Everyone else — both.
How to migrate if you're currently on paper
- Digitise attendance first. It's the faster win and the statutory obligation.
- Layer timesheets on top once attendance is habitual. Start with billable roles; expand slowly.
See time tracking for how Blueprint handles both without double-entry.
Further reading
How to generate GST-compliant RA bills in Indian construction
A practical walkthrough of running-account (RA) bills under Indian GST: what fields are mandatory, how cumulative amounts work, how CGST+SGST vs IGST splits apply, and where TDS 194C fits.
16 Apr 2026 · 3 minRERA milestone tracking: a guide for Indian builders
What RERA expects from builders on milestone reporting, how to structure milestones to match your registration, and how to avoid the three most common compliance gaps.
12 Apr 2026 · 3 minCGST vs SGST vs IGST for construction contractors
The single rule that decides whether you charge CGST+SGST or IGST on a construction contract, with three worked examples covering common edge cases.