Business Risk Cue
A choice that increases financial, legal, or operational exposure if left unaddressed.
Project 03
Research, verify, and organize one jurisdiction-specific contractor licensing and registration file — authorities, classifications, qualifications, applications, local registrations, renewals, restrictions, and stop-work controls — that will govern which services from the Chapter 1 model may actually be advertised, bid, or performed.
These cues appear at the point of work. They identify compliance, professional-review, jurisdictional, and documentation issues before an unlicensed or unverified commitment is made.
A choice that increases financial, legal, or operational exposure if left unaddressed.
An action that must not be taken, or must be stopped, until a specific licensing or regulatory condition is satisfied.
Practical controls that keep the licensing file accurate as applications and renewals actually occur.
Requirements vary by state, county, and municipality. Verify current requirements directly with the authority before relying on this chapter.
A point where an attorney, licensing consultant, or the licensing authority itself must be consulted before proceeding.
A decision, deadline, or figure that must be written down, dated, and retained in the company record system.
This project produces one written, verified contractor licensing and registration file for every jurisdiction named on the Chapter 1 service-area and project-fit matrix. The finished work product is a license-requirement matrix cross-referenced by jurisdiction, service, classification, authority, qualification, fee, bond, insurance, and renewal, supported by an application document checklist, an experience and project-history file, an examination-preparation plan where an exam is required, a financial and background submission plan, a renewal calendar, a license-status verification procedure, and a stop-work procedure.
You will identify the official contractor, trade, business, tax, permit, and consumer-protection authorities for each jurisdiction in the approved service area; match the Chapter 1 service menu against available license classifications; identify scope, monetary, employee, and subcontracting limits; identify work that requires a separately licensed trade professional; gather official applications and instructions; submit applications only after ownership, insurance, and bond information are reconciled; and build the renewal and stop-work controls that keep the business operating on active authority.
This project narrows the Chapter 1 business model to only the services and jurisdictions the business is actually authorized to perform. Chapters 4 through 20 — insurance, banking, pricing, contracts, marketing, and the capstone operating system — all reference the active service and jurisdiction list approved at the end of this project.
This project builds directly on the approved Chapter 1 Business Model Statement and the professionally reviewed structure and company record system created in Chapter 2. The jurisdiction list, service menu, and ownership information gathered in those chapters are the direct inputs to the licensing research performed here.
This project sits ahead of every chapter that depends on active legal authority to operate: the insurance and bonding file in Chapter 4 is matched to the classifications confirmed here, the pricing worksheet in Chapter 7 and every proposal in Chapter 8 may reference only license numbers actually issued, the contract scope in Chapter 9 must respect the scope and monetary limits identified here, and no marketing claim in Chapter 17 may state "licensed" for a jurisdiction or service not confirmed active in this file. The capstone operating system in Chapter 20 verifies this file directly before authorizing limited launch.
This project covers:
This project does not authorize the learner to:
Any service or jurisdiction that cannot be supported by a currently active license, registration, or permit-holder status must be removed from the active service and jurisdiction list before contracting proceeds.
Establish these references before drafting the matrix, and do not change their meaning mid-document.
| Term | Definition |
|---|---|
| Licensing authority | The official state, county, or municipal board or agency that issues and enforces the contractor, trade, or business license or registration in question |
| Classification | The specific license category (general, residential, specialty, trade, salesperson, qualifier, or local registration) that authorizes a defined scope of work |
| Qualifier / responsible managing individual | The individual whose experience, examination, or credentials satisfy the licensing authority's qualification requirement for the business entity |
| Scope limit | The monetary, project-type, employee, or subcontracting boundary attached to a classification |
| Local registration | A business license, tax registration, or contractor-registration requirement imposed by a county or municipality in addition to state-level licensing |
| Permit-holder | The person or entity legally authorized to pull a building or trade permit for a given project |
| Active status | A license or registration currently issued, unexpired, unsuspended, and confirmed through the issuing authority's verification system |
| License-requirement matrix | The single approved document produced by this chapter cross-referencing jurisdiction, service, classification, authority, qualification, fee, bond, insurance, and renewal |
Before research begins, record the following directly on the license-requirement matrix template:
Company legal name: ______ Entity type: ______ Qualifier / RMI: ______
Date started: ____________ Target completion date: ____________ Reviewing professional(s): ____________
Every candidate service in the Chapter 1 model is only as authorized as the license or registration standing behind it. This project builds the single reference — the license-requirement matrix — that every future proposal, contract, permit application, and marketing statement in this book must check against before relying on a claim of "licensed" in a given jurisdiction.
A candidate service is only marked "supported" on the matrix after the specific classification, scope limit, and qualification requirement have been confirmed directly through the issuing authority's official source. A classification confirmed only through a third-party summary, a competitor's advertisement, or an out-of-date bulletin is marked "unconfirmed" and re-verified before reliance.
For every fee, classification, scope limit, exam requirement, and renewal period recorded on the matrix, record the official source (agency name, publication, or statute/rule citation) and the date it was retrieved. Do not record a requirement without its source; an undated, unsourced entry cannot be trusted at renewal time.
Do not advertise, quote, bid, or accept payment for any service until its license or registration is confirmed active by the issuing authority's verification system. A submitted application is not an active license, and a passed examination is not an issued license.
Maintain a single controlled copy of the license-requirement matrix in the Chapter 2 company record system. Do not allow separate, informal notes about license status to circulate among sales, estimating, or field personnel. Every proposal and contract in later chapters must reference the single approved copy.
When a service could plausibly fall under more than one classification, when a project size approaches a monetary limit, or when a local registration requirement is unclear, route the specific question to a qualified licensing advisor or attorney before marking the matrix "supported." Do not resolve the ambiguity by assumption.
PC-013 – PC-018
Compliance Research / Regulatory Qualification
Quantity: one approved license-requirement matrix, one application document checklist, one experience and project-history file, one examination-preparation plan (where an exam is required), one financial/bond/background submission plan, one renewal calendar, one license-status verification procedure, and one stop-work procedure — each dated and reviewed by at least one qualified professional where ambiguity required it.
| Document | Quantity | Format | Content Required | Preparation / Purpose |
|---|---|---|---|---|
| License-Requirement Matrix | 1 | Table, by jurisdiction and service | Authority, classification, scope limit, qualification, fee, bond, insurance, renewal period, official source | The single controlling reference for every later chapter |
| Application Document Checklist | 1 per classification | Checklist | Required forms, identification, ownership, experience, financial, and background documents | Ensures a complete submission on first filing |
| Experience and Project-History File | 1 | Structured file | Owner and qualifier work history supporting classification eligibility | Supports application and, where required, exam-waiver review |
| Renewal Calendar | 1 | Calendar / log | Renewal date, responsible person, advance-notice period, continuing-education and fee requirements | Prevents unnoticed license or registration lapse |
| License-Status Verification Procedure | 1 | Procedure | Steps to confirm active status before a proposal, contract, or permit application | Used before every contract commitment across the book |
| Stop-Work Procedure | 1 | Procedure | Response to suspension, lapse, qualifier departure, or disciplinary action | Prevents continued unauthorized operation |
| Check | Standard |
|---|---|
| Authority identification | Every jurisdiction has its official contractor, trade, business, tax, permit, and consumer-protection authorities identified with current contact information |
| Classification match | Every service in the Chapter 1 model is matched to a specific classification, with scope, monetary, and subcontracting limits recorded and sourced |
| Separately licensed work | Work requiring an electrician, plumber, HVAC technician, engineer, architect, or environmental contractor is identified and excluded from self-performed scope |
| Application completeness | Every application document checklist item is confirmed against the official source, not a third-party summary |
| Renewal control | Every license and registration has a renewal date, responsible person, and advance-notice period recorded on the calendar |
| Stop-work readiness | A stop-work procedure exists and names the trigger conditions and required response |
| Professional review | Ambiguous classification, scope, or local-requirement questions are documented as resolved by a qualified reviewer |
Inspect the completed licensing file using the same checks regardless of which jurisdiction or classification is involved.
Complete the Licensing File Approval Worksheet in the Inspection Checklist section below before beginning Project 04.
Probable cause: the license-requirement matrix was not checked before the proposal template was populated, or a pending application was treated as active.
Confirmation: compare the proposed service and jurisdiction against the license-requirement matrix's confirmed-active column.
Correction: withdraw or revise the proposal to remove the unlicensed service, and route future proposals through the license-status verification procedure before issuance.
Reinspection: repeat the authority check on the corrected proposal and matrix.
Probable cause: the renewal calendar was not created at the same time as the matrix, or a reminder was set too close to the expiration date.
Confirmation: compare the license's actual expiration date against the renewal calendar's reminder date and responsible person.
Correction: immediately trigger the stop-work procedure for any lapsed license, renew as soon as legally possible, and rebuild the calendar entry with an earlier reminder.
Reinspection: repeat the renewal check across every license and registration on the calendar.
Probable cause: the classification was matched from a third-party summary or a similar business's advertisement rather than the official source.
Confirmation: re-verify the classification and its scope limit directly with the issuing authority.
Correction: correct the matrix entry, remove the service from the active list until the correct classification is held, and apply for the correct classification if it differs from what is currently issued.
Reinspection: repeat the classification-match check on the corrected matrix.
Probable cause: the application was filed before legal name, entity type, ownership, or qualifier information was reconciled with the Chapter 2 company record.
Confirmation: compare every field on the rejected application against the Chapter 2 formation and ownership documents.
Correction: correct the mismatched fields, resubmit with the complete application document checklist attached, and record the deficiency notice and response in the company record system.
Reinspection: repeat the application-completeness check before the next submission.
Probable cause: a customer, referral, or opportunity in a new jurisdiction was accepted without confirming that jurisdiction's licensing and registration requirements.
Confirmation: compare the project address against the jurisdiction list on the license-requirement matrix.
Correction: stop work in the unlisted jurisdiction under the stop-work procedure until Sections E through H are completed and confirmed for that jurisdiction.
Reinspection: repeat the authority and classification checks on the updated matrix before resuming work.
Probable cause: a classification, scope limit, or local-registration question was left unresolved to meet an internal deadline.
Confirmation: check the matrix for any entry marked "unconfirmed" or lacking a sourced answer.
Correction: suspend reliance on the affected service or jurisdiction until a qualified licensing advisor or attorney resolves the question and the matrix is updated.
Reinspection: repeat the professional-review check before re-approving the matrix.
This project ends with the approved documents filed for reuse, not left as informal notes.
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PC-013 | Identifies the official licensing authorities for every jurisdiction in the approved service area, with current contact information recorded | |||
| PC-014 | Matches every Chapter 1 service to a specific license classification with sourced scope, monetary, and subcontracting limits | |||
| PC-015 | Identifies local business, registration, and permit-holder rules that apply in addition to state or trade licensing | |||
| PC-016 | Identifies examination, experience, financial, background, and bond requirements attached to each classification and prepares the corresponding submission plan | |||
| PC-017 | Builds a renewal calendar with a renewal date, responsible person, and advance-notice reminder for every license and registration | |||
| PC-018 | Produces an approved compliance checklist and stop-work procedure naming trigger conditions and required responses, filed in the company record system |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
| Item | Standard | Complete (Y/N) | Notes / Correction |
|---|---|---|---|
| Jurisdiction and authority list | Recorded per Section E, with current contact information | ||
| Classification matching | Every Chapter 1 service matched to a sourced classification and scope limit | ||
| Separately licensed work identified | Trade-specific exclusions recorded and cross-referenced | ||
| Application document checklist | Every required document sourced to the official authority | ||
| Experience and project-history file | Compiled in the authority's required format | ||
| Examination-preparation plan | Completed where an exam is required | ||
| Financial, bond, and background submission plan | Every required submission listed with a responsible preparer | ||
| Renewal calendar | Every license and registration has a renewal date, reminder, and responsible person | ||
| License-status verification procedure | Steps defined for use before every proposal and contract | ||
| Stop-work procedure | Trigger conditions and required response named | ||
| Professional review completed | Reviewer named; comments recorded and addressed |
Licensing file declared complete: ______ (Pass/Fail) Date: ____________ Owner name: ____________
Reviewing professional: ____________ Next scheduled review date: ____________
With all six documents completed, review the finished licensing file against the Acceptance Standards table and confirm every jurisdiction's authorities are identified, every service is matched to a sourced classification and scope limit, separately licensed work is excluded from self-performed scope, the application document checklist and supporting files are complete and sourced to official authorities, the renewal calendar names a date, reminder, and responsible person for every license, the license-status verification and stop-work procedures are written and specific, and at least one qualified professional has reviewed and the owner has addressed their comments where ambiguity required it. Complete the Licensing File Approval Worksheet and correct any failed item before beginning Project 04. If an item fails, identify whether the gap is in authority identification, classification matching, application completeness, renewal control, stop-work readiness, or professional review before revising the file.
You have completed the third project in the professional-contractor sequence: researching licensing, registration, and local contractor requirements. This project required you to identify the licensing authorities governing your service area (PC-013), match your service menu to specific license classifications (PC-014), identify local registration and permit-holder rules (PC-015), identify examination, experience, financial, background, and bond requirements (PC-016), track application and renewal deadlines on a controlled calendar (PC-017), and create and approve a compliance checklist and stop-work procedure (PC-018).
You now have one approved license-requirement matrix, an application document checklist, an experience and project-history file, an examination-preparation plan, a financial and bond submission plan, a renewal calendar, a license-status verification procedure, and a stop-work procedure. This file carries directly into the next project: building the insurance, bonding, and risk-management file that must be matched to the exact services, classifications, and jurisdictions confirmed here.
Store your approved license-requirement matrix and its supporting documents in a secure, controlled location. You will verify license status against this exact file before every proposal, contract, and permit application in the remaining chapters of this book.