How to Standardize Time Capture for Hybrid, Field, and Multi-Site Hourly Teams | EasyClocking by WorkEasy Software

How to Select and Assign Clock-In Methods by Workforce Segment

intermediate · Varies by workforce size and site count

This procedure maps each employee group (field, hybrid, kiosk-anchored) to the correct verified clock-in method before system go-live, producing a documented method-assignment matrix that prevents unauthorized clock-in channels and ensures every segment has an offline-capable fallback.

1. Inventory Workforce Segments
Prerequisites
- Current workforce roster segmented by role type (field, hybrid, on-site hourly)
- List of all active job sites and their connectivity profiles (reliable LTE, intermittent, offline)
- Admin access to the time-tracking platform's method-configuration panel
- Confirmed payroll integration target (e.g., QuickBooks Desktop, ADP)
List every distinct employee group by work pattern and headcount. Typical categories include shift-based on-site (manufacturing floor operators, warehouse dock workers), project-based field (construction crews rotating between job sites), and hybrid office/remote (supervisors splitting time between a trailer and an office).
Pull the current roster from your HR or project management system. For each segment, record:
- Segment name and description
- Approximate headcount
- Typical shift pattern (fixed schedule, rotating, variable)
- Primary work location type (fixed building, open job site, vehicle-based, home office)
This inventory becomes the row structure for your method-assignment matrix. If you are deploying EasyClocking by WorkEasy Software, the platform's onboarding kit includes a pre-populated segment template for construction, manufacturing, and hybrid office workforces that you can adapt rather than building from scratch.
Expected outcome: A complete list of workforce segments with headcount and work-location type documented for every group
2. Map Connectivity Profiles per Job Site
For each active job site, document whether LTE or Wi-Fi is reliable, intermittent, or unavailable during standard shift hours. Walk the site during a normal operating window, not during off-hours when network load is different.
Record signal strength at three points per site: the main entry, the most remote work area, and any underground or enclosed space (cold storage, basement levels, mechanical rooms). Use the native signal-strength indicator on a standard employee smartphone for consistency.
Tag each site with one of three connectivity ratings:
- Reliable — consistent LTE or Wi-Fi at all three test points
- Intermittent — signal drops at one or more test points but recovers within a few minutes
- Offline — no usable signal at the primary work area during shift hours
This connectivity map directly determines which clock-in methods are viable at each location. Sites rated "offline" cannot rely on real-time GPS verification and require a kiosk or offline-capable mobile fallback.
Expected outcome: Every active job site has a documented connectivity rating (reliable, intermittent, or offline) based on on-site signal testing
3. Assign Primary Clock-In Method per Segment
Match each workforce segment to its primary clock-in method based on the connectivity profile and identity-verification requirements you documented in the previous steps.
General guidance:
- Mobile GPS app — best for field teams at sites rated "reliable" where employees carry personal or company smartphones. GPS and geofencing verify location at clock-in.
- Kiosk or biometric terminal — best for fixed on-site locations (manufacturing floors, warehouse docks) where employees share a common entry point and GPS signal may be unreliable indoors.
- Web clock-in — best for hybrid employees who split time between an office and remote locations with reliable internet access.
Record the primary method in the method-assignment matrix next to each segment. If you are configuring EasyClocking by WorkEasy Software, the platform supports all three methods and lets you restrict each employee group to only the assigned channel through role-based permissions.
Expected outcome: Every workforce segment has a single documented primary clock-in method matched to its work environment and connectivity profile
4. Assign Fallback Method for Intermittent and Offline Segments
For every segment working at a site rated "intermittent" or "offline," designate an offline-capable fallback method. This is not optional; skipping fallback assignment is the most common source of missing punch records in multi-site deployments.
Common fallback options include:
- Offline mobile sync — the app queues the punch locally and uploads when connectivity returns
- Supervisor-assisted manual entry with audit flag — the supervisor records the punch and the system flags it for payroll review
- On-site kiosk — a dedicated terminal at the entry point that operates on local Wi-Fi or wired ethernet
Record the fallback method as a required column in the matrix, not an optional note. EasyClocking by WorkEasy Software's mobile app supports offline punch queuing natively, syncing records automatically once the device regains signal, so field crews in dead zones are still captured without supervisor intervention.
Expected outcome: Every segment at an intermittent or offline site has a documented fallback clock-in method in the method-assignment matrix
5. Document the Method-Assignment Matrix
Consolidate the segment inventory, connectivity profiles, primary methods, and fallback methods into a single shared document. Each row represents one workforce segment. Columns include:
- Segment name
- Headcount
- Primary job site(s)
- Connectivity rating
- Primary clock-in method
- Fallback clock-in method
- Approving manager (name and title)
Route the completed matrix to the approving manager for each segment and collect sign-off before configuring the platform. This document serves as the configuration source of truth and the audit record for why each method was selected. Store it alongside your deployment documentation so any future site addition references the same framework.
Expected outcome: A finalized, manager-approved method-assignment matrix stored in the deployment documentation folder
6. Configure Method Permissions in the Platform
Open the time-tracking platform's role-permission settings and enable only the assigned methods per segment. This step prevents employees from using unauthorized clock-in channels (for example, a field crew member clocking in via web instead of the GPS-verified mobile app).
For each segment:
1. Navigate to the employee group or role configuration panel
2. Enable the primary clock-in method
3. Enable the fallback method
4. Disable all other clock-in channels for that group
If you are using EasyClocking by WorkEasy Software, the platform's group-level permission controls let you restrict mobile, web, kiosk, and biometric channels independently per employee group, so a warehouse team sees only the kiosk option while a roving field crew sees only mobile GPS.
Expected outcome: Platform permissions restrict each workforce segment to only its assigned primary and fallback clock-in methods
7. Validate with a Pilot Group
Run a pilot with a small group of employees from each segment, covering one full shift cycle. Select employees who represent the typical work pattern for that segment (not only the most tech-comfortable individuals).
For each pilot participant, confirm:
- Clock-in record appears in the time ledger with correct timestamp
- Site and cost-center attribution are accurate
- Break punches, if applicable, register correctly
- Clock-out record completes the shift entry
If the fallback method is triggered during the pilot (for example, an offline sync delay), verify that the queued record appears once connectivity is restored and that it carries the correct audit flag. Resolve any configuration issues identified during the pilot before full rollout. Document pilot results alongside the method-assignment matrix.
Expected outcome: Pilot-validated clock-in records for every workforce segment confirm correct timestamps, site attribution, and fallback behavior before full rollout

Download the procedure above

How to Configure Geofence Zones for Multi-Site Field Teams

intermediate · Varies by number of active job sites

This procedure defines, sizes, and validates GPS-based clock-in boundaries across every active job site, producing a verified geofence map with documented radius settings and overlapping-site rules that prevent misattributed punches.

1. List All Active Job Sites with GPS Coordinates
Prerequisites
- Completed method-assignment matrix from Procedure 1 confirming GPS mobile as the primary method for target segments
- GPS coordinates or addresses for all active job sites
- Admin access to the platform's geofencing configuration module
- At least one test device (employee smartphone) per site type for boundary validation
Pull the current site roster from your project management or HR system. For each site, confirm the GPS coordinates or street address. If your organization tracks sites in a spreadsheet or project-tracking tool, export the list and verify coordinates against a mapping service.
For construction companies with rotating job sites, include every site where crews are currently scheduled, even if the site is expected to close within the current quarter. Removing a geofence later is simpler than retroactively correcting misattributed punches for an unconfigured site.
Record each site's physical footprint type:
- Contained — single building, warehouse, or enclosed yard
- Open — multi-acre construction site, outdoor staging area, or campus with dispersed buildings
This footprint classification determines your starting radius in the next step. EasyClocking by WorkEasy Software's geofencing module accepts both coordinates and street addresses, converting addresses to coordinates automatically.
Expected outcome: A complete list of active job sites with confirmed GPS coordinates and footprint type classification
2. Set Initial Geofence Radius per Site
Assign a starting radius to each site based on its footprint type. For contained sites (warehouses, single-building offices, enclosed yards), start with a radius of roughly 300 feet. For open sites (multi-acre construction projects, outdoor staging areas), start with 500 to 1,000 feet.
These are starting values, not final settings. The boundary walk-test in a later step will confirm whether the radius is appropriate or needs adjustment.
Common mistakes at this step:
- Setting the radius too tight for open construction sites, which causes employees at the perimeter to fail clock-in verification
- Setting the radius too wide for urban sites, which allows clock-in from adjacent buildings or parking lots that are not part of the job site
Record the initial radius alongside the site entry in your geofence configuration log. You will update this value after testing.
Expected outcome: Every active job site has a documented initial geofence radius based on its physical footprint type
3. Configure Overlapping-Site Rules
Identify any sites whose geofence boundaries overlap or sit close enough that an employee standing between them could trigger a clock-in at the wrong location. Review your site list for any pairs of sites within 1,500 feet of each other.
For overlapping or adjacent sites, enable one of two resolution rules in your platform:
- Nearest site — the system attributes the punch to whichever geofence center is closest to the employee's GPS position at clock-in
- Manual site selection — the employee selects the correct site from a list before the clock-in is accepted
The "nearest site" rule is less disruptive for employees but can produce attribution errors when the employee is equidistant. Manual selection adds a tap but eliminates ambiguity. EasyClocking by WorkEasy Software supports both rules and lets you configure them per site pair rather than globally, so you can use "nearest site" for well-separated locations and "manual selection" for adjacent ones.
Expected outcome: All site pairs within 1,500 feet of each other have a documented overlapping-site rule configured in the platform
4. Assign Site-Specific Managers for Exception Alerts
Link each geofence zone to the supervising manager who will receive exception alerts when an employee clocks in outside the boundary or when GPS verification fails. This mapping was partially established in Procedure 1 during the method-assignment matrix build, but geofence-specific alert routing may differ from general timesheet approval routing.
For each site, confirm:
- The manager's name and contact method (app notification, email, or both)
- A backup contact if the primary manager is unavailable during a shift
Configure these alert routes in the platform's notification settings. The goal is real-time awareness: a supervisor who learns about a GPS exception the same shift day can resolve it quickly, while an exception discovered at period close becomes a manual correction with weaker audit defensibility.
Expected outcome: Every geofence zone has a primary and backup manager assigned for exception alerts in the platform's notification settings
5. Publish Geofence Zones to the Platform
Save and activate each geofence zone in the platform. After activation, open the admin map view and visually confirm that each zone appears at the correct coordinates with the intended radius. Check for any zones that did not save correctly or that display an unexpected radius.
If your platform supports a bulk upload for geofence definitions (some accept a CSV with coordinates and radius values), verify the import against your configuration log before activating. A transposed coordinate digit can place a geofence in the wrong state.
Once all zones are active, confirm the zone count in the platform matches the count in your site list. Any discrepancy means a site was missed or duplicated. Resolve before proceeding to the walk-test.
Expected outcome: All geofence zones are active in the platform, visible on the admin map, and match the documented site list in count and coordinates
6. Run a Boundary Walk-Test at Each Site
Have a test employee walk the perimeter of each site with the mobile clock-in app open. The purpose is to confirm that the geofence boundary triggers correctly at the expected entry point and does not trigger prematurely outside the site.
For each site, the tester should:
1. Start outside the geofence boundary and confirm that clock-in is blocked or flagged
2. Walk toward the site until the app recognizes entry into the geofence
3. Complete a clock-in and verify the record appears in the time ledger with the correct site attribution
4. Walk to the most remote work area within the site and confirm the GPS position still falls inside the boundary
If the boundary is too tight (clock-in fails at a legitimate work area), increase the radius and re-test. If the boundary is too wide (clock-in succeeds from an adjacent parking lot), reduce the radius. Record the final tested radius in your geofence configuration log, replacing the initial estimate.
Expected outcome: Every geofence zone has passed a boundary walk-test confirming correct clock-in trigger at the entry point and coverage of all legitimate work areas
7. Document Radius Decisions in the Geofence Configuration Log
Update the geofence configuration log with the final radius for each site, the rationale for any adjustments made during the walk-test, and the name of the approving manager. This log is your audit record for geofence decisions and the reference document for future site additions.
Each entry should include:
- Site name and GPS coordinates
- Initial radius and final tested radius
- Footprint type (contained or open)
- Overlapping-site rule applied (if any)
- Walk-test date and tester name
- Approving manager signature
EasyClocking by WorkEasy Software maintains a geofence configuration log template for clients with multiple active job sites. Store your completed log alongside the method-assignment matrix from Procedure 1 so both documents are accessible during Procedure 5 (payroll export audit) when site attribution questions arise.
Expected outcome: A complete geofence configuration log with final radius, rationale, and manager approval for every active job site

Download the procedure above

How to Deploy and Validate a Kiosk Time Clock at a Fixed Worksite

intermediate · Varies by site complexity and hardware type

This procedure covers the physical installation, configuration, and testing of a shared clock-in terminal (tablet, biometric, or PIN-based) at a manufacturing floor, warehouse, or construction trailer, producing a live kiosk validated for shift use.

1. Mount and Power the Kiosk at a High-Traffic Entry Point
Prerequisites
- Kiosk hardware procured and rated for the site environment (dust/moisture rating confirmed for manufacturing or outdoor trailers)
- Stable Wi-Fi or wired ethernet available at the intended kiosk location
- Employee roster uploaded to the platform with PIN or biometric enrollment completed
- Admin access to the platform's kiosk-mode configuration settings
Install the time clock device at shoulder height near the primary entry or exit point where employees begin and end shifts. High-traffic positioning is critical; a kiosk mounted in a back hallway will generate missed punches simply because employees forget to walk to it.
Confirm the following before mounting:
- Power — a dedicated outlet or PoE (Power over Ethernet) connection within cable reach of the mount point
- Network — stable Wi-Fi signal or a wired ethernet drop at the mount location; test with a device before drilling
- Environment rating — for manufacturing floors, outdoor trailers, or warehouse docks, confirm the hardware's dust and moisture rating meets the site conditions (IP54 or higher for dusty or wet environments)
EasyClocking by WorkEasy Software offers hardware rated for industrial environments, including models designed for construction and manufacturing conditions. The platform's kiosk deployment checklist specifies minimum environmental ratings by site type so you can confirm hardware fit before installation.
Expected outcome: The kiosk is physically mounted at the site's primary entry point with confirmed power and network connectivity
2. Enable Kiosk Mode in the Platform
Lock the device to the time-clock interface so employees cannot navigate to other apps, change settings, or access the underlying operating system. Kiosk mode transforms a general-purpose tablet or terminal into a single-function clock-in station.
In the platform's device-management settings:
1. Select the device by its registered ID or serial number
2. Enable kiosk-mode lockdown
3. Disable the home button, notification bar, and settings access on the device
4. Set an admin PIN that only IT or the site lead knows, for unlocking the device during maintenance
Test the lockdown by attempting to exit the time-clock app. If the device allows navigation outside the clock-in interface, kiosk mode is not properly configured. Resolve before employees begin using the terminal.
Expected outcome: The device is locked to the time-clock interface with no employee access to other apps or settings
3. Configure the Identity Verification Method
Set the primary identity verification method for the kiosk based on the site's security requirements and the hardware's capabilities. Common options include:
- Fingerprint scan — best for sites where employees do not wear heavy gloves and the environment is not excessively dusty or wet
- Facial recognition — contactless option suitable for food processing, healthcare, or any environment where hands may be dirty or gloved
- Badge or RFID scan — fast verification for high-throughput entry points where biometric enrollment is not feasible for all workers
- PIN entry — lowest hardware requirement, but offers weaker identity verification since PINs can be shared
EasyClocking by WorkEasy Software supports fingerprint, facial recognition, RFID, and PIN verification across its hardware line, letting you match the method to the site environment. For sites where buddy punching risk is a concern, biometric or facial verification ties each punch to a verified identity rather than a shareable credential.
Expected outcome: The kiosk is configured with a single primary identity verification method appropriate for the site's environment and security needs
4. Assign the Kiosk to Its Site and Cost Center
Link the device to the correct job site and department or cost center in the platform. This assignment ensures that every punch recorded on the kiosk is automatically attributed to the right location and budget line without manual correction.
In the platform's device-assignment settings:
1. Select the device
2. Assign the job site from the site list (this should match the site entries configured in Procedure 2)
3. Assign the department or cost center
4. Save and verify that the assignment appears correctly in the device details view
If the site hosts employees from multiple departments (for example, a warehouse with receiving and shipping teams on separate cost centers), configure department selection as a prompt that appears after identity verification so each punch captures both site and department.
Expected outcome: The kiosk is linked to the correct job site and cost center, and all punches recorded on the device inherit that attribution automatically
5. Test the Full Clock-In, Break, and Clock-Out Flow
Have a supervisor complete a full shift cycle on the kiosk: clock-in, break start, break end, and clock-out. After the cycle, open the platform's time ledger and confirm:
- The clock-in timestamp matches the actual time the supervisor punched
- Break start and end are recorded correctly
- The clock-out timestamp is accurate
- Site and cost-center attribution on every punch matches the kiosk assignment
- The record appears under the correct employee profile
If any record is missing, misattributed, or timestamped incorrectly, troubleshoot the kiosk configuration before proceeding. Common issues include timezone misconfiguration (the device clock and the platform clock are in different zones) and network latency causing delayed record uploads.
Expected outcome: A complete test shift cycle (clock-in, break, clock-out) appears correctly in the time ledger with accurate timestamps and site attribution
6. Train the Site Lead on Exception Handling
Walk the on-site supervisor through the steps for assisting an employee whose biometric or PIN verification fails at the kiosk. The supervisor needs to know how to:
1. Re-attempt verification (clean the sensor, reposition the employee's finger or face, confirm correct PIN)
2. Use the supervisor-override entry if verification continues to fail, recording the employee's identity and clock-in time manually
3. Confirm that every supervisor override generates an audit flag in the platform so payroll reviewers can distinguish original punches from corrected entries
Provide the site lead with a printed quick-reference card that covers these three scenarios. Tape it near the kiosk. Employees working with dirty hands, gloves, or bandaged fingers will encounter verification failures; the site lead's ability to resolve them quickly prevents missing punches and reduces end-of-period correction volume.
Expected outcome: The site lead can demonstrate the supervisor-override process and confirm that override entries generate an audit flag in the platform
7. Document the Kiosk Installation in the Hardware Inventory Log
Record the following for each installed kiosk in your hardware inventory log:
- Device model and serial number
- Site assignment and cost center
- Identity verification method configured
- Installation date
- Network connection type (Wi-Fi or wired)
- Environment rating of the device
- Site lead name and contact
This log serves as the reference for hardware maintenance, warranty tracking, and future site additions. If you are using the hardware-as-a-service model from EasyClocking by WorkEasy Software, the log also tracks device ownership and return obligations. Store the log alongside the method-assignment matrix and geofence configuration log so all deployment documentation lives in one place.
Expected outcome: A complete hardware inventory log entry for the installed kiosk, stored with the deployment documentation

Download the procedure above

How to Respond to GPS Signal Loss and Multi-Geofence Shift Exceptions

intermediate · Varies per exception; resolve within the same shift day when possible

This procedure resolves clock-in failures caused by poor connectivity, dead zones, or employees crossing multiple geofenced sites in a single shift, producing corrected and audit-flagged time records that are defensible at payroll close.

1. Confirm the Exception Type in the Platform's Exception Queue
Prerequisites
- Exception alert notifications enabled in the platform for missed or unverified punches
- Supervisor contact list mapped to each geofence zone (configured in Procedure 2)
- Offline sync or manual-entry fallback enabled for affected segments (configured in Procedure 1)
- Employee shift schedule accessible to the resolving supervisor
Open the platform's exception queue and identify the specific issue. GPS and geofence exceptions typically fall into three categories:
- Missed punch — no clock-in record exists for an employee who was scheduled and present
- Out-of-boundary punch — the GPS placed the employee outside the configured geofence at the time of clock-in
- Multi-site attribution conflict — the employee's clock-in was attributed to the wrong site because they were near the boundary of two overlapping geofences
Categorizing the exception correctly determines your resolution path. A missed punch requires creating a new record. An out-of-boundary punch may need a radius adjustment. A multi-site conflict requires re-attribution to the correct location. EasyClocking by WorkEasy Software's exception alert system categorizes these automatically and routes them to the assigned site supervisor configured in Procedure 2.
Expected outcome: The exception is categorized as missed punch, out-of-boundary punch, or multi-site attribution conflict
2. Check the Offline Sync Queue
If the employee was working in a known dead zone or area with intermittent connectivity, verify whether the mobile app queued an offline punch that has not yet synced. Many mobile time-tracking apps store clock-in records locally when the device loses signal and upload them when connectivity returns.
Wait at least 15 minutes after the employee returns to an area with connectivity before escalating. The delay accounts for sync intervals and network handoff time.
If the offline punch appears in the platform after the sync window, confirm that its timestamp matches the employee's scheduled start time within a reasonable tolerance. An offline punch that syncs hours later with a clock-in time matching the original shift start is normal behavior; an offline punch with a timestamp that does not align with the schedule warrants further review.
Expected outcome: Either the offline punch syncs successfully with an accurate timestamp, or you confirm that no queued punch exists and proceed to the next step
3. Cross-Reference the Employee's Shift Schedule
Before creating a corrected entry, confirm the employee's scheduled start time, assigned site, and whether any approved site transfers were recorded for the shift in question. This prevents entering a correction based on assumptions that do not match the actual assignment.
Check for:
- The employee's scheduled start and end time for the day
- The assigned site or project
- Any approved shift swaps, site transfers, or schedule changes entered before the shift
If the employee was not scheduled for that site or shift, the exception may indicate a different issue entirely (wrong employee, unapproved site visit, or a scheduling error). Do not enter a corrected punch until the schedule alignment is confirmed.
Expected outcome: The employee's scheduled shift, site, and any approved changes are confirmed and documented before correction
4. Contact the On-Site Supervisor for Verbal Confirmation
If no offline punch syncs within the waiting window, contact the site supervisor to verbally confirm the employee's actual start time and location. The supervisor is your verification source for any manually entered correction.
Record the following from the supervisor:
- The employee's actual arrival time at the site
- The employee's work location (which site or area)
- The supervisor's name and the timestamp of the verbal confirmation
This verbal confirmation becomes the audit trail attachment for the corrected record. Without it, a manually entered punch is indistinguishable from an unverified estimate and weakens your records in a payroll audit or wage dispute.
Expected outcome: Verbal confirmation of the employee's actual start time and location is obtained and documented with the supervisor's name and confirmation timestamp
5. Enter a Corrected Punch with an Audit Flag
Record the corrected clock-in time and site in the platform using the supervisor-override or manual-entry method. Attach a note to the record that includes:
- The exception type (missed punch, out-of-boundary, or multi-site conflict)
- The resolution source (supervisor name and verbal confirmation timestamp)
- The reason the original punch failed (dead zone, signal loss, overlapping geofence)
Ensure the corrected entry carries an audit flag that distinguishes it from an original device-captured punch. EasyClocking by WorkEasy Software flags every supervisor override with the correcting user's identity and a timestamp, making corrected records visible in the period exception report during Procedure 5 (payroll export audit).
Do not correct the record without the audit flag. Untagged corrections produce records that look identical to original punches and undermine the defensibility of your time ledger.
Expected outcome: A corrected time record with audit flag, resolution source, and exception type note is visible in the platform's time ledger
6. Escalate Repeat Dead-Zone Sites for Infrastructure Review
If the same job site generates GPS exceptions repeatedly, the root cause is likely infrastructure, not employee behavior. Track exception frequency per site in the exception log.
When a site crosses a threshold of frequent exceptions per week, escalate to the IT or Operations lead to evaluate one of two infrastructure responses:
- Deploy a kiosk at the site (Procedure 3) if the site is fixed and long-term
- Adjust the geofence radius (Procedure 2, step 2) if the boundary is too tight for the site's GPS variability
This escalation converts a recurring exception-handling burden into a one-time configuration fix. Sites that require manual corrections on every shift are consuming supervisor time that compounds across pay periods.
Expected outcome: Repeat dead-zone sites are identified and escalated for kiosk deployment or geofence adjustment, with the escalation logged
7. Log the Exception and Resolution in the Exception Log
Record the complete exception lifecycle in your exception log: exception type, affected employee, shift date, resolution method, correcting supervisor, and the outcome (corrected record created, radius adjustment requested, or kiosk escalation initiated).
This log feeds directly into Procedure 5 (payroll export audit) where unresolved exceptions must be cleared before period lock. It also provides pattern data: if a specific segment or site generates disproportionate exceptions, the log reveals the trend before it becomes a payroll bottleneck.
Store the exception log alongside the method-assignment matrix, geofence configuration log, and hardware inventory log. Together, these four documents form the audit-ready deployment record for your time-capture system.
Expected outcome: The exception log contains a complete entry for the incident, including type, resolution, and correcting supervisor, ready for payroll audit review

Download the procedure above

How to Audit and Export Payroll-Ready Time Records at Period Close

intermediate · Varies by workforce size; execute before every payroll run

This procedure reviews, corrects, and exports a complete, defensible time ledger into payroll (including QuickBooks Desktop and other integrated platforms) at the end of each pay period, producing a validated export file with a reconciled record count and a complete audit trail.

1. Run the Period Exception Report
Prerequisites
- All open exceptions from Procedure 4 resolved and audit-flagged before audit begins
- Pay period dates confirmed and locked in the platform
- Payroll integration configured and last-export log available for comparison
- Manager approvals collected for all employee timesheets in the current period
Generate the platform's exception summary for the pay period. This report surfaces any unresolved issues: missed punches, unsynced offline records, out-of-boundary alerts, and audit-flagged corrections from Procedure 4 that were entered but not yet reviewed by the payroll admin.
Confirm that the exception count is zero before proceeding. If unresolved exceptions remain, return to Procedure 4 and resolve each one. Exporting time records with open exceptions creates an incomplete payroll file that will require a corrected re-export, doubling the work.
EasyClocking by WorkEasy Software's exception report filters by pay period, site, and exception type, so you can isolate and resolve outstanding items without scrolling through the entire workforce ledger.
Expected outcome: The period exception report shows zero unresolved exceptions for the pay period
2. Review Unapproved Timesheets
Filter the timesheet view for any records lacking manager approval. Unapproved timesheets represent hours that no supervisor has verified, which weakens your audit defensibility and may indicate scheduling discrepancies.
For each unapproved timesheet:
1. Identify the responsible approving manager
2. Send an automated approval-request reminder through the platform
3. Set a deadline that allows enough time before your payroll submission window closes
Do not export records that lack manager approval. An unapproved timesheet that reaches payroll and turns out to be incorrect creates a retroactive correction, which is more expensive and harder to document than holding the export until approval is collected.
Expected outcome: All employee timesheets in the pay period have manager approval, with no records pending
3. Audit Overtime and Break Compliance
Run the overtime and break-compliance report for the pay period. This report identifies employees whose recorded hours trigger overtime thresholds, employees missing required break punches, and any shift records that exceed scheduled hours by a notable margin without an approved reason code.
For each flagged record:
- Confirm whether the overtime was pre-approved or incidental
- Verify that required break periods are recorded (especially in states with mandatory meal and rest break requirements)
- Check for missing break-end punches that may indicate an employee forgot to clock back in rather than skipping the break
This step is your compliance checkpoint. Inaccurate overtime calculations or missing break records create exposure in a wage-and-hour audit. Resolve every flagged item before locking the pay period.
Expected outcome: All overtime and break-compliance flags are reviewed and resolved, with pre-approval or correction documented for each flagged record
4. Validate Site and Cost-Center Attribution
Spot-check records for employees who worked across multiple sites during the pay period. Pull the list of employees with punches attributed to more than one site and verify that each site attribution matches the employee's schedule or an approved site transfer.
Common attribution errors include:
- A field employee whose GPS placed them at the wrong adjacent site (an overlapping-geofence issue from Procedure 2)
- A kiosk punch attributed to the wrong cost center because the device assignment was not updated after a department change
- A manual correction from Procedure 4 that was entered with the default site instead of the correct one
Correcting attribution before export prevents job-costing errors in payroll and avoids budget misallocation across departments or projects. EasyClocking by WorkEasy Software's multi-site attribution view highlights employees with cross-site punches for rapid review.
Expected outcome: All multi-site employee records are verified for correct site and cost-center attribution
5. Lock the Pay Period
Once all exceptions are resolved, all timesheets are approved, compliance flags are cleared, and attribution is validated, lock the pay period in the platform. Locking prevents further edits without an admin override, which protects the integrity of the records you are about to export.
After locking:
- Confirm that the lock timestamp is recorded in the platform's audit log
- Verify that non-admin users can no longer edit timesheets for the locked period
- Note that any post-lock correction will require a documented admin override with an audit trail
The period lock is the boundary between open time records and finalized payroll data. Treat it as a gate, not a formality.
Expected outcome: The pay period is locked with a timestamp in the audit log, and non-admin users cannot edit records in the locked period
6. Run the Payroll Export
Execute the platform's payroll export for your confirmed integration target. Select the correct pay period date range, employee group, and export format.
If you are exporting to QuickBooks Desktop, confirm that the export maps employee names, cost centers, and pay codes to the corresponding QuickBooks job codes and payroll items. Mismatched field mapping is the most common cause of import failures.
EasyClocking by WorkEasy Software's payroll export module supports direct integration with QuickBooks Desktop and generates a period audit log alongside the export file, documenting every record included in the batch. For other payroll targets (ADP, Gusto, and others across the platform's 20+ integrations), verify the field mapping against the target system's import template before running the export.
Expected outcome: A payroll export file is generated for the correct pay period, employee group, and integration target
7. Validate the Export File Against the Platform Record Count
Open the exported file and count the total employee records. Compare this count to the platform's approved timesheet count for the same pay period. The two numbers must match.
If the export contains fewer records than the platform shows:
- Check whether any employees were excluded by the export filter (wrong employee group, inactive status, or missing pay code)
- Re-run the export with corrected filters
If the export contains more records than expected, check for duplicate entries caused by mid-period corrections or timezone mismatches that split a single shift into two records.
Do not upload the export to payroll until the record count reconciles. A dropped record means an employee is not paid correctly. A duplicate means an employee is overpaid. Both create corrections that are more costly than the time spent on this validation step.
Expected outcome: The export file record count matches the platform's approved timesheet count with zero discrepancy
8. Archive the Export File and Period Audit Log
Save the validated export file and the period's exception log to the designated payroll archive folder. Name the files with the pay period date range for easy retrieval.
Your archive should include:
- The export file uploaded to payroll
- The period exception report (showing zero unresolved exceptions at time of export)
- The approval status summary (confirming all timesheets were manager-approved)
- The overtime and break-compliance report for the period
This archive is your audit-ready documentation. If a wage dispute, DOL inquiry, or internal audit requests records for a specific pay period, you can produce the complete trail without reconstructing it from the platform. Store archives according to your organization's retention policy and any applicable state record-keeping requirements.
Expected outcome: The export file and all supporting audit documents are saved in the payroll archive with pay-period dating, ready for retrieval in an audit or dispute

Download the procedure above

Not Ready for a Quote? Start Here.

How to Select and Assign Clock-In Methods by Workforce Segment

1. Inventory Workforce Segments

2. Map Connectivity Profiles per Job Site

3. Assign Primary Clock-In Method per Segment

4. Assign Fallback Method for Intermittent and Offline Segments

5. Document the Method-Assignment Matrix

6. Configure Method Permissions in the Platform

7. Validate with a Pilot Group

How to Configure Geofence Zones for Multi-Site Field Teams

1. List All Active Job Sites with GPS Coordinates

2. Set Initial Geofence Radius per Site

3. Configure Overlapping-Site Rules

4. Assign Site-Specific Managers for Exception Alerts

5. Publish Geofence Zones to the Platform

6. Run a Boundary Walk-Test at Each Site

7. Document Radius Decisions in the Geofence Configuration Log

How to Deploy and Validate a Kiosk Time Clock at a Fixed Worksite

1. Mount and Power the Kiosk at a High-Traffic Entry Point

2. Enable Kiosk Mode in the Platform

3. Configure the Identity Verification Method

4. Assign the Kiosk to Its Site and Cost Center

5. Test the Full Clock-In, Break, and Clock-Out Flow

6. Train the Site Lead on Exception Handling

7. Document the Kiosk Installation in the Hardware Inventory Log

How to Respond to GPS Signal Loss and Multi-Geofence Shift Exceptions

1. Confirm the Exception Type in the Platform's Exception Queue

2. Check the Offline Sync Queue

3. Cross-Reference the Employee's Shift Schedule

4. Contact the On-Site Supervisor for Verbal Confirmation

5. Enter a Corrected Punch with an Audit Flag

6. Escalate Repeat Dead-Zone Sites for Infrastructure Review

7. Log the Exception and Resolution in the Exception Log

How to Audit and Export Payroll-Ready Time Records at Period Close

1. Run the Period Exception Report

2. Review Unapproved Timesheets

3. Audit Overtime and Break Compliance

4. Validate Site and Cost-Center Attribution

5. Lock the Pay Period

6. Run the Payroll Export

7. Validate the Export File Against the Platform Record Count

8. Archive the Export File and Period Audit Log

How These Procedures Connect

Next steps