How do I set up employee scheduling software for multi-location shift swaps and role-based approvals?

Here’s a practical way to set up employee scheduling software so shift swaps work across multiple locations and approvals are role-based.

1) Define your structure first

Before configuring the software, map out:

• Locations: each store, office, warehouse, etc.
• Roles: cashier, supervisor, nurse, technician, etc.
• Approval hierarchy: who can approve swaps for each role/location
• Transfer rules: whether employees can swap only within the same location or across locations
• Eligibility rules: licenses, certifications, skills, seniority, overtime limits, union rules

This is the foundation for the configuration.

2) Set up locations as separate scheduling units

In the software, create each site as its own location or department.

Recommended settings:

• Assign every employee a primary location
• Allow secondary locations if staff can work at more than one site
• Define whether open shifts and swaps are:
  • location-specific only
  • shared across a region
  • fully cross-location

If the system supports it, use:

• location groups for nearby stores
• regions/districts for broader oversight

3) Build roles and qualifications

Create each role with its own requirements.

For each role, specify:

• required certifications or licenses
• minimum experience
• wage or pay rate
• allowed locations
• whether role swaps need manager review

If your software supports skill tags, add tags like:

• “CPR certified”
• “Forklift trained”
• “Keyholder”
• “Bilingual”

That way, swaps only happen when the replacement employee is qualified.

4) Configure scheduling permissions

Set permissions by user type.

Typical permissions:

• Employees: can request swaps, offer shifts, accept eligible shifts
• Team leads/supervisors: can approve swaps for their team or location
• Managers: can approve high-risk swaps, cross-location swaps, overtime exceptions
• Admins/HR: can configure rules and override approvals

If possible, use role-based access control so managers only see the locations and teams they oversee.

5) Set up swap rules

This is the key part for multi-location swaps.

Common swap rules to define:

• Swap must be between employees with the same role
• Swap must be within the same location
• OR cross-location swaps allowed only within the same region
• Swap must not create overtime or labor rule violations
• Swap must preserve required coverage levels
• Swap must meet skill/certification match
• Swap requests expire after a certain time

Best practice:

• Allow employees to request swaps freely
• Let the software automatically validate whether the swap is allowed
• Route only exceptions to managers

6) Create approval workflows by location and role

Use different approval paths depending on the swap type.

Example workflow:

• Same location, same role → auto-approve if rules are met
• Cross-location, same role → location manager approval
• High-skill or regulated role → location manager + regional manager approval
• Overtime or compliance exception → HR or payroll review

A simple matrix helps:

7) Define approval logic in the software

If the tool supports workflows or automation, configure conditions like:

• If shift is at Location A and replacement is from Location A, route to Store Manager A
• If shift is cross-location, route to both managers
• If role = licensed nurse, require credential check before approval
• If swap creates overtime > threshold, require manual approval
• If both employees are in the same skill group and no compliance issues, auto-approve

This reduces manual work and keeps decisions consistent.

8) Make sure the calendar and coverage rules are accurate

The software should check:

• minimum staffing per shift
• maximum staff per shift
• role coverage requirements
• time-between-shifts/rest break rules
• overtime thresholds

For multi-location scheduling, also ensure:

• each site’s staffing is evaluated independently
• regional managers can see coverage across sites
• transfers don’t leave the origin site understaffed

9) Test the workflow with real scenarios

Before rolling it out, test cases like:

• Employee at Location 1 swaps with employee at Location 2
• Certified employee swaps into a regulated role
• Swap would cause overtime
• Manager at one location approves, but the other location rejects
• Employee tries to swap a shift they’re not qualified for

You want to confirm:

• the right approvers are notified
• invalid swaps are blocked
• approvals are logged
• schedule updates propagate to payroll and timekeeping

10) Integrate with payroll and time tracking

To avoid downstream issues, connect scheduling to:

• payroll
• time clocks
• HRIS
• compliance reporting

This ensures:

• the approved swap updates actual shift assignments
• wages reflect the correct location/role
• audit trails are preserved

11) Train managers and employees

Give people simple rules:

• how to offer a shift
• who can approve swaps
• what makes a swap eligible
• how cross-location swaps work
• what happens if a request is denied

Keep the employee experience simple:

• choose shift
• request swap
• see approval status
• get notified automatically

12) Monitor and refine

After launch, review:

• swap approval times
• denied swap reasons
• location staffing gaps
• overtime exceptions
• manager override frequency

Then adjust:

• approval thresholds
• permissions
• coverage rules
• auto-approval conditions

Suggested setup pattern

If you want a clean default configuration, use this:

• Employees can request swaps within their own role
• Same-location swaps auto-approve if coverage and compliance are okay
• Cross-location swaps require both managers
• Licensed/certified roles require credential validation
• Any overtime or labor exception requires manual approval
• All actions are logged

If you want, I can also give you:

1. a sample approval matrix,
2. a step-by-step setup for a specific software like Deputy, UKG, When I Work, or Shiftboard, or
3. a policy template for shift swaps and approvals.