Ad Litem Consulting, Inc.
Technical Standards
Includes: - Load Files - Cost Codes - Quotes - For Vendors - For Firms  |
Newsletter Signup
Read about litigation tech strategies and best practices for the case and firm.
|
Litigation Support Department Includes:
- Budget Spreadsheet - Needs Assesment - Case Technology Plan - Task and Check Lists - Member's Area Access  |
Intro
Acknowledgements
License
Preface
1.00 Introduction 2.00 Business Standards
2.02 Cost Codes for Litigation Support
2.03 Request for Quotes ("RFQs")
2.04 Quotes
2.05 Weekly Updates
2.06 Color Blindness
2.07 Quality Control
2.08 Required Test Load
3.02 File, Folder and Volume Naming
3.03 CD Content and Organization
3.04 Organization of Sub-Folders
3.04.02 OCR Folder
3.04.03 Data Folder
3.04.04 Project Folder
3.04.05 Attach Folder
3.06 Data Files
3.07 Database Conventions
3.08 Native Files
3.09 Project Specifications Document
3.10 Bibliographical Coding Manual
3.11 Image Format
3.12 OCR
3.13 Slip-Sheets or Unitization Rules
3.14 Video
3.15 Synchronization
3.16 Transcripts
3.17 Delivery Media
4.02 IPRO
4.03 Dataflight's Concordance and Opticon
4.04 Image Capture Engineering
4.05 Summation
4.06 iCONECT
4.07 inData TrialDirector
4.nn Additional Titles to Follow
5.02 File / Folder / Volume Name Conventions
5.03 Database
5.04 Media Content
5.05 Load Files
5.06 OCR
5.07 Opticon Load Files
5.08 Image Format
5.09 Transcripts
5.10 General Errors / Issues
5.11 Real Experiences
All of the examples in the "things not to do" section are, unfortunately, real. These types of problems eat up a lot of billable time. As the document matures, the list will probably get longer. There are a lot of creative people out there working the controls. What they create is what your firm will use for review, productions and exhibits.
People are welcome to submit their experiences at http://www.eDiscovery.org.
These examples are not meant to criticize any product or person. These examples explain the types of problems one may encounter, by product, regardless of product, firm, vendor or persons involved. One goal of this document is to give both good and bad examples that anyone technical person can use to improve their products.
If you use this document, please let me know.