> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/review-tool-concepts/document-review/policy-engine.md).

# Policy Engine

In Protege, policies are essential guidelines used to evaluate content for legal risks during document editing or attachment review. Think of these as heuristics or guidelines the AI is coached to look for. These policies are organized into policy groups, which allow users to apply multiple policies collectively to specific document types for thorough analysis.

Policy Engine is also where you manage **Attributes** (the **Attributes** tab). Create categories such as market or product there — not in Settings — so policies can target the right content.<br>

**Document Evaluations Structure:**

A Document Evaluation is a structured assessment that can be applied to each type of document reviewed within the Protege Review system. This evaluation assesses documents against specific criteria defined by the organization’s policy requirements.

**Example**: Basic Review (included in most customer's environment). Included Policy Groups:

* Trademark and Claims Policy Group. Included Policies:
  * Trademark Identification
  * Claim Identification

**Policy Group Structure:**

A policy group consists of multiple policies bundled together. Users can assign policy groups to specific document types to streamline the review process. For instance, a policy group may include various policies relevant to a particular category or context.

**Example**: Core SaaS Policies. Included Policies:

* Claims: Identify claims about the product or service.
* Competitive References: Generally avoid references to competitors; focus on the value of the organization’s products, services, or features.
* Compliance Guidelines: Ensure compliance with industry regulations and standards.

\
**Policy Structure:**

* **Name**: Competitive References
* **Description**: Generally avoid references to competitors; focus on the value of the organization’s products, services, or features.
* **Steps**:
  1. Identify the sentences that reference competitors.
  2. Provide an explanation for the text, emphasizing the importance of focusing on the organization's offerings rather than competitors.

**Example Policy:**

* **Policy**: A policy represents a specific guideline or rule used to assess content for legal risks. Each policy consists of the following components:
  * **Name**: Describes the title of the policy, providing a clear indication of its purpose.
  * **Description**: Offers a brief explanation of the policy's objective and guidelines for compliance.
  * **Steps**: Outlines the actions or procedures involved in implementing the policy's guidelines effectively.

***

By leveraging policies and policy groups, users can ensure thorough and consistent evaluation of content for legal risks, ultimately enhancing compliance and mitigating potential liabilities. If you have any questions or need further assistance regarding policy management or document review processes, please don't hesitate to reach out to our support team.\ <br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tryprotege.com/review/review-tool-concepts/document-review/policy-engine.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
