Review 2.0 FAQ

Is Review 2.0 included in my current contract?

Yes. Review 2.0 is available to all customers who already have Review included in their contract.

Do I have to change anything to use Review 2.0?

No. The main change is an updated button in the Word add-in when you run a review. You do not need to make any changes on your side.

When will I get access to Review 2.0?

Review 2.0 will be available to all users starting May 4th. If you would like access to it prior to that date, please reach out to your CSM.

Why are playbooks moving away from checklists?

Review 2.0 replaces checklists and clauses with positions, which are easier to create and manage. A position combines the logic of both checklists and clauses into a single, unified format. This creates a more streamlined and accurate review process.

Can I submit TDF in Review 2.0?

Yes. TDF still works in the same way that your TDF is sent to Implementation and Engineering teams and they work on it.

What happens to Ivo Flags?

Ivo Flags are not included in the current version of Review 2.0. For now, users can use Assistant in their place. Support for Ivo Flags is planned for a future release.

What are Benchmarks?

Benchmarks is a feature in Review 2.0 that compares the contract currently under review against the customer’s own historical contracts stored in Repository Intelligence. When enabled during a review, it shows how the agreement’s terms compare to past negotiated positions.

How do I create and update Review 2.0 playbook?

See this article.

What’s different between Review 1.0 and Review 2.0?

Review 2.0 is a ground-up rebuild of Ivo’s contract review experience.

The biggest change is that Review 2.0 evaluates the entire agreement and all playbook positions holistically. Instead of generating multiple separate flags on the same clause, it produces one consolidated recommendation per topic.

Positions replace the old checklist items, making it easier to capture your standard position, fallback language, and edge cases in one place using plain language. If a position is not relevant to the agreement being reviewed, it is automatically marked as N/A.

Review 2.0 also allows users to run up to three playbooks in a single review, with results consolidated into one review experience.

Another major upgrade is Deal Context. In Review 1.0, Deal Context only influenced Ivo Flags. In Review 2.0, it shapes the full review, including which positions apply, which fallbacks appear, and which items are marked N/A.

For customers with Repository Intelligence, Benchmarks is also new. This feature allows users to compare the current contract against their own historical agreements during review.

What are triggers?

Triggers are contextual questions based off your positions that help inform deal context, improving the review process.

How many playbooks can I run at the same time in Review 2.0?

You can run up to three playbooks at the same time in Review 2.0.

Will implementation services still be offered?

Yes, we still offer implementation services for customers who prefer not to handle playbook creation themselves.

Why can't I use benchmarks in Review 2.0?

Benchmarks are generated based on the contracts in your repository. If you are unable to access Benchmarks, it likely means your repository access has not been set up yet. Please reach out to your CSM to get repository access enabled.