Contractor License Lookup by State: PE Mapping in 2026

Executive Summary

Contractor license lookup by state is a jurisdiction-routing problem followed by an identity-resolution problem. This research asset covers 50 states plus the District of Columbia, with official entry points, credential scope, searchable keys, documented fields, bulk routes, and access limits. It is a checked routing matrix as of October 13, 2026, rather than a national list of acquisition-ready companies. California supports business, license-number, and personnel searches; Washington documents number, Unified Business Identifier, and business or owner-name searches. Those different keys require different collection strategies. ^{[1] [2]}

The important distinction is the unit of record. Florida places the approved business entity on an individual's contractor license. North Carolina separates licensees from examination qualifiers, while Wisconsin identifies its Dwelling Contractor credential as held by an organization or business. A name appearing in a contractor database needs its role established before becoming a company record. Oregon permits its responsible managing individual to be an owner, officer, partner, or employee. Qualifier relationships can support a join; they cannot independently establish beneficial ownership. ^{[3] [4] [5] [6]}

Bulk availability helps discovery but does not establish complete coverage. California's downloadable master omits cancelled, revoked, and expired nonrenewable licenses. ^[7] Pennsylvania's current search returns active registrations only. ^[8] Minnesota documents a nightly spreadsheet and uses Issued for active credentials. ^[9] These are different population and refresh rules, not interchangeable definitions of an active operating company. Scope varies too: North Carolina's board states a $40,000 project threshold. ^[10] Arkansas describes $50,000 for its commercial-license trigger. ^[11] Project thresholds are scope conditions, not revenue estimates.

The recommended acquisition-mapping protocol preserves raw licensee names, jurisdiction-qualified credential IDs, native classifications, exact status wording, qualifier roles, source dates, and unresolved conflicts. It joins those observations to a legal-entity registry and company evidence before deduplicating businesses. Statistical denominators must match the research unit: the Census Bureau defines an establishment as a physical location and excludes nonemployers from Statistics of U.S. Businesses. The coverage arithmetic below is explicitly hypothetical; this report supplies no measured national resolution rate, ownership finding, or acquisition-interest estimate. ^[12]

Introduction and Background

A private equity (PE) analyst searching for contractors should first identify the research question. Discovery asks which potentially relevant operators appear in a credential system. Verification asks whether a named target matches a particular record. Trade screening asks what work a credential covers. Entity reconciliation asks whether a person, business name, legal entity, and location belong together. The same portal may answer these questions differently.

California distinguishes contractor business searches from associated-person searches and separate salesperson registrations. Louisiana separates company-name inputs from names used when an individual owns the license. Neither structure supports treating every returned name as an independent acquisition target. ^{[1] [13]}

The practical starting point for “general contractor license requirements by state” is the regulator's current scope statement, followed by the relevant local department. Oklahoma says general contractors are not currently required to hold a state license, while retaining trade and roofing routes. Austin describes local general-contractor registration within a Texas system where general contractors do not require a state license. An absent statewide credential does not settle trade licensing or municipal registration. ^{[14] [15]}

This informational report focuses on the contractor credential-to-company bridge; it is not licensing advice. It does not repeat broad market mapping, general entity-registry directories, or applicant instructions about examinations. The matrix is designed for research operations: which source to open, which identifiers to preserve, what a field establishes, and where a join remains unresolved.

Docket describes company research with supporting excerpts and collection dates. That delivery model is relevant to evidence handling, but the regulator remains the authority for its credential. The distinction between a sourced research file and a licensing record is maintained throughout.

Research Methodology and Record Taxonomy

The research prioritizes opened regulator pages, official verification interfaces, documented export schemas, and agency instructions. Built-in page fetches were attempted first; blocked pages used the supplied rendering fallback. A retrieved navigation page counts as a verified route, not a successful record search. Agency-described fields are labeled documented; inspected result fields are labeled observed.

Coverage is qualified. Organization results or detail labels were inspected in Alabama, Delaware, and Illinois. Many portals returned shells, unlabeled controls, CAPTCHA challenges, or inaccessible detail pages. Representative person and organization records were not tested across every jurisdiction; an attempted Maine individual-record test also failed. Unverified is a substantive finding, not a blank to fill from another state.

The operational record types are:

• Credential: License, registration, certificate, or tax credential with jurisdiction and native identifier (ID).
• Licensee: Person or organization to which the credential is attributed.
• Classification: The agency's permitted-work category.
• Endorsement: An additional scope dimension such as residential or commercial.
• Qualifier: A person with a defined examination or supervisory relationship.
• Location: An address whose role needs verification.
• Status: Exact agency wording and observation date.
• History: Separately retrieved changes, prior names, or agency documents.

These are research categories, not universal statutory vocabulary. Hawaii lists entity, sole proprietor, and responsible managing employee credentials. South Carolina separates its contractor and residential programs, with firm authorizations in the latter. ^{[16] [17]}

Table 1 distinguishes acquisition-mapping inputs and delivery models. The primary axis is evidence delivered, not authority to issue a contractor license.

Source authority is field-specific. A research provider can organize and review findings, but its company file does not replace an agency credential record. Conversely, that record can establish a licensing relationship without answering ownership, scale, service-mix, or acquisition-interest questions.

The 50-State Contractor License Lookup Matrix

Table 2 routes analysts to an official lookup or the agency page documenting it. Every row was checked on October 13, 2026. U means unverified this session. “Documented” identifies agency-described fields or exports; “observed” identifies inspected form, list, or result features. General contractor is abbreviated GC. DBA means doing business as; RMI means responsible managing individual; RME means responsible managing employee; QP/QI mean qualifying party/individual; QA means qualifying agent; UBI means Unified Business Identifier; SIC means Standard Industrial Classification; WC means workers' compensation. Oregon CCB numbers identify its board credentials; Hawaii CT is a contractor credential prefix. Iowa PMSB means Plumbing and Mechanical Systems Board. CSV means comma-separated values; NAICS means North American Industry Classification System; FOIA denotes a Freedom of Information Act records route.

The evidence link is the search page where readable. Otherwise, it is the regulator's routing or scope page, from which the current lookup should be entered. A routing citation is not a successful interactive-portal test.

The matrix's strongest use is routing. Declaring completeness from one row per state would ignore source boundaries. Maine's general-contractor scope differs from its licensed trades, New York combines local home-improvement jurisdictions with a registry covering public work and private projects covered by Article 8 of the Labor Law ^[47], and Missouri's verified state route here is electrical contracting. Collection plans should follow those boundaries. ^{[61] [62] [39]}

For state contractor licensing board directories, record the board and credential family together. Arkansas combines licenses and registration certificates, while South Carolina divides contractor and residential programs. Massachusetts' verified Hub covers home-improvement registrations and history; its separate construction-supervisor route was not established here. An agency name alone does not define the target universe. ^{[11] [52] [37]}

For contractor license public records, use the current records route. Idaho links formal-action information; Nevada provides public-record and board-action routes. Those routes do not establish that a clean lookup contains a complete historical file. Preserve the retrieved document scope and record when retention is unverified. ^{[28] [43]}

Resolving a License Record Into a Target Company

A company identifier should be a jurisdiction-qualified legal-entity identifier supported by a registry record. A contractor number remains a credential key. Joining them should create a reversible evidence relationship, rather than replacing one identifier with the other. California's Secretary of State documents entity numbers, jurisdictions, addresses, and officer, director, member, and manager information. The same office says ownership and shareholder information are not made of record. ^[18]

A useful license-to-company evidence record contains:

• Raw licensee: Preserve spelling, punctuation, suffixes, and source.
• Credential key: Combine jurisdiction, program, type, and native number.
• Person or organization: Record the observed category and supporting evidence.
• Native classification: Retain original codes and descriptions.
• Qualifier relationship: Keep role and associated credential separate.
• Exact status: Preserve wording without a generic active substitution.
• Dates: Separate issue, expiration, effective, update, and collection dates.
• Address role: Label mailing, business, branch, or unspecified.
• DBA bridge: Capture an explicit doing-business-as relationship.
• Legal entity: Preserve registry jurisdiction, exact name, and entity ID.
• Matching evidence: Record identifiers or documents supporting the join.
• Conflict: Retain contradictory names, entities, addresses, and dates.
• Outcome: Mark resolved, unresolved, person-only, out of scope, or duplicate.

These are recommended collection fields, not claims that every portal publishes them. Delaware's observed rows expose business-related data, while Wisconsin identifies an organization credential. Florida describes a different starting point: an individual license linked to an approved business. ^{[25] [5] [3]}

Proceed in a fixed order:

1. Preserve the row. Normalize a separate search value without changing evidence.
2. Resolve the holder. Identify person, organization, or uncertain type.
3. Search the registry. Use exact name, explicit DBA, and jurisdiction first.
4. Check the bridge. Seek a source explicitly linking credential or trade name to entity.
5. Check company evidence. Reconcile website legal disclosures and locations.
6. Review conflicts. Keep competing candidate entities unresolved.
7. Cluster cautiously. Merge rows only after establishing the company relationship.

Matching name and address can identify a candidate join. This report recommends an explicit bridge or corroborating entity-specific evidence before accepting it. Similar trade names and shared addresses should trigger review rather than automatic merging.

Jurisdiction-specific rules help. Minnesota requires the exact Secretary of State filing name, with an assumed-name filing for a different name. Iowa requires separate registration for businesses with separate federal identification numbers. Nebraska requires separate registrations for different business names. These rules explain why one website can coexist with multiple credential rows. ^{[63] [32] [42]}

A qualifier is not an automatic parent-company or beneficial-owner link. Georgia permits one person to qualify multiple companies. North Carolina describes qualifiers as people passing exams on behalf of a license. Oregon permits employee qualifiers. Shared qualifier names should become typed relationships, not common-ownership findings. ^{[27] [4] [6]}

Trade Scope, Status and Coverage Gaps

A universal “licensed contractor” flag discards information useful for acquisition mapping. Preserve native scope, then map it into a declared research taxonomy. A commercial-service mandate might include electrical maintenance and exclude new residential construction. That research decision should follow classification evidence and company evidence separately.

Table 3 gives a limited classification crosswalk. Official category claims were checked on October 13, 2026. Suggested research buckets are editorial categories, not agency equivalence determinations.

The same letter can have different meanings. California A is a work classification; Virginia A is a monetary class. Local labels change too: Lafayette says its previous Class C was updated to Class B. Preserving codes and effective dates prevents manufactured equivalence. ^{[64] [58] [19]}

Status normalization needs the same restraint. Keep active, inactive, suspended, expired, revoked, pending, or other wording as a source value, then add a separately defined research interpretation. California says an inactive license cannot be used to practice or bid for work. Minnesota uses Issued for active credentials. Maine publishes its own definitions and certified-history route. ^{[66] [9] [36]}

Recommended screening outcomes are:

• Current credential observed: Relevant native status is captured.
• Historical credential only: Current authorization is not established.
• Application or pending: Completion remains unestablished.
• Local-only coverage: State verification is insufficient locally.
• Person-only evidence: No operating-entity bridge is accepted.
• Scope unresolved: Trade, endorsement, or threshold remains uncertain.
• Access blocked: Required detail could not be retrieved.
• History unverified: No complete history claim is supported.

These labels are research outcomes, not regulatory determinations. An expiration date is not necessarily a closure date. Pennsylvania's active-only search omits other statuses; California's master excludes several historical categories, while its personnel file excludes disassociated personnel. ^{[8] [7]}

Bond and insurance fields require context. California's schema includes bond and workers' compensation information; Washington combines contractor and compensation checks. Such fields cannot independently prove insurance adequacy for an acquisition or operating quality. Registration also need not represent an agency endorsement, as Pennsylvania expressly states. ^{[7] [2] [8]}

Data Analysis and Evidence

The useful quantitative result is unit-consistent coverage, not a license-row count. Define the numerator as resolved unique in-scope legal entities. Define the denominator as unique potentially in-scope organization-license clusters reviewed. Report unresolved organization clusters and person-only clusters separately. These are proposed research metrics, not measured benchmarks.

The statistical denominator requires care. Census defines an establishment as a single physical location; a firm can combine establishments under common ownership or control. Statistics of U.S. Businesses excludes nonemployers. A credential dataset containing sole proprietors should not be compared directly with an employer-business denominator without accounting for that difference. ^[12]

Census's construction presentation distinguishes 236 Construction of Buildings, 237 Heavy and Civil Engineering Construction, and 238 Specialty Trade Contractors. These groupings frame a universe but do not automatically convert state classes into North American Industry Classification System (NAICS) codes. This is a dated Census presentation, not evidence that a particular contractor currently files under a particular code. ^[67]

Project-value rules illustrate why scope is not company size. North Dakota says licensing applies when a job exceeds $4,000. ^[49] North Carolina states $40,000 or more for its general-contractor threshold. ^[10] Arkansas describes $50,000 or more for commercial work including labor and materials. ^[11] Tennessee describes $25,000 or more for prime contractors and construction managers, with separately described subcontractor categories. ^[65] These are selected examples, not a complete requirements guide.

Virginia adds aggregate tests. Class A includes a project of $150,000 or more or $1 million or more in aggregate construction work in a 12-month period. ^[68] Class B includes projects from $30,000 to below $150,000, or aggregate work from $250,000 to below $1 million in a 12-month period. ^[68] Preserve the project and aggregate alternatives together. Neither is verified target revenue.

Hypothetical calculation: A fictional review contains 120 potentially in-scope organization-license clusters. If 84 resolve to unique in-scope legal entities, 24 remain unresolved, and 12 resolve outside the mandate, resolution is 84 / 120 = 70%. Another 30 person-only clusters are reported separately, outside that organization denominator. Every quantity here is invented solely to demonstrate the formula.

Record source yield separately: candidate clusters contributed, accepted entities contributed, duplicate overlap, unresolved bridge rate, and access failures. Many rows with repeated people, classes, and locations can coexist with few resolved companies. No national empirical licensing-to-company conversion rate was established.

Case Studies and Real-World Examples

License-to-company reconciliation (Hypothetical Example)

All names, identifiers, website details, and outcomes in this example are fictional. Harborline Building Services appears on a contractor record with a number, electrical classification, current native status, mailing address, and qualifying employee. A researcher finds a limited liability company (LLC), Harborline Building Services LLC, in an entity registry and a website using the shorter trade name.

This is initially a candidate join. The analyst preserves the raw licensee name and marks the holder uncertain until an agency record establishes whether it is the company or individual. Florida's guidance shows why: a company can appear on an individual's credential. Oregon's employee-permitted qualifier role also prevents that person's name from becoming an ownership finding. ^{[3] [6]}

The fictional website's legal footer names the LLC and prints the same credential number. A current agency document names the LLC as the licensed business. The registry supplies its entity identifier. The analyst accepts that bridge and attaches the credential observation to the entity, preserving date and scope.

The website lists another service location. It is recorded as a company-reported address, rather than another acquisition target. The mailing address remains attached to the license observation. Neither address is overwritten, and local authorization at the new location remains a separate question.

Now alter the fictional facts. There is no legal footer, the registry contains another similarly named entity, and the only shared field is the qualifier's name. The outcome is unresolved, with both candidates and the missing bridge documented. Georgia permits a qualifier to serve multiple companies, so the person match cannot settle the join. ^[27]

Ownership, revenue, headcount, insurance adequacy, quality, and acquisition interest remain unanswered in both fictional versions. Resolved identity is a prerequisite for further research, not a substitute for it. The deliverable is a reviewable company-to-credential relationship with explicit limits.

Implications and Future Directions

A maintainable contractor license database by state needs a change log, not just bookmarks. Recommended entries include:

• Regulator change: Previous agency, replacement, and official announcement.
• Route change: Old URL, redirect/failure, replacement, and checked date.
• Field disappearance: Previous field, new layout, and affected joins.
• Scope change: Credential family, local carve-out, or exemption affected.
• Classification change: Native codes and source-stated effective date.
• Export change: Population, schema, cadence, or method changed.
• Access change: Login, CAPTCHA, JavaScript, terms, or request requirements.

Quarterly review is a proposed cadence. Material announcements should trigger earlier checks. Montana reports registration conversion at the start of 2026, yet retains older employee-registration wording. ^[40] Utah announces changes effective April 20, 2026. ^[69] Alabama describes exemptions effective October 1, 2026. ^[70] Rhode Island's residential-license page announces January 2028, not a 2026 rollout. ^[71] Uncertain operative scope should be escalated to the agency.

Bulk contractor license data should be obtained through documented exports or records routes before considering automation. California documents master files; Connecticut provides rosters; Oregon describes its self-service list. Availability does not establish blanket permission to automate, republish, or use personal information for outreach. ^{[7] [24] [6]}

South Carolina's roster form prohibits commercial solicitation using public-record personal information and defines that term in a consumer-product/service context. This report does not determine its application to acquisition outreach. Pennsylvania separately requires Press Office permission for reuse. Counsel or the agency should address unclear intended uses. No national automation permission or request-rate policy was verified. ^{[72] [8]}

Retain requested records, response scope, collection date, and unresolved questions. Blocked portals should lead to official contact or records requests while the company file stays incomplete. A future refresh can expand observed-field coverage without retroactively describing this session's untested detail records as verified.

Conclusion

Contractor license lookup by state is most useful to PE origination when a credential is treated as one evidence layer in a company file. The routing matrix identifies official entry points and exposes local boundaries, registration-versus-license differences, person-versus-organization distinctions, and access gaps.

The recommended sequence is straightforward: choose jurisdiction and credential family, preserve the record, identify its holder, retain native scope and status, establish a legal-entity bridge, and only then cluster company relationships. When the bridge is missing, unresolved is the appropriate output. A qualifier, similar name, shared address, or additional location should never settle ownership or identity by itself.

Coverage should use a company-oriented denominator. License rows, qualifying people, trade names, and establishments are different units. Keeping them separate makes exclusions, duplicates, person-only evidence, and unresolved joins reviewable. It prevents a large download from becoming an unsupported claim of market completeness.

Maintenance belongs inside the design. Store checked dates, source-update dates where supplied, and changes affecting routes, fields, scope, and reuse. Preserve earlier findings when current records change. The resulting asset helps analysts discover and verify candidates while treating ownership, scale, quality, and transaction interest as separate questions.