title: What are the core elements to include in Support Documentation?
body: <p>I have created an <strong>application which needs 'hand-over'</strong> to the support group in the next month.</p>
  
  <p>The application is <strong>fairly small</strong> (2 months development), and consists of two client side applications and a database, it's written in c# for the windows platform.</p>
  
  <p><strong>I have a broad idea</strong> of what to include in a support document, but I haven't needed to make very many support documents so far in my career and I want a solid list of items to include. </p>
  
  <p>I guess my <strong>goal</strong> is to make the <strong>lives of everyone</strong> in the support group <strong>easier</strong> and as stress free as possible.</p>
  
  <p><strong>So I guess my questions are:</strong></p>
  
  <ol>
  <li><p>What should a support document absolutely contain</p></li>
  <li><p>What additional things have you put in support documents to make them extra useful.</p></li>
  <li><p>What other activities can be done before hand-over to make all our lives easier?</p></li>
  </ol>