BuildSuiteBuildSuite
GitHub Book a demo

BuildSuite Workforce

Attendance to payslip, without a spreadsheet in between.

Mark a whole gang in one screen, let overtime slabs calculate themselves, and generate a WPS bank file your bank accepts first time.

Field attendanceOvertime slabsPayslipsWPS SIF export
Book a demo
app.buildsuite.io / workforce / field attendance
On roll148
Present today132
Overtime hrs214
Payroll₹12.42 L
GangTradePresentOT hrs
Gang AShuttering28 / 3046
Gang BSteel fixing24 / 2438
Gang CMasonry31 / 3452
Gang DFinishing22 / 2630

Overtime calculated automatically · bank file in your bank’s exact format

Key features

Made for gangs, not desk staff.

Attendance

Mark a gang at once

Full day, half day, absent and overtime per category from the mobile app, a tablet kiosk, or a biometric device that syncs into check-ins.

Overtime

Slabs that calculate

Configure your rules once — weekday, weekend, holiday, night — and stop arguing about hours at month end.

Payroll

Bulk payslips

Salary structures with allowances and deductions, generated in bulk and emailed out.

Compliance

WPS bank files

Fixed-width SIF export in your bank's exact specification, with the filename preserved.

Costing

Labour cost per project

Every work session lands against the right project, so labour cost reaches the project P&L on its own.

Access

Role-based

Supervisors mark their own gangs. HR sees payroll. Nobody sees more than they should.

Why it goes wrong

Site payroll fails in four predictable places.

None of them are exotic. They are the same four every contractor hits, every month, and every one of them starts with the same root cause: the muster and the payroll live in different places.

01
Attendance errors delay the whole runOne disputed gang holds up 148 payslips while somebody walks back through paper
02
Overtime and deductions get miscalculatedSlabs applied by hand differ by whoever applied them, and nobody can show their working
03
WPS and SIF files are assembled manuallyA fixed-width format rebuilt in a spreadsheet every month, rejected by the bank on a stray character
04
Labour cost never reaches the projectPayroll closes, and the project P&L still shows last month’s labour — or none at all

Capture

However the mark is made, it lands once.

A tower site with a turnstile and a villa site with one supervisor and a phone should not need two systems. They do not: every capture method writes to the same muster record, tagged to the project it was worked on.

Four ways to capture attendance, feeding one muster record Supervisor app marks a whole gang Tablet kiosk at the site gate Biometric device syncs into check-ins Worker self-mark geofenced One record Daily muster 148 on roll · 132 present Labour cost to the project P&L, by cost code Payroll run hours, OT and absences However the mark is captured, it lands in the same record — and only once.

Why one record matters

The moment attendance exists in two places, month end becomes a reconciliation. One record means the number HR pays against and the number the project is charged are the same number, not two that agree most of the time.

Single source

When the site has no signal

Marks queue on the device and sync when the phone next sees a network. A supervisor is never blocked, and nothing is lost to a basement or a remote plot.

Offline first

The monthly run

From locked muster to a file the bank accepts.

Every step reads the step before it. Nobody retypes an hour, and the WPS SIF file is generated to your bank’s exact fixed-width specification rather than assembled by hand in a spreadsheet.

From locked muster to a WPS bank file 01 Muster locked at month end 02 OT slabs applied weekday, weekend, holiday 03 Deductions advances, mess, fines 04 Approved by HR and the PM 05 Payslips + SIF bank file, exact spec Nobody retypes an hour. The file your bank accepts is generated, not assembled.
Locked
The muster closes and stops movingLate corrections become dated amendments, not silent edits
Approved
HR and the project manager both signFull audit trail — who approved which gang, and when
Exported
SIF in your bank’s specification, filename preservedRejected files are usually a format detail, not a data problem

Overtime

Configure the rules once. Stop arguing about hours.

Weekday, weekend, night and public holiday each carry their own multiplier. Set them to match your contracts and local law, and the muster does the arithmetic every month after — identically, and with its working visible.

How overtime slabs turn hours into pay Slab Hours Rate Pay Weekday 8 h 1.00× ₹520 Weekday overtime 2 h 1.25× ₹163 Weekend 8 h 1.50× ₹780 Public holiday 8 h 2.00× ₹1,040 Base ₹65/hour. Configure the multipliers once; the muster does the arithmetic every month after.

One worker, one week — illustrative rates

Where the money actually goes

Holiday hours cost double, and they are the hours most often recorded loosely. Seeing the multiplier against the hours is usually the first time a contractor can price a shift decision before making it.

Cost visibility

Different rules per site

A Qatar site and a Kerala site do not share overtime law. Slabs are configured per company, per site or per labour category — not hardcoded into one global setting.

Multi-region
Before

Paper muster rolls

Rewritten into Excel, argued over, then keyed into payroll a third time.

After

Marked once on site

Attendance, overtime, wages and cost all read from the same entry.

Result

Payroll in one run

Al Fikree cut a multi-day monthly process to a single approval.

Get started

Bring one messy project to the demo.

Thirty minutes on your BOQ, your labour categories, your cost codes — and you’ll know whether it fits.

Book a demo Or self-host it