1. Match the contracting business
Compare the proposal's legal business name with the official record. Resolve similar names, DBAs and qualifier relationships instead of assuming a personal license belongs to the company. Hawaii's entity–RME guidance illustrates why the relationship matters.
2. Read the credential type
License, contractor registration, business registration and bond filing are distinct. A business name inferred to be a trade does not establish a trade credential. Minnesota's mechanical bond guidance is one example of a record that should not be called a state mechanical license.
3. Match the work
Read the classification or endorsement, not just an active label. Oregon's endorsement chart shows why residential versus commercial scope requires more care than a two-word label.
4. Check the jurisdiction
A city record is not statewide authority. Ask the project jurisdiction about local requirements and permits, and use the relevant state guide for the authority split.
5. Recheck current status
A roster snapshot or old certificate is not a current status check. Save the official result and date before committing. Resolve unfamiliar status codes with the issuer; do not infer work eligibility from the word active embedded in a longer label.
6. Verify insurance separately
Ask for current evidence and confirm project-specific coverage questions with the insurer. Neither a license nor a bond is a universal guarantee that a loss will be paid.
7. Read the record's limits
Public complaint history may be incomplete, and allegations are not findings. Read actual orders and dates. A blank field, no search result or unavailable portal must not be presented as a successful check.
8. Resolve mismatches before signing
Get a written scope, identify who will perform regulated portions, and clarify conflicting evidence with the authority. This checklist is an investigation aid, not a finding that a contractor broke the law or that a particular contract is enforceable.
Keep the result as a decision record
Use separate fields for the contracting entity, issuer, credential number, type, classification, status, date checked, project jurisdiction and outstanding questions. Link the supporting record to each conclusion. Avoid one blanket “verified” checkbox that conceals missing scope or insurance checks.
Classify the next action as resolved for this question, clarification needed, or source unavailable. A resolved identity match still leaves the work-scope question open if the classification is missing. If the project changes, review the affected scope again rather than copying the previous conclusion.
Example: a matching name is only the first step
Illustrative example: the business name matches, the credential is current, but the quote includes a trade outside the displayed scope. Save the successful identity check, ask who will perform that trade, and verify the relevant credential. Do not dismiss the mismatch because other checks passed.
Likewise, if an official portal is down, tell the contractor which evidence remains outstanding and return to the issuer when available. An outage should delay the conclusion, not become either a favorable certification or an accusation of unlicensed work.