End of Branch Use Cases

In certain situations, such as time-sensitive reviews, reviewing only end of branch documents and all associated attachments, can save considerable time. The case team can bulk tag the less inclusive thread members based on review of the end of branch email, ensuring consistency in the handling of identical information.

When reviewing end of branch email, you will lose attachments over the course of the thread (for example, contract drafts). Go back and review attachments to individual emails. This will add additional context to the thread and, depending on your tagging criteria, review of attachments could change the review call on the thread.

End of branch functionality can be particularly useful when deploying an investigative workflow for hot document identification. When running a targeted search to determine "Who’s Who” or “What’s What,” identify the end of branch documents and review threads in their entirety. This can help you quickly determine what information was disseminated to whom and when. End of branch functionality used with Hypergraph also provides an efficient solution to investigating a communication web.

When you use the end of branch filter during a privilege review it will give you the ability to follow privileged material through the thread. This reduces the need to run additional privilege searches across the database as the end of branch review is inclusive of all the emails.

Use end of branch functionality to create or strengthen seed sets for Predictive Coding. For example, you can run targeted searches for exemplar documents, add a thread expansion and then add an end of branch restriction. You can then review just the end of branch emails. If you find individual emails within the thread are relevant while others are not, open the associated document view and tag each member of the thread individually. You can then run Predictive Coding on just the relevant documents.