How to Figure Out What You Actually Need to Hold

Why this matters

Most shops assemble their credentials by accretion. Something was needed once, somebody got it, it renews on autopilot, and nobody has ever asked whether the current mix matches the work the shop actually sells today. That produces two failures at the same time: paying to renew something no job requires, and performing a scope nobody in the building is credentialed for, usually a scope that was added a couple of years ago by saying yes to a good customer.

This is the audit that fixes both. It takes an afternoon for a small shop, produces a grid you can re-run whenever the business changes, and ends with a register rather than a feeling.

Step 1: Write your scope list in the statute's language

List what you actually sell, then rewrite each line the way a licensing statute would describe it. "Maintenance plans" is a marketing name. "Periodic inspection and consumable replacement on an existing system, without alteration" is a scope. "Bathroom remodels" is a package. "Alteration of existing supply and waste piping within a structure" is a scope.

This rewrite is the whole step and it is the one people skip. Licensing statutes gate defined acts. If your list is written in package names, every later comparison against a class definition becomes a judgment call, and judgment calls made by the person who wants to sell the job all resolve the same way.

Step 2: Map every place you perform work, in layers

Jurisdiction is not one line on a map, it is a stack. For each area where you actually put a truck, write down the state, the county, the incorporated city or town if the address is inside one, and any special district with its own authority. The service address decides this, never the customer's billing address and never your office address.

Pay attention to unincorporated pockets. A county service area that looks uniform on a dispatch map frequently contains addresses inside a city boundary with its own registration requirement and its own inspector.

Step 3: Build the grid and ask one question per cell

Scopes down the side, areas across the top. In each cell, answer exactly one question: what must be held, by whom, before this scope may lawfully be performed at an address in this area?

One question per cell keeps the audit honest. The temptation is to answer "do we have a problem here," which the mind resolves optimistically. "What must be held" has to be answered with a named credential or a "nothing," and "nothing" is an answer you will want to source.

Step 4: Split every requirement into entity-level and person-level

The same grid produces two different registers. An entity requirement travels with the company and fails once, for everyone. A person requirement travels with an individual and fails for that person's assignments only, unless that individual is the qualifier the entity credential hangs on, in which case it fails for everyone with a one-step delay.

Write which one each requirement is at the moment you record it. Retrofitting this later is unreliable because the credential names rarely tell you.

Step 5: Sort by consequence, not by name

Four classes, in descending severity:

• Required to perform. Without it the work is unlawful.
• Required to be paid. The work may be lawful, but a filing gap can bar you from enforcing the contract, perfecting a lien, or invoicing at all.
• Required to bid. Public work, prequalification programs, and some prime contractors gate the bid rather than the work.
• Required by contract. A specific customer made it a condition. It binds you to that customer only, and it disappears when the contract does.

The class decides how hard you chase a gap, and it is not predictable from whether the item is named a license, a certification, or a registration.

Step 6: Find the exemption edges before you rely on them

Almost every licensing scheme carves something out. The common shapes are a monetary threshold below which no credential is required, a routine-maintenance or repair carve-out that excludes alteration, an owner-occupant exemption, and an employee-of-the-property-owner exemption. Where these exist, they are drafted narrowly and defined by the physical work, not by the intent or the billing arrangement.

Two habits keep you out of trouble. First, read the exemption text itself rather than a summary of it, because the operative words are usually a list of what does not count. Second, never let a threshold exemption be evaluated by the salesperson, because a job priced just under a threshold is exactly the job that grows once the wall is open.

Step 7: Add the federal overlays that attach to the work, not the map

Some requirements ignore your jurisdiction grid entirely because they attach to the work or the property. Two that reach a large share of residential trades:

• Refrigerant handling. Under the EPA's Section 608 program, a technician must hold the appropriate certification type to open a system containing a regulated refrigerant or to purchase that refrigerant. It is federal, it is person-level, and it does not expire.
• Lead-safe renovation. Under 40 CFR Part 745 Subpart E, a firm performing renovation, repair, or painting for compensation that disturbs painted surfaces in housing or a child-occupied facility built before 1978 must be a certified firm and must use a certified renovator. The rule's minor repair and maintenance carve-out applies where the work disturbs 6 square feet or less of interior painted surface per room, or 20 square feet or less on the exterior, and does not involve window replacement, demolition of painted surface areas, or the practices the rule prohibits.

Note the shape of both: they are triggered by a physical condition on a specific job, so they cannot be answered by the grid's columns. They get their own row and a per-job trigger question.

Step 8: Get the ambiguous cells answered in writing

Some cells will not resolve from published material. Write the question with the scope in statute language, the exact address layer, and who would perform the work, then send it to the administering body and keep the reply. A written answer from the body that enforces the rule is not a guarantee, but it is a different conversation with an inspector than "somebody told us on the phone."

Step 9: Turn the grid into register rows

One row per requirement, with the issuing authority, whether it is entity or person-level, the consequence class from step 5, the holder, the expiry or "no expiry," and one named owner responsible for its renewal. A grid that stays a grid gets stale. A register with owners and dates is what the expiry cadence runs on.

Step 10: Re-run on a trigger, not a calendar

Re-run the grid when you add a scope, add a service area, lose the qualifying individual, or take a job type you have never taken. An annual re-run catches nothing, because the change that creates exposure is a yes said in March and the annual review happens in December.

Worked example: eighteen cells, seven requirements, three gaps

A residential shop with six service lines expanded into a second service area last year and a third this spring. Six scopes across three areas gives 18 cells.

The 18 cells collapsed to 7 distinct requirements, because most cells produce the same answer. Sorted by level: 4 entity-level and 3 person-level.

Four of seven were already held. Three were not, and the three gaps behaved very differently.

The missing business registration in the third service area touched all six scopes in that one column, which is 6 of the 18 cells - one modest filing darkening a third of the grid. It was not a stop-work item in that jurisdiction, but it sat in the required-to-be-paid class, which is the class that turns into a collections problem rather than an inspection problem.

The two lead-safe gaps touched a single scope, but that scope crossed all three areas and represented a meaningful share of the shop's residential renovation revenue. They were required-to-perform, and the trigger was the property, not the map: pre-1978 housing, compensated work, painted surfaces disturbed above the minor repair and maintenance carve-out. The shop's honest answer to "how many of last year's jobs met that trigger" was that nobody had ever asked the question at intake, which is itself the finding.

The remediation split by lead time. The registration was a filing. The firm certification had a published processing window at the administering authority, so the shop stopped selling that scope on pre-1978 properties until the certification issued, and put the trigger question - year built, painted surfaces disturbed, square footage - into the intake script so the answer stops depending on which estimator takes the call.

Verifying you did this right

Three checks, in order:

Every cell has a named source. Not "we believe," a named body, a published class definition, or a written answer. A grid full of confident blanks is the same document you started with.

Every scope line survives being read to an inspector. Read your step 1 rewrite aloud and ask whether an inspector would recognise the act you described. If the line still contains a package name, the cell under it was never really answered.

The gaps have owners and dates. A gap found and not assigned is worse than a gap not found, because the next person who reviews the file will see it listed and assume somebody is on it.

The field failure this whole procedure prevents is narrow and specific: a shop that has been doing a scope competently and safely for years, on a credential that covers most of what it does but not that scope, discovering it at the moment a customer's insurer asks who performed the work. Nothing about the work was bad. The paperwork answer was simply never assembled, and it cannot be assembled retroactively.

References

• U.S. EPA, 40 CFR Part 745 Subpart E, Renovation, Repair and Painting rule, for firm certification, certified renovator requirements, and the minor repair and maintenance carve-out
• U.S. EPA, Section 608 technician certification under the refrigerant management program
• The state licensing board and each local business registration office for the areas where work is performed, for class definitions and local filing requirements
• See related: Who Administers What and Where to Ask; The Difference Between a License, a Certification, and a Registration; The License and Bonding Requirements That Vary by Jurisdiction