How Does the Screening Report Work?


How the Screening Report Works

In this article, we’ll further explore how the Screening Report feature works. Also called a Contract Status Report,” Screening Reports quickly extract key information about Contracts by comparing tagged Issues and terms with the current status of Issues outlined in a designated Playbook.

Note: While a Playbook isn’t required to Analyze a Contract in the Contract Analyzer, the option to download a Screening Report will not appear in the Analyzer until a Playbook has been added.




Screening Report Columns

The Screening Report will pull key information from the current turn of your Contract. The same five columns of information will always show, though the information displayed in each column will differ depending on your current Issues and what’s contained in your Playbook.

The five columns listed in the Screening Report are:

  • Issue
  • Status
  • Deviation Guidance
  • Drafter’s Note
  • Language



Issue: Lists the pre-configured Issues from your Playbook. The Issues in the Screening Report will always be listed in the same order as they are listed in the Playbook.



Status: Assigns a Status for that specific Issue, based upon the corresponding Issue in the Playbook.

The different Status Fields within a Screening Report are generated by the expert-driven AI system of the DocJuris Analyzer and will be based on the established Positions in your Playbook. More on Status Prioritization below.




Deviation Guidance: Instructions to a User of a Playbook on what approvals must be sought regarding an Issue in a Contract.



Drafter’s Note: Plain-language guidance for a reviewer about a Preferred Position or Counterparty Position meant to explain a position.

Note: If there are multiple Positions for an Issue in a Playbook with corresponding Drafter’s Notes for each (e.g., Preferred, Fallback, and/or Reject), the Screening Report will pull the Drafter’s Note from the matching Position for that Issue based on the given Language (listed in bold in the Language column).




Language: Lists relevant Language of an Issue based on the pre-configured Positions and Position Tags of that Issue in the Playbook. The Screening Report will list the Issue language in BOLD and display the language of where the Report found those associated clauses, provisions etc. in the Contract.mceclip7.png


Status Column Prioritization

The Status column reflects the Status of the Issue for that Contract based on your pre-defined positions of your Playbook. As the Screening Report extracts part of the Contract for the Language Field, a Status is assigned based upon the corresponding Issue of the Playbook.


In general, an Issue Status on the Screening Report will be highlighted based on the Playbook position as: Fallback (Orange), Concerning/Red Flag (Red), May require review (Gray)Potentially Acceptable (Green) or Escalate Directive (Yellow).

The following screenshot is from an example Screening Report, and shows how different Statuses might be highlighted in the Report based on a Playbook.


ScreeningReport_STATUS_MARKEDUP_SAM57_EDITEDforArticleScreenshot.png A. Fallback (Orange):

This Status reflects a Counterparty’s Fallback Position in the Playbook. Signals that a Counterparty’s Contract or proposed Incoming Redlines is acceptable subject to the Fallback Position.

B. Concerning/Red Flag (Red):

This Status signals that concerning language for that Issue Tag has been found that is a red flag, or should be removed, based on your established Positions for the Issue. This Status also signals when associated language for the Issue is Concerning or Missing from the contract.

C. Potentially Acceptable (Green): Appears when language in the Preferred Position for that Issue in the Playbook is found in the Contract.


Note: In this example, if the Preferred Position for an Issue is that the Language should not be present in the Contract, the Screening Report will highlight that status in green as a "not found" to signal that that language was not found in that Contract.


D. May require review (Gray):

This Status appears in the Screening Report column when no Position Tag has been defined for the Issue, or if it does not match any Position Tags. Standard Match clauses are also highlighted in Gray in the Contract Analyzer. 

E. Concerning (yellow flag) / Escalate Directive (Yellow): 

This Status appears in the Screening Report column when an Escalate Directive has been added to a Counterparty position. This Status appears when a concept is included in a contract but contains problematic language or redlines that require an escalation and approval.



The Status of each Issue listed on your Screening Report is prioritized based on the Issue and Position Tags in your Playbook. If there is a Position Tag for the Issue, the Status highlights will be prioritized in the Language column in the following order:

  1. Missing
  2. Concerning (red flag)
  3. Concerning (escalation required)
  4. Concerning (fallback)
  5. May require review
  6. Not found
  7. Potentially Acceptable


Additionally, the Status will evaluate whether the Language of the Issue has been found Missing, May Require Review, or Concerning (Red Flag) in the Contract, based on the Playbook:

  • Missing: The language as outlined in the Issue of the Playbook is not found by the Contract Analyzer.
  • May Require Review: The Contract Analyzer has highlighted language that is questionable.
  • Concerning (Red Flag): An Issue within the Playbook has been found OR there are “gaps” within the language as compared against the Playbook. Example of this is when a Contract contains the word “defend”, but it is not found in the same sentence as “indemnify”.