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.01 Media Labels

    The following information should be visible on the CD, DVD, Tape, or a space provided where the information can be written clearly later. Some vendors forget to write their own contact information on the labels. It is helpful to have the contact information for the media’s creator.

     

    Please reference the examples on the following pages.

     

    Required Fields

    Sample Values and Examples

    Vendor Name

    ACME Scanning and Coding

    Vendor Address

    123 Main Street

    Vendor Phone

    (555) 555-1212 (voice) / (555) 555-1213 (fax)

    Date of Media Creation

    12/02/2003

    Format Type

    CD, DVD

    Volume Name

    Examples are "FER001, FER002, FER003"

    X / Y

    Examples are "1 / 3", “2 / 3”, “3 / 3”; or just “1 of 1”

    Bates Ranges

    Examples are "FER000001 – FER001300"

    Client-Matter Number

    Example, "320123 – 00123"

    Image Count

    13,000 TIF images

     

    A Note on Handwriting

    A hand-written label is not acceptable. Handwritten labels are cryptic and illegible. Further, a pen can damage the media. Vendors should not make the firm re-label media. The purpose of the label is to provide a complete picture of the origin and content. If a label must have handwriting, script is preferred. Cursive handwriting is never acceptable. Bear in mind that other people have to read your writing.

     

    Remember, the firm is making significant investment of the client's money. The media provides the first impression of the vendor's work. Perception is reality. If the delivery looks boiler room, then the Litigation Support persons will view the vendor as boiler room quality. If a vendor is sloppy on their label, chances are they are sloppy in all else they do.

     

     

     

    Basic Information – Generic Template

     

    Basic Information – Example with Play Data


    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