What Records Do I Need for an AB5 Compliance Audit in 2026?

What Is an “AB5 Audit,” and What Does the Documentation Prove?

There is no single federal examination, certification, or universal checklist officially called an “AB5 audit.” AB5 is California Assembly Bill 5, principally associated with Assembly Bill 5’s restrictions on misclassified workers; the core provisions took effect on January 1, 2020, with later implementation dates for certain provisions. The term “AB5 audit documentation guide” can therefore describe an internal review, a California Labor Commissioner inquiry, a private due-diligence process, or a broader audit covering wage, hour, payroll, immigration, leave, and safety rules. An employer should define the audit’s jurisdiction and purpose before collecting records, because documentation suitable for a California classification review may not answer every federal requirement.

Also worth reading: How Can an HR AI Compliance Audit Reduce Regulatory Risk? · How Do HR Audit Software Tools Measure Labor-Law Compliance in 2026? · How Do Employers Build an HR AI Audit Checklist for Compliance in 2026?

A defensible file does more than show that someone wrote a worker classification memo. It establishes how the company decided which test applied, what facts it considered, who reviewed the decision, and whether the decision was supported by payroll records, contracts, emails, time entries, expense reports, invoices, and structured interviews. It should also preserve adverse evidence, such as a manager’s right-to-control instructions, rather than presenting only documents selected to support the employer’s preferred conclusion. That approach is not an admission of liability; it helps legal reviewers understand the actual arrangement.

The documentation should connect each legal classification to a verifiable fact. For example, a signed independent-contractor agreement proves little if the worker’s day-to-day conduct is inconsistent with it. Conversely, a timekeeping system, a client acknowledgment pattern, and documented rejection of control can help explain the relationship. Audit files should separate summaries from underlying evidence, identify confidential material, and state the date, author, purpose, and source of every generated record.

No document package guarantees compliance, and even a well-designed audit can miss conduct that was never recorded. Its value lies in making the classification decision traceable, testing it against the governing standard, and showing that the employer corrected inconsistencies instead of continuing them. As of September 24, 2026, any external guide claiming that one form, contract, or AI-generated report completes an AB5 audit should be treated as incomplete unless it also addresses the worker’s real working conditions and related labor obligations.

Which AB5 Rules and Exceptions Must the Audit Cover?

California Business and Professions Code section 2750.3, enacted through AB5, generally applies the “ABC test” to specified relationships for work performed in California on or after January 1, 2020. A business must satisfy all three elements: the worker must be free from the control and direction of the hirer; the worker must work outside the usual course of the hirer’s business; and the worker must be customarily engaged in an independently established trade of the same type as the work performed. Merely calling a person a contractor, signing a waiver, or issuing a 1099 does not satisfy that statutory test.

Coverage is not determined only by the number of workers currently visible on the payroll. Under the calculation used for section 2750.3, an enterprise must consider employees and contractors performing labor or services for the same client during a 90-day period in the prior 12 months, with a threshold of 25 for many relationships. Some sector-specific rules use the enterprise threshold, while others may apply only to the hiring party’s own workforce, so a headcount calculation must document which statutory rule is being used. Exclusions and grandfathering provisions may apply depending on industry, relationship, and date, meaning that a worker should not be swept into a routine AB5 review without checking exceptions.

The audit should also distinguish AB5 classification from federal employee status under the Fair Labor Standards Act and similar tests. California’s ABC test is not identical to the federal economic-realities or common-law test, and federal agencies enforce federal wage and hour rules independently. A worker can be misclassified under one framework but not another, while a compliant outside classification can still trigger minimum-wage, overtime, payroll-tax, or recordkeeping obligations. California law may also require expense reimbursement, notices, and other protections that are not resolved by the ABC test alone.

Documentation of the legal basis is therefore more reliable than a generic “AB5 check.” The file should identify the applicable provision, effective date, industry, worker location, relationship, exemptions considered, and factual assumptions. If the result depends on a narrow exception, the employer should preserve evidence supporting every element rather than relying on the exception’s label. Where California, federal, and local requirements differ, the stricter operational practice may be sensible, but it should not be mislabeled as the legal minimum.

What Documentation Package Creates a Defensible Audit File?

A strong audit file normally contains a governing index, legal-scope memo, classification analysis, evidence inventory, underlying records, approval history, and remediation record. The index should be specific enough for a reviewer to locate a timecard, amendment, or interview note without searching an employee’s personal devices or shared drives. Evidence should be preserved in its original form when possible, with a working copy used for review and an accurate record of any redaction. Metadata, access restrictions, and chain-of-custody notes matter when the audit is expected to be independently reproducible.

Classification evidence should cover the substance of the relationship rather than only formal paperwork. Useful categories may include hiring and onboarding materials, schedules, location rules, required training, performance reviews, access to internal systems, expense policies, tool provision, client communication, acceptance or rejection of work, ability to subcontract, marketing, and payment terms. Time records can show when work occurred, but they usually do not prove freedom from control by themselves. Interviews should be documented consistently, with dates, participants, questions, material answers, follow-up requests, and conflict disclosures.

The file also needs the records that explain how pay was administered. That may include payroll registers, wage calculations, regular-rate analysis, overtime records, bonus and commission records, deductions, reimbursements, timesheets, pay stubs, and records showing how employment-tax withholding was treated. Federal wage records commonly must be retained for at least 3 years, while supporting records such as agreements and job descriptions are commonly retained for at least 2 years under the Department of Labor’s general recordkeeping guidance. Tax records may need longer retention, including at least 6 years in certain circumstances, so the audit schedule should not use one period for every category.

Immigration, leave, safety, and collective-activity issues may belong in a separate workstream rather than inside the AB5 classification memo. Relevant materials could include Form I-9 documentation, payroll and contractor tax records, injury logs, safety training records, leave administration files, and preserved evidence of protected concerted activity. Mixing those subjects into one undifferentiated file can increase privacy risk and make legal review slower. A clean structure allows the reader to see both what the employer examined and what it intentionally placed outside the classification analysis.

How Should an Employer Conduct the Review and Correct Problems?

The first practical step is to define the population and the legal question. An employer should identify every worker relationship being tested, the applicable business entity, the worker’s work location, the relevant dates, and the industries in which the workers perform services. This step prevents a familiar worker from being treated as a representative sample when separate exemptions may apply to different groups. The population definition should be saved, dated, and approved, with later changes documented rather than silently replacing the original scope.

The second step is to collect consistent evidence across the selected population. A questionnaire can organize questions, but it should not become a substitute for observing operational reality or examining existing records. Reviewers should compare written policies with actual schedules, payment patterns, client instructions, and control exercised in practice. Material inconsistencies should be flagged for interview, legal review, or correction, and reviewers should avoid assuming that a person is independent merely because that person works from home or uses a personal computer.

The third step is to apply and document the correct legal test. The file should show each element considered, contrary facts, unresolved assumptions, and the decision maker’s rationale. Where the facts are close, the employer should obtain advice from California employment counsel or a qualified labor specialist rather than force a categorical answer into a template. An AI system may retrieve rules, organize evidence, or identify missing fields, but its output should be labeled as preliminary until a responsible human verifies current law, scope, and factual support.

The fourth step is remediation. If the review identifies misclassification, unpaid wages, overtime, expense-reimbursement issues, or inaccurate tax withholding, the response may include corrected pay, revised agreements, operational changes, tax corrections, notices, and updated training. Records of the correction should be separate from the original analysis while still linking to it, so a future reader can see what was found, what changed, and whether the change reached managers and payroll. As a general urgency rule, a potential problem affecting current pay, immigration documents, or workplace rights should be reviewed promptly even if a formal audit has not yet begun.

Manual Review, Outside Specialists, or AI-Assisted Documentation?

There is no single best AB5 audit method because the strongest method depends on workforce size, industries, document quality, legal exposure, and internal expertise. The comparison below concerns documentation approaches, not a promise that software or a consultant can determine legal status without human judgment. A small company with five similarly situated workers may handle a targeted review internally, while a multi-state platform with several contractor categories may need counsel-led testing across different jurisdictions.

These are planning ranges rather than quoted market rates. As of September 24, 2026, U.S. specialist and software prices vary widely, and California firms may charge more than smaller-market providers. An employer evaluating AI-assisted documentation should ask whether source documents are used to train shared models, whether access is role-based, whether audit logs exist, and whether human reviewers are available to verify outputs.

The best workflow is often staged: internal HR or operations prepares the population and records, software extracts and organizes evidence, and a qualified reviewer tests the legal conclusions. The employer should document which tasks were automated, which facts were independently checked, and which remain unresolved. Buying a larger platform does not remove the need to collect accurate time, pay, and management records, while hiring a lawyer does not help if management supplies incomplete facts.

Which Mistakes Most Often Weaken an AB5 Audit?

The most frequent error is testing paperwork instead of practice. Companies often collect independent-contractor agreements, invoices, and 1099 forms while overlooking emails assigning schedules, requiring daily attendance, or approving work in a way that suggests control. Another error is treating all contractors as one category when some perform work integral to the business and others provide a distinct specialty. The file must classify relationships by actual duties and client, not simply by the legal label chosen at onboarding.

A second mistake is using an outdated headcount or scope method. Businesses can cross the 25-relationship threshold only when certain conditions are met, and the calculation may look across related entities, a client, or a defined period. Contractors, staffing agencies, franchises, and labor services can also introduce separate legal questions. A spreadsheet should show the source, counting period, included workers, exclusions, and reviewer’s conclusion so that the threshold is reproducible.

A third mistake is relying on AI to pronounce a worker “independent” from sparse data. Automated systems may miss control embedded in scheduling, chase inconsistent language, or produce a confident answer without checking an exception. They may also expose sensitive worker data if uploaded to a service with inadequate retention controls. Every material AI-generated conclusion should be traced to an underlying record, checked by a named reviewer, and dated against the law and facts then available.

The final common mistake is correcting documents without correcting operations. A revised contract will not outweigh unchanged supervisory practices, and backdated notes can make a file less credible. Corrections should address pay, time capture, manager instructions, system access, expense practices, and communication with the affected parties. The audit should retain the old record where appropriate, document the reason for change, and show that the correction was implemented rather than merely recommended.

When Should an Employer Start or Escalate the Review?

Preparation is sensible before a formal complaint, audit notice, lawsuit, or immigration-related concern. An employer with active payroll, a growing contractor population, or inconsistent management practices should establish a documented review process before scaling the arrangement. Public agencies, large client contracts, financing reviews, and corporate acquisitions may request workforce classification information, and being able to respond accurately is better than reconstructing records under a short deadline. Routine preparation should not be confused with a conclusion that wrongdoing occurred.

The timeline should be tied to the fact pattern. A classification issue affecting ongoing compensation can require action within the current payroll cycle, while a documentation gap may warrant a preservation notice and staged review. If records are incomplete, preserve available data immediately and record what is missing rather than backfilling it after the fact. Counsel may need to assess deadlines that vary by claim, and agencies do not all use the same filing window.

Some issues deserve faster legal review. Examples include threatened mass-action activity, termination of workers after organizing or discussing wages and working conditions, a government investigation, collective-bargaining obligations, suspected wage theft, or a request to produce records under an unexpected legal process. National Labor Relations Act protection can arise from many employee activities, not only formal union organizing, and a supposed audit should not be designed to suppress protected discussion. Employers should also separate wage records from retaliation-related records and preserve them without assuming that one audit answers all claims.

For less urgent situations, a 30-day preparation sprint may be a useful internal benchmark, but it is not a statutory safe harbor. A larger review should have milestones for population definition, evidence collection, legal testing, worker-impact analysis, correction, and final approval. If the deadline is too short to follow that sequence, document the limits and involve qualified counsel. Acting too early without scope can produce unreliable conclusions, while waiting for months can deepen payroll exposure or erode evidence.

What Does an AB5 Compliance Audit Cost, and Where Does AI Help?

There is no government-mandated AB5 audit fee because AB5 is legislation, not a single licensed certification program. Internal costs are driven by staff time, data collection, and remediation, while external costs depend on the number of workers, jurisdictions, evidence volume, and whether the work is a screening exercise or a legal opinion. The ranges in the comparison table are budgeting aids only, and a request for proposals should state the exact service, deliverable, number of records, and expected response date.

Compliance platforms may price by employee, contractor, module, workflow, or enterprise subscription. Planning estimates range from about $200 to several thousand dollars per month, with implementation, data migration, legal review, and training potentially increasing the first-year total. AI can reduce manual work by extracting dates and terms from agreements, grouping similar relationships, comparing job descriptions with actual schedules, and flagging workers with missing payroll or time records. Those tasks are useful because they improve consistency and traceability, not because the model can safely deliver a final legal judgment.

The largest cost may be correcting past conduct rather than generating a report. Retroactive overtime, inaccurate payroll-tax treatment, reimbursements, penalties, back pay, or operational restructuring can exceed subscription fees by a wide margin. An audit budget should therefore reserve funds for remediation and independent review, rather than treating the final memo as the project’s endpoint. Employers should also budget for records preservation, access controls, worker privacy, and periodic testing after management rules change.

AI-powered labor compliance tools are most credible when their outputs are explainable, versioned, and reviewable. The employer should ask for examples of audit logs, source linking, model and rule updates, administrator permissions, encryption, data-location terms, deletion procedures, and documentation of human review. Outputs should be treated like an attorney work-product draft, not a sealed determination, and a responsible person should approve the final conclusion. The strongest business case is faster evidence organization and earlier detection of inconsistencies; the weakest claim is that software can eliminate legal judgment or make an unsafe classification safe.