SMB Pulse

Read a contract properly before signing

Have each contract read clause by clause, schedules included, see in plain words what to push back on, and export the redline once you have decided.

Pick a use case and follow its guide

Read a contract properly before signing

0 of 4 steps done

Sign in to try the demo
  1. Step 1. Open Operations, then contracts.upload. In file_ref, type the attachment's file name and press Run contracts.upload. The run turns SUCCEEDED. The app keeps the original, stores every numbered clause with its section and page, schedules and appendices included, and types the key terms it finds, each with the clause it came from. It proposes the contract's type and parties from the title and the opening, marked unconfirmed. A file that cannot be read is refused in plain words and nothing is stored. Repeat for each contract. Open contracts.upload

  2. Step 2. Open Operations, then contracts.confirm_parties. In contract_id, type the filed contract's id. Check the proposed type and parties and type them in contract_type, our_party and counterparty, then press Call contracts.confirm_parties. Under ANSWERED, the contract's status is confirmed. Only the header changes; the clauses and terms are untouched. A contract that is not confirmed cannot be reviewed. Open contracts.confirm_parties

  3. Step 3. Open Operations, then contracts.review. In contract_id, type the confirmed contract's id and press Run contracts.review. The run turns SUCCEEDED. The contract reader returns its findings, each with a severity, the problem, the market norm, the language to suggest and a playbook for asking, and each quote copied by the app from the stored clause. The business's other confirmed contracts are read alongside, so a term that reaches into another contract is named. The review ends with the app's own disclaimer that it is not legal advice. The reader words each finding, so the wording differs from run to run. Open contracts.review

  4. Step 4. When you have decided what to ask for, open Operations, then contracts.export_redline. In review_id, type the review's id and press Run contracts.export_redline. The run turns SUCCEEDED and files two downloads under the run: the marked-up contract, with deleted words struck through and inserted words underlined, and a summary giving each finding's heading, clause and page, problem, market norm, suggested language and playbook, ending with the disclaimer. A review that suggests no change is refused and nothing is written. Nothing is sent to the other party. Open contracts.export_redline

Did it fit your work?