Nursing Duty Roster & Hospital HR/Payroll Software for Indian Hospitals

A nursing duty roster is a staffing math problem before it's a scheduling problem

A roster isn't a calendar with names on it. It's the output of a calculation that has to account for leave reserve, night-duty equity, and skill-mix requirements simultaneously, and most of the reference material hospitals actually use for that calculation is decades old. The Staff Inspection Unit's 1991-92 norms — still the basis for staffing at central government hospitals — recommend a 10% leave reserve for maternity leave, earned leave, and routine days off, plus an additional 45% posts reserve specifically for units that run 365 days a year, 24 hours a day. On top of that, nurses doing three-shift rotation are entitled to 8 days off per month and 3 national holidays per year under the same norms.

These SIU norms also fix reporting-line ratios that most rostering conversations skip entirely: the nursing sister to staff nurse ratio is recommended at 1:3.6, the assistant nursing superintendent to nursing sisters ratio at 1:4.5, and the deputy nursing superintendent to assistant nursing superintendent ratio at 1:7. A roster that only tracks bedside staff coverage and ignores this supervisory chain will look adequately staffed on a dashboard while actually running without the layer of oversight the same norms assume exists.

What that means in practice is that a ward's sanctioned nursing strength is not the number of nurses needed to cover three shifts a day — it's that number plus roughly 55% more, once leave reserve and 24/7 posts reserve are both accounted for. A hospital that staffs to the bare shift-coverage number, without the reserve built in, is staffing for a ward with no one ever going on leave, which is not a real ward.

This gap between sanctioned strength and actual bedside coverage is where most tier-2/3 hospitals quietly run understaffed without anyone framing it that way. A ward budgeted for exactly the headcount needed to cover three shifts looks fully staffed on an org chart, right up until the first nurse takes earned leave or falls sick, at which point every remaining nurse absorbs the gap through unplanned overtime — which is itself the kind of pattern the Ministry's own working-hour guidance, covered below, is specifically trying to prevent.

Night duty distribution is where fairness and compliance intersect most visibly. A commonly used planning example: a ward needing 60 night duties covered in a month, with 19 nurses available, distributes as 16 nurses doing 3 nights each and 3 nurses doing 4 nights each:

That's a genuinely fair split — every nurse does at least 3 nights, only a few do a 4th, and the total adds up exactly. Building that distribution by hand across dozens of nurses, multiple wards, and rotating leave requests is exactly the kind of constraint-satisfaction problem spreadsheets handle badly and software handles as a matter of course.

Multi-location hospital groups compound this further. A group running the same specialty ward at two or three facilities often wants roster fairness measured across the group, not per site — a nurse who's covered a disproportionate share of nights at one facility shouldn't lose that history if she transfers to a sister facility mid-year. This is the same group-visibility problem we describe for bed management and OT scheduling in multi-location hospital ERP for chains and groups, applied to staffing fairness instead of patient capacity, and it's routinely the piece that gets lost when each facility runs its own disconnected roster spreadsheet.

The Indian Nursing Council's ratio numbers genuinely conflict across sources, worth flagging directly

Reference material on the 1985 Indian Nursing Council and Trained Nurses' Association of India norms disagrees on a specific, checkable detail: several sources state the recommended general-ward staff nurse ratio as 1:3 for teaching hospitals and 1:5 for non-teaching hospitals, while other equally citable sources state the reverse — 1:3 for non-teaching and 1:5 for teaching. Both framings appear in circulation as "the INC 1985 norm" without qualification. Rather than pick one silently, the honest position is that a hospital citing this ratio for policy purposes should verify against the original TNAI/INC 1985 documentation directly rather than a secondary summary, because secondary sources on this specific figure are not currently consistent with each other. What both versions agree on, and what actually matters more for day-to-day staffing than the exact direction of the ratio, is that teaching and non-teaching hospitals are not meant to be staffed identically — a system that applies one blanket ratio across every facility in a group, teaching status ignored, is already diverging from every version of the 1985 norms regardless of which direction the specific numbers run.

The Health Ministry's newer draft guidelines add explicit working-condition rules on top of the ratio question

Separately from staffing ratios, the Ministry of Health and Family Welfare has issued draft guidelines on nurses' working conditions that set out obligations closer to standard labour protections than clinical staffing math: normal work hours capped at 40 hours per week and 8 hours per day unless genuine exigency requires otherwise, with compensatory offs for overtime; duty rosters prepared and communicated in advance, with prior approval required for any change; mandatory internal complaint committees under the POSH Act, 2013; and specific measures for nurses' safety during night shifts, including adequate lighting in and around work areas. Nursing News India carries the fuller text of the draft guidelines, including provisions on staff accommodation and grievance redressal timelines that go beyond what's summarised here. None of this is aspirational language — each point is a concrete audit item, and a roster system that publishes shift assignments only a day or two ahead, or that changes them without documented approval, is out of step with the Ministry's own stated expectation.

The four new Labour Codes changed hospital payroll math on 21 November 2025

The Code on Wages 2019, the Industrial Relations Code 2020, the Code on Social Security 2020, and the Occupational Safety, Health and Working Conditions Code 2020 — collectively consolidating 29 older central labour laws — came into force on 21 November 2025. For hospital HR and payroll specifically, three changes matter immediately:

• EPF coverage widened. The Employees' Provident Fund now applies to every establishment with 20 or more employees, regardless of sector — previously EPF applicability was tied to a scheduled-industry list, and this removes that restriction entirely.
• A single wage definition, effective immediately for most calculations. "Wages" now means basic pay, dearness allowance, and retaining allowance, and this combined figure must equal at least 50% of an employee's total remuneration; everything above that 50% ceiling (HRA, special allowances, and similar components) is excluded from the wage base used for PF, gratuity, and bonus calculations. This took effect for ESI, gratuity, and bonus calculations from 21 November 2025, though the EPF-specific rollout carries a transition window running to November 2026.
• A five-year coverage lock-in. Once an establishment crosses the EPF or ESI threshold and becomes covered, the 2026 Rules prevent it from later seeking exemption or restructuring out of that coverage for five years — a real constraint for a growing hospital that crosses the 20-employee line and might otherwise have considered contract restructuring.

Separately, the existing Employees' Pension Scheme, 1995 continues in force for a maximum of one year from the Social Security Code's commencement date — that is, until 20 November 2026 — or until a revised pension framework replaces it, whichever comes first. The Press Information Bureau's factsheet on the Code on Social Security sets out the government's own summary of the expanded coverage and its stated intent. Full operational clarity across all four codes, including detailed central rules, was still described as "under consultation" as recently as early 2026, so a hospital's payroll configuration should be treated as needing at least one more review cycle before this transition is considered fully settled.

What a growing hospital needs to watch for as it crosses these thresholds

The 20-employee EPF threshold and the 10-employee ESI threshold matter most, in practice, to exactly the hospitals this content is aimed at: a 30-bed or 50-bed facility that has grown from a handful of founding staff into a real employer, often without anyone formally tracking the headcount moment it crossed into mandatory coverage. Because the 2026 Rules lock in coverage for five years once it applies, the cost of not tracking this proactively isn't just a compliance gap — it's a hospital administrator discovering, potentially during an inspection or an employee dispute, that coverage should have started months or years earlier, with the associated backdated contribution and penalty exposure that implies. A payroll system that flags headcount thresholds automatically, rather than relying on someone remembering to check, is solving a problem that has a real financial consequence attached to it, not a theoretical one.

Maternity Benefit and ESI interact in a way payroll software has to get right, not approximate

Two separate statutes cover maternity leave, and an employee is entitled to benefits under only one of them for the same period, determined by her ESI eligibility on the date leave commences — not a hospital's preference or convenience. Under the ESI Act, an insured woman earning up to the ESI wage ceiling, with at least 70 days of contribution in the preceding two contribution periods, receives 26 weeks of maternity benefit at full average wage, funded through the ESI scheme. Under the Maternity Benefit Act, 1961 (amended 2017), a woman not covered by ESI — typically because she earns above the ESI wage ceiling, or the establishment isn't ESI-covered — is entitled to the same 26 weeks for the first two children (12 weeks from the third child, adoption, or surrogacy), paid directly by the employer, provided she has worked at least 80 days in the 12 months before her expected delivery date.

The specific trap payroll software needs to handle correctly: an employee's ESI eligibility is assessed on the date her leave begins, not on the date she joined or was hired. A nurse who crosses the ESI wage ceiling mid-pregnancy, say from a increment, is evaluated under whichever Act applies as of her leave start date — manual payroll tracking misses this transition regularly, because it requires checking a wage threshold against a moving date rather than a fixed employment record. A detailed HR-practitioner guide to the Maternity Benefit Act walks through this and several other edge cases — including the 80-day threshold for recent joiners and the correct way to count pre- versus post-delivery weeks — in more depth than a policy summary can cover. Crèche facility obligations add a further threshold: establishments with 50 or more employees — counting contractors and trainees, not just direct payroll — must provide one, a headcount rule that's easy to miscalculate if contract nursing staff aren't included in the total.

This retention question extends past payroll into personnel records generally: attendance registers, leave records, and disciplinary files carry their own retention expectations under state Shops and Establishments Acts and the consolidated labour codes, distinct from the clinical retention schedules we cover in medical records retention rules for Indian hospitals. The two record sets are governed by different statutes but often get treated identically inside a single HR module, which is worth checking explicitly rather than assuming.

What nursing roster and HR/payroll software specifically needs to do

OneCity's own HRMS & Payroll module and its attendance and leave component cover staff records, attendance capture, shift management, leave balance tracking, and payroll with EPF, ESI, professional tax, and TDS built in — this page is the regulatory backdrop those features exist to answer to.

There's a connection worth making explicit between rostering and the rest of a hospital's operational software: a nurse's roster assignment determines which ward's patient records she has a legitimate reason to access, and that mapping is exactly the input a role-based access system needs to stay accurate. If HR and clinical access control run on separate, unsynchronised systems, a nurse rotated off a ward last month can retain access to that ward's records this month simply because nobody updated a second system to match the roster change. We cover the access-control side of this directly in role-based access control under the DPDP Rules, and the two systems — roster and access — work best when they're the same system, not two that have to be kept in sync by hand.

What to check before choosing nursing roster or hospital payroll software

Frequently asked questions

Related reading