GullyHR configures the module around the way you already plan training: your programme categories, your calendar, the nomination and approval route, the assessment and certificate formats, the certifications that carry a renewal date, and who is allowed to see whose record. We then load your existing training history and certificates so the module opens with a real past rather than a blank one, and train the HR administrators and managers who will run it. You decide the programme list, which roles carry mandatory or periodic training, who approves a nomination, and who owns the calendar once it is live. It is delivered as a configuration and rollout engagement, alongside employee records and performance, not as a standalone training tool.
The training calendar becomes something people can see rather than something one person holds.
Planned programmes are laid out by month, department or role and made visible to employees and managers, so a session is announced once in a place people can check instead of chased individually.
Nominations arrive as a tracked request instead of a group message.
Employees nominate themselves or managers nominate their team, HR approves or allots the seats, and the confirmed list is the one the system holds rather than a set of replies somebody counted by hand.
Attendance is recorded against the employee, not on a paper register.
Session attendance is marked against each participant's own record, so completion becomes a fact anyone with access can check rather than a signature on a sheet in a file somewhere.
Assessments show whether the programme landed, not just that people attended.
Pre- and post-programme assessments can be recorded per participant where the programme calls for one, giving a before-and-after view rather than only a completion tick against a name.
Feedback is kept where it can be read before a programme is repeated.
Participant feedback on the content and the facilitator is captured against the session, so the decision to run a programme again, change it or drop it rests on what attendees said.
Certificates live against the employee record and carry their renewal date.
Certificates issued for internal programmes and external qualifications are stored on the employee record, with an expiry date where the certification is time-bound, so renewals surface before they lapse.
Development plans link an agreed action to the training that addresses it.
An individual development plan sits on the employee record, connecting the development points agreed at appraisal to specific programmes, so a plan is a set of scheduled actions rather than a paragraph in a review form.
Management can see the training picture without asking for a file.
Standing reports cover programmes run, attendance, completion by department or role, and certifications due for renewal, built from the same records the calendar and attendance already capture.