HumaRun is loading.
Skip to content
Distributed teams

Different locations. A shared way of working.

Give each location its own schedule, working week and approvers, while everyone works from one employee record and one set of roles.

All solutions

Context gets lost between locations.

Teams in several places keep different hours, holidays and managers, and what one place agreed does not always reach another. Set each place's calendar and approvers once, so all share the facts.

A suggested starting planThree steps · not a product screen
Suggested
  1. FirstMap places and reporting linesEntities, worksites, managers, and each place's country and time zone
  2. ThenSet each place's working timeShifts, working weeks and holidays for each worksite, with approvers
  3. NextCheck coverage and accessReview exceptions, team calendars and what each role sees
A suggested order, not a rollout plan

From many places to one rhythm.

Four routines for teams that do not share an office.

  • A schedule for each place

    Plan shifts and rotations for each worksite, with its own break, overtime and rounding rules. Clock-ins are timed by HumaRun, not by the device, and a worksite can add a location, QR code or worksite PIN check to each punch as evidence.

  • Working weeks and holidays

    Set the working week and holidays for each legal entity or worksite, so leave days are counted the way each place works. Your organization enters or imports the public holidays and company closures each place observes.

  • Approvers who follow the team

    Requests go to each person's own manager, and a manager can hand approvals to a colleague for set dates while away. Each leave policy sets its own approval steps.

  • A country and time zone per entity

    Each legal entity carries its own country, currencies and time zone, and pay groups belong to a legal entity.

Access that follows the work and the place.

Everyone sees what their role and their place allow.

  • Employees

    See their own record and requests from a phone or tablet browser, and nothing of anyone else's.

  • Managers

    See and decide for their direct reports, wherever those people work, and cannot change an employee's record.

  • Place-scoped roles

    A role can be limited to selected worksites, branches, departments or a legal entity, so a regional lead sees only their own place.

What works across places and what keeps it consistent.

Built for several locations, with the controls that come with it.

Included

  • Shifts, rotations and rules for each worksite
  • Working weeks and holidays for each legal entity or worksite, entered or imported by your organization
  • A country, currencies and time zone for each legal entity
  • Roles limited to a worksite, branch, department or legal entity
  • Requests and approvals on a phone or tablet browser
  • A web app that runs in phone browsers and can be added to the home screen
  • Shared kiosks and worksite location policies that flag or block a punch
  • Work-from-home and on-duty requests
  • Username sign-in for staff without email
  • Payslips released to employees
  • Notification email
  • Punches from a device that can export a punch file or call HumaRun's push receiver

Controls built in

  • Clock-ins are timed by HumaRun, not by the device
  • A manager sees and decides only for their direct reports, wherever they work
  • A role limited to a place sees only that place
  • Approvals handed to a colleague for set dates, and never passed on again
  • Each leave policy sets its own approval steps

Bring the right questions.

A clear conversation starts with how your teams work across places.

  • Where do people work, and which countries and time zones are involved?
  • How many schedules or shift patterns do you run at each location?
  • How is attendance recorded at each location today?
  • Which holidays and leave rules differ from place to place?
  • Who approves for each team, and what should employees handle themselves?

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.