Setting up Search Tags

Article author
Gaby Estrada
  • Updated

DocJuris Playbooks use Search Tags to find and highlight language relevant to Contracts. When you type and create a Tag and press "Enter" on your keyboard, pressing "Enter" is effectively adding OR between the Tags. Or, if you're looking at pre-configured tags, simply select one. More on the different tag fields below.

For a detailed written guide with an example of how to use Search Tags to create Key Concepts within an NDA Playbook, click here.

Issue and Position Tags

There are four places to add Tags inside of a Playbook Issue:

  • Pre-configured Tags: DocJuris has a Natural Language Processing (NLP) data set that locates and classifies over 300+ Issue clause types. If you choose one of these Pre-Configured Issue Tags, DocJuris will find the legal concept in an uploaded contract and provide locations, relevancy, and number of incidences within the document.
  • Custom Issue Tags: If the Pre-Configured Issue Tags are not sufficient, or if a User needs a more specified Issue, a Custom Issue Tag can be created. By default, each individual tag in a DocJuris Issue or Position Tag is separated with an OR operation.

For example, when creating Tags, typing indemnity [PRESS ENTER] harmless will search for the word indemnity OR the word harmless in any single paragraph/provision.

  • Custom Must Match Tags - these are the same as Custom Issue Tags, except these Tags join other Tags with AND.

For example, if you select a pre-configured Tag for indemnity, and type/enter pollution as a Must Match Tag, the Playbook will look for all indemnities that must also match pollution.

  • Position Tags - Position Tags are the second layer of search that highlights words inside of a matched paragraph. They work similar to Custom Issue Tags, except they search within a matched provision which is found, and then highlights language in red/green/amber depending on the Position Type (Accept/Reject/Fallback, respectively). The user is then able to click the Matched Language in the contract and reverse scroll back into the Playbook to view guidance instantaneously.

For example, once you Issue Spot indemnity using one of the Tags above, you can use a Position Tag at the fallback level to highlight gross negligence in orange.

Best Practices

Dos:

  • Look at sample contracts and find trends in the type of clause that the playbook issue relates to. For example laws of the state of is a good start for a tag relating to governing law.
  • Tag phrases that have a unique relationship to the related provision. For example, "intellectual property" or "act of God".

Don'ts:

  • Using common/general words and phrases in a single Tag such as notwithstanding, equipment, or the party.
  • Not using operators to both expand (e.g., ! and * ) and limit (e.g., &) your search. More on the Operators below.

f0afec2f-a75f-4eba-84de-86854f893f8c.webp

Examples of Connectors and Descriptions

Connector Description An Example Search Tag Common Mistakes
None Typing two or more consecutive words in a tag is automatically treated as a phrase. Although not necessary, " " is used to match an exact phrase (note, again, DocJuris automatically treats consecutive words as an exact phrase to be searched). IMPORTANT: in other words, adjacent terms are treated as phrases! intellectual property "intellectual property" - phrases do not require quotes in an individual tag, as each tag and series of words is considered a phrase
\"term\" To find words in quotes (e.g., defined terms), escape the quotes with \. This is helpful to only match parts of the contract where a defined term exists. \"Representatives\" "Representatives" - in order to flag a definition, the quotes must be "escaped" with a \ slash
& In a single tag, & will search for expressions linked in a paragraph. exclusive & jurisdiction exclusive AND jurisdiction or /p - DocJuris uses &
* A wildcard to match words with variable characters; you do not need to use the placeholder to find hyphenated terms - we do that automatically. advis*r adviser OR advisor - OR is not a recognized connector in DocJuris
! Searches for words in a contract with multiple endings (i.e., used to accept any suffix to a word within a tag) indemn! indem* - asterisks are for single characters
| As stated in the overview, DocJuris automatically treats a series of tags as an OR expression. However, when an OR expression is needed to join another operator such as &, the use of | can link expressions as OR. This is helpful to condense several & tags to a single tag for simplicity and speed. For the avoidance of doubt, the OR expression can be wrapped in a parenthetical for the same effect. defect | design defect|design - don't forget spaces.
/s The expressions on either side of /s must be found within one sentence. indemnity /s injury indemnity & injury - searches the entire paragraph not just the sentence
+s The expressions on either side of +s must be found within one sentence AND the expression on the left-hand side of +s must precede the expression on the right-hand side. limits +s liability +s liability - requires another word or term to the left and a connector
/n The expressions on either side of /n must be found within n words of one another. rep! /5 warrants rep! / 5 warrants - a space cannot be used between / and 5
term % another term The expression on the left-hand side of % must be found in the paragraph, and the expression on the right-hand side of % must NOT be found. compet! % competent compet! NOT competent - NOT is not a recognized connector due to its potential applicability as a term. Use % for not.
twrm /s% another term The expression on the left-hand side of % must be found in the sentence, and the expression on the right-hand side of % must NOT be found in the same sentence. law* of /s% texas NOT Texas - NOT is not a recognized connector due to its potential applicability as a term. Further, a term should be used to the left and right of /s%
-(w) The expression determines whether deletion is detected in an incoming document (e.g., an analyzed document contains redlines where a word or series of words are deleted). The term to be detected that is deleted should be within the parenthesis. ~(late fees) fees % late - when looking for language that is "redlined" or "deleted" by the counterparty, ~(words) should be used
+(w) The expression determines whether insertion is detected in an incoming document (e.g., an analyzed document contains redlines where a word or series of words are inserted. The term to be detected that is added should be within the parenthesis. +(gross negligence) gross negligence - trick answer! DocJuris will detect the insertion of gross negligence, but using +(words) is more accurate if the goal is identify insertions or additions by the counterparty in a markup
hasredline() The expression determines whether a change is detected from the counter party. A word or term must be used to the left and joined with another term. Note: Expression can be used with other connectors and always requires a term. indemn! & hasredline() term /5 hasredline()" hasredline() - requires another word or term to the left and a connector
(func range x y) Identifies a range of numbers – useful for notice days, insurance amounts, etc. A word or term must be used to the left and joined with another term. CGL /s (func range 1,000,000 3,000,000) (func range 5 10) - requires another word or term to the left and a connector

Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.