GullyHR designs your onboarding and induction process and implements it with you. We map how joining works today by talking to HR, reporting managers and recent joiners, agree the steps and approvals with you, write the process down, build the forms and induction material, configure the workflow in your HR system and brief the managers who run it. You appoint one process owner, share your current joining documents, take the decisions on probation duration and confirmation authority, and release managers for a short briefing. It runs as a defined project against a scope agreed before we start.
Pre-joining runs on a schedule, not on somebody's memory.
From offer acceptance to the joining date: who stays in contact with the candidate, when the appointment letter goes out, who raises the request for a seat, laptop, email ID and access, and what the joining-day plan actually says.
Joining documents are collected against a checklist.
A document list by employment type, with a collection method, a person responsible and a due date. At any point the process can show which documents are in, which are pending and which must be collected again.
Day one follows a fixed sequence.
Identity and document verification, signing of the appointment letter and its annexures, statutory and bank declarations, policy acknowledgements, asset handover and workplace introduction, each step leaving a signature or a record behind it.
The employee record is created once, correctly.
Agreed rules for employee code, joining date, designation, department, reporting manager, location, cost centre and pay-relevant fields, so the record made at joining is the one attendance, payroll inputs and management reports all read from.
Induction follows a written programme, not whoever is free.
What the business does, how it is organised, the policies that affect this employee, leave and attendance rules, conduct expectations and safety where it applies, with content and length set by role rather than fixed for everyone.
The reporting manager owns the first weeks.
A department orientation the manager runs: the team, the work, the systems and tools, the first assignments, and a written statement of what is expected of the employee during probation.
Probation is tracked while it is running, not read afterwards.
Checkpoint conversations at defined intervals, a short record of what was discussed and agreed at each, and an alert that reaches the manager before the probation end date rather than after it has gone.
Confirmation is a decision somebody takes.
A confirmation review with the reporting manager, a documented recommendation to confirm, extend or not confirm, the approval route for each outcome, and the letter and record update that follows the decision.
New joiners are asked how the start actually went.
A short structured feedback point in the first weeks and another near confirmation, with the questions written down, the answers recorded, and a review that turns a repeated answer into a change in the process itself.