Assess Compliance Timeline For New State Wage Theft Prevention Act

---
name: wage-theft-prevention-act-compliance-timeline
task_id: corporate-governance/assess-compliance-timeline-for-new-state-wage-theft-prevention-act
description: Board-ready compliance timeline memorandum for a newly enacted state wage theft prevention statute, analyzing worker classification risks, wage notice and pay stub obligations, multilingual posting requirements, and third-party staffing liability
activates_for: [planner, solver, checker]
---

# Skill: State Wage Theft Prevention Act Compliance Timeline

## 1. Subject-matter triage
- Treat the assignment as a board-facing compliance timetable, not a litigation memo: the core output is the sequence of obligations, risk inflection points, and remediation priorities.
- Inventory all relevant source categories first: statute text, internal audit, workforce records, pay practices, postings, contracts, staffing arrangements, and any implementation guidance.
- If the materials involve multiple facilities, worker groups, languages, or staffing channels, separate them before analysis; do not generalize from one location or workforce subset to the entire enterprise.
- If the source set is missing a required document category, note the gap and bound the conclusion accordingly.

## 2. Failure modes the skill is correcting
- Treating worker classification as a binary pass/fail without analyzing each prong of the applicable multi-factor test independently.
- Collapsing wage notice, pay stub, and posting obligations into one compliance question instead of testing each obligation against its own statutory content and timing requirements.
- Ignoring the strategic importance of any statutory cure window or phased effective date, which can change the compliance timeline and penalty posture.
- Failing to organize exposure by violation type and by affected worker group, which obscures executive-level risk.
- Overlooking joint, vicarious, or contractual exposure arising from third-party staffing or payroll arrangements.
- Leaving timeline analysis abstract by omitting deadline anchors, responsible owners, and sequencing dependencies.
- Stating conclusions without tying them to the controlling statute, regulation, or other authority that supports the rule.
- Repeating internal-document language verbatim when a paraphrase will do, which can create leakage and reduce usability.

## 3. Legal frameworks / domain conventions that apply
- Worker classification: apply the governing state test for independent contractor status, typically an ABC-style or equivalent multi-factor framework, and analyze each prong separately; failure of any required prong defeats classification under that statute.
- Wage notice requirements: identify the statute’s required notice content, delivery timing, update obligations, and retention expectations for newly hired workers and for changes in terms.
- Pay stub requirements: test each wage statement against the statute’s required elements, including identifying information, pay period data, itemization, deductions, and any required rate disclosures.
- Posting obligations: determine whether workplace notice requirements apply, including any language-based posting triggers tied to workforce composition or location.
- Cure or safe-harbor provisions: if the statute offers a cure period, identify the trigger, the deadline, the consequences of curing, and what remains exposed after cure.
- Penalty structure: separate civil penalties, statutory damages, repeat-offender consequences, and any willfulness enhancement; organize them by violation type and accumulation rule.
- Third-party staffing liability: review agency, payroll, or PEO arrangements for representations, cooperation duties, audit rights, notice flows, and indemnity; assess whether the company still bears statutory exposure notwithstanding outsourcing.
- Reclassification consequences: if contractor status is not sustainable, assess operational consequences of conversion or termination, including any WARN-style notice issues if applicable under the governing law.
- Authority discipline: every rule cited in the memorandum should be tied to the statute, regulation, or recognized authority that supplies it; avoid bare conclusion statements.

## 4. Analytical scaffolds
- Begin with a phased timeline: effective date, grace or cure period, first compliance date, ongoing recurring obligations, and escalation points after noncompliance.
- For each worker category or location, run the same sequence: classify the role, test notice compliance, test pay stub compliance, test posting compliance, and test any staffing overlay.
- For each issue, state:
  1. the governing rule and authority,
  2. the specific source fact or document that implicates it,
  3. the timing or scale of exposure,
  4. the cross-document interaction that changes the risk,
  5. the operational or regulatory consequence.
- When source documents include internal audit findings, compare them against current practices and identify whether the same issue persists, has narrowed, or has worsened.
- When contractor reclassification is in play, separate legal status analysis from cost analysis; do not assume the internal cost model captured overtime, benefits, taxes, or notice obligations.
- When multiple sites or language groups are present, enumerate them before analysis and assess each site or group independently; if only one site or group exists, say so expressly.
- If a cure period exists and full remediation is not feasible before it expires, prioritize the highest-exposure items first and state what can still be cured later.
- If termination of contractor relationships is a contemplated response, test whether a mass separation or conversion plan implicates federal or state notice requirements before recommending action.
- For third-party staffing, compare contract language, actual practice, and statutory allocation of responsibility; contract allocation alone does not eliminate statutory exposure.

## 5. Vertical / structural / temporal relationships
- The compliance timeline should move from identification to remediation to verification to ongoing monitoring; do not present obligations in a flat list divorced from sequencing.
- A cure period, if available, is a temporal fork: during the window, the memorandum should distinguish curable deficiencies from residual exposure after the deadline passes.
- Staffing-agency compliance and worker classification interact: the same individuals may present direct, joint, or contractual exposure depending on the operating model and agreement structure.
- Internal audit findings can aggravate risk if the company knew of the issue and did not remediate promptly; note whether the audit predates the new statute or overlaps with the effective period.
- Reclassification, payroll changes, and posting updates may have different implementation dates; do not assume one remediation step fixes all others at once.
- If the statute phases in obligations, map each phase separately so the board can see what must be done immediately versus what recurs or becomes mandatory later.

## 6. Output structure conventions
- Use a board-ready memorandum format with a short executive summary, followed by a phased compliance timeline, risk analysis, and action plan.
- Include a legend that defines severity levels once and apply the same ordinal labels consistently across issues or timeline items.
- For each material issue, give the governing authority, the affected workforce or process, the deadline or trigger, the risk severity, and the downstream consequence.
- Organize the timeline by phase or deadline rather than by source document alone, so the board can see sequence and dependency.
- Include a remediation matrix that pairs each action with an owner, implementation deadline, and dependency on other steps.
- Include a section addressing cure-window strategy, if any, and a separate section for staffing or outsourcing exposure where applicable.
- End with a concise Recommended Actions block using imperative verbs, named responsible roles, and timing anchors tied to the statute or implementation milestone.
- If the deliverable is meant to become a .docx memorandum, draft in clean prose with headings that can be pasted directly into a board packet.