Ad Litem Consulting, Inc.

Native Files

Relational Databases

Spreadsheets are not printer friendly. Spreadsheets are rarely formatted to accommodate the printed page. As such, when vendors convert a spreadsheet to .TIF file, the results can be hundreds or thousands of pages of almost useless information and lots of blank pages.

The following is the approach the firm wishes to employ in representing spreadsheets in the database, review and production:

In the Database: 

For every spreadsheet, there should be a record. Add the appropriate full metadata to the record. Include a hyperlink to launch the spreadsheet as a native file. For the image, put a placeholder explaining that the document is being reviewed as native file. Therefore there is no image of the spreadsheet.

The File: 

Files should retain their original filenames and be read-only. These files go under the traditional X:\ATTACH\[client#]\[matter#]\[DB]\

Production Options –

Native:  Spreadsheets should be produced natively. The CD label should have a Bates stamp. Included with the CD is a cover-page, bearing the next Bates stamp number. The cover-page should include a list of every native file, along with filename, file date and all other attributes.

Petrified: Spreadsheets should be converted to .TIF, per our technical standards. Any load files you return should reference the internal control number as well as the new production Bates start and end numbers.

Printed: Spreadsheets should be “blown back” to paper with any associated text and production Bates number.

Native Files

Relational Databases