- Open the editor and name the Playbook.
- Add a Topic — one for each clause you negotiate.
- Write the Positions and Rules — a Starting position, an optional Fallback or two, and a Not acceptable position.
- Save it, then run it on a contract.

Open the editor
There are two ways in, and they are not quite the same.From the Templates library — the full-page editor
From a project — the modal
Name it
Add a Topic
A Topic is one subject of negotiation: Working hours, Place of work, Termination. A Playbook usually has one Topic per clause you actually negotiate — typically 6 to 10 for an employment contract, 3 or 4 for an NDA. Click Add topic (or Add first topic on an empty Playbook) and give it the noun of the negotiation, not the action: “Working hours”, not “Check working hours”. The name is what shows on the Review result, alongside the risk badge. A new Topic arrives with two Positions already in place — a Starting position and a Not acceptable position — each holding one empty Rule. A Fallback is not there by default; you add one only if you need it.
Write the Positions and Rules
Inside each Topic you describe what you’d sign, what you’d take under pressure, and what you’d refuse. Each Position holds one or more Rules — specific, testable conditions Libra evaluates against the contract. Use Add rule in the Position header for each extra one; once a rule box has text in it, an Improve with AI icon button appears in its top-right corner if you want Libra to tighten your wording.Starting position
- Weekly working time does not exceed 40 hours.
- The agreed gross monthly salary compensates for no more than 10 overtime hours per month.
Fallback position (optional, and you can have several)
- Weekly working time does not exceed 45 hours, with above-market overtime compensation.
Not acceptable position
- Weekly working time exceeds 50 hours.
- Overtime is uncapped or uncompensated.
Attach Ideal language (optional)

Save it, then run it
Add the next Topic (Place of work, Salary, Termination…) and write its Positions and Rules. Repeat until the Playbook covers the things you actually negotiate, then click Save. On a Playbook you’re creating, Save is the only header action. Once it’s saved the editor switches into edit mode: the primary button becomes Start Review, with Save kept alongside for further changes. Start Review opens Select Documents to review, so you can go straight from writing the Playbook to running it. A Playbook held in more than one language shows a language picker in its top row, read-only viewers included. Whichever language is showing there is the one Start Review runs against. The saved Playbook is filed under the Reviews tab of the Templates library and appears on the project Review page under My Playbooks. Share it and anyone it reaches can run it too.Build and edit a Playbook by chatting beside it
You don’t have to fill the form in by hand. The full-page Playbook editor carries the floating chat panel — on a Playbook you’re creating and on one you’re editing — so you can ask for structure instead of typing it.On a new Playbook
On an existing Playbook
When you both edit at once
Worked example: an employment-contract Playbook
Here’s how a real Playbook might look:Topic 01: Working hours
Topic 01: Working hours
- Weekly working time does not exceed 40 hours.
- The agreed gross monthly salary compensates for no more than 10 overtime hours per month.
- Ideal language: “The weekly working time is 40 hours. Reasonable overtime up to 10 hours per month is compensated by the agreed monthly gross salary.”
- Weekly working time exceeds 50 hours.
- Overtime is uncapped or uncompensated.
Topic 02: Place of work
Topic 02: Place of work
- Place of work is named (city, region, or country).
- Remote work is permitted up to 2 days per week.
- Place of work is named, but remote work is not permitted.
- Place of work is unspecified.
- Employer can unilaterally relocate the employee with less than 4 weeks’ notice.
Topic 03: Salary
Topic 03: Salary
- Gross monthly or annual salary is specified in figures.
- Payment cadence is monthly.
- Salary is described in vague terms (e.g. “competitive”).
- Payment cadence is irregular or undefined.
Tips for writing good Topics, Positions, and Rules
Topics: one negotiation, one Topic
Topics: one negotiation, one Topic
Positions: be honest about your Fallback
Positions: be honest about your Fallback
Rules: testable, not aspirational
Rules: testable, not aspirational
Rules: prefer multiple narrow rules over one big rule
Rules: prefer multiple narrow rules over one big rule
Ideal language: write what you'd actually sign
Ideal language: write what you'd actually sign


