Contractor audit prep
Use this when subcontractors, COIs, mixed duties, and owner/officer questions are part of the file.
Learn more →Class codes and documentation
Class codes and workers' comp audits: what documentation helps without claiming to decide the code
When class-code questions come up, clean documentation about duties and operations usually helps more than vague titles or last-minute descriptions.
Quick answer
This page is not about giving binding class-code advice. It is about documenting job duties, operations, crew roles, and supporting context clearly enough that the packet is easier to understand and discuss.
The practical goal is to replace vague labels with organized notes that explain what people actually do and where that support lives in the packet.
What documentation usually helps most
Useful support explains work being performed, not just the title on the payroll record.
| Support item | What it can clarify | Common weak spot |
|---|---|---|
| Role descriptions | What the employee or owner actually does | Titles are present but duties are not |
| Operations notes | What types of work the business performs | Descriptions are too broad or too generic |
| Crew or task notes | How responsibilities are split in practice | Mixed roles are left unexplained |
| Owner/officer notes | Whether owners also work in the field | Separate support is missing |
| Packet narrative | Where a question can be answered quickly | Support exists but is hard to find |
Common documentation mistakes around class-code questions
- Relying on job titles alone
- Waiting until a question is raised before documenting duties
- Treating mixed roles as if they are self-explanatory
- Scattering operations notes across email and internal docs
- Confusing documentation support with binding advisory advice
How to support role and duty questions more clearly
- Document the main operations the business performs.
- Write short duty notes for roles that are mixed or likely to raise questions.
- Separate owner/officer role support where needed.
- Keep those notes inside the packet workflow, not outside it.
- Use professional advice where needed for actual classification decisions.
Keep reading
Subcontractor COIs
Organize vendor proof, expiration dates, and follow-up before missing COIs become the whole story.
Learn more →Owner / officer payroll
Document owner pay, role notes, and supporting records more clearly before review starts.
Learn more →Audit checklist
Start here if you want the core record list before you build the full audit file.
Learn more →What auditors ask for
Review the requests that come up most often so you can gather records in a cleaner order.
Learn more →Audit documents
See the main record groups and the supporting files that usually answer follow-up questions.
Learn more →Frequently asked questions
Does this page tell me the correct class code?
No. It focuses on documentation support, not binding classification advice.
Why are duty notes useful?
Because they help explain real work being performed when a title alone is too vague.
Who benefits most from this workflow?
Contractors and mixed-role businesses where duties are likely to need explanation.
Important scope note
Practical prep guidance only.
This page is about documentation support only. It does not provide legal, tax, or binding classification advice.
Support the duties story with better records, not just better labels
The Construction Kit includes job-duty support and packet notes designed for contractor audit files that need clearer documentation.