check list

[surenuff]

Does anyone out there know of, have a copy of, or a link to a good check list that a techinician can use on each and every call to document the pressures/temperatures, superheats, subcools, etc. etc. etc. that one finds to help them diagnose failures, and provide a record of tests and measurements they used to come up with the diagnosis, and provide for future reference? I would really like to find a procedure for documentation of the steps taken to test, and to provide a tech with a list of inofo that would aid them in making a timely yet profitabe

[flange]

I find it best to make your own documentation, with maybe the aid of a document "borrowed" from another contractor. For example, when i walk through a potential service account, I always look at the log books of the other contractor for an idea of their type of service provided, and also a blank copy of a service ticket or log if available. I then make my own forms based upon what I WANT to be there.

[knewguy]

Like flange suggested create your own.

I always like useing the equipment manufacturer guideline for

each system that I work on.

On commercial systems they come with a sequence of operation

if you can found the literature left with the equipment.

You can always take the model # of the unit and search it on line.

[HVACJOEK]

We like to see the guys use the service ticket, as long as it doesn't ruffle any feathers.

[surenuff]

I think it is good to be specific on the service ticket as well. But I guess what I am asking about is more of a list of things the service tech should check "list" that would not only help clear up later questions of what was done or not done, and could be arranged in such a way to help the technician see the total picture on each job to help have a higher and faster correct diagnosis percentage. I have seen several different "flow chart", and the like that were aimed at this, but never one that I felt was a really, really good one. I was hoping someone out here had made one or came across one they felt was really helpful and accurate. I can make one, and maybe that is what I should do as was suggested earlier, I was just hoping to save some time.

[surenuff]

I find it best to make your own documentation, with maybe the aid of a document "borrowed" from another contractor. For example, when i walk through a potential service account, I always look at the log books of the other contractor for an idea of their type of service provided, and also a blank copy of a service ticket or log if available. I then make my own forms based upon what I WANT to be there.

Thanks all, for the advice.

[wgrr]

I think it is good to be specific on the service ticket as well. But I guess what I am asking about is more of a list of things the service tech should check "list" that would not only help clear up later questions of what was done or not done, and could be arranged in such a way to help the technician see the total picture on each job to help have a higher and faster correct diagnosis percentage. I have seen several different "flow chart", and the like that were aimed at this, but never one that I felt was a really, really good one. I was hoping someone out here had made one or came across one they felt was really helpful and accurate. I can make one, and maybe that is what I should do as was suggested earlier, I was just hoping to save some time.

I have one that the SW Bell guys used back in the day. PM me with your email address and I will scan one in and send it to you. It would be easy to recreate and add to it in a spreadsheet. Then you could print it out after filling the info in to leave onsite. If I hand wrote my reports no one would be able to read it.

[pdrake65]

Does anyone out there know of, have a copy of, or a link to a good check list that a techinician can use on each and every call to document the pressures/temperatures, superheats, subcools, etc. etc. etc. that one finds to help them diagnose failures, and provide a record of tests and measurements they used to come up with the diagnosis, and provide for future reference? I would really like to find a procedure for documentation of the steps taken to test, and to provide a tech with a list of inofo that would aid them in making a timely yet profitabe

This was posted on a thread a while back from one of the guys. Forgot I even had it until I read this thread. Maybe it will help you out:

[surenuff]

This was posted on a thread a while back from one of the guys. Forgot I even had it until I read this thread. Maybe it will help you out:

I thank you!! Yes, this is along the lign of what I was seeking. I wanted something that would give a record of temps/pressures ODT/IDT and all of the other readings that should be considered in making a diagnosis about the operation of a system.

[achzdck]

Indepth but suggestions would be- observations of systems condition/hacked or well built/falling apart-actions taken -foreseeable future problems -safety issues and customers outlook for upgrades and their attitude on my advise...merely suggestions .Maybe an 1/8 of a page for your personal thoughts would cover all the above.

[surenuff]

Indepth but suggestions would be- observations of systems condition/hacked or well built/falling apart-actions taken -foreseeable future problems -safety issues and customers outlook for upgrades and their attitude on my advise...merely suggestions .Maybe an 1/8 of a page for your personal thoughts would cover all the above.

THanks!!! I have read many online and a few from other sources, and took advice from this site, and surenuff it seems like the best way to have everything I want it to have and not other things that I do not want on it, is to start from scratch and build my own using information that I want on it. I am using an excel spreadsheet and in a short time I will compete it. I am sure there is a perfect one out there developed by someone smarter than me, but I have not found it yet.