How to Use Reviewer Choices for Privilege Log Reasons with Chronicle

Chronicle makes it easy to use reviewer choices for privilege logs reasons once reviewers code documents.

How? Chronicle empowers project leads to guide reviewers' specification of the privilege reason via Relativity Fields and Choices and leverage Chronicle's concatenation capabilities.

With this understanding, let's dive into the specifics of how Relativity users can leverage Chronicle to populate priv log reasons based on reviewer choices for priv log reasons

Instructions

Start by setting up your fields and choices.

1. Create two new single-choice fields that will be used to store the combinations of phrases that should be used for the priv reasons.

   1. "Priv Description Prefix"

   2. "Priv Description Suffix "

2. Specify Choices for the Prefix, e.g.,

   1. "Confidential email "

   2. "Confidential email from outside counsel "

   3. "Confidential email from in-house counsel "

3. Specify Choices for the Suffix, e.g.,

   1. "discussing the acquisition of business assets post-merger. "

   2. "discussing disclosure of business contacts during the merger. "

   3. "discussing the appropriation of funds during the merger. "

4. Add these Fields to a Layout for your reviewers to work with.

   1. Optionally make them required (this is really up to how you want the workflow to go)

   

   
   

Setup your Priv Log template using concatenation.

1. Navigate to the Chronicle Privilege Logs tab and create or edit a Priv Log.

   1. If creating, give it a name and select a saved search.

   2. Add any other columns you need besides Priv Reason.

2. Add a new Column

   1. 

      Name = "Privilege Reason" (or similar)

   2. Outcome = “{{Priv Description Prefix}} {{Priv Description Suffix}}”

      1. Note the space between the two fields.

3. Save the Priv Log

Turn the reviewers loose and watch the Priv Log entries roll in!

At this point, Chronicle takes over, and any documents coded as privilege (based on your Saved Search) will show up in your Priv Log, and the Priv Reason column will show the concatenated values of the Prefix and the Suffix fields!

Bonus: Having a backup in case your choices don't cover everything!

Now, it's possible that the list of reasons you specify in your choices only covers some things. One way to handle this is to add a new field to act as an override if the choices aren't cutting it.

1. Create a new fixed-length text field - Priv Description Override.

2. Add this to your layout alongside the two choice fields we created earlier.

3. Update your Priv Log column definition to use an Outcome so that when there is no value for Priv Description Override, we concatenate the Prefix and Suffix (as defined above) but use it if it's there.

   
   

   

   
   

And that's it!

Guiding the reviewers in their coding will save time on the backend by reducing the variance in reasons you have to QC. Now it's time for you to try using reviewer choices for your next privilege log by adding Chronicle to your workspaces.

Ready to use reviewer choices for priv log reasons leveraging Chronicle? Reach out ➜