

Confirm Privilege Status annotation occurs on the Final Privilege Status field on the Domains and Entity objects. This annotation is intended to identify whether a Law Firm Domain or Legal Entity is either Privilege Conferring, Privilege Neutral, or Privilege Breaking. These decisions are crucial and directly influence document privilege predictions when Populate Privilege Results is run. By following the Annotating in RelativityOne or Annotating in Excel steps, you will annotate all necessary objects.
If a specific Entity plays a dual role, both legal and business, we suggest that you give them a Final Privilege Status of Privilege Conferring. This will drive higher Recall as part of populate privilege results, and our analysis will still be able to determine documents where the individual is sharing business advice rather than legal advice.
The Final Privilege Status field can be annotated in RelativityOne on the Domains and Entities objects. See Annotating in RelativityOne for more information.
The Final Privilege Status field can also be annotated by exporting Domains and Entities lists to annotate in Excel and importing them back into RelativityOne with an overlay. This import should be completed using the Import/Export application. This can be helpful for end-clients who need to have input, but don’t operate in RelativityOne. See Annotating in Excel for more information.
Confirm Privilege Status annotations should be performed by someone with the role of Case SME. For more information see Roles and security permissions.
Use the Suggested annotation workflow to complete annotations quickly and accurately. Not using the Suggested annotation workflow could result in errors.
You can only edit the Final Privilege Status field on the Domains or Entity object when the Confirm Privilege Status pipeline step has a status of Ready to Apply Annotations.
You can also edit the Final Privilege Status for Domains when the Classify Domains pipeline step has a status of Ready to Apply Annotations and you can edit the Final Privilege Status for Entities when the Validate Entities pipeline step has a status of Ready to Apply Annotations. Although you can edit the Final Privilege Status field during these pipeline steps, we suggest for you to wait until the Confirm Privilege Status pipeline step for a more streamlined workflow.
The definitions for Final Privilege Status differ for Domains and Entities.
Following are Final Privilege Status definitions for Domains:
Final Privilege Status | Definition | Impact |
---|---|---|
Privilege Conferring | This domain belongs to an organization primarily consisting of individuals providing legal advice (e.g., outside counsel). Individuals under this domain are presumed to be Privilege Conferring by default. | Entities with this domain without its own Final Privilege Status will be treated as privilege-conferring. Mentions of this organization in the document text may also be flagged as potentially privileged. |
Privilege Neutral | This domain belongs to an organization that does not inherently provide legal advice, though some individuals under the domain may do so (e.g., in-house domains or third-party service providers). | The domain alone does not indicate privilege status unless tied to specific privileged individuals. |
Privilege Breaking | This domain belongs to an organization whose involvement negates privilege, such as an opposing party or counsel. | Presence of individuals from this domain in a communication may result in a document being predicted as not privileged, even if other privileged parties are included. |
Following are Final Privilege Status definitions for Entities:
Final Privilege Status | Definition | Impact |
---|---|---|
Privilege Conferring | This entity (e.g., a person or team) is capable of providing legal advice, such as an attorney or legal advisor. | All communications involving this entity will be analyzed for privileged content. Mentions of this entity in the text may also be flagged as potentially privileged. |
Privilege Neutral | This entity does not inherently confer privilege (e.g., non-legal employees), but may be involved in privileged conversations alongside counsel. | The entity’s presence does not indicate the presence of privilege, but it does not automatically negate its presence either. |
Privilege Breaking | This entity’s inclusion in a communication breaks privilege, such as an opposing party or unauthorized third party. | Any document including this entity may be treated as non-privileged, regardless of other participants. |
If your Matter SMEs have access to RelativityOne, they can complete the Confirm Privilege Status annotations directly on the Entity and Domain object.
To annotate Domains for Confirm Privilege Status:
To annotate Entities for Confirm Privilege Status:
Once the Final Privilege Status has been set on all appropriate objects, see Confirm Privilege Status to complete the pipeline step.
To annotate Domains and Entities using the Mass Actions available:
All domains annotated as Law Firm require the Organization Name fields populated and entities annotated as Legal Role require a First Name and Last Name fields populated. Domains and Entities missing these fields will result in a failure during Apply Annotations.
If your Matter SMEs do not have access to RelativityOne, they can complete the Confirm Privilege Status in Excel using the Import/Export application.
To prepare all Excel files for Matter SME annotations:
To import Matter SME annotations back into RelativityOne:
Once the Final Privilege Status has been set on all appropriate objects, see Confirm Privilege Status to complete the pipeline step.
The following fields are available for annotating during the Confirm Privilege Status pipeline step:
Object Type | Field | Required | Description | Notes |
---|---|---|---|---|
Domain (Priv) | Final Privilege Status |
Required for select Domains |
This field determines whether a domain is considered Privilege Conferring, Privilege Neutral, or Privilege Breaking when used as contextual information to help make a privilege prediction on a document. | Only those domains predicted as Law Firm, and the top 100 communicating domains predicted as 3rd Party must be annotated on the Final Privilege Status field. |
Entity (Priv) | Final Privilege Status |
Required for select entities |
This field determines whether an entity is considered Privilege Conferring, Privilege Neutral, or Privilege Breaking when used as contextual information to help make a privilege prediction on a document. | Only those entities predicted as Legal Role must be annotated on the Final Privilege Status field. |
It is important that you annotate the Final Privilege Status field for:
Failure to annotate will invoke the default decision logic for Confirm Privilege Status.
If an Entity does not receive a Final Privilege Status value, it’s Final Privilege Status will be determined using the following decision logic:
If a Domain does not receive a Final Privilege Status value, it’s Final Privilege Status will be determined using the following decision logic:
Why was this not helpful?
Check one that applies.
Thank you for your feedback.
Want to tell us more?
Great!