Skip to main content
LOIS applies the playbook across the contract, identifies provisions that do not meet your standards, and proposes changes directly in Microsoft Word.

​
This workflow is best when your organization has defined positions

Use a playbook-driven review when you need to:
  • Apply your organization’s contract standards consistently
  • Identify provisions that do not meet those standards
  • Add language required by your organization
  • Use approved fallback positions
  • Flag issues that require approval or escalation
Playbooks are useful for the issues your organization handles repeatedly or considers important. For a broader first-pass review that does not require defined rules, use Review and redline a third-party contract.

​
Start with an existing playbook

This workflow assumes that your organization has already created a playbook for the relevant agreement type and party role. For example:
  • Customer-side SaaS agreement
  • Vendor-side MSA
  • Mutual NDA
  • Data processing agreement
  • Business associate agreement
The playbook contains the checks LOIS will apply during the review, including your organization’s preferred positions, fallback language, and escalation requirements. Creating or editing the playbook happens separately from reviewing a contract. If you need to create or update one, see Building playbooks.

​
Configure your review before running the playbook

Open the contract in Microsoft Word, open LOIS for Word, and select Review.
1

Confirm that the correct organization profile is selected.

The profile tells LOIS which organization it is acting for. If you work across multiple entities, confirm the profile matches the party to this contract before running the review.
2

Select the playbook that matches the contract.

Choose the playbook for the relevant agreement type and your organization’s role.
3

Add any contract-specific context, risks, or concerns.

The playbook already provides your organization’s standard positions. Use the context box to provide information specific to this contract, such as:
  • Your organization’s role (e.g., customer, vendor, licensor, or licensee)
  • The value or importance of the relationship (e.g., a routine purchase or a high-value strategic relationship)
  • Your negotiating leverage (e.g., limited leverage or a competitive vendor selection)
  • The level of intervention you want (e.g., light touch or a more comprehensive review)
  • Any relevant jurisdictional or regulatory requirements (e.g., GDPR, HIPAA, or industry-specific requirements)
  • Any terms that have already been agreed (e.g., do not change the pricing terms)
Example review instruction
4

Choose what LOIS should review.

Select the scope that matches your task:
  • Full document reviews the entire contract against the playbook.
  • Redlines only reviews the tracked changes made to the contract.
  • Selected text reviews only the language selected in Word.
Use Full document for a first-pass review of third-party paper. Use Redlines only when you want to review changes made to a previously reviewed contract. Use Selected text when you want to review a specific provision rather than the whole contract.
5

Configure issues and comments.

Turn on the settings you want for this review:
  • Find issues with AI identifies risks beyond the checks contained in the selected playbook.
  • Suggest a comment for every redline prepares a comment for each proposed change.
If Suggest a comment for every redline is off, LOIS generates comments for AI-identified issues when it determines that a comment would be helpful. For playbook checks, LOIS generates a comment only when the playbook includes comment guidance.
6

Select Run review.

Confirm that the selected playbook reflects both the agreement type and your organization’s role. A customer-side playbook and vendor-side playbook may take different positions on the same provision.

​
LOIS applies the playbook to the selected scope

After you select Run review, LOIS evaluates the contract against each check in the playbook. It identifies:
  • Provisions that pass the playbook’s standards
  • Provisions that fail the playbook’s standards, ranked by severity: high, medium, or low
  • Required language that is missing
  • Additional issues identified by AI, if that option was selected
The results appear in the Review tab as the checks are completed.

​
Review the playbook results

Each check shows:
  • A risk rating of high, medium, or low, or a pass result
  • An explanation of how the contract compares with the playbook
  • A proposed redline when a change is recommended
  • A proposed comment if comments were requested
Sort the checks by severity or document order. Open each check to review its explanation and any suggested redline or comment. You can accept, edit, or skip individual suggestions.

​
Chat with Composer to handle exceptions

If you have questions about a check, want to explore another approach, or need to make an exception to the playbook, select the speech bubble to chat with Composer.

​
Example prompts

  • “Apply the first fallback position instead of our preferred position.”
  • “The business has approved a 24-month liability cap. Revise the proposed redline accordingly.”
  • “Propose a narrower change that preserves the protection required by the playbook.”

​
Add the selected redlines and comments to the contract

LOIS does not modify the contract until you approve and apply a result. When you are ready to add a recommendation, choose from the following options:
  • Apply to insert the proposed redline and related comment
  • Redlines only to insert the proposed change without a comment
  • Comments only to insert the comment without changing the contract
The applied changes appear in Word as tracked changes under your name.

​
Complete your review before sending the contract

After applying your selected recommendations, review the contract as you ordinarily would before sending it to the counterparty. Confirm that:
  • The redlines reflect the legal and commercial positions you want to take
  • Any playbook escalations or required approvals have been resolved
  • Any exceptions to the playbook have been approved
  • The comments are appropriate to share with the counterparty
  • The document contains only the tracked changes and comments you intend to send
You retain control over the final positions and the version shared with the counterparty.

​
Update the playbook when your organization’s position changes

A playbook should reflect how your organization currently reviews and negotiates contracts. If reviewers repeatedly override the same check or use a different fallback, consider updating the playbook rather than treating each instance as an exception. Save useful negotiated language as precedent and update playbook checks when your organization adopts a new standard position.

Playbooks overview

Building playbooks

Composer

Review and redline a third-party contract