Crew Pay

V2 now has its own Settings > Crew pay, closing the crew-pay half of V1 parity. Open Settings > Crew pay to schedule policy versions, set crew splits, and set each team member's pay mode. Read access needs View financial reports; saving anything (a policy version, a crew split, or a member's pay mode) needs Manage team, and saving a policy version additionally needs all-location access, since a policy is an org-wide setting.

The Crew Pay report itself lives on Business > Reports, inside the same Operations card as Crew productivity and Overdue invoices — see Operations Reporting for its exact columns and totals.

Final calculation requires verified source data

When the active policy excludes tax or matching line items, final Crew Pay needs a canonical accepted proposal option and its snapshot, with the option total, snapshot total, and job total matching. Tax exclusions require verified tax details; keyword exclusions require itemized details. Applicable subcontractor payouts come from the ledger. Missing required inputs block the calculation with job-specific requirements. A blocked period withholds totals and export rows rather than treating missing facts as zero.

The current calculation supports itemized residential, generic/authored, Holiday Lights quote-item, and commercial zone-line snapshots. Manually created jobs without an accepted itemized option, unsupported snapshots, and legacy aggregate-only custom-item totals remain blocked when the active exclusions need those missing inputs. Some per-visit plan jobs whose totals do not match the accepted full-term option, and renewal jobs without verified option lineage, also stay blocked under those exclusions pending a verified mapping. Policies that do not require the missing inputs can still calculate pay. The current workflow has no manual controls for entering missing tax or line items. Approved timecards continue to subtract breaks; Crew Pay keeps its existing job-hours basis.

What is not shipped yet: V1's job-level compensation override screen, the route-day hourly-only toggle, explicit callback-linked-to-original-job forfeiture, and the dashboard's tip visibility are still V1-only. Those sections below stay marked (V1). The focused V2 field app has its own supported Workforce, Time, and Crew Pay experience, documented in Workforce, Time, and Crew Pay.

In V1, Crew Pay uses versioned policies instead of hardcoded percentages. That means an office can change pool percentages, daily caps, overtime rules, solo rates, and pay periods without rewriting old payroll history. V2 ports this directly: each save creates a new dated policy version, and closed pay periods and older jobs keep whatever policy was active when their pay was computed.

In V1 web, open:

• Settings > Crew Pay to schedule a new policy version
• Team > Crew Pay to review modeled payouts and edit crew split defaults
• Jobs > Job Detail to override compensation for one job (V1 only)
• Schedule > Day Route View to mark a truck day as hourly-only (V1 only)

What Is Editable

Each crew pay policy version stores the same fields V1 did, grouped into Commission, Payroll, Minimum wage, and Exclusions sections on the V2 form:

• Standard pool percentage
• Elite pool percentage
• Solo rate
• Callback threshold percentage
• Daily revenue cap
• Leader max share
• Pay period cadence (weekly or biweekly)
• Pay period start day
• Overtime threshold hours
• Overtime multiplier
• Default minimum wage, plus a per-state minimum-wage overrides box
• Callback source label and callback rate period (monthly or per pay period)
• Commission exclusion keywords (separate equipment/rental and

subcontractor keyword lists), and checkboxes to exclude tax and subcontractor payouts from commissionable revenue

When you save a new version, CE Pro applies it prospectively from the effective date forward. A Policy History panel beside the form shows every saved version, which one is active, and its pool/solo/leader/overtime settings at a glance.

How Payouts Work

V1 crew payouts are built in layers:

1. CE Pro finds the policy version that matches the job's service date, unless the job has a saved policy override.
2. CE Pro calculates commissionable revenue by removing:

• Sales tax
• Equipment and rental line items
• Lift and access-equipment line items
• Subcontractor scope
• Subcontractor payouts

1. CE Pro applies the crew's split template and any job-level participant overrides.
2. If the truck day or job is marked hourly-only, hourly pay is used instead of the commission pool.
3. Daily revenue caps are applied at the crew/day level before the commission pool is split, and linked callback-origin jobs do not consume cap room for the rest of that crew-day.
4. Commission participants earn a minimum-wage base plus a top-up only when their earned commission falls short of that floor.
5. Hourly-only participants earn hourly pay with overtime based on the active policy, and overtime thresholds only count hourly-only hours.

Unused split shares are not redistributed. If a split slot is assigned to an hourly-only or salary-like participant, that portion stays with the company.

V2 adds one thing V1 never had: an actual pay-period-close lock. Closing a period recomputes eligible, still-open job rows from verified source data before applying the lock. Already locked rows retain their frozen participant-level history, so reopening a policy or split later cannot silently change pay that was previously closed. Missing required tax or item inputs blocks a new calculation or close; incomplete results are not frozen.

Crew Defaults

In V1, each crew can store a default split template. This is the normal starting point for that crew's jobs. V2 ships the same idea on the Settings > Crew pay page's Crew split panel.

Use Settings > Crew pay (V1: Team > Crew Pay) to:

• Pick a crew from the dropdown
• Set or change the crew leader (one radio button per crew, labeled Crew lead)
• Adjust each member's Share %
• Select Save crew split

Example:

• Crew Lead: 57%
• Technician: 43%

You can change those percentages any time. CE Pro validates that:

• The total split equals 100% (the form shows a running total and blocks saving otherwise)
• The leader share does not exceed the policy's leader max share

Team Member Defaults

V1 team records store default compensation behavior for each person:

• Commission eligible by default
• Hourly default with that person's hourly rate

V2's Team member pay defaults table on the same Settings > Crew pay page covers the same ground with the owner's chosen vocabulary: each member has a Pay basis of Performance or Hourly (V1 called these same two modes "Commission eligible" and "Hourly default" in its own docs) and an Hourly rate ($/hr) field, saved per member with its own Save button.

These are defaults only. Actual payout can still change because of:

• Crew split templates
• Job-level compensation overrides (V1 only — see below)
• Route-day hourly-only settings (V1 only — see below)

This is useful for weekend crews, overnight crews, and salary-like field support people who should always stay hourly in CE Pro.

Job-Level Overrides (V1)

V2's crew-pay service can already store a per-job policy pin and a per-job participant list, and it computes and persists each job's pay automatically from the active policy, crew split, and member settings. What is still missing is the office-facing screen: there is no Job Detail control yet to open a job and hand-edit its compensation the way V1 does below.

In V1, open any job and use the Crew compensation section to:

• Pick the policy version used on that job
• Mark the job as hourly-only
• Mark the job as callback / rework
• Link a callback to the original job
• Override the participant list
• Override each participant's pay mode
• Override hourly rates
• Override split percentages for that job only

Use this when:

• A weekend crew should stay hourly
• A manager works the route but should not receive commission
• A helper should keep their commission share while the lead stays hourly
• One job needs a different split than the crew default

Route-Day Hourly Override (V1)

In V1 Schedule > Day Route View, each truck day can be marked Hourly only.

This is the fastest way to handle:

• Overnight crews
• Weekend crews
• Training days
• Salary support days
• Non-standard work that should not use commission

When a route day is hourly-only, commission previews are hidden for that truck/day and job overrides can still refine the participant mix if needed.

Callbacks And Elite Rate

The policy-level pieces of this are in V2 today: the Callback threshold % and Callback rate period fields on the policy form, the Callback source label (V1's default is touch up), and the Crew Pay report's own Callbacks column all exist. Elite rate eligibility is calculated per crew using the policy's configured elite pool percentage and callback threshold.

In V1, callback and rework jobs use explicit payroll flags rather than being inferred from notes.

When a job is marked as callback / rework:

• It can use the configured callback source label, such as touch up
• It counts toward callback rate tracking
• It can be linked to an original job (V1 only)
• The original job's commission pool can be forfeited when linked (V1 only)

The explicit callback/rework flag on a job, linking it to an original job, and forfeiting that original job's pool are not confirmed in the current crew-pay release — there is no job-detail screen yet to set them (see Job-Level Overrides above).

Crew Pay Dashboard

V2's Crew Pay report replaces this dashboard; see Operations Reporting for its exact columns. It does not carry over every V1 dashboard row: there is no per-crew retained split share, base wage, or commission top-up breakout on the report card (only period-wide totals for those), and there is no tip visibility at all on the new report.

The V1 web Crew Pay dashboard for reference showed:

• Active policy version
• Commissionable revenue after exclusions and caps
• Total crew pay
• Retained split share
• Base wage totals
• Commission top-up totals
• Hourly totals
• Crew tip totals with cash, check, and card method visibility
• Recent jobs with the applied policy version

This gave payroll and ops a cleaner read on what changed and why.

Crew Tips (V1)

Tip collection itself (card, cash, and check) is current V2 functionality covered elsewhere; only the V1 Crew Pay dashboard's tip visibility described here — cash/check/card totals broken out per crew alongside base, top-up, and hourly pay — remains unported to the new Crew Pay report.

Customer tips are tracked separately from crew pay. They do not change the commission pool or the hourly / commission payout math.

The V1 web workflow supports tips in three places:

• The hosted invoice payment page
• Mobile payment collection when the crew collects payment in the field
• Manual cash or check payment logging in the payment collection flow

Tip suggestions are always calculated from the taxable amount using:

• 10%
• 15%
• 20%
• Custom amount
• No tip

When a tip is collected:

• Card tips are added during checkout before Stripe payment submission
• Cash and check tips can be recorded alongside the collected payment
• The Crew Pay dashboard shows total tips for the selected period
• Tip totals are broken out by payment method so payroll and ops can see where the money came from
• Individual crew member rows show allocated tip visibility alongside base, top-up, and hourly pay

Operating tips:

• Start with a policy version that mirrors your current agreement, then schedule future versions as you learn from production.
• Use crew split templates for the normal case; job-level overrides remain a V1-only exception path until V2 ships that screen.
• Mark overnight and weekend routes hourly-only at the route-day level first (V1 only today — in V2, set the affected members' pay basis to Hourly instead).
• Keep state minimum wage overrides current if crews cross state lines.
• Review retained share totals regularly so managers understand when hourly-only participants occupied commission slots.