One Person Can Have Several Duties. Hours Still Have to Add Once

Multiple shifts in one day are normal in Indian factories, security agencies, and multi-outlet operations. A setter may run 06:00–14:00 on Line A and return 18:00–22:00 for a changeover. A guard may finish Gate 1 at 14:00 and start a second site at 16:00. A naive timesheet that allows only one in and one out will either merge those duties into an 16-hour blob or drop the second duty entirely.

The correct record is one employee, several shift events, and one hours total. Each event needs its own scheduled shift, site or post, check-in, check-out, unpaid break, and approval status. Totals are derived: paid hours for the day, paid hours for the week, overtime, and rest-day premium. If you store only the daily total, you cannot explain which duty created the overtime, and you cannot prove rest between the two duties.

Do not create a second employee record to 'keep sites clean.' That is the fastest path to double pay. The identity stays one. The assignments multiply. Client billing and factory cost centres should slice the same events by site, not by cloned names.

• Store each duty as its own in-out event with site and shift context
• Derive daily and weekly totals from events; do not type a second total
• Keep one employee identity across every site and duty
• Never clone a person in the master to make a second shift 'fit'

Split Duties Need Two Check-Ins and Two Check-Outs

A split shift is two (or more) paid blocks separated by an unpaid gap on the same calendar day. Example: 10:00–15:00 and 18:00–23:00. If the employee only punches once in the morning and once at night, the unpaid 15:00–18:00 gap becomes paid time unless someone remembers to subtract it. That 'remembering' is how split-shift payroll goes wrong.

Require a check-out at the end of block one and a check-in at the start of block two. The gap is then visible. Policy decides whether travel between blocks is paid; the system should not guess. If the gap is a mandated break rather than a split, that is a different template and should not use two shifts. Mixing 'unpaid lunch' with 'split duty' in one rule set is how factories accidentally pay or dock the wrong interval.

Calculate each block, then add. Block 1: 10:00–15:00 with no unpaid break is 5.00 hours. Block 2: 18:00–23:00 with no unpaid break is 5.00 hours. Day total is 10.00 hours, not 13.00. If the daily overtime threshold is 8.00, the report should show 8.00 regular and 2.00 overtime, attributed to the day, with both blocks still visible for audit. Rounding each block independently and then adding can produce a different overtime result than adding minutes first; pick one method and keep it.

• Use a separate check-in and check-out for each paid block
• Treat the gap as unpaid unless policy explicitly pays travel or on-call
• Add block durations, then apply the daily overtime threshold
• Keep both blocks on the audit trail after the total is calculated

A Second Site on the Same Day Is a Second Assignment

When the second duty is at another location, the roster must say so before the person travels. Example: a maintenance technician finishes Plant A at 14:00 and is due at Plant B at 16:00. If attendance at Plant B is marked against Plant A's geo-fence, it will fail or, worse, be forced through as a manual override with no site context. Payroll then cannot bill the second plant, and the first plant looks overstaffed after 14:00.

Create the second assignment as a shift on the second site, with its own fence, grace, and break rule. The first assignment should end with a check-out. The second should start with a check-in at the second fence. If the employee is still showing as on duty at Plant A, supervisors at both sites will make bad coverage decisions.

Travel time needs a written rule. Some employers treat the gap as unpaid. Some pay a fixed travel allowance. Some count travel toward hours when the second site was assigned the same morning. Whatever the rule is, it should not be inferred from GPS breadcrumbs. Record the two duties, record whether travel is payable, and keep the original punches.

• Assign the second site as its own shift before the person leaves the first
• Check out of site one and check in at site two; do not stretch one punch
• Attach each event to the site that must be billed or costed
• Write the travel-time pay rule; do not infer it from location traces

Enforce Rest Between Shifts and Rest-Day Overtime

Two legal-looking shifts can still be an unsafe day. A 06:00–14:00 factory duty followed by 15:00–23:00 'overtime support' is a 17-hour spread with a one-hour gap. Rest between shifts is a roster control, not a payroll afterthought. If the minimum rest is 11 hours, the second duty should not have been publishable. If the business still needs the work, it belongs to a different person or to a later day.

Rest-day overtime is a different category from ordinary second-shift hours. If Tuesday is the weekly off and the employee works 08:00–16:00 plus 18:00–22:00, both blocks may attract weekly-off premium rather than ordinary overtime, depending on policy. Mixing them into 'extra hours' understates cost and mis-states statutory reporting. Keep rest-day hours in their own column even when they came from two punches.

Security work produces a sharp version of this. A 12-hour night ending 06:00, a verbal request to 'just cover the gate until 10:00,' and a second 12-hour night starting 18:00 is three duties pretending to be two. Track the middle cover as its own event. If you fold it into the night that just ended, you hide both the rest violation and the extra pay.

• Block a second duty that violates the minimum rest from the previous check-out
• Keep weekly-off and holiday work in premium columns, including split blocks
• Record held-over covers as new events, not as stretched original shifts
• Show spread-of-hours for the day alongside paid hours

Where Hours Get Double-Counted

Double-counting is the characteristic failure of multi-shift tracking. The usual mechanisms: (1) a daily total typed on top of automatically summed blocks; (2) an overtime row copied from a supervisor chat and also generated from punches; (3) the same person imported twice, once per site; (4) a split shift stored as one long shift and as two short ones; (5) a midnight-crossing night counted in both days. Any one of these will survive a casual glance at a spreadsheet.

Prevent it with a uniqueness rule: one paid minute belongs to one event. Totals are always computed. Overtime is always computed from those totals using the policy, then approved, never typed as a parallel fact. If a supervisor needs to add a duty that was missed, they add an event, not a number. If they need to correct a punch, they correct the punch and leave the total to recalculate.

Reconcile before payroll with three cross-checks: sum of event hours versus daily totals, sum of daily totals versus weekly totals, and sum of weekly totals versus the payroll export. Then scan for employees with two identities, overlapping in-out intervals, and events with no site. Overlapping intervals — still checked in at Site A while already checked in at Site B — are almost always a missing check-out, not heroic double presence.

• Never store a typed total alongside derived event hours
• Add a missed duty as an event, not as an overtime number in a side column
• Reject overlapping in-out intervals until a missing check-out is resolved
• Reconcile event, day, week, and export totals before the pay run

Close Factory and Security Multi-Shift Days Cleanly

A factory example that should become a test case: Ramesh, fitter. Event 1: 06:00–14:30 at Plant A, 30-minute unpaid lunch, 8.00 paid hours. Event 2: 16:00–20:00 at Plant A tool room, no unpaid break, 4.00 paid hours. Rest between events is 1.5 hours. Day total 12.00 hours. If daily OT starts at 8.00, that is 8.00 regular and 4.00 overtime, provided the second event was approved as overtime and rest policy allows it. If rest policy forbids it, the second event should have been refused at scheduling, not argued at payroll.

A security example: Meena, unarmed. Event 1: Site 12, 06:00–18:00, 12.00 hours. Event 2: Site 19, 20:00–00:00, 4.00 hours. The gap is 2 hours. Site 12 and Site 19 must both appear on the client reports. Payroll pays Meena 16.00 hours under the applicable OT and rest-day rules. Billing charges Site 12 for a 12-hour post and Site 19 for a 4-hour extra cover. If those two commercial facts are collapsed into 'Meena worked 16 hours,' both clients will dispute.

Attend Mitra is designed so multiple check-ins and check-outs can sit on one employee, each against a published shift and site, with hours rolled up once for payroll. Supervisors see overlapping or rest-breaking assignments while the roster is still a draft. Payroll sees approved events rather than a single in-out that cannot explain a split day. Cross-midnight math is how to calculate night-shift hours for payroll. Late-plus-extra days need how to calculate half day and overtime together. Totals follow how to calculate employee hours for payroll. Build the week with how to schedule hourly employees.

• Test a same-site split and a two-site day before going live
• Keep client or cost-centre hours aligned with the events, not with a person total only
• Refuse rest-breaking second duties at scheduling when policy requires it
• Export event-level hours with the payroll total so disputes can be answered