Consulting on Y2K issues can be profitable, but it also 
        exposes you to tremendous risks if you dont have 
        the proper legal protection behind you.
        
        Y2K and the Law
        Consulting on Y2K issues can be profitable, but it also 
        exposes you to tremendous risks if you don’t have 
        the proper legal protection behind you.
        
        
			- By Harry Brelsford
- February 01, 1999
Ive been eating a lot of rubber-chicken lunches 
        lately. My firms entry into the small-business Y2K 
        consulting area has resulted in the requisite lunch invitations 
        from fraternal, business, and trade associations to discuss 
        Y2K. But Y2K has been more than chicken lunches for me. 
        This consulting area has also forced me and other consulting 
        MCSEs to evaluate how we conduct our business and perform 
        our work.
      Warranty of Merchantability
      Before delving into Y2K specifics, let me discuss a few 
        legal matters that many MCSEs encounter. The first matter 
        involves how well software applications work and whos 
        responsible when they dont. Perhaps youve 
        experienced this when youve installed an operating 
        system or application that doesnt work perfectly 
        all of the time. Although we MCSE-types understand that 
        thats life, our secular business clients see things 
        differently. These are the business managers who start 
        backing out $2,000 or more per hour in lost company revenue 
        when BackOffice checks out. These people want someoneperhaps 
        youto be responsible. In short, your clients 
        network downtime may expose you to financial liabilities 
        you didnt anticipate. Often, this is because clients 
        assume that youre responsible for the fitness or 
        warranty of merchantability of the software 
        you install and maintain. 
      Clearly, such shouldnt be the case. If your client 
        purchased an application from a software manufacturer, 
        you should modify your consulting engagement letter to 
        state that you are ultimately not responsible for the 
        softwares performance. The engagement letter that 
        I use clearly delineates that Im a consultant retained 
        to install software purchased by the client. I make no 
        claims toward the fitness of the software product itself. 
        Periodically, I also try to manage client expectations 
        by reminding them that Im serving as their consultant 
        to install their software. Its only smart.
      Y2K Specifics
      This leads me to the pluses and minuses of having a Y2K 
        consulting practice, traps and all. It is, indeed, a popular 
        and profitable offering that MCSEs should consider. But 
        by offering your Y2K consultant expertise, youre 
        clearly exposed to potential legal liabilities. Heres 
        the drill.
      Suppose you assess a business Y2K fitness using 
        techniques that youve learned from Y2K consulting 
        books and the Web (and the articles in this issue!). You 
        issue a letter that reflects not only your findings but 
        also the work you performed to cure the Y2K problems. 
        Several months hence, the magic day arrives: January 1, 
        2000. When everyone returns to work that following Monday 
        (January 3rd), the business that you certified 
        as Y2K-compliant begins to experience strange computer-related 
        occurrences. Such occurrences prevent the business from 
        performing its work fully. Shortly thereafter, you receive 
        a letter asking you to appear in civil court to defend 
        yourself. Bummer.
      This unfortunate case study is likely to become reality 
        for those MCSEs who try to enter the Y2K consulting field 
        unprepared. So what can you do? First, spend the $1,000 
        or so it takes to have a fully qualified contracts attorney 
        review your engagement letter and Y2K certification letter. 
        Well-prepared communications and documentation can save 
        your bacon. Second, fully explain those forms of communication 
        (engagement letter, Y2K findings, and so on) to your client 
        at the beginning of the engagement and, if possible, during 
        and at the end of the engagement as well. This isnt 
        just a courtesyit makes your actions and behavior 
        that much more defensible before judge and jury. Third, 
        read on for my discussion regarding professional liability 
        and errors and omissions insurance.
      BackOffice to Boardroom
      The services MCSEs perform are no longer limited to the 
        back office. Instead, theyre often observed from 
        the boardroom, making it more important than ever to have 
        some form of insurance to protect you. As a professional, 
        this insurance is typically known as professional liability 
        insurance or errors and omissions insurancecall 
        it malpractice insurance if you like. Here, the idea is 
        that, as a professional, youre held to a high standard 
        of performance. But if youre negligent, for whatever 
        reason, you might be responsible for the financial damages 
        and havoc youve wreaked on the injured party. 
      Well, being the smart MCSE that you are, somewhere along 
        the way youd better have acquired professional liability 
        insurance to protect your assets (and your behind too!). 
        This type of insurance will protect you from claims. Properly 
        structured, itll pay off any damage awards assessed 
        against you plus cover your legal fees. Do not provide 
        Y2K consulting services without it. You can acquire such 
        insurance from a number of insurance brokerages. To find 
        an insurance agent to underwrite your professional liability 
        insurance needs, start by asking the attorney you retained 
        to draft your engagement letter who his or her insurance 
        broker is. If that doesnt work, ask that accountant 
        you hired to manage all of your Y2K consulting practice 
        profits!
      Merchant of the Trade
      Our industry is changing. We MCSEs, MCPs, MCSDs, and 
        the like are no longer viewed as just hackers, mere computer 
        guys and gals. Now clients and top management view us 
        as experts. With this increased visibility comes increased 
        likelihood of litigation. And, like the architect who 
        appears in court when a suspended dance floor crashes 
        in a hotel, MCSEs, et al., will get to know the courtroom 
        when enterprise-wide WANs fail because of design negligence. 
        In fact, I now take project meeting minutes just like 
        architects and general contractors do on construction 
        projects.
      So what does it all mean? Should you vacate your MCSE 
        designation and join the ski patrol up on a mountain pass? 
        Perhaps not. By managing your professional consultant 
        affairs intelligently, you can join the ranks of happy, 
        healthy, and wealthy MCSEs across the land. So, rewrite 
        that engagement letter with your attorney, be careful 
        about what you say (especially in written reports), and 
        acquire professional liability insurance. And be sure 
        to raise your consulting rates to cover those insurance 
        premiums! Good luck.