The policy vacuum, and how it closes

At fifteen people, HR is a founder answering questions in a chat window. It works precisely because everyone can see everyone. The failure arrives at around forty, when someone asks a question whose answer was previously improvised, how much notice do I owe, does a Friday off cost me two days, when does my leave reset, and discovers that the answer depends on who they asked and when.

By then the decision has been made, badly, several times. What a company at this stage needs is not primarily a tool. It is for the rules to exist somewhere other than in one person's head, applied identically to everyone, from the day they are written.

EPF and ESI applicability, Professional Tax registration in each state of operation, and TDS deduction under Section 192 do not begin at a threshold anyone will notice passing. Setting the platform up with correct identifiers and rates from the first employee costs nothing; retrofitting them across eighteen months of history is a genuine project with a genuine exposure.

• Collect PAN, Aadhaar, UAN and bank details at joining, not at the first payroll run.
• Register for Professional Tax in each state you actually operate in, including states where one remote employee sits.
• Decide whether the ₹15,000 EPF wage ceiling is applied as a cap, and apply that decision consistently.
• Run the declaration cycle in April rather than deferring it, so no correction has to be crushed into February.

Leave is the only policy every employee interacts with, which is why a bad one does far more damage. The irritant is rarely the policy itself; it is uncertainty about the balance, about whether a request was seen, and about what a Friday-and-Monday will actually cost.

A balance should be computed from an accrual rule rather than maintained by hand, so that the number the employee sees when applying is the number the approving manager sees and the number payroll uses. Where a sandwich rule applies, its outcome should be visible at the point of applying rather than discovered on the payslip.

Minimum entitlements sit under the applicable state Shops and Establishments Act, or the Factories Act for covered establishments. A company with people in more than one state may need more than one quota under a single policy.

A policy that cannot be shown to have been issued and accepted is difficult to rely on at the moment it matters. Acknowledgement therefore has to be recorded per employee and per policy version.

Versioning is the part usually omitted. When a policy is revised, an earlier acceptance should not automatically stand in for the new wording, publishing a new version should re-open acknowledgement for everyone it applies to. HRMagix ships twenty-five workplace policy templates in the Documents module on exactly this basis: the employer writes their own rules into them, issues them, and the platform records who accepted which version and when.