# Pay the right rules, wherever the work happens

When your team works across states, cities, and provinces, every location has its own overtime, sick leave, and pay rules. Findd applies the right rules to every shift based on where the work happened, and sends payroll-ready hours to your payroll provider.

_Screenshot: One employee's week across California and Nevada sites, with daily overtime in CA and weekly overtime in NV_

-----

## Why it gets complicated

One worker can cover shifts in two cities in the same week. One city has its own sick leave law, one state has daily overtime, and one union local pays overtime after eight hours, but payroll gets a single total. Someone has to split it all out by hand, or it gets paid the wrong way.

With Findd, you can take on contracts in new cities and states without building a new payroll process. Every shift is paid under the rules for where it happened, and your payroll team stops splitting hours by hand.

-----

## Rules follow the location of the work

Findd records where each shift happened from the location of the punch, and applies that location's overtime rules. Each employee also has a default policy, so a shift is never left without the right rules.

_Screenshot: Punch details for a Nevada shift: the punch on the map and the overtime policy detected from GPS_

## Sick leave by city and state

Each job is tied to its city, and each city is tied to the right sick leave bucket. Hours worked in a city with its own sick leave law earn leave under that law, and balances stay separate.

_Screenshot: Separate sick leave balances for each city on the employee app_

## Overtime by state, union, or job

Daily, weekly, 7th-day, and California overtime, union overtime rules, and job-specific rules can all run in the same company. Findd sets them up for you during implementation.

**Overtime, calculated by where the work happened**

The same week can mean different overtime. Findd applies each location's rules to every shift, based on where the work was done.

Pay week · Oct 25 to Oct 31 · The same schedule at two sites

- Four 10-hour shifts
- 40 hours in the week

Overtime rules (which rules apply at each site):

| Rule | Westfield, CA | Riverside, OH |
|---|---|---|
| Weekly overtime after 40 hours | Yes | Yes |
| Daily overtime after 8 hours | Yes | No |
| Double time after 12 hours in a day | Yes | No |
| Seventh consecutive day premium | Yes | No |

- Westfield Distribution Center, California: 8.00 h overtime, Timecard, week of Oct 25, created by pay rules, Regular 32.00 h, overtime 8.00 h, 40.00 h, 2 overtime hours on each 10-hour day
- Riverside City Hall, Ohio: Regular time only, All 40 hours are regular time. Ohio follows the weekly rule, and the week stopped at 40 hours.

Union agreements can add their own overtime rules, and Findd applies those too.

## Hours split across sites and jobs

Workers transfer between jobs, sites, and roles during a shift, so hours land on the right job, in the right jurisdiction, and costs land on the right contract.

_Screenshot: Timecard split: Building A 1:30-3:15, Building B from 3:15, with pay and bill_

## The work location on every shift, for payroll

The state where the work happened is saved on every shift and sent with your payroll data, so your payroll provider can apply the right taxes. Findd prepares the hours, and your payroll provider calculates and files the taxes.

[Learn more about integrations](../../products/integrations/index.md)

_Screenshot: Payroll export file with 284 people split by work state: California, Ohio, and Pennsylvania_

-----

## The Findd Operating System

When you use TLM with HR, WorkOps, and Intelligent Dashboards, every new site is set up once: its location, its rules, and its jobs. Workers clock in at the site, the right rules apply automatically, and dashboards show labor costs and overtime by state, city, and contract.

Learn more about the [Findd Operating System](../../products/frontline-operating-system/index.md)

_Screenshot: Overtime by state, city and site, with the change from the week before_