Klu for legal work
Acest conținut nu este încă disponibil în limba selectată.
The assistant appears in the Lex sidebar as Ask Lex. Typing / in the
composer opens its commands: a command sets how the assistant should work on the
turn — the structure of the output and which sources it must consult — so you do not
have to spell that out each time.
This page is reference. For a first conversation, see Getting started.
The commands
Section titled “The commands”| Command | Does | Needs |
|---|---|---|
| Contract analysis | Full structured read of one contract | A contract in the conversation |
| Compare clauses | Side-by-side clause comparison across documents | Two or more pinned documents |
| Cross-check documents | Field-by-field consistency check between documents | Two documents |
| Legal memo | A memo: question, law, analysis, conclusion | A question; ideally relevant material indexed |
| Deadlines | Every deadline and time limit, as a chronology | A document containing dates |
| Summary | Executive summary of the conversation | An existing conversation |
| Report | The conversation as a downloadable PDF | An existing conversation |
The five legal commands require your firm’s document module to be switched on, since each of them works from documents.
Contract analysis
Section titled “Contract analysis”What it does. Reads one contract end to end and reports it in a fixed order: parties, object, duration, financial terms, obligations, penalties, termination clauses, risks and applicable law. It extracts the structured facts first — parties, object, value, duration, payment terms, penalties — then looks for legislation applicable to that type of contract, and closes with the standard legal disclaimer.
What it needs. The contract available to the assistant: pinned with @,
dropped into the conversation, or already in a knowledge base.
When to use it. A contract has landed and you need a structured picture before advising — the terms as written, plus what jumps out as risk. Also useful as a first pass on an inherited file.
Compare clauses
Section titled “Compare clauses”What it does. Compares the pinned documents clause category by clause category — liability, termination, confidentiality, penalties, force majeure, governing law — in a side-by-side table per category, and calls out the significant differences and the risks they carry.
What it needs. Two or more documents pinned with @. This command compares what
you pin; it is not a search across everything.
When to use it. Negotiating against a counterparty’s draft and wanting the delta from your own template. Or checking that a family of contracts your firm produced actually says the same thing.
Cross-check documents
Section titled “Cross-check documents”What it does. Checks the same facts across two documents and reports every field as matching, mismatching or missing from one side, in a table. Then it explains each mismatch: what the discrepancy is, why it matters, and what it recommends doing about it — closing with a verdict of consistent, minor discrepancies, or significant issues.
The fields it prioritises are the ones that usually break a file: full name, date of birth, employer name and address, employee address, job title, employment start date, contract type, gross annual salary, holiday pay, weekly hours, and company registration number. Any other field present in both documents is compared too.
What it needs. Two documents — pinned with @, or uploaded in the same message.
When to use it. Anywhere a third party will reject a file over an inconsistency: an employment contract against a payslip or an employer statement, a set of documents assembled for a financing application, an annex against the body of an agreement.
Legal memo
Section titled “Legal memo”What it does. Drafts a memo in the classic shape: the question or issue, the applicable law and precedent it retrieved, the analysis applying the law to the facts, and a clear conclusion — with the standard legal disclaimer.
What it needs. A question, and the facts stated in the conversation. It searches the indexed material for the applicable law, so it works best when the relevant codes, decisions or firm documents are within its reach.
When to use it. The first draft of an internal note or client advice. Read it as a draft: the structure and the retrieved sources save the time, your judgement supplies the answer.
Deadlines
Section titled “Deadlines”What it does. Pulls every time-sensitive item out of the referenced documents — deadlines, limitation periods, notice periods, filing dates, renewal dates — into a chronological table of date or period, type, description and consequence, and highlights anything imminent or already passed.
What it needs. One or more documents containing dates.
When to use it. Taking over a file and needing the calendar implications immediately; or checking a long contract for renewal and notice windows before it auto-renews on you.
Worth being clear about the boundary: this command reads dates out of documents. It does not put them in your diary. Your firm’s actual terms and reminders live in Deadlines and calendar, and you can ask the assistant about those in plain language.
Summary and Report
Section titled “Summary and Report”Summary condenses the conversation into an executive summary — key points, parties, dates, obligations — kept to about a page.
Report turns the conversation into a downloadable PDF with a title, the findings, data tables and conclusions organised under headings. Individual answers can also be exported directly with Export PDF, and to Word where your firm has enabled that for the assistant.
What the assistant can look up on its own
Section titled “What the assistant can look up on its own”You do not need a command for these; ask in plain language and the assistant reaches for the right source. Everything it returns is scoped to your firm and to what your role lets you see.
Your firm’s records
| Ask about | For example |
|---|---|
| Clients | “find the client with CUI …”, “which clients are prospects?” |
| Case records | “open cases for Popescu SRL” |
| Case files (dosare) | “list active matters at Tribunalul Cluj” |
| Portal change history | “what changed on dosar 1234/2026 this month?” |
| Deadlines | “what is due this week?”, “my overdue terms” |
| Your documents | “what does our standard NDA say about penalties?” |
Public legal material
| Ask about | For example |
|---|---|
| Legislation | “art. 1357 cod civil”, “răspundere civilă delictuală” |
| Cross-references between articles | “what does art. 48 cod civil refer to?” |
| Constitutional Court decisions | “decizia 114”, “decisions on …” |
| Court cases from the portal and the Supreme Court archive | “cases with party X at Judecătoria Sector 1” |
Two commands you may have seen elsewhere — a standalone data-extraction command and
a legislation-search command — are not in the Lex / panel: extraction is covered by
cross-checking, and legislation search works better as a plain question. The general
planning command is also left out of Lex. Nothing is lost; ask for what you want.
The starting suggestions
Section titled “The starting suggestions”An empty conversation offers four one-click starts: analyse a contract, compare clauses across contracts, search for a client, and the status of active cases. They are shortcuts into the same behaviour described above.
Two things to keep in mind
Section titled “Two things to keep in mind”Commands change the method, not the standard. Every command still cites its sources, still carries a grounding badge, and still tells you when it could not substantiate something. Read those signals — see Legislation and case-law research.
Output is a draft. Contract analysis, memos and comparisons are AI-generated and can be incomplete or wrong. Verify the sources and confirm the citations before anything goes to a client, a court or a counterparty.