Decide Which Monthly Report You Are Producing

A monthly attendance report is not a single spreadsheet. HR may need a muster-roll style grid for a labour inspector. Payroll needs payable categories that map to salary, overtime, and loss of pay. A client or internal cost centre needs whether contracted coverage was delivered. If those three audiences share one Present/Absent sheet, each team will recut the file and the organisation will end the month with three competing totals.

Name the audience before you name the columns. An inspection or statutory view usually needs the establishment, the named person, calendar days, hours of work, overtime, weekly off, and leave. A payroll attendance summary needs present days, paid leave, unpaid leave, LOP, overtime units, holiday work, and any arrears adjustment. A client or billing view needs the post, shift window, and whether the contracted headcount was covered. Those are related projections of the same events, not interchangeable numbers.

Write the conversion rules in plain language. Until the business decides whether a late check-in is still Present, whether a missing punch is Absent or Exception, and whether a weekly off that was worked is overtime or a separate premium, the monthly report is a negotiation. The report should apply those rules the same way for every employee in the period.

• Separate labour-inspection, payroll, and client-billing versions of the month
• Define how events become Present, Absent, Weekly Off, Leave, Holiday, OT, and LOP
• Do not force every audience to read the same Present/Absent grid
• Document the period, timezone, and employee population the report covers

Build the Column Set Before You Fill Any Cell

Start with identity and context, then add status quantities. Every row needs a stable employee ID, legal name, department or cost centre, and the site or post that owns the day. Then add the calendar: either a day-wise grid for the month or a summary of days and hours. The status columns that most Indian shift operations actually use are Present, Absent, Weekly Off, Leave, Holiday, Overtime, and LOP. If any of those is missing, payroll or an inspector will ask you to rebuild the file.

Keep leave types visible. Casual, sick, earned, unpaid, maternity, and compensatory off do not have the same payroll or statutory effect. A single letter L hides whether the day is paid and whether the leave balance was actually debited. Overtime and LOP should be quantities, not flags. OT = Yes cannot feed a salary engine; record approved hours or units, and keep LOP as days or hours according to the pay policy.

Add the evidence columns that let a reviewer defend the status: scheduled shift, first in-time, last out-time, regular hours, and exception count. A monthly summary that shows only totals is hard to reconcile when an employee disputes two days or a client questions a billed post. The summary should still be readable; the evidence can live in a linked detail sheet or system drill-down rather than in a 40-column printout.

• Include Present, Absent, Weekly Off, Leave, Holiday, OT, and LOP as first-class columns
• Keep leave type and OT/LOP quantities instead of collapsing them into flags
• Retain employee ID, site, and period on every row
• Link summary totals to first-in, last-out, and exception detail

Derive Status From Events, Not From a Typed Cell

A supervisor typing Present into a monthly grid is not a report process. Status should be computed from check-in, check-out, the assigned shift, the leave calendar, the holiday calendar, and the weekly-off roster. That is the only way the same employee, on the same day, receives one consistent outcome across sites and reviewers.

Test the collisions that break homemade files. An employee on approved earned leave should not also appear as Present because a punch arrived from a previous roster. A weekly off with approved worked hours is not Absent, and it is not ordinary Present; it belongs in the weekly-off-worked or premium column your policy defines. A public holiday with no work is Holiday, not Absent. A half-day leave plus four paid hours should split rather than overwrite. These cases are where a monthly attendance summary either earns trust or creates disputes.

Keep unresolved exceptions out of the final status until someone decides them. A missing check-out is not yet Absent and not yet a full Present day. If you force every cell to look complete so the grid prints neatly, you hide the exact days payroll should not close. Show Exception or Pending as a visible state, then convert it only after approval.

• Compute status from punches, shift, leave, weekly off, and holiday calendars
• Prevent leave, weekly off, and holiday from being overwritten by a stray punch
• Split half-day and mixed-status days instead of forcing one letter
• Leave unresolved exceptions visible until they are approved

Roll Up Multi-Site and Multi-Shift Months Without Double Counting

Field, plant, and security teams often move people between sites inside one month. The company-level monthly attendance report must count the person once. The site-level report must attribute each day or shift to the location that owned the assignment. If both views simply sum raw punches, one employee becomes two FTEs and overtime appears twice.

Choose an attribution rule and apply it everywhere. The cleanest default is to tag each approved shift with the site on the roster for that day, then roll hours and statuses from those tagged shifts. Mid-month transfers, dual-site days, and night shifts that start at one location and end after midnight need an explicit owner. Do not let a GPS ping at a second gate silently create a second Present day.

Close site by site, then produce the company rollup from the locked site totals. A central HR user should not be asked to interpret every local exception. Site reviewers confirm the people and posts they actually supervise; HQ checks that the rollup matches employee master, joining and exit dates, and that no active employee is missing from the month.

• Count each employee once at company level and by assigned site at site level
• Attribute days and hours from the rostered site, not from incidental GPS pings
• Document night-shift and month-boundary ownership before closing
• Roll up from locked site reports rather than a second manual company sheet

Lock the Month After Payroll, Then Version Any Correction

Once payslips are generated from a monthly attendance summary, that version must freeze. A well-meaning edit to one Absent day after payday silently desynchronises payroll, the muster roll, and the client file. Locking does not forbid justice; it forces a late change into a numbered adjustment with a reason, an approver, and a target cycle.

Record what you locked: period start and end, version number, locker, timestamp, headcount, present days, leave days, weekly offs, holidays, OT hours, LOP, and open exception count. If a correction is later approved, create version 2 for the report pack and a corresponding payroll adjustment. Do not overwrite version 1. Inspectors, auditors, and employees all need to see which file produced the paid month.

Retention is part of the report, not an afterthought. Keep the locked summary, the employee-day detail, and the exception log together for the period your statutory and client contracts require. A PDF of totals without the events behind it cannot answer a query six months later.

• Freeze the attendance summary that payroll actually used
• Route post-lock edits as versioned adjustments, not silent overwrites
• Store locker, timestamp, status totals, and exception count with each version
• Retain summary, day-level detail, and exception log as one pack

Produce Inspection, Payroll, and Billing Views From One Source

The labour-inspection or muster-roll view should follow the format the inspector or contractor compliance team expects: named workers, establishment, daily marks or hours, overtime, weekly offs, and leave. It should not expose salary rates or internal pay codes. Generate it from the same locked events as payroll so the inspector is not looking at a parallel handwritten register.

The payroll attendance report maps those events into pay categories: payable present days or hours, paid leave, unpaid leave, LOP, overtime, holiday work, and arrears. This is the file finance uses, not a reprint of the inspector grid. The client or billing view is different again. It answers whether a post, shift, or contracted headcount was covered, which may not equal the employee’s payable hours when a relief guard, overlap, or non-billable extra hour is involved.

Attend Mitra is built so verified attendance, leave, weekly offs, overtime, and site tags can feed all three views from one period close. Managers review exceptions before lock; analytics then produce the monthly attendance summary, while payroll and client reports remain separate projections rather than competing spreadsheets. Run one complete month this way before you scale the pack to every site. Hours behind the grid come from how to calculate employee hours for payroll. Clear exceptions first with how to reduce attendance errors before payroll, then prepare attendance for payroll. A starter layout is the attendance report template; analytics views live in workforce analytics.

• Generate muster-roll, payroll, and client versions from the same locked events
• Keep inspector views free of salary rates and internal pay codes
• Do not treat billed post coverage as identical to payable employee hours
• Review exceptions, lock the period, then export the three official views