Running a Mixed Workforce: Permanent, Contract and Daily-Wage Staff in One System

Ask most Indian employers how many people work for them and you will get a pause, then a qualified answer: so many on the rolls, plus a contract team at the plant, plus however many walk-ins were engaged this week. That hesitation is not sloppiness — it reflects a genuine structural fact. A single business commonly runs several workforces at once, each with a different engagement model, a different pay rhythm and a different set of obligations. The mistake is not having three workforces; it is pretending you have one.

The pretence usually takes the form of a single employee master that everyone gets pushed into, with a 'type' field bolted on to tell them apart. It looks tidy for about a quarter. Then someone runs a headcount report that silently includes last month's walk-in labourers, or a payroll run that assumes a monthly CTC for a person paid by the day, and the tidiness turns out to have been a liability.

Three workforces, three rhythms

The clearest way to see why separation matters is to look at what each group actually needs from the system on an ordinary day.

• Permanent employees: a full profile, leave balances, a monthly pay run, appraisal cycles, self-service access and a long document trail.
• Contract and deputed staff: site and supervisor scope, attendance against a deployment rather than a desk, and wage rules driven by state minimum-wage schedules rather than a negotiated CTC.
• Daily-wage and walk-in workers: registration that takes minutes rather than an onboarding workflow, attendance marked by a supervisor on site, and payment on a daily or weekly cycle that cannot wait for month-end.

These are not variations on a theme. A monthly pay run and a daily-wage pay run are different processes with different inputs, and a system that treats the second as a special case of the first will keep producing surprises.

Separate registers, one platform

The resolution is not three systems — that just moves the problem into the gaps between them. It is one platform with genuinely separate registers: walk-in workers registered apart from permanent employees, with their own attendance marking, their own salary components and shifts, and their own pay runs and payslips that are independent of monthly employee payroll. Each workforce is operated on its own terms, while leadership still gets a single consolidated view when they ask how many people are on site this week.

Compliance does not follow the same split

Here is the part that catches employers out: the operational separation between these groups does not map neatly onto the compliance separation. It is tempting to assume that statutory obligations attach only to the permanent roll, but minimum-wage schedules, overtime rules and PF/ESI eligibility can apply well beyond it, depending on engagement terms, wage levels and how long someone has been engaged. Getting this wrong is not a reporting inconvenience — it is a liability that surfaces during an inspection, often years later.

1. Hold minimum-wage rates by state and skill category, and apply them to the workforce they actually cover — not just to permanent staff.
2. Calculate overtime against the rules that apply to each engagement type rather than a single company-wide assumption.
3. Assess PF and ESI eligibility per worker on the facts, and keep the record that shows how the assessment was made.
4. Track PPE issue and return for anyone entering a site, regardless of which register they sit in.

That last point is worth dwelling on, because safety obligations are indifferent to employment category. A walk-in worker on a shop floor needs the same protective equipment as a permanent one, and if something goes wrong, 'they were only engaged for the day' is not a defence. A PPE policy with a per-worker issue and return record closes that gap.

What good looks like

A well-run mixed workforce feels unremarkable from the inside. Supervisors mark site crew attendance on their phones with location capture, and it lands in the same place HR looks. Walk-in workers are registered on arrival against a site and a supervisor, and a registration report can be pulled for any date range. Daily-wage payroll runs on its own cadence with its own components and payslips. Monthly payroll runs untouched by any of it. And when the board asks for total headcount by site, one number comes back rather than three spreadsheets and an apology.

None of this requires treating your workforces as the same. It requires the opposite: acknowledging that they are different, giving each the register and the rhythm it actually needs, and letting the system do the consolidation instead of asking a person to do it in Excel at the end of every month. In MyBridge, the Daily Wage module runs exactly this way — walk-in workers, supervisor-marked attendance, independent payroll and PPE tracking, sitting alongside the permanent employee register rather than inside it.