Contract Review & AI Analysis

Review setup options

What each of the six setup fields changes, and which ones actually affect the result.

6 min read · Content updated:

The setup screen is short by design — six fields, no hidden switches. Two of them materially change the analysis, and the other four decide how the result is labelled and where it is filed. Two minutes here saves re-running a review that answered the wrong question.

The six fields

File Name
Rename the document before it is saved, so it is findable later. This is the name it will carry in Files.
Review Side
Which party you represent. The most important field on this screen — see below.
Review Language
The language the findings are written in: English, Turkish, Spanish, French or German.
Jurisdiction
The governing law the contract should be judged against: United States, Türkiye, Spain, France or Germany.
Save to
The workspace the reviewed document is filed in. Choose deliberately — it decides who can see the result.
Playbook
The rule set to measure against, or No playbook / Default review for a general review. Selecting one shows how many rules it contains.

Review Side is the setting that matters most

Contracts are not symmetrical. A payment term that is excellent for the supplier is poor for the customer, and a liability cap protects one side at the other's expense. Harmonity detects the parties in the document and asks whose interests it should argue for.

  • Pick a party and every finding is written from that party's point of view — what exposes you, what you should push back on.
  • Neutral perspective reports what is unusual or unbalanced without taking a side. Use it when you are assessing an agreement rather than negotiating it.

Language and jurisdiction

These two are independent, and neither has to match the language the contract is written in.

Review Language
Only affects the language the findings are written in. Harmonity reads the contract in its original language either way, so a Turkish contract can produce English findings.
Jurisdiction
Affects the analysis itself. It tells the review which body of law and which market conventions to judge the terms against, so choose the law the contract is actually governed by, not where you happen to be.

Playbook and workspace

Playbook
Only active playbooks appear in the dropdown, and only those in scope for the workspace you are saving to. If one you expect is missing, check it is not still a draft. Selecting a playbook shows its rule count and confirms the contract will be reviewed against those rules.
Save to
The reviewed document and its findings are stored in the workspace you choose here, so this also decides who else can open the result. A colleague who is not a member of that workspace will not see it.

Common questions

Where did Risk Assessment and the analysis toggles go?

They are not part of the review setup. The screen has six fields and no switches — depth is not something you configure here.

Can I change the jurisdiction after a review has run?

Not for a completed review; jurisdiction shapes the whole analysis. Run the review again with the correct jurisdiction selected.

The playbook I want is not in the list.

Two usual causes: the playbook is still in draft rather than active, or it is scoped to a different workspace than the one selected under Save to.

Does Review Side change which clauses are found, or just how they are described?

Both. A clause that is unremarkable for one party can be a material risk for the other, so changing sides changes which clauses are flagged as well as the wording of the recommendation.

About this guide

Imported from the application Help Center on 23 September 2026. The original content date is preserved. Product workflows and screenshots have not been revalidated against current account permissions and availability.