First Responder, Military, and Senior Discounts.
First Responder, Military, and Senior Discounts.
HVAC technicians are expected to know HVAC.
They are not expected to know everything.
Modern HVAC equipment includes:
Eventually, every technician will encounter something they do not know.
At Klein Cooling, this is acceptable:
“I don’t know yet.”
This is not:
Pretending that you do.
You are allowed to not know.
You are not allowed to make shit up.
There is an important word attached to the Klein Cooling version of “I don’t know.”
“I don’t know yet, but I’m going to figure it out.”
That may mean:
“I don’t know” does not mean:
Shrug and leave.
It means:
Stop guessing and start finding out.
This is where technicians get themselves in trouble.
The customer asks:
“What’s that code mean?”
You don’t know.
There are two available responses.
“That’s a communication fault between the indoor and outdoor control modules caused by the inverter board.”
Sounds impressive.
Also completely invented.
“I’m not sure what that code means on this model. Let me look it up.”
Use Response B.
Every time.
Technicians sometimes confuse confidence with competence.
They are not the same thing.
You can say something incorrect:
very confidently.
The equipment remains unimpressed.
Do not increase your certainty simply because the customer asks:
“Are you sure?”
If you’re not sure:
Say so.
“That’s what I’m investigating. I don’t have enough evidence yet to tell you that.”
That answer is infinitely better than confidently selling a repair that does not solve the problem.
Confidence should follow evidence.
Evidence should not be invented to support confidence.
You may remember:
“I think that code means discharge temperature.”
Fine.
Check.
You may remember:
“I think that DIP switch should be ON.”
Fine.
Check.
You may remember:
“I’m pretty sure this model energizes O in cooling.”
Excellent.
Check.
Manufacturer literature exists specifically because nobody should be expected to memorize every control strategy used on every piece of HVAC equipment ever manufactured.
Use it.
This should not be controversial.
If you do not understand how the equipment operates:
Read the manual.
If you do not know what an error code means:
Read the manual.
If you do not know the required airflow configuration:
Read the manual.
If you do not know what a switch setting does:
Read the manual.
If you do not know the manufacturer’s diagnostic procedure:
You can probably guess where this is going.
There is no additional compensation awarded for diagnosing equipment without instructions.
Manufacturers place wiring diagrams on equipment for a reason.
Use them.
When diagnosing electrical and control problems:
Do not stare at a bundle of wires and announce:
“Something’s not sending power.”
Wonderful.
Which thing?
To where?
Under what condition?
At what voltage?
Follow the diagram.
Calling manufacturer technical support does not mean:
You failed.
It means:
You are using an available technical resource.
Before calling, however, do your homework.
Have relevant information ready:
Do not call technical support and say:
“It’s not working. What do you think?”
They were not hiding behind the condenser watching the call.
Give them data.
Technical support can be extremely valuable.
It also does not eliminate the need to think.
If technical support recommends a test:
Perform the test.
If they provide a specification:
Compare your measurement.
If they recommend a component based on information you supplied:
Make sure the information you supplied was accurate.
Do not document:
Tech support says board.
Document the relevant testing and findings that support the diagnosis.
Tech support is a resource.
It is not a Ouija board.
Sometimes another technician has seen the exact problem before.
Ask.
Send:
Not:
Bro wtf is this
followed by seven blurry photographs.
Although internally, we understand the emotion.
Give enough information for someone to help.
Yes.
Call Kevin.
But before calling:
Have measurements.
Good:
“3-ton heat pump. Cooling call present. 24.6 VAC at Y entering the outdoor board. Contactor isn’t being energized. Board is showing code X. I verified the pressure switches are closed. Here’s what I’m seeing…”
Excellent.
Not:
“This thing is being weird.”
Define:
weird.
The equipment does not have a weird terminal we can meter.
There is no award for spending three hours refusing to ask for help.
If you are stuck:
Recognize it.
Take a moment.
Review what you know.
Then use the appropriate resource.
A 10-minute phone call can sometimes prevent:
Ask for help.
Not knowing what is wrong does not authorize:
Let’s try a capacitor.
Then:
Let’s try a contactor.
Then:
Maybe the board.
Then:
Could be the thermostat.
Then:
At this point probably the TXV.
No.
Parts are not diagnostic instruments.
Replacing enough components will eventually change something.
That does not make it diagnosis.
This deserves its own section.
If you do not understand the refrigeration readings:
Do not add refrigerant to see what happens.
Before adjusting charge, establish the appropriate charging method and evaluate the relevant operating conditions.
Adding refrigerant is not:
Troubleshooting juice.
If airflow is wrong, correct or account for airflow.
If operating conditions are inappropriate for charging, recognize that.
If you don’t know:
Find out before opening the cylinder.
The control board frequently becomes the final suspect in an incomplete diagnosis.
Technician:
“Everything else checks out, so it has to be the board.”
Maybe.
Prove it.
Determine:
What input should the board be receiving?
Is it receiving it?
What output should the board produce under that condition?
Is it producing it?
Are safeties or logic preventing that output?
Does manufacturer troubleshooting support the conclusion?
“Has a lot of wires attached to it” is not a failure mode.
The TXV has endured enough.
Before condemning a metering device:
Verify the conditions and measurements required to support that diagnosis.
Do not use:
Pressures weird.
Coil freezing.
Superheat funny.
Probably TXV.
as a diagnostic progression.
See Section 07.
And probably several future sections.
Excellent.
Now we know something.
Say:
“I haven’t worked on this particular control before. I’m going to pull up the manufacturer information so I can make sure I’m testing it correctly.”
That statement should increase customer confidence.
You have just told them:
I am not going to experiment on your equipment.
If diagnosis requires research or assistance, communicate.
Example:
“I found something in the control sequence that I want to verify before recommending a repair. I’m going to check the manufacturer information.”
Or:
“I’ve completed the initial testing, but I don’t have enough evidence yet to condemn that board. I’m going to contact technical support.”
This is professional.
Disappearing into the truck for 35 minutes while the customer watches through the blinds is less professional.
Tell them what you’re doing.
Silence can feel uncomfortable.
The customer may be standing beside you.
They may ask:
“So what’s wrong with it?”
You may not know yet.
Say:
“I’m still testing. I don’t want to tell you something until I can support it.”
That sentence is Klein Cooling.
Use it.
Sometimes the reason the diagnosis feels confusing is because:
more than one thing is wrong.
Do not force every symptom into a single explanation because a single explanation would be convenient.
Example:
A system may have:
and
and
These conditions can coexist.
HVAC equipment is not contractually limited to one problem per visit.
Sometimes:
the system works perfectly while you are there.
Congratulations.
That does not prove:
Nothing is wrong.
Use:
If you cannot reproduce or verify the failure:
Say that.
“The system is currently operating and I have not been able to reproduce the reported failure. Here are the measurements I obtained and what I recommend monitoring.”
That is a legitimate conclusion.
Inventing a failed component because the customer expects an answer is not.
If you cannot reproduce an intermittent problem after reasonable testing:
Document it.
Do not transform:
Could not reproduce failure
into:
System normal.
Those statements are not identical.
One means:
The reported problem did not occur during today’s testing.
The other may imply:
There is definitely no problem.
We may not know that.
Words matter.
Separate:
from:
Example:
Known:
Outdoor unit stopped operating during test.
Known:
24 VAC cooling call remained present.
Known:
Control board displayed fault code X.
Suspected:
Intermittent board failure.
Those are different categories.
Do not document suspicion as established fact.
A theory becomes a diagnosis when the evidence supports it.
This is equally important.
You may know:
The compressor stopped.
You may not yet know:
Why.
You may know:
The breaker opened.
You may not yet know:
What caused the overcurrent condition.
You may know:
The coil froze.
You may not yet know:
Whether airflow, refrigerant, controls, or another condition caused it.
Say what you know.
Investigate what you don’t.
Do not fill the space between them with confidence.
Sometimes the customer wants an immediate answer.
“But what do YOU think it is?”
You may have a leading theory.
You can say:
“I have a suspicion, but I haven’t confirmed it yet.”
That’s fine.
Do not convert a 60% suspicion into a 100% diagnosis because someone asked twice.
The equipment gets the deciding vote.
The same rule applies internally.
If the office asks:
“So what’s wrong with it?”
and you do not know yet:
Say:
“I’m still diagnosing.”
Do not invent a diagnosis so Housecall Pro has something pretty to display.
The CRM can wait.
Certain failures may require:
Explain why.
Document what has already been established.
Provide a reasonable next step.
This is not failure.
It is recognizing the limits of the available evidence.
Every HVAC company eventually encounters the Parts Cannon.
Symptoms:
Replace capacitor.
Didn’t fix it.
Replace thermostat.
Didn’t fix it.
Replace board.
Didn’t fix it.
Replace motor.
Didn’t fix it.
Replace TXV.
Still doesn’t work.
At some point somebody should consider:
diagnosing the equipment.
Klein Cooling does not operate the Parts Cannon.
Parts are replaced because testing supports replacement.
This is important.
Sometimes you will make a diagnosis.
Then new information will show:
You were wrong.
Do not hide it.
Do not manipulate the explanation to make the original diagnosis sound correct.
Do not blame the equipment for changing its mind.
Say:
“The additional testing changed what we’re seeing. My original diagnosis doesn’t appear to be correct. Here’s what I found.”
Then correct course.
Being wrong once is fixable.
Defending a wrong diagnosis after the evidence changes is a choice.
Good technicians change their minds.
That is not inconsistency.
That is diagnosis.
Your first theory is not your child.
You do not have to defend it.
If new measurements contradict it:
Let it go.
The goal is not:
Prove I was right at 10:17 AM.
The goal is:
Fix the air conditioner.
A technician using:
is not demonstrating ignorance.
They are demonstrating:
professional discipline.
The technician who refuses to look something up because they think they should already know it is considerably more dangerous.
Apprentices especially must understand:
You are expected not to know things yet.
Ask.
Do not hide confusion.
Do not perform a procedure you do not understand merely because you are embarrassed to ask.
There are no stupid questions.
There are, however, extremely expensive guesses.
Ask the question.
Experience does not exempt anyone from this policy.
In fact, experience can create a different danger:
“I’ve seen this a hundred times.”
Maybe.
Perform the tests anyway.
The 101st system is allowed to have a different problem.
Pattern recognition is valuable.
Verification still wins.
These are acceptable Klein Cooling sentences:
“I don’t know yet.”
“Let me verify that.”
“I haven’t worked on this particular control before.”
“I want to check the manufacturer procedure.”
“I have a theory, but I haven’t proven it.”
“I can’t reproduce the failure right now.”
“The measurements don’t support replacing that component.”
“I need another set of eyes on this.”
“I was wrong about my first diagnosis.”
Those sentences do not make a technician sound weak.
They make a technician sound:
trustworthy.
“Probably.”
when we’re about to sell an expensive repair.
“They all do that.”
without evidence.
“It’s gotta be the board.”
“Let’s throw a capacitor at it.”
“Add a pound and see.”
“I’ve never seen this, but I’m pretty sure…”
“Don’t tell the customer, but…”
No.
If you don’t know:
Say you don’t know yet.
Then go find out.
When you are uncertain, ask yourself:
What do I actually know?
What have I measured?
What am I assuming?
What does the sequence of operation say should happen?
What is actually happening?
Is there manufacturer information available?
Have I checked the wiring diagram?
Do I need technical support?
Would another technician help?
Am I replacing a part because testing supports it—or because I have run out of ideas?
Am I adding refrigerant because the charge is demonstrably incorrect—or because I don’t know what else to do?
Am I afraid to tell the customer I don’t know yet?
If the answer to that last question is yes:
Get over it.
Then tell them the truth.
You will encounter equipment you do not understand.
You will encounter error codes you have never seen.
You will encounter failures you cannot immediately reproduce.
You will encounter wiring diagrams that appear to have been drawn during a hostage situation.
You will occasionally stare at an air conditioner and think:
What the hell is this thing doing?
Fine.
Stop.
Think.
Measure.
Read.
Ask.
Call.
Verify.
Do not guess.
Do not bluff.
Do not shotgun parts.
Do not add refrigerant because you’re confused.
Do not condemn the board because you ran out of components.
Do not defend a theory after the evidence disproves it.
And never confuse:
“I don’t know.”
with:
“I can’t find out.”
At Klein Cooling, “I don’t know” is an acceptable answer.
“I don’t know, so I guessed” is not.
END OF SECTION 12