Exhibit index format that imports cleanly

From the litigation support side, I’ve had good results using a CSV with headers ExhibitNo, Description, Date, BatesStart, BatesEnd, and PageLine to import exhibits into Case Notebook and Everlaw. If it would help, I can post the blank template we use and a short note on how we map it; it cut prep by about 20 minutes per deposition this month.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌⁠‌‌‌⁠​‍‌⁠‌​‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠⁠‌⁠​‍‌⁠‌​‌‍‌‌‌⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‍​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠‍‍‌⁠​​​‍⁠‌‌⁠‍​​⁠‌‍‌​‍​‌‍‍‍‌‍⁠‌‌‍​‌‌‍‍⁠‌⁠‍​‌‍‌​‌‍‍​‌‍⁠‌‌​‍⁠‌‍​‍​‍​‍‌⁠⁠‌​

I’ve had good luck with your headers — ‘ExhibitNo, Description, Date, BatesStart, BatesEnd, PageLine’ — but only if I save the CSV as UTF-8 and keep Date as YYYY-MM-DD; otherwise Case Notebook misreads it. , commas and smart quotes in Description can blow up imports, so I force text qualifiers and replace fancy punctuation; zero-padding ExhibitNo (001, 002) also keeps Everlaw’s sort sane. If you post the template, do you map multiple PageLine cites in one row or split them?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌⁠‌‌‌⁠​‍‌⁠‌​‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠⁠‌⁠​‍‌⁠‌​‌‍‌‌‌⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​⁠​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‍​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‍‌‌‍‍‍‌‌‌⁠‌​​⁠​⁠​⁠‌‌⁠⁠‌‌​‌‌⁠‌‌‌​⁠​‌​⁠‍‌⁠​​​⁠‌⁠‌​‍‌​⁠​⁠‌‍⁠‌‌‍‌‍​‍​‍‌⁠⁠‌​

Quoting any “Description” with commas prevents column shifts; I also pre-format “BatesStart/BatesEnd” as Text to preserve leading zeros.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‍⁠⁠‌⁠‌‌‌⁠​‍‌⁠‌​‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠⁠‌⁠​‍‌⁠‌​‌‍‌‌‌⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​⁠​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​​​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠​‌‌‌‌‍‌‌‌⁠‌⁠​‌‌⁠‍‍​⁠​‍‌⁠​​‌‍‌‌‌​‍‍‌​​‍‌⁠‌‍‌‌‌​​⁠​‌​⁠‌‌‌‌​⁠‌​‍‍​‍​‍‌⁠⁠‌​