This workflow is best for incoming third-party paper
Use this workflow when another party sends you their contract and you need to:- Identify legal, commercial, and drafting risks
- Find missing or one-sided provisions
- Generate a first set of proposed redlines
- Add comments explaining requested changes
- Prioritize the issues that need closer review
Configure your review before running it
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 that the profile matches the party to the contract.
2
Select No Playbook.
This allows LOIS to review the contract based on your instructions rather than a set of predefined checks.
3
Add the legal and business context for the review.
Use the context box to tell LOIS what perspective to take and what to prioritize, including:
- 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.
- Redlines only reviews the tracked changes made to the contract.
- Selected text reviews only the language selected in Word.
5
Configure comments.
Turn on Suggest a comment for every redline if you want LOIS to prepare a comment for each proposed change. If you leave this setting off, LOIS generates comments for AI-identified issues when it determines that a comment would be helpful.
6
Select Run review.
LOIS reviews the contract clause by clause and surfaces results as the review progresses.
Decide which recommendations to apply
Each result may include:- A risk rating of high, medium, or low, or a pass result
- An explanation of the issue
- A proposed redline
- A proposed comment
Use follow-up instructions to refine individual clauses
For a provision that needs more analysis, select the speech bubble to chat with Composer and ask a focused follow-up question.Example follow-up prompts
- “Explain how this limitation of liability provision affects the customer.”
- “Revise this indemnification clause so that it is mutual.”
- “Propose a narrower change that preserves the existing structure.”
- “Draft a fallback position if the vendor rejects this redline.”
- “Draft a question for the business stakeholders about whether this renewal structure is acceptable.”
Apply the changes you want to make
LOIS does not modify the contract until you approve and apply a result. When you are ready to apply 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
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 business decisions, required approvals, or input from relevant internal stakeholders have been resolved
- The comments are appropriate to share with the counterparty
- The document contains only the tracked changes and comments you intend to send
Use a playbook when positions must be applied consistently
An instruction-driven review works well for identifying issues and preparing an initial redline. Use a playbook when your organization needs LOIS to apply specific:- Preferred positions
- Approved fallback language
- Escalation requirements
- Approval thresholds
- Prohibited terms