Every organization runs on a set of rules, expectations, and boundaries that govern how employees conduct themselves, protect company assets, handle sensitive information, and interact with one another. The challenge most HR teams face is not the absence of these policies but the difficulty of maintaining them in an accessible, organized, and enforceable way. Policies buried in PDF attachments sent during onboarding rarely get read twice. Disciplinary actions managed through email chains lack the structure needed for fair, consistent enforcement.
Horilla HRMS addresses both sides of this through its Policies and Discipline module, available within the Employee section, which provides a centralized, structured space for publishing company policies, recording disciplinary incidents, and defining the action types used when those incidents occur.
Navigating to Policies and Discipline
From the left sidebar, click on Employee to expand the module menu. The options available include My Dashboard, Employees, Organization Chart, Work Structure, Work Requests, Work Schedules, and Policies and Discipline. Selecting Policies and Discipline opens a dedicated page organized into three tabs: Policies, Disciplinary Actions, and Disciplinary Action Type.
Each tab handles a distinct but related function, together forming a complete framework for how the organization communicates expectations to employees and responds when those expectations are not met.
Tab One: Policies
The Policies tab is described in the interface as the place to create and manage company policies shared with employees. It displays all configured policies in a card-based layout, with each card representing a distinct policy category. Each card shows a preview of the policy content including its title, purpose statement, and the beginning of its body text, along with a View Policy link at the bottom for accessing the full document.
Each policy card has an edit icon for updating the policy content and a delete icon for removing policies that are no longer applicable (Marked as 1 in the attachment). The Create button(Marked as 2 in the attachment) in the top right allows HR administrators to add new policy categories and documents as the organization’s needs evolve. The view policy button (marked as 3 in the attachment) is used to view a detailed description of the policy in a pop-up window.
Having all of these policies in one accessible location within the HRMS means employees can refer to them at any time rather than having to search through email archives or shared drives to find the document they need. It also means HR can update policies in one place and have the updated version immediately available to everyone, rather than re-sending documents and hoping they get read.
Tab Two: Disciplinary Actions
The Disciplinary Actions tab is described as the place to record and track disciplinary incidents for employees. Unlike the Policies tab, which is forward-looking in that it communicates expectations, the Disciplinary Actions tab is retrospective, capturing what has actually happened when those expectations were not met.
The tab displays a list of recorded disciplinary incidents with the following columns:
- Employee shows which employee or employees the action applies to. A single entry can cover multiple employees, as shown by entries labeled with a count such as two employees, which is useful when a disciplinary incident involves a group.
- Action Taken shows the type of disciplinary response that was applied, such as First Warning, Last Warning, Suspension, or Dismissal. This field references the action types configured in the Disciplinary Action Type tab.
- Login Block indicates whether the disciplinary action resulted in the employee’s system access being blocked. This is a meaningful field for cases where an employee is suspended or dismissed and their access to company systems needs to be revoked as part of the disciplinary process. A value of No means access was not blocked, while Yes indicates it was.
- Action Date records when the disciplinary action was taken, providing a timestamp that is essential for maintaining accurate records and supporting any formal review or appeal process.
- Attachments shows whether any supporting documentation, such as a written warning letter, evidence of the incident, or a formal notice, has been uploaded alongside the record. If no file has been uploaded, this is indicated explicitly.
- Description provides a brief summary of the incident or the basis for the action taken, such as noting which policy was violated.
The Actions column on each row provides edit and delete options, as well as a copy icon for duplicating a record where a similar action needs to be applied in a related case.
This structured record-keeping serves several important purposes. It ensures that disciplinary processes are documented with dates, descriptions, and outcomes, which is essential if an employee disputes an action or if a formal grievance process is initiated. It creates a consistent trail showing how similar incidents were handled across different employees, which supports fair and non-discriminatory enforcement. And it gives HR managers a clear history of prior actions when assessing how to respond to a repeat incident.
Tab Three: Disciplinary Action Type
The Disciplinary Action Type tab defines the categories of disciplinary responses available to HR when recording incidents. It is described as the place to define disciplinary action types used when recording employee incidents.
The list view shows each action type with three columns: Title, Type, and Login Block.
- Title is the descriptive name of the action as it will appear when HR selects it while recording an incident. The default action types configured in Horilla include Dismissal, One Month Suspension, Last Warning, and First Warning.
- Type classifies the action into a broader category. The available types are Dismissal, Suspension, and Warning. This classification allows the system to distinguish between the severity levels of different responses, which can be used for filtering, reporting, and ensuring that escalation processes follow a logical progression from warnings to suspension to dismissal.
- Login Block specifies whether this action type automatically triggers a system access block for the affected employee. Dismissal is configured with Login Block set to Yes, meaning that when a dismissal action is recorded, the employee’s access to the HRMS and associated systems is blocked as part of the action. Suspension and Warning types are configured with Login Block set to No, reflecting that employees in those categories typically remain employed and retain system access.
This automation around login blocking is particularly valuable for reducing the operational gap that often exists between a dismissal decision being made and the employee’s access being revoked. By tying the block to the disciplinary action type, the system ensures that access control happens as part of the documented process rather than as a separate manual step that might be delayed or forgotten.
Why This Module Matters
Handling policies and discipline through informal channels, whether that is email, verbal communication, or paper files, creates gaps that eventually cause problems. Policies that employees haven’t read cannot be fairly enforced. Disciplinary actions that aren’t documented cannot be defended if challenged. Inconsistent responses to similar incidents open the organization to claims of unfair treatment.
The Policies and Discipline module in Horilla HRMS closes these gaps by making policy communication structured and accessible, disciplinary recording formal and traceable, and action type definitions consistent and predictable. For organizations that want to build a workplace where expectations are clear, and consequences are applied fairly, having this infrastructure in place is not optional. It is foundational.
The Policies and Discipline module in Horilla HRMS brings together three interconnected functions that every organization needs, but few manage well in a single place. Publishing and maintaining company policies in an accessible format, recording disciplinary incidents with the structure needed for fair and defensible enforcement, and defining the action types that govern how incidents are categorized and responded to- all of this sits in one module within the Employee section. For HR teams looking to move beyond informal policy management and ad hoc disciplinary handling, this is the kind of structured foundation that makes a measurable difference in both compliance and employee experience.
Download Horilla HRMS from the App Store or Play Store and explore the free HR Experience In Your Hands.
