Skip to main content
GullyHR

HR technology and automation · Rehabilitation hospitals

Core Employee Management for Rehabilitation hospitals

Core employee management is the GullyHR module that holds one record per employee, covering personal, statutory, salary, reporting and document details, alongside your organisation structure, departments, locations, designations and reporting hierarchy. Access to each part of that record is set by role, so an employee sees their own, a manager sees their team, and salary is not open to everyone with a login.

An HR administrator updating employee records at a laptop with tidy folders nearby.

The operating context

Validate one employee master across locations and roles

A rehabilitation hospital works with patients for weeks or months. Physiotherapists, occupational and speech therapists, nurses and attendants build slow progress together, and the team holds only as long as its people stay.

Rehabilitation physiciansPhysiotherapistsOccupational therapistsSpeech and language therapistsProsthetists and orthotistsRehabilitation nurses
Hospital colleagues reviewing a staff duty roster and credential records

The decision to work through

Map identifiers, departments, reporting lines and required fields, then check who can view or change each field. Workforce to consider: Rehabilitation physicians, Physiotherapists, Occupational therapists.

Records and configuration to test

Field mapping, duplicate review and role-permission matrix. A workforce issue to consider: Physiotherapy, occupational therapy and speech teams run separate lists, and the weekly team conference becomes a reading of reports.

An exception to test

Test a location transfer and a restricted field with employee, manager and administrator accounts.

Which parts of your business should the scope cover?

The right workforce and approval structure depends on the operations you run. Confirm which of these apply, and whether they share one HR process.

  • Neurological rehabilitation hospitals for stroke and brain injury
  • Spinal cord injury rehabilitation centres
  • Orthopaedic and post-surgical rehabilitation hospitals
  • Paediatric rehabilitation and cerebral palsy centres
  • Cardiac and pulmonary rehabilitation programmes
  • Geriatric rehabilitation and long-stay care units

When to consider this service

  • Three files hold the same employee's bank details and at least two of them are out of date.
  • A new manager inherits a team and has to ask around to find out who actually reports to them.
  • Offer letters, ID proofs and certificates are spread across email attachments, a shared drive and a physical file, in no particular order.
  • A promotion happened in April and the reporting line on record still shows the old manager.

Businesses this service is designed for

  • Companies holding employee data in spreadsheets, joining-form folders or both, with no agreed master.
  • Multi-location or multi-entity businesses where the same structure has been recorded differently at each site.
  • Companies that have just hired their first HR administrator and need something structured for that person to work from.
  • Businesses facing a funding round, a customer audit or an inspection where employee records will be looked at.

What the system needs to support

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.

Configure, validate and prepare users

Map the approved process to fields, user roles, permissions and workflow rules. Inspect the source data and identify migration, integration and reporting requirements before configuration.

  1. 01

    Structure mapping

    We go through your organisation chart, departments, locations and designations as they actually operate, and agree the structure to configure.

  2. 02

    Field and access decisions

    We agree which employee fields you genuinely use and who, by role, may view or edit each of them, including salary and statutory identifiers.

  3. 03

    Data collection

    Existing employee data is gathered from your spreadsheets, files or current system into the format we specify, with gaps identified rather than guessed at.

  4. 04

    Data migration

    The prepared data is loaded into the platform against the configured structure, departments, designations and reporting lines.

  5. 05

    Data verification

    Migrated records are checked against your source data and the discrepancies, which there always are, are corrected before go-live.

  6. 06

    Reporting hierarchy setup

    Each employee's reporting manager is confirmed and configured, because attendance, leave, appraisal and exit approvals all depend on this line.

  7. 07

    Roles and permissions

    Owner, HR administrator, manager and employee roles are created with the access agreed during configuration.

  8. 08

    Administrator training

    HR administrators are trained to maintain records and process changes; managers and employees are shown how to see their own or their team's information.

  9. 09

    Go-live and review

    The module goes live, and after a short period we review whether the structure and access rules are working or need adjusting.

Test migrated records, approvals, exceptions and permission boundaries with representative users. Agree acceptance, user training, support ownership and the handling of remaining issues before go-live.

Agreed configuration and handover

  • A configured employee database matching your organisation structure, departments, locations and designations.
  • Migrated employee records, verified against your existing data before go-live.
  • A configured reporting hierarchy that attendance, leave, performance and exit approvals run on.
  • Role-based access rules for owner, HR administrator, manager and employee users.
  • Employee documents loaded against individual employee records.
  • A record of data gaps and discrepancies found during migration, for you to close.
  • An HR administrator training session covering record maintenance and change processing.
  • Reference documentation for maintaining the employee database going forward.

What your team provides

  • Current employee data in the format you hold it, including the awkward cases.
  • The organisation chart as it actually works, not as it was drawn.
  • Access rules for each role, including the awkward one about who may see salary.
  • A named person on your side who signs off the migrated data.

Share personal records only after the scope, access and handling arrangements are agreed.

Responsibilities and approvals

The client owns employee records and approves policies, spending and employment decisions. GullyHR's assigned responsibilities are documented in the engagement.

Providing employee data

GullyHR
Specifies the fields and format required, and flags what is missing or inconsistent in what is supplied.
Your team
Supplies current employee records from spreadsheets, files or an existing system.

Confirming the organisation structure

GullyHR
Configures departments, locations, designations and reporting lines as agreed.
Your team
Confirms the structure and reporting lines to be used, including any change intended alongside implementation.

Deciding access rules

GullyHR
Sets out the role-based access options and configures the rules agreed.
Your team
Decides who, by role, may see or edit salary, statutory and document details.

Verifying migrated data

GullyHR
Loads the data and checks it against source records before go-live.
Your team
Reviews a sample of migrated records and confirms the data is right before it goes into use.

Keeping records current

GullyHR
Trains the administrators and remains available for configuration changes such as a new location or designation.
Your team
Owns day-to-day updates, joiners, movements and changes, once trained.

How we agree that the work is complete

Review these outputs with your process owner and agree the evidence required for sign-off.

  • The employee database mirrors your departments, locations, designations and reporting lines as they really are.
  • Migrated records are checked back against your own files, and the check sheet is signed by your HR lead.
  • Each role sees and changes only the fields in the agreed access table.
  • Data gaps and discrepancies found during migration are listed, with an owner on your side for each.
  • Your HR administrator has been trained to maintain records and process changes.

Data, configuration and adoption

This is the record the other GullyHR modules read from and write to. An attendance entry, a leave approval, a payroll input and an appraisal all point at the same employee and the same reporting line, so nothing has to be kept in step by hand and a change of manager takes effect everywhere at once. Access is role-based and configured to your structure, which means a manager sees their own team without raising a request each time, and salary is visible only where you have said it should be. Employees and managers reach the module on whatever device they log in from. Where employee data currently sits in another system, we specify the export needed and migrate it in; an ongoing live connection to that system would be a separate piece of work to scope and confirm, not something to assume. The system holds the structure faithfully, but it cannot tell you the structure is wrong, which is why the mapping conversation matters more than the configuration.

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Read the full core employee management service guide →

Agree the engagement before work starts.

Demonstration and scoping

A walkthrough against your current structure and data, followed by an agreed scope for fields, structure, access and migration effort.

Configuration and migration

Structure and access are configured, existing data is migrated and verified, and the module goes live for HR and managers.

Ongoing support

Continued support for structure changes such as a new site, department or grade as the business grows.

Scope and exclusions

  • Confirm product fit, licensing and the implementation scope before committing. Custom development, third-party integrations and GullySystem services are separately agreed; they are not automatically included.
  • You want a data-entry team to key in your records, which this configuration and migration work does not provide.
  • You have no current employee data to migrate and no one who can supply or confirm the rules.
  • You want a standalone product bought off the shelf without a GullyHR engagement around it.
  • You need payroll calculated inside the record, which stays with your accountant or provider.
Confidentiality, specialist review and accountability

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Applicability depends on locations, workforce arrangements and the issue under review. Confirm applicable requirements with your qualified adviser before adopting policies or employment actions; this service is not a legal certification.

Employment-law opinions, statutory filings, professional or clinical standards and safety-critical technical decisions require the appropriate qualified professional; include those dependencies in the scope.

Questions before you decide

For rehabilitation hospitals, identify who owns these records: field mapping, duplicate review and role-permission matrix. Start with an anonymised example and the decision you need to make; agree the sample and access before sharing personal data.

Discuss your HR system

Tell us the teams and locations involved, what is happening today and what you want this work to resolve.

Start with your business need

What does your HR team need to solve?

Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.

  • A free first conversation with an HR practitioner
  • A clear scope and fee before any paid work
  • A practical next step for your business

Let’s start with your business

Share your contact details and the HR challenge on your mind. We’ll help you find the right starting point.

Include your country code, for example +44 or +1. Indian numbers can be 10 digits.

Your details stay private. Privacy policy