Review Modes

When you start a Document Review, you choose one of three modes to configure what Judicio checks for. Each mode generates a set of compliance checks -- the specific items Judicio will evaluate in your documents. The difference is in how those checks are created.

The three modes at a glance

	Smart	Template	Custom
How checks are created	AI reads your files and suggests checks	You select a pre-built template	You describe what to check in plain language
Setup time	~30 seconds (AI generates checks)	~10 seconds (pick a template)	~1 minute (write your query)
Customization	Edit AI suggestions before starting	Override individual template checks	Full control over the query
Best for	First-time reviews, unfamiliar document types	Recurring reviews of the same document type	Specific questions or niche requirements

Detailed mode guide

Smart Mode

Smart Mode

Smart mode lets Judicio's AI analyze your uploaded files and automatically generate a set of compliance checks tailored to the document type, parties involved, and clause structure it detects.

How it works:

1. You select your files and choose Smart mode.
2. Judicio scans the document metadata -- document type, parties, key clauses, and page count.
3. The AI generates a suggested review name and a set of checks, each with:
   • A check name (e.g., "Termination Clause Review")
   • A severity level (must_have, should_have, or nice_to_have)
   • An acceptable position -- the preferred clause language
   • A fallback position -- an alternative that is still OK
   • An unacceptable position -- language that should be flagged
4. You review and edit the suggested checks before confirming.

When to use Smart mode:

• You are reviewing a document type for the first time and are not sure what to check
• You want a comprehensive review without manually defining every check
• You want to discover issues you might not have thought to look for

Recommended for first reviews

Smart mode is the best starting point when you are new to a document or document type. After reviewing the AI-suggested checks, you can save them as a template for future use.

Example: You upload a SaaS agreement you have never seen before. Smart mode detects it is a software services contract with two parties, identifies clauses related to SLAs, liability caps, data protection, and IP assignment, and generates checks for each -- complete with acceptable and unacceptable positions for your side of the negotiation.

Template Mode

Template Mode

Template mode lets you select from pre-built review templates designed for common document types. Templates contain a curated set of checks that have been optimized for specific contract categories.

How it works:

1. You select your files and choose Template mode.
2. Browse available templates -- both system templates (provided by Judicio) and your own saved templates.
3. Select a template. The checks are loaded automatically.
4. Optionally override individual checks to adjust severity levels, positions, or add new checks.
5. Confirm and start the review.

When to use Template mode:

• You regularly review the same type of document (e.g., NDAs, employment agreements, lease agreements)
• Your team has standardized review criteria that should be applied consistently
• You want fast, repeatable reviews with minimal setup

Available system templates include:

• Non-Disclosure Agreement (NDA)
• Employment Agreement
• Commercial Lease
• Software License Agreement
• Service Level Agreement (SLA)
• Vendor/Supplier Agreement
• Share Purchase Agreement

Custom templates

You can save any review configuration as a custom template. See Review Templates for details on creating, managing, and sharing templates with your team.

Example: Your firm reviews 20 NDAs per week. You create a template with your standard NDA checks (confidentiality scope, term and termination, carve-outs, remedies, governing law). Every associate on the team selects this template and gets consistent results.

Custom Mode

Custom Mode (Ask Judicio)

Custom mode -- also called "Ask Judicio" -- lets you describe what you want to check in plain language. Judicio interprets your query and either generates structured checks from it or runs a free-form analysis.

How it works:

1. You select your files and choose Custom mode.
2. Type your review query in the text box. You can be as specific or as broad as you like (up to 5,000 characters).
3. Judicio generates a set of checks based on your query. You can review and edit them.
4. Confirm and start the review.

When to use Custom mode:

• You have a very specific question about a document (e.g., "Does this contract allow assignment without consent?")
• You need to check for something not covered by existing templates
• You are conducting a focused review on a narrow issue rather than a comprehensive review
• You want to combine multiple specific concerns into a single review

Writing effective queries:

Query quality	Example
Too vague	"Check this contract"
Good	"Check for unfavorable indemnification clauses, missing limitation of liability, and one-sided termination rights"
Excellent	"Review this vendor agreement from the buyer's perspective. Flag any clauses where: (1) indemnification is uncapped, (2) liability limitation excludes IP infringement, (3) termination for convenience requires more than 30 days notice, (4) auto-renewal locks us in for more than 12 months"

Be specific about your perspective

Tell Judicio whose side you are on. "Review from the tenant's perspective" or "Flag issues unfavorable to the buyer" helps the AI calibrate what counts as acceptable versus unacceptable.

Example: You are reviewing a commercial lease and your client is concerned specifically about break clauses and rent review mechanisms. You type: "Analyze the break clause provisions and rent review mechanisms from the tenant's perspective. Flag any provisions that restrict the tenant's ability to exercise a break or that allow upward-only rent reviews."

Checks: the building blocks of every review

Regardless of which mode you choose, the review is driven by compliance checks. Each check has the following components:

Component	Description	Example
Name	What this check looks for	"Limitation of Liability"
Description	Additional context for the AI	"Check whether liability is appropriately capped"
Severity	How important this check is	must_have, should_have, or nice_to_have
Acceptable position	The preferred clause language	"Liability capped at 12 months of fees"
Fallback position	An alternative you can live with	"Liability capped at total contract value"
Unacceptable position	Language that must be flagged	"Unlimited liability for the service provider"

The severity level directly influences the risk level assigned to findings. A "must_have" check that fails will produce a high-risk finding, while a "nice_to_have" check that fails will produce a low-risk finding.

Choosing the right mode

Combine modes over time

Many teams start with Smart mode for new document types, refine the checks after reviewing results, save them as a template, and then use Template mode going forward. Custom mode is always available when you have a one-off question that does not fit your templates.