GullyHR reviews how your HR runs today, maps the processes in scope step by step, configures the matching modules with your entitlements, approval routes, roles, letter formats and reports, migrates your existing employee, attendance and leave data, trains each user group separately, and stays through the first live cycle of every process it has configured. You give us access to the people who actually run HR, your data in whatever state it is in, and the decisions that are yours alone: which modules come first, who approves what, and what each role is allowed to see. This is a defined project with an agreed scope, sequence and acceptance point, not an open-ended retainer and not a licence handed over with a login.
We find out how your HR actually runs before anything is configured.
A working review of your current processes, data, systems and the places people improvise: who approves leave in practice, where attendance really comes from, and which spreadsheet everybody quietly treats as the true one.
Every process in scope is mapped step by step, exceptions included.
Onboarding, attendance and leave, payroll input, movement or exit are written out as steps, approvals and exceptions before configuration begins, because the exceptions are what break a system after go-live.
The platform is configured to your process, not left on a default.
Organisation structure, departments, locations, designations, reporting lines, leave entitlements, approval routes, letter formats and reports are set up against the mapped process and tested with real cases from your business.
Your existing data is consolidated and loaded before go-live.
Employee master data, attendance history, leave balances and salary components are pulled out of spreadsheets, files or an older system, cleaned into one format, loaded, and checked back against your own records.
Approvals and notifications match who really signs off.
Each request type is configured with the route it takes in practice, including the promoter who wants sight of anything touching salary, and the notifications that tell an approver a request is waiting.
Every role gets the access it needs and nothing more.
Owner, HR administrator, manager and employee roles are defined against your reporting structure, so a manager sees their own team and salary data reaches only the people you have decided should see it.
Policies, letters and forms move into the document centre.
Your current handbook, policies, letter formats and forms are collected, the duplicates and superseded versions are flagged, and what remains is uploaded, categorised and version-controlled in one place.
Where another system has to sit alongside this one, we say plainly what is possible.
Biometric devices, payroll packages and accounting systems are reviewed for what can genuinely be exchanged, in what format, and where a specific integration would have to be scoped and built as its own piece of work.
Each user group is trained on the part of the system it will actually use.
Separate sessions for HR administrators, managers and employees, built around the handful of actions each group performs, not a tour of every screen the platform has.
Someone is available during the first live cycle.
The first payroll month, the first appraisal round or the first week of leave requests is when real questions surface. GullyHR stays reachable through that cycle for each process configured.
Configuration is corrected once practice has met the design.
After the first cycle we look at what people actually did in the system, where they worked around it, and adjust entitlements, routes or forms so the configuration matches reality rather than the plan.