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.04.04 Project Folder

    These files identify the project, associated information such as attorney name and all the treatments such as stamping or OCR. These files are extremely helpful when identifying an “orphaned” volume. They are also helpful when an old project begins again after a one-year hiatus.

     

    1.       Bibliographic Coding Instructions:

    This document identifies how the database was codified. This document shows which fields were coded and any rules around the codes themselves, such as valid document types.

     

    2.       Project manuals:

    As available.

     

    3.       Vendor contact information:

    A simple text file that tells us which vendor made the CD and their contact information.

     

    4.       Source information:

    If there was an intake form, include it here. What was the source of the project – boxes or electronic discovery? Sometimes we need to backtrack from the produced CD to the originating data.

     

    5.       Ranges information:

    Show a list of the Bates ranges on the CD.


    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