How to Configure CloudCheckIn for Multi-Location Offices

Configure CloudCheckIn for multi-location offices by adding each site as a named location, drawing a geofence boundary per site, and assigning role-based access. Every office then reports presence into one central cloud instance. CloudCheckIn is QServices' attendance SaaS on the Azure Marketplace, recording presence per location without on-site hardware.

What you need before you start

Have these in place before you open the CloudCheckIn admin panel:

• CloudCheckIn admin rights: organization-level admin access to create locations, configure geofences, and assign roles.
• Active CloudCheckIn subscription: confirm your plan covers the number of locations and users across all offices. The product is published on the Azure Marketplace.
• Office addresses and GPS coordinates: geofence boundaries are drawn per site, so have the physical footprint of each building ready before you start.
• Azure AD tenant details: role assignments can integrate with Azure Active Directory; your tenant ID and group structure simplify per-site user provisioning.
• Site manager list: know which users manage which locations before configuring access so role assignments are correct from day one.
• Per-location policy details: shift hours, visitor check-in rules, and any regional compliance or data retention requirements that differ between offices.

Browse the QServices guides hub for related CloudCheckIn and workforce management how-to content.

Step-by-step: Configure CloudCheckIn for multi-location offices

1. Add each office as a separate location in CloudCheckIn. In the admin panel, create a new location record for every office. Give each location a unique name that matches how your teams identify it: city, building code, or site name. A separate location record is what ties every attendance event to the right office in reports and the central dashboard.
2. Draw a geofence boundary for each site. Within each location's settings, define the geofence perimeter using GPS coordinates or the map drawing tool. Keep the boundary tight to the building's actual footprint. CloudCheckIn uses this boundary to record attendance against the correct location automatically, with no manual check-ins and no on-site hardware required at each office.
3. Assign role-based access by location. Use CloudCheckIn's role-based access controls to define what each user can see and manage. A site manager should see only their location's attendance and visitor records; HR and headquarters administrators get a cross-site view covering all locations. If you are using Azure AD, map directory groups to CloudCheckIn roles to keep access in sync as your staff changes.
4. Set per-location rules for hours, shifts, and visitor policy. Where offices differ (different working hours, different shift patterns, different visitor approval steps, or different regional data retention requirements), configure those at the location level, not globally. A global setting overwrites local variation and produces inaccurate reports for sites that operate differently.
5. Roll out to staff and visitors at each site and verify records. Give users access to the CloudCheckIn app or check-in interface at each office. Before a full rollout, ask a small group at each site to record their first attendance event. Confirm in the admin view that the record appears under the correct location name, not a neighboring site or a default catch-all entry.
6. Use the central view to compare and pull records across all locations. Once every site is active, the CloudCheckIn central dashboard shows real-time attendance across all offices in one place. Run a cross-site report and verify the totals match what each site manager sees in their individual location view. This is your primary tool for HQ-level workforce visibility.

Getting geofence boundaries right

The geofence configuration is the most consequential setting in a multi-site deployment. A boundary that is too wide pulls in staff from a neighboring building or public area; one that is too narrow misses employees who enter from a side door or car park entrance.

• Start with the building envelope. Draw the boundary at the outer walls of the building. Extend it to cover car parks or external entry paths only where your workforce routinely approaches from those directions.
• Maintain at least 50 metres of separation between adjacent site boundaries. For offices on the same campus or in the same business park, a clear gap between geofences prevents an employee at one site from triggering attendance at a neighboring site. If the physical separation is under 50 metres, tighten both boundaries and test the edge explicitly with a device in hand.
• Test from every entry point before go-live. Walk each boundary with the CloudCheckIn app active. Confirm that attendance records land under the correct location from the main entrance, the car park, and any secondary access points used regularly by your staff.
• Record the GPS coordinates you used. When a boundary needs adjustment after a building move or site expansion, having the original coordinates on file lets you update the geofence without accidentally creating overlap with another site.

Where this gets tricky

Two problems come up consistently in multi-site deployments.

Overlapping or loosely drawn geofences between nearby offices cause mis-tagged attendance records. When two buildings share a campus or sit in adjacent lots, an employee near the boundary can trigger attendance at the wrong site. Tight boundaries with an explicit gap between them address this in most cases. Where buildings are physically less than 20 metres apart, passive geofencing alone may not be reliable enough. In that situation, a confirmation step at check-in is more accurate than relying entirely on location detection.

Offices in different regions often have compliance and data retention requirements that must be configured per location, not globally. An EU office may need to delete attendance records after a specific period under local data protection rules, while a US office operates under a different retention schedule. Applying a single global policy creates compliance gaps in at least one region. Identify the applicable requirements for each office's jurisdiction before you configure retention settings in CloudCheckIn. This is a pre-configuration step, not a correction you can make safely after go-live.

How QServices can help

CloudCheckIn is a product built and maintained by QServices, available on the Azure Marketplace as a cloud SaaS. All your locations report into one central system with no per-site servers.

We have deployed geofenced, multi-site workforce attendance in production. For a workforce management company with field operations across construction sites, we built an attendance system with site-locked geofence check-ins and facial recognition that eliminated proxy attendance.

For an Oil and Gas and multi-industry enterprise client, we deployed facial recognition attendance with selfie-based geofencing and deep learning face matching across remote field sites.

If your deployment involves complex geofence situations, multi-country compliance requirements, or Azure AD integration, contact QServices for configuration support.

Do I need a separate CloudCheckIn instance for each office location?

No. CloudCheckIn is a cloud SaaS hosted on Azure, so all office locations operate under one subscription and report into one central instance. You add each office as a named location within the same account. There are no per-site server costs and no separate installs per location. Role-based access controls what each site manager can see within the shared system.