Im building a install check list to cover various setting that need to be configured as part of every build the idea is to have a master check list and either tick yes, or n/a if not applicable on this scheme.

For instance for reference see attached image of what ive built currently.

Wondered if anyone had some things to they would add to this / a template sheet they have been working on ?

Screen shot of my checklist (work in progress) [Link: imgur.com]

Your list is a start.

Do you ever use ARC (Audio Return Channel)? This usually interacts with CEC.

In addition to a setup list, an operational proof checklist would be a good idea too. Every source should be checked with every remote -- in every spot where the customer might want to use the remote.

Network setup is important too. Do you have a backup of the router settings? Have you reserved IP addresses? If your network allows remote administration, have you checked this operation?

Check out https://process.st . I think you could easily adapt it for a list that's always with you, and make a number of different lists for different applications.

Firmware updates and customer account info/passwords.

It was pretty powerful when my Dish guy finished the job and went over his checklist with me. It lets Dish affirm my satisfaction and the installer confirm he did his job per spec.

"So, let's just run over the installation today:"

Can you have a look around and make sure we cleaned up properly and left no dirt or trash behind?

Do you understand how to 1) record a show, 2) skip commercials .... blah blah

Are you satisfied that you know how to use the system, and you have the proper contact information for additional support?

Did we change the default password and do xyz for additional security provisions?

Did I offer you the opportunity to subscribe to a plan that would ensure your house didn't explode when the stars were out of alignment?

If so check here, give a thumbprint here, hold your child up to the sky and proclaim eternal satisfaction.

>>>> win, win, win

A while back I was supervising a satellite installation at one of my customer sites and the installer and I were knocking heads with the implication of: "stand out of my way son and let a professional do this." In the interest of getting him off the site as fast as possible, I stood back. Since the customer was out of town, I was asked to sign off on the installation. This was done with a phone call to an off shore rep. When it came to the point of "are you satisfied?", I said NO and went through a litany. The worst point was the negative drip loop (water would run down the wire, then directly into the positively angled, un-caulked ingress hole). This was an unacceptable answer and she asked again and again, saying that she could not enter a negative report. Finally, she said that she would transfer me to a supervisor. Unfortunately, he was out to lunch or there was a long line because I waited for about 15 minutes. I think that I was being punished. Anyway, I was transferred to a US based guy who understood my points and sent out a "fixer" the next day (Saturday) who cleaned everything up (after taking lots of pictures). I hope that the original contractor is now flipping burgers somewhere. (... er ... No, that's a bad idea because he'd probably make someone sick -- but you get the idea)

Ive done some more work on the checklist see below, still a work in progress, let me know if theres anything you think its missing.

Heres a link to the shared google doc : [Link: docs.google.com]

Update the router firmware? Adjust relative levels for each input of the AVR?

CEC applies to all of the devices and ARC might require CEC. In any case, one must check ARC.

Are you a company with 6 or more techs doing a lot of jobs ?

Because smaller companies it made more sense for the boss to come out a spend 1 hour doing all the little things at the end of the job.

In 3 or 4 person companies when I would project manage the jobs. it would just piss off the techs. To have a checklist

I share some of brucewayne’s concerns. The technicians might respond better if you turned this into a documentation standard, collecting items such as IP addresses, input assignments, passwords, and such.

Certainly, the techs should be responsible for testing the system, but if the list is too basic, they’ll be insulted. You could ask your techs to help you build the checklist.

At one point we used a subcontractor on some of our jobs. He thought that he was so good that he did not need to check his work. We would get calls from him that “it doesn’t work”, hinting that it was our design issue, or the call would come from the customer shortly after he left. We’d go out and have the system working in minutes — and it was not a design issue. (These were difficult issues, such as plugging into the wrong IR port, or not plugging in at all) Needless to say, we “fixed” our issue with him real fast, I know that he worked for our competition for a while, probably putting blots on their reputation (and the industry) too.

It’s not just our industry. I was on a site a day after the electrician’s helper installed some outlets. One did not work at all and another was tied to a dimmer. Our TV did not appreciate that dimmer.