HumaRun is loading.
Skip to content
HR & people teams

More context for the people involved.

Keep employee records in one place, let employees send their own requests, and give every approver a clear responsibility.

All solutions

Employee details in too many places.

Details sit in spreadsheets, inboxes and personal files, and every change depends on someone remembering to pass it on. Begin with one record and a named approver for each request.

A suggested starting planThree steps · not a product screen
Suggested
  1. FirstSet up the record and rolesStructure, employee records, managers and what each role sees
  2. ThenOpen requests and documentsProfile changes, shared documents and an approver for each route
  3. NextAdd hiring and developmentHiring, goals, learning and engagement on the same records
A suggested order, not a rollout plan

From scattered details to clear routines.

Four routines an HR team keeps consistent.

  • Requests with a clear approver

    Employees ask to change their details, and the record updates only once it is approved. The request goes to their manager, or to an HR administrator if there is none, and a manager can hand approvals to a colleague for set dates. Bank and tax detail changes have their own checks before they apply.

  • Documents and acknowledgements

    Keep each employee's documents with versions and expiry dates, and send letters from templates with merge fields. A document reaches the employee only when you share it, and you can ask them to acknowledge the current version. A simple electronic signature inside HumaRun, signed in order or in parallel by people in your organization, with a completion certificate.

  • Joining, changes and leaving

    HR starts onboarding from a template you set up, with tasks for the starter, their manager or HR. Transfers, promotions and manager or contract changes are approved first. Offboarding is prepared ahead of a planned end date, and the end itself is an approved decision.

  • History that keeps the past

    Job, department, manager and worksite changes take effect from their date, and the earlier record is kept, so you can see who reported to whom, and when.

One record, a view for each role.

Everyone works from one record, with the view their role allows.

  • Employees

    See their own record, history and shared documents, and ask to change their details. Nothing of anyone else's.

  • Managers

    See their direct reports and decide their team's requests. They cannot change an employee's record.

  • HR

    Maintain records across the organization. Restricted HR notes and sensitive documents need a permission of their own.

Bring the right questions.

A clear conversation starts with how your people team works.

  • How do managers ask for employee changes today, and who approves them?
  • Which documents need renewal or acknowledgement, and who tracks them?
  • Who should see which employee details, and who covers an absent approver?
  • What happens when someone joins, moves or leaves, and who owns each step?
  • Which development areas would you explore first: hiring, goals or learning?

These are for your own preparation, and nothing is submitted from this section. Use fictional examples, and please do not send employee, banking or confidential candidate records.