GullyHR configures two connected workflows: how a new joiner is taken from offer acceptance through documents, induction and probation confirmation, and how an existing employee's status changes through transfer, promotion or role change. We set up the pre-joining task list with owners and due dates, the document requirements, the onboarding checklist, the probation timing calculated from each joining date, and the approval levels for each type of change, then train HR administrators and managers to run them. You decide what belongs on the checklist, which documents you collect, how long probation runs and who signs off a transfer, a promotion and a salary change. It is delivered as configuration and training within a GullyHR software engagement, not as a standalone onboarding tool.
Everything that must happen before day one has an owner and a due date.
Asset arrangement, system and email access, seating, statutory enrolment paperwork and the welcome note are tracked as pre-joining tasks assigned to named owners, so nothing waits on the new joiner arriving to be noticed.
Joining documents are collected against the employee record, not into a folder.
The document list you actually require, such as identity proof, education and previous employment documents and the signed offer or appointment letter, is collected and stored on the employee's record with what is still outstanding visible.
Every new joiner goes through the same onboarding checklist.
The first days and weeks run to a configured checklist covering documentation, access, introductions, policy acknowledgement and statutory enrolment, so the experience does not vary by which manager the joiner reports to.
Induction becomes something you can confirm rather than assume.
Induction sessions and topics are tracked against each new joiner, so you can see who has been through safety, policy or role induction and who is still pending it, weeks after they joined.
Probation confirmation arrives as a task before the date, not after it.
Probation duration is configured to your policy and the review date is calculated from each employee's joining date, so the manager is prompted while there is still time to hold a proper confirmation conversation.
A transfer follows one route and updates the record when it is approved.
Movement between departments, locations or reporting managers is raised as a request, approved by the levels you set, and applied to the employee record so attendance, approvals and reporting follow the employee to the new position.
A promotion is recorded once, with the designation and salary change attached.
The promotion request carries the new designation and, where applicable, the revised salary, moves through the approval levels you define, and lands on the employee's history rather than in a letter and a separate payroll instruction.
Any other change to a role or status uses the same approval route.
Role changes, reporting line changes, location changes and status changes are raised through one change-request workflow, so an informal decision cannot quietly become a record change nobody approved.