August 2 Is the EU AI Act Deadline. A Six-Van HVAC Shop Is Out of Scope — the Tech-Hiring Screener Is Not.

Does the EU AI Act apply to a heating and air company in Tulsa that has never shipped a condenser past the Arkansas line? No. Say it out loud, then keep reading, because it is half the answer.

Between January 1 and August 2 of this year, four separate AI laws came into force in places where you actually do business. Three of them are not about you. One of them is, and it does not land where owners expect. It lands on the resume ranker you switched on in May when you could not find a service tech with an EPA 608 Universal card, and on the voice that picks up your phone at 9:40 on a Saturday night in July.

Three of the four laws are not about a contracting business

Start by throwing things out, because the shortest compliance file is the one where most of the work is proving something does not apply.

California SB 53 took effect January 1. It is aimed at the handful of companies that build very large AI models — the ones with hundreds of millions in revenue and rooms full of graphics processors. If you install ductless mini-splits in Fresno, it does not reach you. Texas TRAIGA also took effect January 1, and it is built around intent: it goes after AI used deliberately to discriminate, deceive or manipulate. A shop using a scheduling tool to fill Tuesday's board is not the target, and the Texas attorney general has to give notice and a window to fix a problem before filing. The EU AI Act carries its August 2 compliance date for high-risk and transparency duties, and it does reach American companies — but only when the results of the system are used by people in Europe. A residential changeout in Broken Arrow is not that.

There is one real exception worth knowing. If your controls division watches building alarms for a European-owned client's sites overseas, or if you license your own scheduling or load-calculation tool to contractors in Germany or Ireland, you are inside the EU rules and you need an actual attorney, not a blog post. That is rare. For most contractors, the honest line is: for an HVAC contractor, 2026 AI compliance is not about the software you build — it is about keeping a record of the automated decisions you already let run on hiring and on customer calls.

The one that bites: hiring, in Illinois, Colorado and New York

Post a service tech opening in June and you get 40 to 180 applications in four days, most of them from people who have never brazed a line set. Every applicant tracking tool sold to contractors now ranks them for you. That ranking is an automated decision about employment, and employment is exactly where the state laws bite.

Illinois amended its Human Rights Act effective January 1 of this year to cover AI used in employment decisions, and it already had a law requiring consent before AI reviews a recorded video interview. New York City has required an annual bias audit and ten business days' notice to candidates since 2023 — if you have a branch in Queens, that is you. Colorado's statute is the broad one, aimed at what it calls consequential decisions, and hiring is first on that list. None of these ban the tool. They require you to know it is running, tell people it is running, and be able to show your work.

What that means in practice for a six-van shop: get a letter from your hiring vendor stating whether ranking is automated and whether they have run a bias audit, turn off any setting that auto-rejects without a human looking, and keep the applicant list — name, rank, outcome — for a year. You already keep applications a year for federal recordkeeping. Add one column.

The ten-minute triage every new tool goes through

You do not need a policy binder. You need one repeatable decision that your office manager can run whenever somebody in the shop turns on something new, including the free thing a comfort advisor found on his own.

flowchart TD
  A["New AI tool switched on in the shop"] --> B{"Does it help decide who gets hired?"}
  B -->|Yes| C["Vendor letter + applicant log kept 12 months"]
  B -->|No| D{"Does it talk to a customer with no person on the line?"}
  D -->|Yes| E["Disclose it is an assistant + keep the call record"]
  D -->|No| F["One line on the shop AI inventory"]
  C --> G["Office manager reviews the list each quarter"]
  E --> G
  F --> G

Three outcomes, one list, one review. The inventory itself is a spreadsheet with five columns: tool name, who turned it on, what it touches, does a customer or applicant hear it, date reviewed.

What the Saturday-night booking agent has to say out loud

The no-cool calls that come in between 6 p.m. Friday and 8 a.m. Monday are where an answering agent earns its keep, and they are also the second place the law shows up. Three rules cover it.

First, truthfulness. Utah's approach is the simplest to satisfy: if a caller asks whether they are talking to a person, the answer has to be immediate and honest. Build that into the agent's opening line anyway — customers who find out later feel tricked, and a tricked customer does not sign a maintenance agreement. Second, recording. If you record calls and you work in California, Illinois, Pennsylvania, Washington, Massachusetts or Maryland, you already needed consent from everyone on the line, and that has nothing to do with AI. The agent must announce recording exactly the way your old phone system did. Third, what the agent is allowed to say. It can quote your published diagnostic fee, confirm a two-hour arrival window and take a model and serial number. It must not state that a compressor is covered under warranty, promise a same-day arrival during a heat event, or quote a flat-rate repair price it cannot back up. Those are consumer-protection problems in every state, AI or no AI.

The file itself: eight pages, one afternoon

When somebody — a state attorney general's office, a plaintiff's lawyer, a national accounts client doing vendor review — asks what AI you use, this should already sit in a folder on the shared drive:

• The one-page tool inventory described above.
• The vendor letter from your hiring platform about automated ranking and bias auditing.
• Your applicant log for the last twelve months, with outcomes.
• The exact opening script your phone agent uses, with the disclosure and recording notice in it, dated.
• A sample of ten call transcripts attached to their jobs in ServiceTitan, FieldEdge or Housecall Pro — whatever you run.
• A half-page note saying who reviews this and how often, signed by you.

That is the whole thing. Nobody is asking a mechanical contractor for a model card or an impact assessment. They are asking whether you know what is running in your own business.

What this costs a six-van shop

Assume an office manager loaded at $34 an hour, four hours to build the file the first time and one hour each quarter to refresh it, plus ninety minutes of an employment attorney's time at $350 to read the hiring piece once. Illustration only — your rates will differ.

Compare that to the retainer on a single discrimination charge, which is a five-figure conversation before anyone argues the facts. This is the cheapest insurance in your office.

Where a checklist stops and a lawyer starts

Three situations need a real employment or regulatory attorney, not a spreadsheet. If you hire across state lines — a Colorado branch and an Illinois branch under one company — the strictest rule usually wins, and figuring out which one is strictest is legal work. If you are a franchise and your franchisor supplies the hiring tool or the phone agent, you need to know in writing who is responsible for what. And if any part of your work touches Europe, stop reading and call counsel before August 2.

Also worth saying plainly: federal preemption of these state rules is still unsettled as of this summer. Do not let a vendor tell you a coming federal law makes the state requirements moot. Until that actually happens, Illinois law binds you in Illinois.

Frequently asked questions

My hiring is all word of mouth and my nephew screens resumes. Do I have anything to do?

Almost nothing. Write one page saying you use no automated ranking in hiring, date it, and keep it. The whole point of the file is being able to answer the question quickly, and "we do not use it" is a perfectly good answer if it is true and written down.

Does the AI answering our phones have to tell every caller it is not a person?

It has to answer honestly when asked, and in some states you need clear disclosure up front. Practically, put it in the greeting everywhere. A caller with no heat at 11 p.m. does not care who takes the address, but they care very much if they find out later they were misled about it.

Our dispatch software started suggesting repair-or-replace recommendations. Is that regulated?

Not by these AI statutes. Recommending a changeout is not a decision about employment, credit or housing. It can still be a consumer-protection problem if the recommendation is dressed up as a technical finding nobody verified, so keep the static pressure readings and amp draws behind it.

Do I need to keep call recordings forever now?

No. Match whatever your existing retention practice is — most shops keep one to two years alongside job records. What matters is that the recording attached to the job matches what the customer was told and what the tech found.

One last practical note. Most of what these rules ask for on the phone side — disclose that it is an assistant, announce recording, keep the transcript attached to the job — should come standard from whoever answers your line after hours. CallSphere builds voice and chat agents that answer contractor phone lines around the clock, book the call into your dispatch board and hand you the transcript with it, which is exactly the record this file needs. Ask any vendor to show you the greeting script and the transcript export before you sign; if they cannot, you are the one holding the paperwork problem.