引導式測驗 · 中等 等級

AI合約起草工具測驗

測試起草與審閱有何不同,條款庫和劇本如何塑造人工智慧草稿,並檢查是否發現無聲的起草錯誤。

問題 1 的 8

指南如何區分合約起草和合約審查?

預覽每個問題8 問題

當您參加測驗時,就會出現答案和解釋。

  1. 指南如何區分合約起草和合約審查?
    • Drafting is done by paralegals and review by partners
    • Drafting only covers short agreements, review covers long ones
    • Review uses AI while drafting never does
    • Drafting creates language from deal terms, while review evaluates language someone else wrote
  2. 為什麼指引說起草錯誤比審查問題更難發現?
    • Drafting tools hide their output from lawyers
    • Nothing contradicts them, so an omission or wrong cross-reference looks fine on a quick read
    • Drafts are always longer than reviewed documents
    • Drafting errors appear only in the metadata
  3. 指南說好的人工智慧草稿取決於哪三家公司控制的輸入?
    • Billing rates, client lists and matter numbers
    • Court rules, statutes and case law
    • A clause library, a playbook and precedents
    • Email archives, calendars and time entries
  4. 為什麼指南說工具直接編輯合約文字而不是使用追蹤更改很重要?
    • It destroys the audit trail of what changed
    • It makes the document incompatible with PDF
    • It doubles the file size
    • It prevents the use of defined terms
  5. 該指南將哪種工具描述為作為 Word 加載項運行?
    • Datasite
    • 法術書
    • Colossus
    • STRmix
  6. Which rule-based check does the guide recommend running after an AI generates a draft?
    • Counting how many times the word 'shall' appears
    • Confirming the draft is under a set page count
    • Confirming that every capitalized term is defined and every cross-reference points to an existing section
    • Checking that the font matches the firm letterhead
  7. How does redlining an AI draft against firm standards help the reviewing lawyer?
    • It automatically sends the draft to the counterparty
    • It removes the need for any human review
    • It converts the draft into a signed contract
    • It shows exactly where the draft departs from vetted text
  8. According to the guide's outlook, what will increasingly set AI drafting tools apart?
    • The quality of each firm's own clause library and playbook
    • The number of languages the interface supports
    • Whether the tool runs on a phone
    • The color scheme of the redlines