Monthly working-hours gaps and reminders

A monthly working-hours gap is expected hours minus recorded hours: missing punches, days still open, or shifts that closed short of what the roster said. It is an operations signal for close week, not a statement of legal working-hour caps, and not a utilisation or billing report. Chase the gap before payroll freeze so loss of pay is a decision after regularisation and leave, not a surprise on the payslip.

This page sits in the monthly people-ops loop as the attendance-hours chase. LOP handoff mechanics stay on attendance to payroll and LOP. The last mile of lock-calculate-payslips stays on the payroll-run checklist. Do not treat those three as copies of each other.

Define expected hours before you subtract

You cannot spot a gap without a published expected figure for the period. Expected hours usually come from the roster: working days in the attendance month, times the shift length, adjusted for joiners, exits, approved leave, weekly offs, and holidays your policy treats as not-worked. If expected is “whatever the director feels,” every gap is an argument.

Recorded hours usually come from closed punches: in to out, minus unpaid breaks if you configured them, plus any regularised duration your policy allows. Open days (in without out) are not recorded hours yet. They are exceptions. Counting them as zero and counting them as a full shift are both policy choices — pick one in writing and apply it only after the exception queue has had its chance.

Do not import a nationwide cap, factory-act table, or “maximum weekly hours” here. Those questions belong in a later compliance article that this site has not published. Your expected figure is the company’s roster math for this cycle.

A gap is a difference between two numbers you defined. If either number is informal, you are not measuring hours. You are rehearsing a dispute.

Where gaps come from

• Missing in or missing out. The day is incomplete. Auto punch-out may have closed it at a default time, or auto-absent may have marked the day. Either way, the hours may not match what the person claims. Regularisation is the path if policy allows a correction.
• Open days still sitting in the calendar. Nobody closed them. They will become whatever your freeze rule says — often unpaid — unless a manager acts.
• Short shifts. The person punched a window shorter than the roster, after grace. That may be half-day attendance, half-day leave, LOP, or an allowed short day. The gap report should not invent the outcome; it should list the day for a human decision.
• Wrong shift instance. Night work dated to the civil morning, or a swapped roster never updated, so expected and recorded attach to different days.
• Identity misses. New joiners not on the roster, exits still attracting expected days. Those are master-data gaps dressed as hours gaps.

Do not treat a timesheet shortfall (unallocated client hours) as this gap. Presence versus effort is a different article. This chase is expected roster time versus attendance time.

The close-week process

Run the gap list on a fixed weekday before freeze, not on payday morning. Attendance management is useful here if it can show a monthly calendar, logs, pending regularisation, and a team matrix so managers are not hunting through chat screenshots.

1. Build the list per employee: expected hours, recorded hours, open days, pending regularisation, pending leave that overlaps the period.
2. Drop rows that are already explained (approved leave, weekly off, holiday) so managers do not “explain” rest days as missing work.
3. Send each manager only their team. A company-wide dump is how everyone ignores the file.
4. Set a reply-by time that is still before attendance close, which is still before payroll input freeze.
5. HR records outcomes: regularised, leave applied and approved, confirmed unpaid, or deferred to next cycle under a named exception.

The reminder is not a motivational poster. It is a queue with owners. If the only reminder is “please complete attendance,” managers will complete nothing measurable.

What the reminder should contain

• Employee name and ID.
• Dates still open or short, not a single monthly total without dates.
• Whether a regularisation or leave request is already sitting with the manager.
• The close datetime (IST, or your named timezone) after which the day will freeze as policy default.

Totals without dates produce fake closures: a manager “confirms 8 hours” for a day that still has no punch. Dates without totals bury people who are short every day by twenty minutes. Send both.

Regularisation and leave so LOP is a decision

A gap is not automatically LOP. LOP is what remains unpaid after you have applied the rules you published: allowed regularisation, approved paid leave, holidays, and rest days. If HR types LOP from the gap report without offering the exception path, employees learn to fight payslips instead of closing days.

Typical decision tree for one short or open day (adapt to your policy; this is not law):

1. Is the day a weekly off or holiday? Then it should not be in the gap list as missing work.
2. Is there a pending regularisation? Manager approves or rejects before freeze.
3. Should the person apply leave (full or half-day) instead of claiming presence? Leave close must still beat payroll freeze.
4. If neither correction nor paid leave applies, the unpaid remainder is LOP (or your unpaid code), derived for payroll — not negotiated on payslip day.

Spell regularization in policy titles the way your product and articles do; employees may still search “regularisation.” One term in the SOP, one alias in search, not two conflicting processes.

Do not reopen the entire month because one manager was late unless you have a written off-cycle rule. Late explanations become next-cycle items. That is how a freeze stays real. The payroll-run checklist then consumes frozen inputs; it should not become the place where hours are still being hunted.

What not to do with the gap report

• Do not publish it as proof of legal overwork or underwork. You have not established statutory caps on this page.
• Do not auto-fill punches to kill the gap. That destroys the presence record.
• Do not mail the whole company a leaderboard of “short hours.” Shame is not a close process; it also mixes honest outdoor work with genuine misses.
• Do not mix billing utilisation into the same spreadsheet. Delivery owners will hijack the HR freeze.

A plant with overtime and a plant with strict shift end will show different gap shapes. Expected hours must follow that roster. Copy-pasting another company’s expected figure is how you manufacture a crisis.

Joiners, exits, and mid-month shift changes

Pro-rate expected hours from the joining date and through the last working day. A joiner who started on the 18th should not carry expected hours for the 1st–17th. An exit on the 12th should not remain expected through month end. Mid-month shift-length changes (moved from 8-hour to 9-hour roster) need a dated expected figure, not an average that hides the change.

If the gap list is wrong because identity is wrong, stop chasing minutes and fix the roster. Hours math on the wrong headcount is theatre.

Cadence during the month, not only at freeze

Weekly gap snapshots for managers reduce close-week volume. A person with three open days by the 10th is cheaper to fix than the same three days discovered on the 2nd of next month. Keep weekly notes light: open days and pending requests only. Save the full expected-versus-recorded total for close week so you do not argue incomplete months as if they were final.

HR’s job is to make the queue visible and to refuse silent defaults. The manager’s job is to decide presence, leave, or unpaid for each dated line. Payroll’s job starts after that decision exists in the record.

Name a backup owner when a manager is on leave during close week. Unassigned queues become company-wide LOP, which is not a policy — it is neglect. The backup should receive the same dated list, not a verbal “look after the team.” If a site is offline for a known outage, record the outage as a mass exception with a time window, then regularise or mark on-duty under the written rule. Do not wait to discover fifty open days in the gap report and invent hours in a side sheet.

Short shifts that repeat on the same person are a pattern, not fifty one-off gaps. Close them day by day for this payroll cycle, then ask whether the roster length is wrong, the grace is fiction, or the person needs a different shift. Changing expected hours after freeze to make the gap disappear is the same as auto-filling punches. Change the roster from a named effective date going forward.

When recorded hours exceed expected hours, treat that as a separate queue: possible overtime, a missed weekly off, or a double punch. This article’s job is the shortfall before freeze. Do not silently convert extra minutes into a billing asset or into unpaid time without a policy line. Extra is not the inverse of a gap until you say what extra means.

---

List expected hours against recorded attendance hours, with dates, before you freeze. Remind managers with a dated queue. Finish regularisation and leave so LOP is chosen, not stumbled into. Do not use this chase as a legal hours-cap article, and do not turn the payroll-run checklist into a second hunting ground. Close the gaps, then calculate.