So most of these things are basics to the seasoned A+ and Network+ person, but you would be surprised about how over the years we have had to teach the paperwork engineers how to do some of these things. Why did I bring up this ‘maintenance checklist’? Because these are the types of things you are going to promise to your client or address in your service level agreement. But before we get there, let’s talk about doing ANY work at all and protecting yourself, your techs, and your business. A while back Derek discovered the following template, which saved his butt many times over the years. He calls it the engagement form. The client signs it BEFORE any work is done and it is updated or signed again 1x per year (there might be updates-wink).

Let me also give this disclaimer; use of these materials does not necessarily mean they are legal or binding, make sure to have them reviewed by an attorney before putting them in to production. These forms were valid for SC, but that does not mean it is valid for your business or market. Bottom line, have them reviewed; they can save you a bunch of heart ache down the road. Second disclaimer, although I have listed some prices/pricing, they are in model only, and in no way represent what you should charge or what your market it is like. It is a possible idea to start with but always subject to change, i.e., at your executive reviews (discussed in later chapter). Also realize that I provide these templates as-is, in hopes that you understand who, what, where, when, and how these items might have ramifications with your offer-ings. They also represent a mind-set that you and your techs need to have to posture these relationships in a professional manner to clearly standout against the propaganda they are getting from the friends who happen to know computers.