How to Say No to Work Outside Your Licence

Why this matters

The decision to stay inside your licence is easy in the office and hard in a customer's hallway, with a technician who could genuinely do the work standing next to a customer who is already frustrated. Shops do not lose this on principle. They lose it on wording, because nobody decided in advance what the sentence was, and an improvised refusal sounds like reluctance rather than a fact.

There is a second payoff most shops miss. Every decline is a data point about demand for a credential you do not hold, and a shop that logs them turns a year of awkward conversations into the business case for the next credential it buys.

Step 1: Draw the line before the phone rings

Write a standing list of the work actions your shop declines on licence grounds. Actions, not job types: originate a new branch circuit, alter a gas line, replace a water heater's potable connections, cut a structural opening. Whatever your scope statement excludes. See related: The Scope a Credential Actually Authorizes.

Put the list where dispatch and the technicians can see it, and put the name of the referral partner next to each line. A decline with a name attached is a service. A decline without one is a dead end, and it is the version that gets talked around on site.

Step 2: Know which no you are giving

Two different refusals get delivered in the same tone and they should not be:

• "We do not do that" is a business choice. You could, you are authorized, you have decided not to. Negotiable in principle, and the customer can reasonably ask why.
• "We are not licensed for that" is a fact about authorization. Not negotiable by you, by your owner, or by the customer, and the customer cannot buy their way past it.

Say which one you are giving. Blurring them trains customers to push on the second kind, because they have heard the first kind soften before.

Step 3: The words

State it as a fact about the work, then about your classification, then hand them the next step. Three short sentences, in that order:

"That work needs an electrical contractor's licence. We hold the mechanical classification, so it is outside what we can perform. I can give you two names, and I can still handle the rest of what you called about."

The order matters. Leading with the work rather than with yourself keeps it from sounding like a personal limitation, and closing on what you can still do stops the call from ending as a refusal.

Four phrasings to drop, because each one invites a negotiation:

• "I'm not allowed to." Puts an absent authority in the room and invites the customer to argue with it through you.
• "Technically we can't." The word "technically" tells the customer this is a formality you might waive.
• "I could, but..." Concedes capability and reframes a legal boundary as reluctance. It is the single most common way this goes wrong, and it is usually said out of pride.
• Apologizing for the requirement. "I'm sorry, they make us..." positions you and the customer on the same side against the rule, which is exactly the alliance you do not want when the next sentence is "so can you just..."

Say it once, plainly, and stop talking. Filling the silence is where technicians talk themselves into it.

Step 4: Find the partial yes before you decline anything

Decline the action, never the job, and check for the partial yes first. Most mixed requests split cleanly, and the split is usually lopsided in your favour because the gated item is typically the small add-on rather than the headline work.

Scope the partial yes explicitly, in writing, including where your work stops and what has to happen before it can start. "We will set and connect the unit at the existing disconnect. The new circuit has to be in and inspected first, by the electrical contractor" is a sequence the customer can act on. "We'll do our part" is not.

Step 5: Hand off so the relationship survives

A referral is only worth giving if it holds up. Three standards:

• Two names, not one. One name reads as a business arrangement and leaves the customer stuck if that contractor is booked.
• Verified, not remembered. Check that the partner's licence is current before you hand out the name, the same way you would want yours checked. See related: How to Verify a Credential Someone Claims to Hold.
• Warm where it matters. On a job where sequencing matters, call the partner yourself and set the order of operations, because a customer coordinating two trades will get the sequence wrong and the delay will attach to whoever they spoke to last.

Then follow up. A shop that calls a week later to ask whether the other trade got out has spent five minutes to stay the primary relationship on that account.

Step 6: Log the decline, and read the log

Record every licence-based decline: the date, the customer, the action declined, the credential it needed, and whether the customer was an existing account. Two reasons, one defensive and one offensive.

Defensively, a written record that you identified the requirement and named it is what separates you from the outfit that did the work anyway, if the customer hires someone unqualified and it goes badly.

Offensively, the log is a demand signal, and here is the rule for reading it. Unit of analysis: one credential line, counted over a rolling twelve months. A missing credential becomes a candidate for acquisition when declines attributable to it reach 6 or more in the rolling twelve months and at least 3 of those requests came from customers you already serve. Both conditions, not either, because raw volume can come entirely from strangers who called once, and existing-customer demand is the part that also protects the accounts you have. Step size: one credential added per coverage review cycle, never a batch, because acquisition capacity is the constraint and a plan that starts three at once finishes none of them. Feed candidates into the coverage review rather than acting on them mid-year. See related: The Credential Coverage Review SOP.

Step 7: The pushback lines and what they are actually asking

Four you will hear, with what is behind each:

"The last guy did it." Possibly he was licensed for it. Possibly he is the reason you were called. Do not litigate it: "He may have held that licence. We don't, so I can't."

"We'll pull the permit under our licence, just do the work." Usually from a general contractor or a property manager, and it is the most dangerous one because it sounds like a solution. A permit pulled under someone else's licence does not authorize you to perform work outside yours. The permit records who is responsible for the project; it does not extend anyone's classification to you.

"Just leave it off the invoice." They are offering to hide the record they can see. The records that matter are the ones they cannot: the inspection, the eventual insurance claim, the next contractor who opens the wall and photographs it, and the customer's own phone.

"It's a five-minute job." Duration is not one of the axes any scope statement is bounded on. It is bounded on the work, the system, the magnitude and the role. Say that plainly and it usually ends the conversation, because it is obviously true once stated.

Worked example: one call, and a year of the log

A homeowner calls about a failing unit and wants five things: the unit replaced, the existing disconnect reused, a condensate line rerouted, the thermostat replaced, and the electrical panel upgraded while everyone is there.

Four of the five are inside the mechanical classification. The panel upgrade is not. The technician gives the three sentences, scopes the partial yes in writing including the note that the panel work should be scheduled either well before or well after the changeout rather than the same week, and hands over two verified electrical contractors. The job books at 4 of 5 items, the customer books the panel separately, and the shop calls the electrical contractor to set the order.

Now the log, read at year end. Seventeen licence-based declines across three credential lines:

Run each row against the rule rather than against instinct. The electrical row clears both conditions, 11 against a floor of 6 and 7 against a floor of 3, and becomes the single candidate carried into the coverage review under the one-per-cycle step size.

The gas row is the interesting one and it needs to be reported honestly: it fails the rule, on count, at 4 against a floor of 6. It fails despite having the highest existing-customer share of the three at 3 of 4, which is the number that makes people want to promote it. Under the rule as written it is tracked, not actioned. If that feels wrong, the argument belongs at the review where the gate gets set, not at the row where it is inconvenient. A threshold you renegotiate per row is not a threshold.

The structural row fails both conditions and is noise: two strangers, once each.

Note what the log produced that a year of conversations would not have. Not a feeling that "people keep asking us for electrical." A count, a base, and one candidate.

How to verify you got this right

The consistency check. Ask three technicians, separately, what they say when asked to do one specific action on your decline list. If you get three different answers, step 1 exists on paper only, and the softest of the three answers is the one your customers are hearing.

The log completeness check. Compare the decline count against your quote records for the same period. Declines that never made it into a quote record usually never made it into the log either, and the on-site verbal decline is exactly the one worth capturing.

The referral audit. Pick five referrals you gave last quarter and confirm the partner's licence was current on the day you gave the name. A stale referral list transfers your credibility to somebody who has stopped maintaining theirs.

The partial-yes rate. Across your declines, count how many kept some scope. If most declines lost the whole job, step 4 is not running and you are declining jobs when you only needed to decline actions.

References

• Your state or local licensing statute, for the classification scope that defines which actions you may perform and which require another licence holder
• Your permit office, for confirmation that a permit issued to one licence holder does not extend authorization to another party performing the work
• See related: The Scope a Credential Actually Authorizes, How to Check a Job Against Your Credentials Before You Quote, The Credential Coverage Review SOP, How to Verify a Credential Someone Claims to Hold