Skip to main content
Skip to main content

βš™οΈ End-to-End Payroll Setup

Setting up construction payroll for the first time β€” or migrating to a new system β€” requires getting the configuration right before a single paycheck is cut. The steps have a strict dependency order: you can't assign a worker to a classification that doesn't exist yet, and you can't set up a classification without knowing the time calculation mode.

This page walks through the full setup sequence, the decision points at each step, and finishes with the payroll run lifecycle and a verification checklist.

The dependency chain​

Each step depends on the one before it. Skip a step and the downstream configuration breaks.

1
1. Time calculation mode
ST/OT/DT Active, Weekly Only, or ST/OT β€” determines how hours split
2
2. OT thresholds
Daily and weekly breakpoints, 7th-day toggle, AWS selection
3
3. Union locals
Trade, jurisdiction, effective dates, trust fund destinations
4
4. Wage rates
Base wage + fringe line items per classification per local
5
5. Worker assignments
Classification, union local, apprentice period (if applicable)
6
6. Project configuration
PW required, wage determination, state/county, DIR project ID

Step 1: Choose the time calculation mode​

The time calculation mode determines how raw hours are split into straight time, overtime, and double time. This is the most consequential setting in the system because everything downstream β€” OT thresholds, rate application, paycheck math β€” depends on it.

Decision tree​

Is the project in California?

  • Yes β†’ Use ST/OT/DT Active (daily overtime with double time after 12 hours)
  • No β†’ Continue below

Does the union CBA require daily overtime?

  • Yes β†’ Use ST/OT/DT Active or ST/OT (depending on whether the CBA includes double time)
  • No β†’ Continue below

Is this a federal prevailing wage project in a daily-OT state (Nevada, Alaska, Colorado)?

  • Yes β†’ Use ST/OT Active (daily OT without DT, unless state law adds DT)
  • No β†’ Use Weekly Only (FLSA standard β€” OT after 40 hours/week)
ModeWhen to useDaily OTWeekly OTDT
ST/OT/DT ActiveCalifornia, or CBA with DTβœ… after 8 hrsβœ… after 40 hrsβœ… after 12 hrs daily, 7th day 8+
ST/OTDaily OT states without DT, or CBA with daily OT onlyβœ… after thresholdβœ… after 40 hrs❌
Weekly OnlyFLSA-only states (most of the country)βŒβœ… after 40 hrs❌
Multi-state companies

If you operate in multiple states, you'll likely need different time calculation modes for different projects. Set the mode at the project level, not company-wide.


Step 2: Configure OT thresholds​

Once the mode is chosen, set the specific hour thresholds that trigger each premium.

Standard thresholds (California)​

ThresholdValueNotes
Daily ST max8 hoursHours 1–8 at 1.0Γ—
Daily OT start8 hoursHours 9–12 at 1.5Γ—
Daily DT start12 hoursHours 13+ at 2.0Γ—
Weekly OT start40 hoursAfter 40 ST in the workweek
7th consecutive dayEnabledFirst 8 hrs at 1.5Γ—, 8+ at 2.0Γ—

Alternative workweek (AWS) thresholds​

If the work group has an approved AWS under California Labor Code Β§511:

AWS typeDaily ST maxDaily OT startDaily DT start
4Γ—1010 hours10 hours12 hours
3Γ—12 (rare)12 hours12 hoursβ€”
9/809 hours (8 on short day)9 hours12 hours

Remember: the AWS exemption only applies to scheduled days. Hours on unscheduled days revert to standard thresholds.

FLSA-only thresholds​

ThresholdValue
Weekly OT start40 hours
Daily thresholdsNone (no daily OT under FLSA)
7th dayNot applicable

Step 3: Set up union locals​

A union local is identified by its trade, local number, and geographic jurisdiction. Each local has its own CBA with its own rates, effective dates, and trust fund accounts.

What you need for each local​

FieldExampleWhy it matters
Union nameIBEWIdentifies the international union
Local number11Specific chapter
TradeInside Wireman (Electrical)Maps to craft classifications
JurisdictionLos Angeles CountyGeographic scope for rate applicability
CBA effective date06/01/2025Rates change when a new CBA takes effect
CBA expiration date05/31/2028Alerts you to upcoming rate changes
Trust fund nameIBEW Local 11 TrustWhere fringe remittances are sent
Trust fund EINXX-XXXXXXXRequired for ERISA reporting
Remittance addressTrust admin mailing addressMonthly fringe payments

Common pitfalls​

  • Overlapping jurisdictions: Some locals cover overlapping counties. Verify which local has jurisdiction for your specific project location.
  • Expired CBAs: When a CBA expires without a new agreement, the existing rates typically remain in effect until a new CBA is ratified. But verify β€” some CBAs have built-in escalators.
  • Multiple crafts, same local: Some locals represent multiple crafts (e.g., laborers and cement masons). Each craft has different classifications and rates within the same local.

Step 4: Enter wage rates​

Wage rates are entered per classification within each local. This is the most data-intensive step.

Three rate paths​

Union rates (CBA)

  • Source: the CBA itself (usually a wage schedule appendix)
  • Structure: base wage + each fringe line item separately
  • Example: Journeyman Electrician, IBEW Local 11 β€” Base $48.50, H&W $12.50, Pension $9.75, Vacation $4.25, Training $1.00

Prevailing wage rates

  • Source: federal (SAM.gov wage determinations) or state (e.g., California DIR)
  • Structure: base wage + total fringe (may or may not be broken out by component)
  • Example: Electrician, Inside Wireman β€” Base $58.33, Fringe $31.75

Employee rates (non-union, non-PW)

  • Source: employer's internal pay structure
  • Structure: hourly rate only (benefits handled separately through HR/benefits systems)
  • Example: Electrician β€” $42.00/hr

Rate entry checklist​

For each classification, confirm:

  • Base wage amount
  • Each fringe line item amount (if union/PW)
  • Effective date and expiration date
  • Which fringe components are subject to OT premiums (check CBA language)
  • Apprentice period percentages (if applicable β€” e.g., 1st period at 50%, 2nd at 55%, etc.)
  • Foreman differential (typically 10–15% above journeyman base)

Step 5: Assign workers​

Each worker needs to be linked to their classification, union local (if applicable), and any special attributes.

Worker record fields​

FieldExampleNotes
NameJohn SmithAs it appears on payroll records
ClassificationJourneyman ElectricianMust match a rate entry
Union localIBEW Local 11Links to the local's rates
Apprentice periodβ€” (or "3rd period")Determines apprentice rate percentage
Hire date03/15/2024For seniority calculations
Default projectCourthouse RenovationCan work on multiple projects

Apprentice assignments​

Apprentices require additional configuration:

PeriodPercentage of journeymanHours required
1st period50%0–1,000 hrs
2nd period55%1,001–2,000 hrs
3rd period60%2,001–3,000 hrs
4th period65%3,001–4,000 hrs
5th period70%4,001–5,000 hrs
6th period75%5,001–6,000 hrs
7th period80%6,001–7,000 hrs
8th period85%7,001–8,000 hrs

Exact percentages and hour ranges vary by trade and local. On prevailing wage projects, apprentice rates are based on the PW journeyman rate, not the CBA journeyman rate (unless the CBA rate is higher).


Step 6: Configure projects​

Each project has its own compliance requirements that affect how payroll is calculated and reported.

Project configuration fields​

FieldExampleWhy it matters
Project nameCentral Library RenovationIdentification
StateCaliforniaDetermines which state OT rules apply
CountyLos AngelesAffects PW rate lookup (county-specific)
Project typePublic works β€” buildingDetermines PW rate schedule
Prevailing wage requiredYesTriggers PW rate validation
Federal PW (Davis-Bacon)YesRequires WH-347 filing
State PWYes (California DIR)Requires eCPR/A-1-131 filing
Wage determination #CA-2025-0042Links to the specific rate schedule
DIR project ID2025-123456California-specific registration
Time calculation modeST/OT/DT ActiveCan override company default
GC or subcontractorSubcontractorAffects CPR submission chain

Multi-project workers​

Workers frequently move between projects within a pay period. Each project may have different:

  • Time calculation modes (California project vs. Nevada project)
  • Rate sources (PW vs. private)
  • Reporting requirements (CPR vs. no CPR)

Track hours by project by day. A worker who spends Monday–Wednesday on a PW project and Thursday–Friday on a private project has two different rate structures and two different reporting obligations in the same week.


The payroll run lifecycle​

Once setup is complete, every pay period follows this cycle.

1
Open period
Define the pay period dates and confirm project assignments
2
Collect timesheets
Workers submit daily hours by project, task, and classification
3
Rate resolution
System determines which rate source governs: CBA, PW, or employee rate
4
Time calculation
Hours split into ST/OT/DT per the project's time calculation mode
5
Pay calculation
Base Γ— hours + OT premiums (base only) + fringe Γ— total hours
6
Review & approve
Supervisor reviews exceptions, approves timesheets, verifies rates
7
Lock period
Finalize β€” no further edits without an adjustment in the next period
8
Generate outputs
Paychecks, fringe remittances to trust funds, certified payroll reports

Rate resolution: which rate wins?​

When multiple rate sources apply to the same worker on the same project, rate resolution follows this priority:

  1. Component-by-component: Compare each component β€” base wage, H&W, pension, vacation, training, etc. β€” across all applicable rate sources (CBA, federal PW, state PW) and use the highest value for each. The resulting total may exceed every individual source total. See the rate comparison example for a worked demonstration.
  2. Document which source governs each component: The "winning" source will often differ by line item (e.g., CBA base + PW health & welfare).
  3. Employee rate floor: If a non-union worker's regular rate exceeds the PW base, the regular rate governs for base wage

The result is a "blended" rate that meets all applicable requirements. See Scenario 6 in the worked examples for a full dollar-amount walkthrough.

The three outputs​

Every locked pay period produces:

  1. Paychecks β€” issued to workers, reflecting base wage Γ— ST/OT/DT hours, minus taxes and authorized deductions
  2. Fringe remittances β€” sent to union trust fund administrators (monthly), itemized by H&W, pension, vacation, training, per worker per hour
  3. Certified payroll reports β€” filed with the contracting agency (weekly on most public works projects), listing every worker's hours, classification, rates, and gross pay by project

On prevailing wage projects, all three outputs must reconcile. The paycheck gross plus the fringe remittance total must equal the worker's total compensation at or above the prevailing wage determination.


Verification checklist​

Before running the first payroll, verify every configuration element. An error caught here costs minutes; the same error caught on a CPR audit costs thousands.

Time calculation​

  • Correct mode selected for each project's state (ST/OT/DT for California, Weekly Only for FLSA-only states)
  • Daily OT threshold set correctly (8 hours for California standard, 10 for 4Γ—10 AWS)
  • Weekly OT threshold confirmed at 40 hours
  • 7th consecutive day rule enabled for California projects
  • AWS elections documented and DLSE-reported (if applicable)

Union locals​

  • All applicable locals created with correct jurisdiction
  • CBA effective and expiration dates verified
  • Trust fund names, EINs, and remittance addresses entered
  • Multiple crafts within the same local set up as separate classifications

Wage rates​

  • Base wage matches CBA wage schedule or PW determination
  • Each fringe line item entered separately (not as a lump sum)
  • Fringe OT rules configured per CBA language (straight-time vs. premium)
  • Apprentice period percentages match the applicable apprenticeship standards
  • Foreman differential applied to correct classification
  • Rate effective dates match CBA/PW determination dates

Workers​

  • Each worker assigned to correct classification and local
  • Apprentice period verified against hours worked to date
  • Default project assignment set
  • Multi-project workers have hours tracked by project by day

Projects​

  • Prevailing wage flag set correctly (federal, state, or both)
  • Wage determination number linked and rate schedule verified
  • DIR project ID entered for California public works
  • State and county correct (affects PW rate lookup)
  • Time calculation mode overridden if different from company default
  • GC vs. subcontractor role set (affects CPR submission chain)

Test payroll​

  • Run a test pay period with known hours for 2–3 workers
  • Verify ST/OT/DT split matches manual calculation
  • Verify gross pay matches expected base Γ— hours + OT premium
  • Verify fringe amounts match expected rate Γ— total hours
  • Verify CPR output shows correct hours, rates, and gross by project
  • Verify fringe remittance report matches trust fund requirements
  • Compare test output against the worked examples scenarios

Was this page helpful?