Executive Summary: For a California contractor, an entity change requires more than carrying the old license number into a new credit file. California law distinguishes a nontransferable license from conditional reissue or reassignment of its number.[1] Reconcile the business now performing the work, the current license record and the transaction roles before relying on earlier evidence.
Which business needs to be associated with the license?
Begin with the transaction roles. The borrower, contracting business and payment recipient may not always be the same legal entity. Identify which entity your lending policy needs licensed for the work and document any relevant relationship to the borrower.
Do not force every name into one field simply to obtain a match. Equally, do not assume that a familiar trading name or owner proves the current licensed business is the one performing the work.
Why does an entity change matter in California?
CSLB explains that contractor licenses are associated with business entities rather than necessarily with the qualifying individual.[2] The same person continuing in the business does not, by itself, establish that the license covers a newly formed entity.
The lending review should therefore connect the current source record to the relevant transaction party. It should not treat an unchanged owner, crew or business address as a substitute for that evidence.
What if the borrower is a holding company?
Record the separate roles and the relationship your policy requires. The question is whether the proper operating entity holds the relevant license and whether the lending file supports the transaction structure. A name difference can be legitimate without being irrelevant.
Keep this article's scope to California entity-and-license reconciliation. It does not determine the legality of a particular structure or supply a rule for every other state.
How is an entity change different from a name change?
A business-name update and a change in legal entity are different events. Establish which occurred using the appropriate records before deciding how the earlier license evidence can be reused.
CSLB's name-change guidance says a corporate name change at the Secretary of State does not automatically update the name at CSLB. It also connects a corporate license number to a specific corporate registration number.[3]
What should the analyst compare?
Compare the current legal name, entity type, state registration identity and license record. Preserve the earlier versions and the source explaining the change. A short note such as “new DBA” is insufficient if the supporting records actually describe a new corporation or LLC.
Can the number remain the same?
California Business and Professions Code section 7075.1 permits reissue or reassignment of a license number under specified conditions.[4] That means number equality alone cannot settle the entity question.
The statute also prohibits transfer of the license itself. Preserve that distinction: do not describe every number reassignment as a transferable license, and do not decide that a particular borrower qualifies for a statutory path from a few matching fields.
What evidence should the review collect?
Build a short reconciliation package tied to the current lending decision. The package should establish the relevant entities, the change event and the current license association without turning the analyst into a licensing adjudicator.
Use an evidence checklist such as:
• License response. Keep the returned business name, entity type, license number and status together; these appear in the documented contractor response.[5]
• Current transaction parties. Identify the borrower, licensed performer and payee where their roles differ.
• Earlier licensed business. Retain the name, entity identity and license record used in the prior review.
• Change evidence. Identify the official record or other permitted evidence showing what changed and when.
• Current license record. Obtain the present business name, license number, entity description and status.
• Number continuity explanation. If the number remains the same across an entity change, obtain evidence explaining the current association rather than assuming transfer.
• Review disposition. Record the responsible owner's conclusion, remaining questions and permitted next action.
Cobalt's contractor response can include businessName, licenseNumber, entity, status, expirationDate and a source URL.[6] Those fields can support the package, but they do not independently determine legal eligibility for reassignment.
What should remain unresolved?
Keep an unresolved state when the license record still names the old entity, the current transaction role is unclear, or a claimed reassignment lacks sufficient supporting evidence. Specify which fact is missing and who can resolve it.
Do not replace the old company name in a stored license response with the new applicant name. That would create an apparent source match unsupported by the record.
How can the API fit into this review?
Use the documented license-number search to retrieve the current record for the relevant state. Cobalt's contractor-search request requires a license number, state and callback URL.[7] Confirm the actual result before allowing it to change the lending review.
The endpoint is a data-retrieval route. It is not a legal transfer approval, a determination that every aspect of the project is covered, or a substitute for the transaction's other evidence requirements.
How should the initial response be handled?
Cobalt's initial contractor-search example acknowledges that the completed result will be sent to the callback URL.[8] Keep the review pending until the required evidence arrives and is evaluated.
What should a reconciliation record look like?
The following is illustrative customer-side data, not a Cobalt response. It separates the source record from the lender's unresolved question.
{
"transaction_role": "licensed_performer",
"current_entity_reference": "synthetic-current-entity",
"prior_entity_reference": "synthetic-prior-entity",
"license_source_reference": "retained-license-record",
"entity_change_observed": true,
"number_continuity_explained": false,
"review_state": "current_license_association_required"
}The important behavior is that an unchanged number does not automatically set the final state to approved. The current association and any necessary explanation must be supported separately.
What should the reviewer know about reassignment exceptions?
Use the controlling statute and current CSLB process for the specific situation. Section 7075.1 lists several conditions involving corporations, LLCs and certain family-business circumstances.[9] Do not present a short overview's examples as an exhaustive legal test.
The lender's task is to obtain and evaluate the evidence relevant to its decision. It should not infer that a reassignment occurred simply because the proposed facts resemble one statutory condition.
What should a claim of reassignment trigger?
Request the current source record and the documentation appropriate to establish the claimed association. Record the source, date and responsible reviewer. If interpretation of eligibility is necessary, identify that legal question and route it to the proper owner.
Why is the qualifying individual insufficient by itself?
CSLB's guidance ties the license to the business entity, not merely to the person who qualifies it.[10] Continued involvement by the same individual therefore cannot replace evidence about the licensed business.
Likewise, the presence of a bond or an unchanged address should not be used as a shortcut for the entity association. Review each piece of evidence for the question it actually answers.
Our guide to why an active contractor license is not enough for construction lending addresses broader project-fit questions. This article isolates the entity-change problem so it does not disappear inside a generic active-license check.
What does a worked entity-change review look like?
Consider a hypothetical equipment-finance application in which the earlier file names a sole proprietor but the current contract names a newly formed LLC. The applicant supplies the same license number and says the business is otherwise unchanged. This is an illustrative scenario, not a customer case.
The analyst identifies the current borrower and licensed performer, obtains the current license record and compares its business identity with the transaction documents. If the source still identifies the earlier business, the application needs evidence resolving that difference before the relevant condition can close.
What if the number was properly reassigned?
Retain the current source record and supporting explanation, then have the responsible reviewer determine whether the evidence meets the transaction's requirement. Preserve the earlier license association as history rather than overwriting it.
The same number may appear in both records, but the review still needs to explain why it belongs to the current entity for the current purpose. Number continuity is an observation; the accepted association is a supported review conclusion.
What if only the corporate name changed?
Confirm that the supporting records show a name change rather than a new registration identity. CSLB's name-change guidance explains that a Secretary of State update and the CSLB update are separate steps.[11]
A lag or discrepancy should be described accurately and resolved through the applicable evidence process. Do not automatically classify it as misconduct or automatically ignore it because the applicant has borrowed before.
A familiar license number is a starting reference. The current licensed business is the fact the review must establish.
How should the process handle draws and renewals?
Apply the evidence requirement at the decision stage your policy specifies. A prior loan approval, a later draw and a renewal can involve different documents or transaction parties. Do not assume the first license review covers every later entity change.
Use a trigger that identifies a relevant change in the application or transaction records. Keep the trigger explicit so operations can distinguish a material entity event from a spelling correction or an internal note update.
What should be reused?
Retain prior source records and the reasoning that remains relevant. Obtain the current evidence needed to establish the licensed party for the new decision. A historical association can help target the review without being treated as a current assurance.
Cobalt's SOS API can search by a registry identifier and state, providing another source record for the business-identity side of the review.[12] Keep that registry evidence separate from the contractor-license record; they answer related but different questions.
What should the handoff note contain?
Identify the changed entity, current transaction role, source license record, unresolved association and next action. If an authorized owner permits limited work to continue, state that scope and retain the outstanding condition.
The pre-funding business-verification framework provides a broader structure for these evidence conditions. An entity-change review should resolve its own requirement without silently closing unrelated checks.
What should you test and verify before rollout?
Test a genuine name-only change, a new entity with a different number, a new entity claiming the same number, an unchanged qualifier, and a transaction where the borrower and licensed performer legitimately differ. Use synthetic records and expected reviewer actions.
Which incorrect conclusions should the tests prevent?
The workflow should not infer that an active status resolves identity, that a familiar number proves continuity, or that a changed name always means an unlicensed business. It should direct the reviewer to the missing evidence and preserve the original source values.
Also test a delayed callback and a response tied to an earlier application revision. The completed record must reach the correct review rather than overwriting a corrected transaction party.
What should a Cobalt evaluation establish?
Confirm the California search route, actual returned entity and license fields, callback handling and source references. The documented contractor response exposes data for review; it does not approve a transfer or reassignment.[13]
Bring a permitted entity-change scenario to a Cobalt demo. The goal is to establish how the current source records can support your lender's reconciliation, and where an official licensing record or specialist decision remains necessary.
.jpg){kind=small}
.png)