Legal & Compliance
Draft a privilege log from your document list
Upload your review export as CSV or XLSX and get draft log rows with missing fields flagged. Whether a document is privileged stays the decision of counsel.
or drop it here
- CSV / XLSX
- Up to 50 rows
- 64,000 extracted characters maximum
DOC-004 | 8 April 2027 | From: Counsel Example | To: Project Lead | Subject: Request for advice
- Document: DOC-004
- Subject: Request for advice
Privilege-log workbook, family CSV, exceptions and evidence manifest
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
Drafting a privilege log from your review export
Your review export goes in
You upload the document list from your review platform as a CSV or XLSX file. One run takes up to 50 rows and 64,000 extracted characters. Document ID, date, author, recipients and subject are the usual columns, and their values are carried through exactly as supplied. Parent and attachment rows are grouped by the family identifier already in your export. A file over the limit is rejected before the job starts, so you never get a partial log that looks complete.
The workbook and the exceptions list
You get a draft privilege-log workbook, a family CSV and an exceptions list. Descriptions are written only from the text you supplied and kept neutral. When a row is missing a date or a recipient, it is flagged and moved to the exceptions list instead of being filled in. A summary file records a checksum of your source, a short code that changes if the file changes, so you can confirm which upload the log came from. Your export is not changed.
Templates, and the decision that stays with counsel
You can use the standard log layout or upload your own column template, and the draft rows are written into those columns. The privilege basis always stays an empty field. Deciding whether a document is privileged is the job of counsel, and nothing in the draft is legal advice. Keep sensitive wording out of descriptions where you can, and read every row before the log leaves your team. The job costs 2 AI credits and needs an account.
Questions before you run it
Does it decide which documents are privileged?
No. The privilege basis stays an empty field for counsel to complete. The draft assembles the surrounding metadata so a reviewer is not retyping it, and nothing here is legal advice.
Which columns does it expect in the export?
Whatever your review platform exported: document ID, date, author, recipients and subject are the usual ones. Values are carried through exactly as supplied rather than reformatted.
How are document families handled?
Parent and attachment rows are grouped by the family identifier already in the source and kept together in the family CSV, so an attachment is not logged as a loose document.
What if a row is missing a date or a recipient?
The gap is recorded as a missing-field warning and the row moves to the exceptions list. Nothing is inferred to make the log look complete.
Can I use our own log format instead of the standard one?
Yes. Upload a custom column template and the draft rows are written into those columns.