GullyHR configures the record the rest of the platform depends on: your organisation structure, departments, locations and designations, the reporting hierarchy, the employee fields you actually use, and who may see or change each of them. We then migrate your existing employee data and check it back against your own files before anyone relies on it. You supply the current data, the organisation chart as it really is rather than as it was drawn, and the access rules you want applied by role, including the awkward one about salary. It is delivered as configuration, migration and role-based training within a GullyHR software engagement, not as a data-entry exercise handed back to you.
Each employee has one record instead of an entry in several files.
Personal details, statutory identifiers, salary structure, reporting line and employment status held together, so updating an address or a bank account is one action rather than three.
Your organisation structure is configured as it actually stands.
The structure your business runs on, including a group or multi-brand arrangement where more than one entity sits under common ownership, so employees are not forced into a shape that does not fit.
Departments and locations become fixed choices, not free text.
Departments and work sites set up once and selected from, which is what stops the same location appearing under three spellings and ruining every report built on it.
Designations follow your grade structure rather than the typist's memory.
A designation list configured to your titles or grades, applied consistently across records, so a designation-based report or letter template means the same thing every time.
The reporting line in the system is the one people actually work to.
Each employee's reporting manager is held here, and every approval elsewhere in the platform, leave, regularisation, appraisal, exit clearance, follows it, which is why keeping it current matters more than it looks.
An employee's documents sit against the employee.
Identity proof, offer and appointment letters, certificates and other paperwork are held on the record rather than in a folder named after whoever filed them.
Access to salary and personal data is a decision, not an accident.
Role-based access defined during configuration: an employee sees their own record, a manager sees what their role needs of their team, and sensitive fields go only to the roles you nominate.
Headcount and structure questions are answered by the system.
Counts by department, location, designation and status come from the same records the daily workflow maintains, so a headcount question does not begin with somebody opening a spreadsheet.