Adjudication Reference (Admin)

HR Policies

Admin-side reference for running the [Workmanship & Redo Policy](/workmanship-redo), [Refusal Ladder](/refusal-ladder), and [Sentencing Guidelines](/sentencing-guidelines). Like every page in this handbook, it is published openly on purpose — "nothing here is secret" is the standing rule of the [Employee Credits & Accountability System](/points-accountability), and a crew that can read the adjudication procedure is a crew that can hold it to its own rules. This page is written policy and blueprint; the operational tooling (payout state machine, redo records, refusal counters, precedent register) will run inside the future CRM on the data model already defined for it. All windows, counts, and point values on those pages are generated from the configurable parameter set below — change the parameter and the handbook text regenerates, so documents never drift from the system. Parameter changes are prospective only and require written notice before taking effect (Minn. Stat. § 181.032(d) for anything touching pay).

Configurable Parameters (Current Defaults)

One source of truth. The crew-facing pages quote these values verbatim.

Parameter Registry

ParameterDefaultUsed by
Callback window48 hoursPayout release
Standard redo deadline24 hours / next route dayRedo policy
Priority same-day cutoff1:00 PMRedo policy
Open-redo claim window24 hoursRefusal ladder
Refusal rolling window90 daysRefusal ladder
Refusal debits15Refusal ladder
Owner-completed redo debits20Refusal ladder
Demotion at refusal #2Refusal ladder
Claiming suspension at refusal #3 (14 days)Refusal ladder
Separation at refusal #4Refusal ladder
Emergency deferrals / window1Refusal ladder
Class A debit range15–20Sentencing
Class B debit range4–8Sentencing
Class C debit range1–3Sentencing
Self-report mitigation−3 debitsSentencing
Repeat-offense window90 daysSentencing
Written decision deadline5 business daysProcedure
System-fix amendment deadline14 daysProcedure

Payout State Machine

Every site payout carries a state; only verification events move it.

Payout States & Transitions

FromEventTo
—Crew clocks out of completed sitePending
PendingPhotos pass review AND callback window (48h) closes cleanReleased
PendingRedo triggered (failed photos / inspection / verified complaint)Pending (redo attached)
Pending (redo)Original crew completes redo to standardReleased ($0 redo lines)
Pending (redo)Refusal recordedForfeited → site posted as open redo
ForfeitedAnother crew claims & completes within 24hReassigned (claimer paid original site rate)
ForfeitedNo claim / priority site — owner completesClosed (owner-completed, max-severity event logged)

Adjudication Procedure (Every Incident)

1. Intake: record facts, link evidence (photos, GPS, portal complaint, checklists) to an incident record. 2. Culpability tests per person, business layer first: System test → charge the business for any documentation gap and open a system-fix task (14-day deadline). Substitution test → training/system remedy if a competent peer would plausibly have done the same. Concealment test → concealed raises class by one; self-report applies the standing −3 mitigator. 3. Class & precedent: assign class by closest analogy; search the register for the nearest prior case; deviations from matched precedent require a written reason. 4. Sentence: apply the class range, aggravators, mitigators; deliver individually within 5 business days; post findings-of-record where appropriate. 5. Log: write the incident to the precedent register with charges by layer, test outcomes, and reasoning. It is now case law.

Legal guardrails — never skip
  • Redo time is always clocked and counts toward minimum-wage true-up and blended overtime. 'Unpaid redo' means $0 payout lines, never off-the-clock work.
  • Never claw back or deduct released wages for workmanship (Minn. Stat. § 181.79). Forfeiture applies only to payouts still in pending.
  • Discipline parameters that touch pay require written notice before taking effect (Minn. Stat. § 181.032(d)).
  • Have an attorney confirm the forfeiture/reassignment flow before go-live. (Flagged, not confirmed.)