An audit can start from an ordinary benefits claim

A common starting point is a former contractor who files for unemployment benefits. The state must decide whether wages should have been reported for that person. That benefits decision can expose a classification question even if the company has never been audited before. The employer may receive a questionnaire asking how the work was performed, who supplied tools, how payment was calculated, and whether the person could work for others. The important point is procedural: a claim by one worker can create a factual inquiry that reaches beyond one invoice.

Other triggers are more administrative. A state can compare payroll reports with information returns, review an industry with persistent classification problems, or encounter inconsistent records during a routine unemployment-tax examination. California EDD, Texas Workforce Commission, and New York DOL all publish their own worker-status material, which is a reminder that the letter on your desk belongs to a specific state system. The employer should read the agency name, tax program, period, and response date before importing a federal checklist from somewhere else.

The first question is scope, not outcome

Before debating whether anyone is an employee, determine exactly what the agency is asking about. Some notices name one individual. Others request a list of all people paid outside payroll for several quarters. A narrow benefits inquiry and a multi-year tax audit require different document plans. Create a scope sheet with the covered dates, entity name, account number, named workers, requested records, assigned examiner, and every deadline shown on the notice. That sheet becomes the control page for the response file.

Do not assume the audit period equals the entire history of the relationship. If a designer worked as a project-based outside business in 2024 but shifted into a fixed internal schedule in 2025, the facts may not be constant across the requested quarters. Build the chronology first. It is much easier to explain a changing relationship when contracts, invoices, calendars, equipment records, and manager instructions have been organized by period instead of mixed into one undated folder.

Worker complaints are evidence, not the whole test

A worker may describe the relationship in terms that favor employee status, while the business may describe the same arrangement as independent. Neither label is self-proving. State agencies look to their governing test and the underlying facts. That means an employer response should not attack the worker for filing a claim or rely on a sentence such as ‘they agreed to be a 1099.’ A calmer response explains what services were provided, how assignments were accepted, what control existed, who bore expenses, and what records support those statements.

The same discipline matters when the company believes the worker is mistaken. A hostile email can become part of the record without proving anything about classification. Keep benefits eligibility, performance disputes, and classification analysis in separate lanes. If the notice asks whether the person could reject work, answer that question with facts and representative documents. Avoid padding the submission with unrelated grievances that make the file harder for an examiner to follow.

Industry structure changes what a classification audit needs to examine

The work model matters because the same status test can require very different evidence in construction, delivery, home care, professional services, or a creative agency. California EDD’s published employment-tax audit process says an auditor may review whether individuals paid for services were properly classified and may examine invoices, billings, corporate minutes, or written agreements when worker-classification issues arise. The useful preparation is therefore role-specific, not a generic “contractor folder.”

For a field-based subcontracting model, records about crews, vehicles, tools, bids, job sequencing, and responsibility for rework may matter. For a remote professional, the stronger evidence may be pricing, outside clients, task instructions, software access, and approval practices. Build the evidence around how the service actually operates rather than assuming one contractor agreement proves the same thing in every industry.

A data mismatch can be enough to open the door

Unemployment systems are built around wage reporting. If agency data suggests that services were performed but no covered wages were reported, the agency may ask the employer to explain why. A business that has dozens of 1099 recipients but only one payroll employee can therefore face questions even without a complaint. The useful response is not to infer that the agency has already decided the issue. Reconcile the payment ledger, identify which payees were vendors versus individual service providers, and separate non-labor payments from payments for personal services.

Accounts payable coding often needs cleanup at this stage. A line labeled ‘contract labor’ may combine a marketing agency, a plumber, a freelance designer, and a temporary person working under a manager. Those are not one classification population. Build a payee inventory with role, entity type, service period, gross payments, primary contact, and relationship owner inside the company. That inventory lets the reviewer see which arrangements share facts and which require separate treatment.

Do not silently substitute the IRS common-law framework

The IRS three-category common-law framework is useful for federal employment-tax questions, but a state unemployment program can use a different statute or test. California EDD explains the ABC test and exceptions for its purposes; Texas publishes a direction-and-control test with multiple factors; New York unemployment guidance focuses on supervision, direction, and control. These frameworks overlap in real-world facts but are not interchangeable. A memo should identify the state rule actually being applied before reaching a conclusion.

This distinction prevents a subtle but serious drafting error: writing ‘the IRS says contractor, therefore the state audit should close.’ An IRS analysis may belong in the background file, yet the state examiner is responsible for state coverage. Label each worksheet by legal purpose. If counsel or a payroll professional gives advice, keep a note of which jurisdiction and program the advice addressed so future staff do not reuse it as a universal determination.

A clean response file is built before the interview

Once scope and law are clear, prepare a response index. Put the notice first, then a timeline, worker or role summaries, contracts, invoices, proof of outside business activity where relevant, equipment and expense records, schedules, communication samples, and payroll or 1099 records. Use representative examples rather than cherry-picked screenshots. If a document cuts against the company’s position, do not conceal it; note the fact and explain the period or context accurately.

Finally, designate one internal contact. Examiners receive conflicting answers when founders, bookkeepers, supervisors, and outside accountants reply independently. A single coordinator can collect questions, route them to the person who actually knows the facts, and preserve what was sent. That also makes later appeal or correction work easier because the company has a contemporaneous record of the audit instead of reconstructing it months afterward.

WORKED EXAMPLE

Example: one unemployment claim expands into a role review

A small home-services company receives a benefits questionnaire about a technician it paid on Form 1099-NEC. While gathering invoices, the bookkeeper finds six other technicians working under the same dispatch system. The notice names only one person, but the examiner later requests payment records for the entire technician group.

The company does not respond by sending six identical contractor agreements. It builds a quarter-by-quarter roster, identifies which technicians supplied their own vehicles and tools, preserves dispatch instructions, and marks two people whose arrangements changed during the year. That factual map gives the company a usable audit file whether the agency ultimately confirms or changes the classifications.