Procurato.

In-house legal teams · Workflow 01

Review the liability clause. Leave the deal identity out.

Use an approved AI tool to produce a first-pass comparison between your preferred wording and the supplier’s wording, plus questions for your own legal review.

The moment this is useful

The task on your desk

Procurement wants a response today. A supplier has returned its version of the limitation-of-liability clause, and you need to explain the differences to the business before the next negotiation call. The draft includes named signatories, a project codename, and pricing references that have nothing to do with the clause comparison.

Keep the facts the question depends on.

Keep for the research

  • The actual wording of the two clauses, if permitted for this tool.
  • The cap formula, relevant carve-outs, and which party carries each obligation.
  • The governing law and contract type needed to frame the comparison.

Remove or replace

  • Party and signatory names, email addresses, and signature blocks.
  • Deal codenames, internal document links, and customer references.
  • Unnecessary prices, rollout details, or negotiation notes elsewhere in the draft.

A worked prompt example

Fictional details · Edited by hand after review

Before review

Compare our position with this supplier proposal for Aster Foods Ltd / Northbank Systems, Project Cedar. English-law B2B services agreement. Our position: liability capped at 200% of fees paid in the preceding 12 months, excluding fraud and confidentiality breaches. Supplier proposal: 100% of those fees, excluding fraud only. Procurement contact: Maya Chen, maya@example.com.

Reviewed prompt

Compare our position with this supplier proposal. English-law B2B services agreement. Our position: liability capped at 200% of fees paid in the preceding 12 months, excluding fraud and confidentiality breaches. Supplier proposal: 100% of those fees, excluding fraud only. Create a table of differences, practical consequences, and questions for counsel. Do not invent missing terms or conclude that either clause is enforceable.

Use this workflow

  1. Extract only the two clauses and the minimum contract context. Leave the full agreement out.
  2. Run local detection. Review each highlight: retain relevant legal context and redact identities.
  3. Manually check prices, codenames, definitions, and cross-references; then review the final prompt.
  4. Use the comparison as an issue list. Check it against the complete contract before advising procurement.

What you should have at the end

A clause comparison for the negotiation call, with the legal assessment and final drafting still owned by you.

Redaction does not determine whether contract terms may be shared, protect privilege by itself, or replace substantive contract review.

Questions for this workflow

Should I redact every number in a contract?

No. A percentage cap or notice period can be essential to the question. Keep a number only when it is needed and permitted to share. If an actual price is confidential, use a consistent hypothetical amount and explain that it is illustrative.

Can I upload the contract PDF here?

The redactor works on pasted text. It does not remove information from a PDF, its metadata, comments, or attachments. Copy only the excerpt you intend to review.

Workflow context & further reading

These sources inform the workflow. The example and editing choices are Procurato’s illustration; they are not source-endorsed advice.

From example to your own work

Keep the context. Review the details.

Paste into the local redactor, review each detection, choose what to keep, and check the result before sharing it with your approved AI tool. Names are only part of the review: inspect confidential wording and identifying context too.

Free, no account. Initial model download: about 1.1 GB. Requires WebGPU and several GB of free memory. Detection focuses on English and can miss details. The examples here include manual editing; the tool does not automatically rewrite or summarise your text.