Litigation Support Technical Standards
by Mark Lieb



Sample Content
  • Table of Contents
  • Introduction
  • For Vendors
  • For Firms


    • Business Standards
  • Cost Codes
  • Outgoing Media Kit
  • RFQs
  • Quotes


    • Technical Standards
  • Media Labels
  • Bates Schemes
  • Native Files
  • File-Folder Names


    • Downloads
  • The Standard
  • The Book


    • Software Load Files
  • CaseSoft
  • IPRO
  • To Be Added


    • What Not To Do
  • Media Labels
  • Load Files
  • Transcripts
  • General Errors


    • More Resources
  • LSVA
  • Litigation Support
  • Ad Litem Consulting


    • Mark Lieb
    Ad Litem Consulting



    litgation





    Home | TOC | Previous | Next | Download

    3.13 Slip-Sheets or Unitization Rules

    If not already done by the client or the firm, the scanning company should place a slip-sheet between each document before scanning. After the documents are scanned, the vendor needs to provide logical document breaks. The Firm requires a 1 document to one database record ratio. Between slip-sheeting during scanning and the logical document breaks service, this ratio should be guaranteed. Slip sheets should not appear in the database or images.

     

    The resulting database must maintain the parent-child document relationships through the “BegAttach” and “EndAttach” fields.

     

    When the firm requires the vendor to print documents to paper, a non-white slip-sheet must separate every document. Blue and dark green are the preferred colors for slip-sheets. If the slip-sheets use more than one color please refer to the color blindness specifications.

    Home | TOC | Previous | Next | Download

    Contact Ad Litem

    (C)2005 Ad Litem Consulting, Inc.









    About Litigation Support Technical Standards

    This document was initially designed to eliminate any discrepancy between firm technical needs and how the vendor created the technical aspect of their products. Litigation Support spends needless hours changing the vendor delivery. The firm pays for product that litigation support will have to modify. Today, the document covers as many technical requirements as possible for as many types of discovery and software as possible.

    To get a good idea of the reason for these explicit directions, please visit the final section of this document entitled, “Things not to do”. All of these examples are from real life. All of these examples caused headaches, delaying reviews, productions and more.

    I hope that this document is helpful to you.

























    Template by Steves Templates