Every state contractor-licensing portal in the United States is a little different.
The ways verification *fails* aren't. ContractorRoster has shipped deep license-verification guides for seven states so far — Florida, California, Texas, New York, Virginia, Washington, and Arizona — and the same eight trap patterns surface in nearly every one. Different statute numbers, different acronyms, different status codes; same eight underlying failures, repeating with state-specific dressing.
This is the abstracted version. A checklist that travels with you across state lines, so a multi-state buyer touching ten jurisdictions a month doesn't have to read ten deep dives before signing each contract. Roughly ten minutes per contractor, in any state.
Why a checklist beats seven deep dives (for some buyers)
A homeowner hiring one contractor in one state should read the deep state guide for that state. The state-specific tricks matter — Florida's *Delinquent Active* status, Washington's industrial-insurance account view, New York's NYC-versus-county jurisdiction split, Arizona's Residential-versus-Commercial classification tracks. Those guides exist precisely because each state's portal has its own UI, its own status vocabulary, and its own statute behind the curtain.
But the audience for those guides is one-state-at-a-time. The other audience — the developer running an RFP across four markets, the distributor's territory rep onboarding new dealers in eight states a quarter, the corporate property manager handling vendors in twelve, the construction recruiter calling individual electricians across regions — does not have the time to internalize seven portal idiosyncrasies. They need a checklist that asks the same eight questions regardless of which board they're hitting, and that flags the answer they should not accept.
That is what follows. Each trap is named, defined in one sentence, illustrated with examples from the state guides we've already published, paired with a verification question to ask, and a what-to-do-if-the-answer-is-wrong line. The order is roughly ranked by how often the trap fires, not by severity — the highest-stakes traps for each buyer type are called out in the decision tree at the end.
Trap 1 — Classification or scope mismatch
The license is real. The scope doesn't cover the work. A contractor holds a valid, active license in the wrong specialty or wrong class for what they're being hired to do.
State examples. California: a C-39 roofing license bidding electrical work is out of scope under CSLB rules; a B General Building contractor self-performing more than two unrelated trades on the same job violates B&P Code §7057. Florida: a Certified Roofing Contractor without a solar endorsement quoting a rooftop PV install is operating outside class. Arizona: a B-2 General Small Commercial holder bidding a custom residential build is in the wrong family entirely (residential is the B / B-4 track, not the C-/CR- commercial track). Texas: a Class B HVAC contractor quoting unlimited-tonnage commercial refrigeration is past the statutory cap.
Question to ask. *Which exact license class is on the record, and what scope of work does that class authorize?* If the answer is a vague "general contractor" or "I'm fully licensed," the contractor either doesn't know or is hoping you don't. Pull the portal yourself, read the classification code, and look up what that code authorizes on the board's classification page.
If wrong. The license is functionally absent for *your* job, even though it's real for a different job. Most state recovery funds (Florida's CIRF, Arizona's Residential Recovery Fund, California's CSLB recovery program) treat out-of-class work as unlicensed for claim purposes. Don't sign; either replace the contractor or ask them to subcontract the out-of-scope portion to a properly classified licensee whose name and number you also verify.
Trap 2 — Qualifier or personal-license-versus-business confusion
The license is in a person's name. The contract is with a company. Most states issue specialty and general licenses to a qualifying *individual* — a Qualifier, Responsible Managing Employee (RME / RMO), Qualifying Party, Responsible Master Plumber, Electrical Administrator, Master Electrician — and let that individual qualify a separate business entity. The trap fires when the individual leaves, dies, or detaches from day-to-day supervision, and the business keeps operating under the now-stale qualifier credential.
State examples. California under CSLB rules requires an RMO or RME for every licensed entity, and the qualifier must exercise direct supervision and control — qualifier-for-rent schemes are a recurring CSLB enforcement target. Florida: F.S. §489.119 governs the Qualifier relationship, and a license in a brother-in-law's name attached to a separate construction LLC is a common arrangement worth questioning. Virginia requires a Designated Employee linked to the contractor license *and* a separately licensed Tradesman (Master / Journeyman) actually performing regulated electrical, plumbing, HVAC, or gas-fitter work. Texas: a Master Electrician or Responsible Master Plumber is required for a contracting business to pull permits; a journeyman operating solo is not legally a contractor. New York: NYC DOB Master Electrician and Master Plumber licenses are personal credentials, and the company that shows up at your job works under a *filing representative* relationship to that individual.
Question to ask. *Which named individual is the qualifier (or RME / RMO / RMP / Master / Electrical Administrator / Designated Employee) for this business, and will that person be actively supervising my job?* Then check the portal: confirm the individual's name on the license record matches the person being named, and that the qualifier link to this exact business entity is current.
If wrong. Either the qualifier has detached (in which case the license is at imminent risk and disciplinary action is likely already in motion), or the qualifier is real but absent from the work (in which case you have a credential without supervision — the worst of both worlds on the day something goes wrong). Ask for either the qualifier on-site at key milestones or a different licensed contractor whose qualifier is genuinely in the chain.
Trap 3 — State license versus local registration
"I'm licensed in [state]" often means "I have a city or county registration." For trades or scopes the state doesn't license at all, a contractor pointing to credentials is frequently pointing at a municipal program — which is real, useful, and not the same thing.
State examples. Texas doesn't license general contractors, roofers, painters, landscapers, concrete, masonry, drywall, framing, or flooring at the state level — those trades hold (or don't hold) city registrations through Houston, Dallas, Austin, San Antonio, Fort Worth, or nothing at all. New York has no statewide Home Improvement Contractor license — NYC DCWP, Nassau County, Suffolk County, Westchester County, Rockland, Putnam, and Albany each run their own, none of them reciprocal. Ohio licenses only five trades at the state level (electrical, HVAC, plumbing, refrigeration, hydronics); everything else is city or county. Colorado licenses individuals (Class A/B/C examiners) but not contracting businesses, so a "Colorado-licensed contractor" claim from a company is structurally wrong. Minnesota has no statewide commercial GC license at all.
Question to ask. *Which jurisdiction issued the credential — the state board, a city, a county, or a trade association?* Then verify on that specific issuing authority's portal, not on a search engine.
If wrong. Distinguish *misrepresentation* from *terminology shortcut*. A roofer in Austin saying "licensed in Texas" when they mean a Round Rock contractor registration is usually careless rather than fraudulent; the registration is still a verifiable thing. A contractor who can't name the issuing authority at all is a different situation. For unlicensed-at-the-state-level trades, the verification chain shifts to insurance, bonding, contract terms, and references — there is no statewide recovery fund to fall back on.
Trap 4 — The expired-but-recoverable status (soft-fail codes)
The portal looks green. The contractor is still unable to legally work. Most state boards have at least one status code that reads as "findable" or "active-ish" but means *cannot legally perform contracting work pending a cure*. Buyers see the record show up, see a status that isn't *Revoked*, and stop reading.
State examples. Florida is the headline case: a *Delinquent Active* license is in the DBPR portal, looks like a hit, and per DBPR's own guidance the contractor may not legally practice until the renewal deficiency is cured. Virginia: DPOR distinguishes *Inactive* from *Expired* — inactive is recoverable on payment, expired requires reapplication, and neither is work-eligible. Washington L&I shows *Suspended* registrations alongside the citation that triggered the suspension. Oregon CCB carries a similar *Inactive* status. Ohio suspends licenses for continuing-education lapse — the record still resolves, but the contractor isn't permitted to operate. Most states with renewal-cycle licensing have some equivalent.
Question to ask. *What is the exact status string on the record, and what does the board's own glossary say it means?* Not *what color is the badge*. The badge is decorative. The status string is dispositive.
If wrong. Walk, or wait. A soft-fail status can usually be cured in days or weeks (renewal payment, CE completion, missing-form submission). If you have time, the contractor curing the lapse is fine. If you don't, the contractor cannot legally start the work today, and signing a contract during the lapse exposes you to the same enforceability problems as signing with an unlicensed contractor.
Trap 5 — License active, bond or insurance lapsed
Active license, cancelled bond. Active license, lapsed workers' comp. Active license, expired liability insurance. The license registration and the *dependent* coverages that make the license meaningful run on different cycles, get audited at different cadences, and are surfaced by different state portals — most of which show only the license itself.
State examples. Washington is uniquely good at surfacing this: L&I's verify portal returns bond status, liability insurance status, workers' comp account status, and outstanding L&I citation balance in one query, alongside the registration. Arizona ROC surfaces bond status alongside license status — a clean Active license with a lapsed bond is a contractor you cannot legally hire under ARS §32-1152. California CSLB surfaces bond and workers' comp status on the license-detail page. Florida, Texas, and most other states surface the license only, not the dependent coverages — you have to ask for a Certificate of Insurance and call the insurer separately.
Question to ask. *Is the contractor's bond active and at the statutory minimum for the license class? Is the workers' compensation account current? Is the general liability policy in force, and is it adequate for the project's exposure?* In states that surface the answers (WA, AZ, CA) read them. In states that don't (most of them), request a current Certificate of Insurance naming your property or project as a certificate holder, and confirm directly with the insurer that the policy is in force and the certificate is accurate.
If wrong. A cancelled bond eliminates your recovery path if the contractor walks. A lapsed workers' comp policy makes any injury on your property a serious liability problem for you, not just the contractor — and in most states, it's illegal to have employees on a job site without coverage. Don't sign until the dependent coverages are restored and the certificate reflects them.
Trap 6 — Complaint history is only partially public
Disciplinary actions are usually public. Complaints often aren't. Formal orders, citations, license suspensions, and revocations are part of the public record on most state boards. Complaints that were settled, withdrawn, are still pending, or never escalated to a formal action frequently are not — and a portal that shows zero disciplinary history can hide a pattern of unresolved consumer complaints if the board is selective about what it surfaces.
State examples. Arizona ROC is among the most transparent — complaints, citations, suspensions, and resolutions surface inline on the public record. Oregon CCB exposes consumer claims filed against a contractor's bond. Washington L&I surfaces formal citations but not consumer tips that didn't escalate. Florida DBPR exposes Disciplinary History on a separate tab from the main verification screen — a one-click difference that most consumers never make. New York NYC DCWP exposes complaint history including pending matters, but the county HIC registries vary widely in transparency. Texas TDLR is unusually transparent for a state that doesn't license most trades — administrative penalties surface inline. State boards that license a trade but don't surface complaint history at all (less common, but exists) are a meaningful information gap.
Question to ask. *Does the board's portal include a complaint or disciplinary history tab — and if it does, what does it show?* If the answer is "none visible," check whether the board has a separate complaint database, a public-records request process, or no public disclosure at all. Then ask the contractor directly for a list of any disputes, mediations, or claims filed against them in the last five years — and verify any answer against the board record where possible.
If wrong. A pattern of open or recently-resolved complaints in the same trade and scope as your job is a leading indicator. One complaint over a long career is noise. Three in the last twelve months for similar work is a signal. If the board doesn't expose complaint history at all, ask for references from jobs in the last twelve months and verify them by phone.
Trap 7 — The cross-jurisdiction mismatch
The license is real. The jurisdiction is wrong for your project. A contractor licensed in one city or county takes on a job in another, where their credential doesn't cover the work — common in states that license at the local level, but also a problem in states with strict regional or county overlays.
State examples. New York is the canonical case: an NYC DCWP HIC license does not cover Westchester, Nassau, Suffolk, Rockland, or Putnam — each county runs its own non-reciprocal HIC program. A Nassau County HIC does not cover Suffolk. Texas: a Houston General Contractor Registration does not cover Dallas; a Dallas building-contractor registration does not cover Austin. Colorado: a Denver license does not cover Colorado Springs. Most home-rule cities in Ohio, Missouri, and the Carolinas have similar non-reciprocal regimes. Even in states with strong statewide licensing, county-level overlays for floodplain, coastal, mountain, or historic-district work can require additional jurisdiction-specific endorsements the state license alone doesn't provide.
Question to ask. *Where exactly is the project located — what city, what county, what overlay districts — and which licenses or registrations does that exact jurisdiction require for this scope of work?* Then verify the contractor holds each of them.
If wrong. The contractor cannot legally pull permits in your jurisdiction, and your contract may be unenforceable for the same reason an unlicensed-contractor contract is unenforceable. Either the contractor obtains the missing local credential before signing, or you hire someone who already holds it.
Trap 8 — Out-of-state contractor under temporary registration
The temporary registration is real. The underlying home-state license isn't verified by the host state. Larger states with significant disaster-response or specialty-trade cross-border activity (Florida, Texas, the Carolinas, the Gulf states, the Pacific Northwest after wildfires) commonly allow contractors from neighboring states to register temporarily for specific projects. The host state's portal verifies the registration; it does not independently verify the home-state license that the registration is built on top of.
State examples. Florida DBPR records temporary registrations for out-of-state contractors but does not verify the underlying Georgia, Alabama, or South Carolina license. Washington L&I records reciprocal arrangements with Oregon and Idaho but doesn't surface the full home-state disciplinary history. New York: New Jersey and Connecticut contractors taking on NYC jobs typically register temporarily with DCWP, and DCWP does not verify the NJ or CT credential. Arizona: out-of-state contractors operating in the Phoenix metro under temporary ROC registration leave the underlying California, Nevada, or Utah license unverified by the AZ portal.
Question to ask. *Where is the contractor based, and which is their primary home-state license? What is the license number, and is it currently active in good standing in the home state?* Then pull the home state's board directly and verify.
If wrong. A temporary registration backed by a problematic home-state license (recent revocations, large disciplinary actions, a string of complaints) is a much higher-risk hire than the host state's portal makes it look. Run the home-state verification with the same eight-trap checklist before signing.
What this checklist doesn't catch
Worth being honest about the limits, in the same spirit the state guides are.
Not every state portal surfaces enough data to apply every check. The complaint-history trap is hardest to verify in states that don't expose complaint records at all; the bond-and-insurance trap is hardest in states that show only the license itself. Where the portal is thin, the checklist shifts to direct outreach — call the board, request a Certificate of Insurance, verify with the surety, call references.
Mechanic's-lien history lives at the county recorder or clerk's office in every state we've covered, not on the licensing portal. A contractor with a clean license can still have a pattern of recording liens against past clients' properties, and that pattern is often the single best leading indicator of how disputes get handled. For high-stakes contracts, a county-records search is part of the diligence even when the licensing portal looks clean.
Subcontractor relationships aren't tracked anywhere centrally. The license verifies the entity you are contracting with. The people who will actually be on your roof, in your attic, or in your kitchen on Tuesday morning are frequently subcontractors and labor crews whose credentials you would have to verify separately. For projects above a certain size, asking which subs the GC plans to use and running each one through the same checklist is the second pass.
Litigation history (civil suits against the contractor that didn't go through the licensing board) lives at the state court system, not the board. Some states publish court records online; many don't. For a high-stakes contract — a multi-million-dollar commercial build, a sensitive historic restoration, a celebrity client's residence — local counsel for the project's jurisdiction is the right additional layer, not a checklist.
Which trap matters most for your role
All eight traps apply to every buyer. But the highest-stakes single trap shifts depending on what you're doing.
For a homeowner hiring one contractor, Trap 1 (classification or scope mismatch) is the highest-stakes single failure. It's the failure most likely to void state recovery-fund coverage and the failure most likely to result in a permit being pulled mid-project. Verify classification first, status second, everything else third.
For a property manager running a vendor roster, Trap 5 (license active, bond or insurance lapsed) is the highest-stakes single failure. Properties under management generate ongoing exposure, and a vendor with a lapsed workers' comp policy on an injury claim is the property manager's problem first and the contractor's problem second. Build the workflow around requesting and re-verifying Certificates of Insurance on a quarterly cadence, not a one-time check.
For a developer or GC sourcing across territories, Trap 8 (out-of-state under temporary registration) is the highest-stakes single failure. Cross-border project work is where the host-state portal's verification feels complete but isn't, and the home-state license is the actual credential of record. Build a two-pull verification (host state and home state) into the procurement workflow for any contractor not headquartered in the project's state.
For a supplier or distributor onboarding dealer-installers, Trap 2 (qualifier or personal-license-versus-business confusion) is the highest-stakes single failure. The qualifier relationship determines whether the entity you're extending credit or product to is the same entity that will be legally accountable when something goes wrong. Verify the qualifier's name on the license matches a person on the business's payroll or ownership documents, not a contractor-for-rent relationship.
For a recruiter or staffing firm placing individual tradespeople, Trap 2 again — but in the individual-credential direction. A journeyman or master electrician's personal license follows the person, not the employer; verify the individual's record, not the placing employer's.
Where ContractorRoster fits
ContractorRoster maintains a continuously-updated mirror of every state contractor-licensing database we have access to — 618,395 active records across 15 states (California, Texas, Florida, Virginia, Minnesota, Colorado, Washington, Oregon, Arizona, Illinois, Ohio, New York, Pennsylvania, Nevada, Utah) — with phone, email, website, and Google ratings layered in. For one-off verification of a single name, the relevant state portal is the source of truth and the deep state guide is the right reading.
For multi-state buyers, our $39 per-state CSVs at / give you the starting roster — every active licensed contractor in a city or ZIP — and the eight-trap checklist above gives you the verification flow to run before signing. Together they replace two to four hours of manual board-by-board verification with roughly ten minutes per contractor: pre-enriched contact info, then the same eight questions against whichever state's portal you happen to be looking at that hour.
That ratio — manual hours collapsed to checklist minutes — is what makes a multi-state practice scale.
Next step
Read the deep state-specific verification guide for whichever state your next contract is in: Florida, California, Texas, New York, Virginia, Washington, or Arizona. Each one walks the local portal field-by-field and flags the state-specific tricks the cross-state checklist above can't surface.
For everything else, the eight-trap checklist above is the working tool. Save it. Run it against any state, any portal, any contractor.