The Review Process
A structured approach to reviewing software terms, prioritizing legal judgment and substance.
01
Intake form
Enter the vendor's website URL along with other context for the review such as the software's purpose and concerns you may have regarding it.
02
Apply your team's playbook
You maintain master playbooks for your organization (e.g. Standard T&C, Data Privacy, etc.). Playbooks are a set of requirements and preferences you have regarding your vendors' terms. Pick and update the playbooks as needed for the current review.
03
Scrape Documents
The system will find all legally binding documents on the vendor's website. You decide which documents to include. You can add any documents that may have been missed. These are documents that will be analyzed against your playbooks.
04
First-Pass Analysis
Top tier AI models analyze each document against every playbook item to determine if the requirement is met. The analysis provides reasoning for its determinations including the references clauses, superseding language, governing language, jurisdiction, etc. Each playbook item has an associated list of findings that pertain to it. The analysis includes findings of interest beyond your playbooks specifications along with recommended usage conditions for the software.
05
Legal Judgment
Review every finding. The AI's analysis is a time-saving first draft. Accept, edit, or replace anything the AI produced. You can clearly differentiate & filter between what was the AI's work vs human work. You can add your own findings within the documents if the AI missed a relevant clause. You can view and edit findings within an aggregate summary dashboard and within the documents themselves.
The Analysis Workflow
TermTrax automates the first-pass documents discovery and clause analysis, but every legal judgment remains with the lawyer. Our system identifies critical risks and inconsistencies, providing a clear foundation for your review.
Every requirement in your playbook is accounted for. Every finding cites the exact source clause. Gaps are flagged when the terms are silent on something your playbook requires.