First Responder, Military, and Senior Discounts.
First Responder, Military, and Senior Discounts.
There is an old HVAC documentation system that goes something like this:
“I’ll remember.”
No.
You will not.
By tomorrow, you will have worked on four more systems.
By next week, you will vaguely remember that the house had an air conditioner.
By next year, the customer will call and say:
“Remember when you were here last August and you said something about that wire?”
And Housecall Pro will say:
Completed. Unit working.
Wonderful.
Very helpful.
At Klein Cooling, documentation is part of the job.
Not paperwork after the job.
Not something we do if we have time.
Not something the office should have to chase you down for three days later.
The job is not complete until somebody who was not there can look at the photos and notes and understand:
What the customer called about.
What equipment we worked on.
What we found.
What we tested.
What the readings were.
What we did.
What we recommended.
What the customer approved or declined.
And what condition the system was in when we left.
Your memory is not the customer record.
You cleared the drain.
Great.
Did you document it?
You tested the float switch.
Great.
Did you document it?
You found the capacitor weak but still operational and recommended replacement.
Great.
Did you document it?
The customer declined.
Great.
Did you document it?
Because six months from now, if that capacitor fails and the customer says:
“Nobody ever told me that.”
we need something better than:
“I definitely remember telling him.”
Maybe you did.
Maybe you didn’t.
Maybe he forgot.
Maybe you forgot.
Documentation removes the argument.
If it matters, write it down.
Take pictures.
Good pictures.
Useful pictures.
Not 47 photographs of essentially the same condenser from slightly different angles.
We need photos that tell the story of the job.
When applicable, document:
Equipment model and serial numbers.
Overall equipment condition.
The specific problem or failed component.
Electrical condition.
Drain condition.
Coil condition.
Ductwork or airflow concerns.
Existing damage.
Before-and-after conditions.
Completed installation work.
Anything unusual.
Anything recommended for future repair.
Anything that could reasonably become a question later.
The goal is not:
Take pictures because Housecall Pro wants pictures.
The goal is:
Document the condition of the equipment and our work.
This matters.
You arrive and find:
A burnt wire.
A rusted drain pan.
A disconnected duct.
A broken thermostat.
Water in the auxiliary pan.
Oil around a refrigerant fitting.
A mangled electrical compartment.
A filter that appears to have been installed sometime after COVID but before 2024.
Take the picture before you fix it.
Because once you repair it, the evidence is gone.
You cannot recreate a useful before photo afterward.
Well—
you can.
But now we’re manufacturing evidence.
Let’s not.
For repairs where the work is visible:
Before.
After.
Simple.
Burnt contactor?
Before and after.
Damaged wiring?
Before and after.
Dirty coil?
Before and after.
Drain repair?
Before and after.
Duct repair?
Before and after.
Corroded electrical connection?
Before and after.
The before photo documents why the work was needed.
The after photo documents what we did.
Together, they tell the story without anyone needing to remember it.
Take a clear picture of the data plate.
Not from eight feet away.
Not blurry.
Not with your flashlight reflecting directly off the label so every number disappears.
Not a picture where the model number is technically somewhere in the image if you zoom in 900%.
Readable.
We use model and serial information for:
Parts.
Warranty.
Equipment age.
Equipment matching.
Estimates.
Service history.
Future replacement.
Manufacturer information.
A wrong character can mean a completely different piece of equipment.
If you can’t read the photo:
Take another one.
A data plate tells us what the equipment is.
An overall picture tells us what we’re dealing with.
Take a useful wide shot.
This becomes extremely valuable later.
Where is the equipment?
Closet?
Garage?
Attic?
Horizontal?
Vertical?
How is the ductwork configured?
How much room is around it?
What does the condenser location look like?
What obstacles exist?
A future technician, estimator, or installer may be looking at those photos before going to the property.
Help them.
Because someone else will.
Maybe the office.
Maybe another technician.
Maybe you six months from now.
Maybe an installer.
Maybe a manufacturer.
Maybe a warranty department.
Maybe the customer.
Ask yourself:
If I knew nothing about this job, would this picture tell me anything?
If the answer is no:
Take a better picture.
If you’re documenting a burnt terminal:
Show the burnt terminal.
Do not take a photo of the entire air handler and expect somebody to play:
Where’s Waldo: Electrical Failure Edition.
Take an overall photo for context.
Then take a close-up of the actual issue.
Both matter.
The opposite problem exists too.
You take a photo from three inches away.
There is:
One wire.
Half a screw.
A brown object.
Excellent.
What are we looking at?
Use context.
A good documentation set often includes:
Wide shot → medium shot → close-up.
Where is it?
What component is it?
What specifically is wrong?
Now somebody who wasn’t there can follow along.
Look at the picture after you take it.
Is it clear?
Can you read the label?
Can you see the damage?
Is your finger over the lens?
Is the flash blowing everything out?
Did the camera focus on the wire in front instead of the component behind it?
Take another one.
We are not shooting film.
It does not cost $0.37 every time you press the button.
This may be the most advanced photography training in the manual.
Your phone spends all day:
In your pocket.
In the truck.
In your hand.
In an attic.
Covered in sweat.
Dust.
Coil cleaner.
Whatever was living in that return.
Then you take a picture and wonder why the entire HVAC system appears to be surrounded by heavenly fog.
Wipe the lens.
Miracle.
If the problem is inside a dark air handler:
Illuminate it.
Use the flashlight.
Use the work light.
Use the phone flash if it actually helps.
A photograph of complete darkness does technically prove that the attic was dark.
It proves nothing else.
Photos are important.
Numbers are important too.
Depending on the job, that may include:
Supply-air temperature.
Return-air temperature.
Temperature split.
Suction and liquid pressures.
Superheat.
Subcooling.
Outdoor temperature.
Voltage.
Capacitance.
Compressor amps.
Condenser-fan amps.
Blower amps.
Heat-strip amps.
Static pressure.
Humidity.
Whatever measurements were relevant to the diagnosis or service.
Do not reduce all of that to:
“System running good.”
What does that mean?
Good according to whom?
Compared to what?
Document the numbers that support the conclusion.
Neither is:
“Pressures good.”
“Temps good.”
“Cap good.”
“Amps good.”
We have numbers.
Use them.
Instead of:
Capacitor tested good.
Write:
45/5 µF capacitor tested 44.2/4.9 µF — within rating.
Instead of:
Temperature split good.
Write:
Return 76°F / Supply 57°F / ΔT 19°F.
Instead of:
Pressures normal.
Document the readings you actually used to reach that conclusion.
This is especially important when we’re trying to compare system performance over time.
If you did not take the reading:
Do not enter one.
This should not require explanation.
If a form asks for something you didn’t measure, do not make up a number that looks reasonable.
If the reading could not be obtained:
Say why.
If it wasn’t applicable:
Mark it accordingly.
If you forgot:
Own it.
A blank field is better than fictional data.
Documentation must be true.
Always.
No.
Absolutely not.
Even if the system:
“Probably hasn’t changed.”
The entire reason we’re taking readings is to know what the system is doing today.
Copying old readings into a new report isn’t documentation.
It’s creative writing.
We already have an Operations Manual for that.
Our Preventative Maintenance Performance Report is not busywork.
It creates a consistent record of the system.
Use it.
Completely.
Every time.
The purpose is to build a history.
Over multiple visits, we can begin seeing changes:
Capacitance declining.
Amp draw changing.
Temperature split changing.
Corrosion progressing.
Drain problems recurring.
Blower condition changing.
Refrigerant performance shifting.
Things that may mean very little on one visit can become meaningful when we can compare them over time.
But that only works if the information is actually recorded.
“Yep, it’s running” is not maintenance.
And it is definitely not documentation.
This is huge.
The customer’s complaint should be in the notes.
Not just:
No cool.
What did they actually say?
For example:
Customer reports system stopped cooling yesterday afternoon. Outdoor fan continued running but indoor blower was not operating. Customer cycled thermostat before arrival and system began operating again.
Now we have information.
Compare that with:
No cool. Working now.
One helps the next technician.
One does not.
Ask the customer what changed.
Then write it down when relevant.
New thermostat?
Recent electrical work?
Filter recently changed?
Another HVAC company was there yesterday?
Power outage?
Drain recently cleared?
System has been shutting off intermittently?
Problem only happens in the afternoon?
Those details matter.
Especially intermittent problems.
You may arrive while the equipment is operating perfectly.
The customer’s description may be the most valuable diagnostic information available.
Preserve it.
This is important.
Customer reports refrigerant leak.
is not the same thing as:
Refrigerant leak confirmed.
Customer states previous company diagnosed failed TXV.
is not:
Failed TXV.
Customer reports unit froze yesterday.
is not:
Evaporator coil found frozen on arrival.
Words matter.
Document:
What was reported.
What you personally observed.
What you tested.
What you concluded.
Do not accidentally turn somebody else’s statement into our diagnosis.
Intermittent problems happen.
Customer says the system stopped yesterday.
Today it runs perfectly.
That does not mean:
Customer imagined it.
And it does not mean we invent a failure so we can give them an answer.
Document it.
Example:
System operating normally during today’s visit. Customer’s reported shutdown could not be reproduced. Electrical and operating readings recorded. Recommend monitoring and contacting us if condition repeats.
That’s useful.
That’s honest.
And the next technician knows exactly where things stood.
If you suspect something:
Say it’s suspected.
If something is possible:
Say it’s possible.
If you confirmed it:
Say it’s confirmed.
Those words are not interchangeable.
Possible.
Suspected.
Likely.
Observed.
Confirmed.
Use the right one.
We do not make documentation sound more certain just because certainty looks better on an invoice.
Technicians sometimes think professional notes must sound absolutely certain.
They don’t.
Professional notes need to be accurate.
If you see water around an air handler but cannot determine exactly where it originated without removing the coil:
Say that.
If corrosion exists but the component is currently functioning:
Say that.
If a condition may need monitoring:
Say that.
If the only way to guarantee correction requires additional work:
Say that.
Documentation should reflect reality.
Reality occasionally includes uncertainty.
This protects the customer.
And us.
Before beginning work, document relevant existing conditions.
Water damage.
Rust.
Corrosion.
Broken panels.
Damaged attic access.
Existing ceiling stains.
Damaged ductwork.
Improper drain configuration.
Missing insulation.
Electrical problems.
Anything significant.
Especially anything that could later become:
“That wasn’t like that before you were here.”
Take the picture.
Write the note.
This is not about creating a defense file against the customer.
It is about establishing an accurate condition of the property before work begins.
Documentation is not only for things that make us look good.
If we damage something:
Tell the office.
Tell the customer appropriately.
Photograph it.
Document it.
Then deal with it.
Do not suddenly decide the camera only works when another company caused the damage.
Integrity does not have a photo filter.
If you recommend something:
Put it in the job record.
Weak capacitor.
No surge protection.
Corroded disconnect.
Damaged ductwork.
No float protection.
Dirty blower.
Noisy motor.
Aging equipment.
Drain concern.
Whatever is relevant.
And be specific.
Not:
“Recommend repairs.”
Which repairs?
Why?
How urgent?
What condition led to the recommendation?
Future technicians should not have to decode your thoughts.
This protects everyone.
If you identify a legitimate issue, explain it to the customer, provide the option, and they decline:
Document it.
Professionally.
Not:
“Customer refused.”
Unless they actually climbed onto the table and declared rebellion.
Something like:
“Recommended replacement of weak dual capacitor due to measured value below manufacturer rating. Customer declined replacement at this time.”
Perfect.
No attitude.
No judgment.
Just what happened.
Housecall Pro is not your diary.
Do not write:
“Customer was being ridiculous.”
“Guy wouldn’t listen.”
“Lady kept asking stupid questions.”
“Previous company screwed everything up.”
No.
Write facts.
If a customer interaction genuinely matters to future service, document it professionally.
“Customer requested no additional repairs be performed without prior approval.”
Useful.
“Customer is cheap.”
Not useful.
Also:
Don’t.
This is a good rule.
Would you be comfortable with the customer reading your notes?
If not:
Why did you write them?
That does not mean hide important facts.
Document everything relevant.
But write professionally.
You should be able to stand behind every sentence in the record.
You can document what you found.
You cannot document what was inside another technician’s head.
Bad:
“Previous technician tried to scam customer by telling them TXV was bad.”
You don’t know that.
Better:
“Customer reports previous company diagnosed failed TXV. During today’s visit, system operated normally and recorded readings did not confirm a failed TXV.”
Facts.
Evidence.
No mind reading.
Grace belongs in the notes too.
Installation documentation should show the completed work.
Not just:
New condenser.
We should be able to see, as applicable:
Indoor equipment.
Outdoor equipment.
Data plates.
Electrical connections.
Disconnect.
Drain configuration.
Float protection.
Filter access.
Duct connections.
Lineset.
Tie-downs.
Pad or stand.
Thermostat.
Any unusual work.
Final completed condition.
If something is hidden after the installation is complete:
Photograph it before it becomes hidden.
This matters.
Some of the most important installation work disappears.
Connections get insulated.
Panels go on.
Ductwork gets covered.
Equipment blocks access.
Attic insulation gets restored.
If something matters and nobody will be able to see it afterward:
Take the picture first.
Documentation gives us a way to prove the work that can no longer be visually inspected.
Compressor replacement.
Evaporator coil replacement.
Major electrical repair.
Lineset repair.
Anything where a meaningful portion of the equipment is being opened or changed.
Document the process where useful.
We do not need a National Geographic documentary.
But we should have enough to understand what happened.
This is one of the biggest benefits.
Imagine going to a system you’ve never seen.
Before arrival, you can look at the previous job and see:
The equipment.
The location.
The data plate.
The air handler orientation.
The electrical setup.
The drain.
Previous repairs.
Previous readings.
Existing concerns.
That is incredibly valuable.
Now imagine opening the previous job and seeing:
One blurry picture of a condenser.
And:
“Fixed.”
Do not do that to your coworkers.
A good service history turns every previous technician into part of the next diagnosis.
If a blower motor was replaced six months ago:
We know.
If the capacitor has been declining:
We know.
If the drain has clogged three times:
We know.
If a refrigerant leak was repaired:
We know.
If the customer previously reported an intermittent issue:
We know.
If a recommendation was declined:
We know.
Documentation creates institutional memory.
The company remembers even when the technician doesn’t.
The office should not have to call you and ask:
“What happened at Mrs. Smith’s?”
while you attempt to reconstruct the job from memory.
Good documentation allows the office to:
Answer customer questions.
Build estimates.
Order parts.
Schedule follow-up work.
Review warranty information.
Understand what happened.
Communicate intelligently.
The office wasn’t standing next to the air handler.
Your notes are their eyes.
This matters especially at Klein Cooling.
If another company says:
Bad compressor.
Bad TXV.
Refrigerant leak.
System needs replacement.
And we give a second opinion:
Document the hell out of it.
Customer’s report.
System condition.
Readings.
Photos.
Testing.
What we confirmed.
What we did not confirm.
If we disagree with another diagnosis, our answer should be supported by evidence.
Not:
“Nah, they’re wrong.”
Show why.
Radical transparency requires receipts.
Sometimes we tell a customer:
Monitor it.
That can be the correct recommendation.
Not every rust spot requires immediate replacement.
Not every unusual sound means imminent failure.
Not every aging component needs to be ripped out today.
But if we’re recommending monitoring:
Document the current condition.
Photograph it.
Record relevant measurements.
Then we have a baseline.
If it changes later, we can actually compare.
Monitoring without documentation is just waiting.
A homeowner may never climb into the attic.
They may never crawl behind the air handler.
They may not want to stand next to a condenser in August while you point at a contactor.
Take a picture.
Show them.
“Here’s what I found.”
Now the customer can see the same thing you saw.
That fits exactly with how we want Klein Cooling to operate.
We don’t want customers taking our word for everything.
Whenever practical:
Show them.
A rusty component photographed from two inches away can look like the Titanic.
Be fair.
Give context.
Florida equipment gets rust.
Attics get dirty.
Older systems look older.
Do not use dramatic photos to make ordinary conditions look catastrophic.
Show the customer the truth.
Then explain what it actually means.
Transparency goes both ways.
Not every photo has to show something wrong.
Clean coil?
Document it.
Capacitor in range?
Record it.
Drain working properly?
Record it.
Electrical connections look good?
Document it.
System operating normally?
Document the readings supporting that.
This is especially important on maintenance.
The report should not exist solely to find things to sell.
Sometimes the conclusion really is:
Everything looks good today.
Great.
Prove that too.
It may support a repair recommendation.
It may help a customer understand why work is needed.
It may lead to a sale.
Fine.
But that is not its primary purpose.
Documentation exists to create an accurate record of:
What we found.
If the documentation is being manipulated to make a repair look more necessary:
We have lost the plot.
Take the same pictures and record the same readings whether the findings are good or bad.
If the system is doing something unusual:
Document it accurately.
Do not choose the one moment where the reading looked normal because that’s easier.
Do not choose the one moment where the reading looked terrible because that helps sell the repair.
Use representative readings.
If something fluctuates:
Say it fluctuates.
If the condition changes:
Document that.
Again:
The record needs to be true.
Two-system house?
Three-system house?
Commercial property with multiple units?
Make it obvious which equipment you’re talking about.
Upstairs.
Downstairs.
East unit.
West unit.
System 1.
System 2.
Whatever naming convention makes sense.
Then remain consistent.
Do not document:
“Capacitor weak.”
when there are four condensers outside.
Future Kevin is going to hate Present Kevin.
Help him out.
Before uploading:
Look.
Correct customer?
Correct property?
Correct equipment?
Correct job?
Do not accidentally attach photos from yesterday’s Goodman to today’s Trane.
That creates a very confusing service history.
And potentially a conversation we do not need.
We’re documenting HVAC work.
Not producing a reality show.
Keep customers and their personal belongings out of photographs whenever reasonably possible.
Do not intentionally photograph:
Family photos.
Mail.
Documents.
Medication.
Computer screens.
Children.
Personal information.
Anything unrelated to our work.
We are guests in people’s homes.
Respect their privacy.
Bathrooms.
Closets.
Reflective equipment.
Windows.
Sometimes the photo includes more than you realize.
Look at the image before uploading it.
We need the air handler.
Not an accidental full-body portrait of you sweating through your shirt in an attic.
Although that would accurately document working conditions.
Still.
Delete it.
A photo does not need to be marketing quality to be valuable documentation.
If it clearly shows the condition:
Keep it.
The Jobs Map and social media need attractive photos.
The service record needs useful photos.
Different purpose.
If you finish a beautiful installation:
Great.
Take a couple clean photos.
Straighten the frame.
Move the trash.
Close the panels.
Clean the equipment.
Make it presentable.
Those may eventually be useful for:
Website.
Social media.
Real Jobs Map.
Training.
But documentation comes first.
Get the technical photos.
Then take the pretty ones.
This is important.
If you encounter something unusual:
Take pictures.
Especially if your immediate reaction is:
“What the hell is that?”
We want documentation.
Improvised wiring.
Strange duct modifications.
Unusual equipment configurations.
Animal damage.
Burnt components.
Water damage.
Things installed backward.
Things installed where things should not be installed.
And, of course:
eggs of unknown origin.
Nobody will believe you later.
Take the picture.
This technically belongs in Section 32.
But documentation matters.
Photo first.
Then:
Leave the unidentified attic eggs alone.
We are an HVAC company.
There are limits to our scope.
The worst time to write job notes is:
Tomorrow morning.
Do them while the job is fresh.
Ideally, complete the documentation before leaving or immediately afterward when appropriate.
Once the next call starts, your brain has moved on.
Now details begin disappearing.
What was the capacitor reading?
Was the return 77 or 79?
Which float switch didn’t work?
Was that corrosion on this system or the last one?
Do it while you know.
Section 34 still applies.
We want complete documentation.
We also want an efficient process.
Take photos as you work.
Record readings as you take them.
Build notes during the call when practical.
Do not wait until the end of an eight-call day and attempt to write eight novels from the Wawa parking lot.
Document in real time.
It is faster.
And more accurate.
If typing detailed notes takes forever:
Talk.
Voice-to-text can be incredibly useful.
But—
read it before submitting.
HVAC vocabulary and voice-to-text have an adversarial relationship.
TXV becomes:
“text TV.”
Condenser becomes:
Something involving a condor.
Subcooling becomes:
Who knows.
Customer names become completely new human beings.
Use the technology.
Then proofread the technology.
This takes 30 seconds.
Does it make sense?
Did voice-to-text create a felony?
Did you accidentally write:
“Compressor is drawing 47 amps”
instead of:
4.7 amps?
Did you say indoor when you meant outdoor?
Did you write heating when you meant cooling?
Did you leave out the actual repair?
Read it once.
Ten minutes now saves two hours later.
We have established this.
Documentation needs to be complete.
It does not need to become:
War and Peace: The Condenser Years.
Be concise.
Be specific.
Include the important information.
Customer complaint.
Findings.
Relevant readings.
Work performed.
Recommendations.
Outcome.
Done.
The goal is clarity.
Not word count.
This Operations Manual has already claimed the company’s lifetime supply of words.
There is a balance.
Too much:
A seven-paragraph philosophical exploration of the capacitor.
Too little:
“Fixed.”
Somewhere in the middle lives useful documentation.
Find it.
Before leaving a completed repair or installation:
Take one last look.
Panels installed.
Disconnect closed.
Tools removed.
Work area clean.
Equipment operating.
No hoses attached.
No meter sitting on top.
No screws on the pad.
No trash.
Then take the final photo when appropriate.
There is something valuable about having a record of:
This is how we left it.
Imagine another Klein Cooling technician receives a call from this customer tomorrow.
They open your job.
Can they understand what happened yesterday without calling you?
If yes:
Good documentation.
If they have to call and ask:
“Bro, what did you actually do here?”
We can improve.
Take photos.
Take useful photos.
Take the before photo before touching the problem.
Take the after photo when you’re finished.
Photograph model and serial numbers clearly.
Photograph existing conditions.
Photograph unusual conditions.
Document the customer’s actual complaint.
Separate what the customer reported from what we personally confirmed.
Record the readings that matter.
Never manufacture a reading.
Never copy an old reading.
Document recommendations.
Document declined recommendations professionally.
Document uncertainty honestly.
Document damage—even if we caused it.
Protect customer privacy.
Write notes someone else can understand.
Complete documentation while the job is still fresh.
And remember:
Documentation is not there to make us look right.
It is there to create an accurate record of what happened.
Sometimes that record proves we diagnosed it correctly.
Sometimes it proves the system was operating normally.
Sometimes it shows a condition getting worse over time.
Sometimes it saves another technician two hours.
Sometimes it protects the customer.
Sometimes it protects us.
And sometimes, six months later, a customer will call and say:
“What did you guys find the last time you were here?”
We should not have to answer:
“Hang on. Let me see if Kevin remembers.”
The company should remember.
That’s what the documentation is for.