The Timekeeping Problems That Only Exist in a Field: How One of the World’s Largest Berry Producers Manages Crew Time and Productivity Bonuses Across Remote Operations in Multiple Countries Using UKG

A global fresh berry producer runs crew time and productivity bonuses for remote field operations in several countries on UKG Pro WFM, using CloudApper Crew Punch. Field agriculture breaks most timekeeping assumptions. Workers are spread across remote fields with no connectivity, and crews move, start and stop together, so individual punches at a fixed clock don’t fit. With operations in several countries, pay rules also differ by country.

Workbridge

UKG Personalization

50+ HR gaps UKG leaves open. WorkBridge closes them in days, not months.

Get Started

The company needed UKG Pro WFM as the workforce backbone for its R&D and nursery field crews. CloudApper Crew Punch, running on CloudApper hrPad, captures crew-based time across remote fields, syncs to UKG Pro WFM whenever connectivity returns, and automates the country-specific productivity bonus calculations on top of UKG Pro WFM.

Why Field Agriculture Needs More Than a Fixed Time Clock

The problem begins with the environment. Agricultural field crews operate at locations that may have no Wi-Fi, no reliable cellular signal, and no fixed physical infrastructure to anchor a time clock to. Fixed time clocks, whether hardware-based or soft clock installations, are designed for sites with a reliable connection, and remote agricultural settings often have none. A crew that cannot reach the network cannot punch in. An organization that cannot capture punches in real time ends up falling back on paper timesheets, which introduces the data entry delay, transcription error, and audit trail gap that a workforce management system is specifically meant to eliminate.

The second problem is structural. Agricultural crews work as units. A crew leader brings a group of workers to a field location, starts the work, supervises it, and closes it out. Expecting each individual worker in a crew of fifteen or twenty people to interact separately with a timekeeping device, at a remote field site, before or after physical labor, is an impractical requirement that creates the kind of friction that results in missed punches, incomplete records, and payroll corrections later. As explored in the context of group time tracking for UKG customers, the architecture of individual punch-in punch-out was designed for a fixed-location, individually accountable workforce, not for the crew-based, supervisor-led structure that defines field agricultural operations.

Workbridge

UKG Personalization

We don't replace UKG. We make it finally work your way.

Learn More

The third problem emerges when productivity compensation enters the picture. Agricultural pay models, particularly for harvest and R&D nursery operations, are often tied to output: what was harvested, in what quantity, at what quality level, by which crew, measured against a target. That kind of pay logic requires tracking multiple data dimensions per shift (berry variety, activity type, harvest volume, quality percentage) and applying calculation rules that may differ by country, by operation type, and by individual versus group performance thresholds. That is a custom business rule set that sits on top of UKG Pro WFM. Without an engine built for it, the result for most agricultural organizations is that the productivity bonus piece lives in Excel, which introduces the same reliability and accuracy problems it introduces everywhere else it is used as a substitute for real automation.

What a Crew Punch Platform Actually Requires

The solution this organization implemented through CloudApper rests on a different operating model for time capture. Rather than requiring individual workers to interact with a device, the crew leader operates the system on behalf of the group. Using a tablet running CloudApper hrPad, the crew leader starts the shift for the entire crew at the beginning of the day, logging the project, job type, and location combination that applies to that day’s work. At the end of the shift, the same crew leader closes the group out. The individual workers receive accurate, timestamped timecard records in UKG Pro WFM without each having interacted with a device individually.

The offline capability is what makes this viable for remote field operations. CloudApper hrPad stores punch data locally on the device when connectivity is unavailable and syncs automatically to UKG Pro WFM when a connection is restored. The crew leader does not need to wait for signal, does not need to retry failed submissions, and does not need to maintain a paper backup. The data captured in the field (project, job, location, shift start, shift end, crew members) travels to UKG intact, with the same structure and accuracy as if the punch had occurred in a connected facility.

“So now this follows the timesheet all the way to our payroll system. And when we pay it, we allocate now the dollars to these hours.”

Workforce Systems Lead, Global Fresh Produce Company

The activity entry layer adds the dimension that field operations require and that standard timekeeping does not capture. Beyond start and stop times, the platform records what the crew was doing and where (project code, job type, location), giving operations leadership and HR a timecard record that reflects not just hours worked but the context of those hours. For organizations that allocate labor costs across research projects, nursery programs, or geographic locations, that context is not optional data. It is the foundation of accurate job costing, and without it, the timecard becomes an input to payroll but not an input to operational analysis. As discussed in the context of job costing and cost center management with UKG, the gap between hours captured and hours allocated is where labor cost visibility breaks down.

Cross-Border Complexity: Automating Country-Specific Productivity Bonuses

The timekeeping problem, once solved by the crew punch architecture, is tractable. The productivity bonus problem in one of the company’s countries of operation is in a different category of complexity.

In that country’s agricultural operations, workers earn bonuses tied to harvest performance, but the calculation is not a simple multiplier of units produced. The relevant variables include the berry variety being harvested (which carries different baseline targets), the activity type (picking, thinning, planting each carry different rate structures), the individual worker’s performance against a minimum threshold, and the quality percentage of the harvest: the proportion of what was picked that meets grade standards. Bonuses may be calculated at the individual level, the group level, or both, with the group dimension introducing a shared-accountability component that changes how individual compensation is computed depending on collective performance.

Workbridge

UKG Personalization

Missed punches dropped from 30% to under 5% — without touching UKG's core.

Learn More

This math is a custom business rule set that runs best in an engine built on top of UKG Pro WFM: multi-variable productivity bonus calculations that vary by crop, activity, quality grade, and individual-versus-group threshold simultaneously. For organizations trying to run this without an engine on top of UKG, the calculation either gets pushed to a spreadsheet or pushed to a custom data entry step that manually posts a bonus amount after the fact. Both approaches introduce lag, expose accuracy risk, and remove the auditability that a compliance environment requires.

CloudApper’s productivity bonus engine handles the full calculation automatically. The inputs (berry variety, activity type, harvest volumes, quality percentages, crew composition, and individual performance records) are captured through the same hrPad workflow the crew leader uses for time capture. CloudApper applies the applicable bonus logic, calculates individual and group-level amounts per shift, and allows recalculation after corrections. The output is a payroll-ready CSV or Excel file, with a per-employee audit view of how each bonus was calculated, replacing the manual spreadsheet and multi-handoff process. This is the same principle that drives accurate piecework pay automation in UKG Pro WFM: calculation logic that belongs in a purpose-built engine rather than a spreadsheet that no one fully trusts by the time payroll closes.

What Expansion to a Third Country Reveals About Platform Design

The solution this berry producer deployed across its first two countries of operation expanded to R&D operations in a third country in 2026. That expansion is worth examining not just as a business fact but as a design indicator. When a timekeeping and compensation platform is genuinely built for field agricultural operations: offline-capable, crew-based, activity-aware, and configurable for country-specific pay rules. Adding a new country does not require a new system. It requires configuring the existing one for the new operational context.

The alternative model, point solutions for each country, spreadsheet-based bonus calculations that are rebuilt for each jurisdiction, manual timekeeping processes that depend on whoever is on the ground, does not scale. It produces HR infrastructure that grows in complexity with each new location, creates reconciliation overhead that multiplies as operations expand, and leaves leadership without a consistent data view across geographies.

Workbridge

UKG Personalization

Migrating UKG Ready to Pro? Your customizations come with you. No rebuilds.

See How

For agricultural enterprises managing R&D operations, nursery programs, or harvest operations across multiple countries under UKG Pro WFM, the core infrastructure requirement is the same in every location: accurate crew-based time capture that works without connectivity, activity-level data that supports job costing, and compensation logic that can handle the country-specific pay rules that govern each operation. CloudApper Crew Punch was built to meet that requirement as a UKG extension, adding field-specific capability on top of UKG Pro WFM without replacing the core workforce management platform that already governs scheduling, leave, and HR records. As described in the context of eliminating the attendance blind spot for UKG customers, matching what field operations require to what the WFM platform captures is a structural problem, and a structural problem has a structural solution.

The berry producer in this story did not replace UKG. It added the layer that extends UKG to fit the workforce it actually has: crews in remote fields, in multiple countries, earning pay that depends on how much they harvested, how well they harvested it, and how the group performed against a shared goal. That combination is not exotic in agriculture. It is the norm. And it deserves timekeeping and compensation infrastructure that treats it as such.

If your organization manages agricultural, R&D, or field operations under UKG Pro WFM and needs crew-based timekeeping, offline punch capability, or country-specific productivity bonus automation, CloudApper can design the right extension for your specific operational environment. Contact the CloudApper team to discuss what your field workforce requires.