Small business human resource checklist — the HR policies, statutory compliance, and payroll structure decisions a growing business needs in place from year one.
The question on the owner's desk when the headcount crosses twenty is rarely whether the business needs an HR function. It's what specifically that function has to put in place before the next round of hires lands. Salary computation is currently a spreadsheet. Leave is tracked on paper. The accountant is filing PF and ESI returns through an external consultant. Onboarding is a verbal conversation followed by a Word-document offer letter. None of this is broken yet. It will be — usually around the forty-employee mark, when the first compliance notice arrives, or when the first operator walks out because his PF deposit never showed on his UMANG app for three months running.
A small business human resource checklist exists to make the next ten hires defensible rather than improvised. The checklist below sequences the work in the order operational businesses can actually execute — starting with the items that prevent statutory penalties, then the items that close the routine cycle, then the items that scale cleanly past fifty employees. The broader HRMS subject area discussion for growing operations treats this initial setup as the foundation every later HR decision rests on.
When and why to use this checklist
This setup checklist applies when a business has crossed roughly fifteen to twenty employees and is approaching the thresholds where PF, ESI, professional tax, and shop-and-establishment compliance become mandatory rather than optional. It also applies to businesses already past those thresholds that have been running on improvised processes and need to formalise the HR function before the next compliance review or the next round of hires. Each item below names a specific decision with a named owner and a measurable checkpoint — not a vague "review your processes" instruction.
The small business human resource checklist
The items below split into two phases: foundations that prevent statutory and contractual risk (items 1–6), and operational cadence that scales the HR function through the next phase of growth (items 7–11).
Formalise the HR function with a named owner.
One person carries HR accountability — a dedicated HR executive, a senior administrator with HR exposure, or a founding team member with at least one prior HR role. The role covers payroll, statutory compliance, onboarding, leave administration, and employee query resolution. Operations that defer this past the twenty-employee mark typically find the founder still answering payslip questions at month-end six months later, which is where the operational drag becomes structural.
Sign off an employee handbook with the foundational policies.
Six policies cover the foundational set: code of conduct, anti-harassment, leave structure (privilege leave, casual leave, sick leave, public holidays), attendance and working hours, salary structure and payment cycle, and the at-will employment clause where applicable. The owner and HR head sign off the handbook before the next hire is onboarded. Without the document, disputes around leave entitlement, working hours, or salary structure default to the individual conversation that produced the original offer letter — which is exactly the conversation no one can reconstruct two years later.
Confirm statutory registration against employee count thresholds.
PF registration applies once the employee count crosses twenty (with applicable wage thresholds). ESI registration applies once the count crosses ten in most states (subject to wage ceiling). Professional tax registration applies state-wise. Shop and establishment registration applies under the local state act. The owner and finance head confirm each registration before the threshold-crossing hire is finalised, not after — backdated registration carries interest and damages that compound monthly.
Structure the salary into statutory-compliant components.
The salary structure has to break into basic, HRA, conveyance, special allowance, and statutory deductions (PF employee contribution, ESI employee contribution where applicable, professional tax, TDS) at the point of offer rather than at the first payroll run. Basic-as-percentage of CTC affects PF computation; HRA-as-percentage affects tax exemption; ESI applicability depends on gross wage relative to the current ceiling. The HR head signs off each new offer's salary breakup against the standard structure before issue. This is one of the most under-tested items in setups that later face compliance notices.
Centralise the employee data file from the first hire.
One employee data file covers PAN, Aadhaar (where the employee opts to share), bank account, UAN if pre-existing, date of joining, designation, department, reporting manager, emergency contact, education and prior employment, statutory enrolment status, and contractual documents. The file lives in one place — a structured HRMS, a secured shared drive, or at minimum a defined spreadsheet — not in the founder's email. Where the data sits scattered across email threads, the cost surfaces during the first PF audit, the first investor due diligence, or the first attrition spike when exit formalities require records nobody can locate quickly.
Define the recruitment and onboarding workflow.
The workflow covers job description sign-off, interview panel, offer letter template, document verification, statutory enrolment (PF UAN linkage, ESI registration, bank account verification, PAN-Aadhaar linkage), induction schedule, role-specific training, probation period, and confirmation review. The HR head owns the workflow; the function head signs off the role-specific training plan. Most rollout disappointments at the thirty-to-fifty employee mark trace back to a workflow that was never written down — each new hire is onboarded as a one-off, which is where inconsistency in role expectations and salary structure quietly accumulates.
Set the monthly payroll cycle with named cut-off dates.
The cycle has fixed dates: attendance cut-off (typically 25th of the previous month), leave reconciliation (26th), overtime sign-off by function heads (27th), payroll computation (28th–29th), salary credit (1st of the next month), payslip distribution (2nd), PF and ESI challan filing (15th), professional tax filing per state cycle, and TDS deposit by the 7th of the next month. The HR head signs off the cycle calendar at the start of every financial year. Without fixed dates, payroll slips reactively — and slip becomes the norm. Operations running clean cycles see monthly payroll close in under four hours and corrections drop to under two per cycle.
Plan PF, ESI, PT, and TDS compliance against the monthly calendar.
PF challan filing by the 15th of the following month with the EPFO ECR file. ESI challan filing by the 15th with the ESIC contribution. Professional tax filing per state cycle (monthly, quarterly, or annual). TDS deposit by the 7th of the following month with Form 24Q filed quarterly. Late filings attract interest at 12% per annum under Section 7Q of the EPF Act and damages up to 100% under Section 14B. The HR head and finance head jointly sign off the statutory compliance calendar, with consultant engagement formalised in writing where statutory work is outsourced.
Operationalise leave and attendance tracking with a single source of truth.
Biometric or mobile attendance feeds the leave and payroll record. Leave applications route through a defined workflow with manager approval. Leave balances reflect accruals, consumption, and carry-forward against the policy. The HR head signs off the leave structure annually; line managers sign off team-level approvals monthly. Where attendance, leave, and overtime sit in separate registers, payroll consumes two to three days of HR time every month — and this is exactly the workload that grows with headcount.
Configure employee self-service for routine queries.
Mobile-based self-service covers payslip download, leave balance check, leave application, PF and ESI status, and personal-detail updates. The interface has to work on a basic Android phone for shop-floor or field staff. Operations that defer self-service past forty employees find the HR executive answering 30–40 routine queries per month — work the self-service module removes once it is configured and adopted.
Lock the integration plan with finance and the broader operational system.
Labour cost from payroll feeds the financial books rather than sitting in a parallel ledger. Statutory deductions flow into the chart of accounts cleanly. Where the company also runs an integrated ERP, the ERP and HRMS integration lets the finance head pull labour cost per product without manual reconciliation. The HR head and finance head sign off the integration scope before the HRMS is deployed; deferring integration to Phase 2 typically creates the parallel-spreadsheet problem the HRMS was meant to solve. The payroll compliance guide for compliance-heavy operational workforces builds on this same foundation.
Facing similar workforce management challenges?
See how exactllyHRMS manages payroll governance, attendance management, and statutory compliance — built for operational businesses.
See how exactllyHRMS governs payroll and compliance →What this looks like in exactllyHRMS
The eleven items above translate from intent into operational reality only when the underlying system holds each as a configured workflow rather than a manual checklist item. exactllyHRMS eliminates payroll errors and compliance delays by handling attendance and shift management for factory or field workforces, statutory compliance (PF, ESI, PT, TDS), payroll with Indian pay structures, leave and holiday calendar, and employee self-service for shop-floor and field staff as one connected setup from day one. The biometric and mobile attendance feed the payroll engine directly. Leave applications route through configured workflows that update the same monthly run. PF, ESI, PT, and TDS computations happen inside the payroll engine. EPFO ECR files, ESIC challans, Form 24Q, and state-specific PT challans generate automatically in filing-ready format.
How exactllyHRMS handles this automatically: Item 4 (salary structure) is configured once and applied to every offer against the standard breakup. Item 7 (monthly payroll cycle) runs from one calendar with attendance, leave, and overtime feeding the same record. Item 8 (statutory compliance) absorbs EPFO, ESIC, PT, and CBDT rule changes through configured updates rather than manual rebuilds — which removes the largest single category of compliance interest, damages, and operator-trust erosion. exactllyHRMS handles PF, ESI, and TDS computation errors automatically. See it live in a free demo against your current payroll cycle and statutory calendar.
