Holiday requests run by email, the department calendar hangs on a wall or sits as a spreadsheet on a shared drive. Whoever wants to know if someone is around next week has to ask.
The HRM plugin maps absences in Redmine, where the work is planned. It is about presence and absence, not about salary or personnel files.
How it works day to day
- Define user types. Internal staff, external providers and guest accounts are distinguished. The type decides what someone sees and what is recorded for them.
- Request an absence. Holiday, sickness, training or working from home is entered by the employee, always as a period from and to.
- Approve. The responsible person sees the request and approves or rejects it. The process stays traceable.
- Use the overview. The calendar shows who is unavailable and when. Planning shows the absence, while the reason stays with the HRM area and supervisors.
What changes
- Requests do not sit in mailboxes but in one place with a history.
- Whoever plans sees the absences without asking HR.
- Employees enter their own data instead of one person maintaining a spreadsheet.
What the plugin does not do
It is not a payroll system and not time management with time accounts. Overtime and undertime are recalculated on every view and not carried forward. Holiday entitlement starts fresh each year and remaining days are not transferred automatically. There is no clock-in and clock-out, a period is booked, also after the fact.
What employees can handle themselves is described on the page employee self service.
Which functions the Redmine HRM plugin brings along and what it costs is described on the product page.