Before you begin your review, you can use the Analyse Complaints workflow to generate a structured analysis of your complaint. Vincent AI identifies claims, defenses, parties, and legal issues for your review so you can begin matter preparation. This article covers how to select analysis tasks and work with the results
Important: All Vincent AI output requires final review and due diligence by a qualified legal professional before use in litigation strategy, pleadings, or court proceedings.
Select and run tasks
When you upload a complaint, Vincent identifies the document type and generates a set of tasks. Each task appears as a selectable card on the screen. You can run tasks individually or select several to process simultaneously.
Tip: You do not need to run all tasks at once. Select the tasks most relevant to your current matter stage, then return to add more as your analysis develops.
- In Clio Work, click Vincent in the left navigation.
- Upload your complaint. For upload instructions, see Analyse Legal Documents in Clio Work.
- On the Analyze a Complaint screen, review the tasks Vincent has generated.
- Select the tasks relevant to your immediate work. You can select multiple tasks and run them together.
- Click the arrow to submit.
Understand tasks and outputs
Vincent generates tasks based on the complaint's specific content, claims, and jurisdiction. The tasks below are representative of what you may see when you upload a complaint.
Extracts and analyses all causes of action pleaded in the complaint. Each entry includes the cause of action, applicable governing law, supporting facts, related parties, and source citations.
Proposes defenses to each claim from your client's perspective. Each entry includes the defence theory, governing legal standard, how the law applies to the specific facts alleged, and source citations. Vincent asks which party you represent before generating output. The Defenses output is perspective-aware — every defence is grounded in the governing legal standard and the facts alleged by the opposing party.
Tip: Run Claims before selecting Defenses or Client Questions. Both tasks use the claims analysis as recommended input and produce more targeted output when run in sequence.
Extracts a chronological sequence of facts from the complaint. Each entry identifies the date or time period, describes the event, quotes the relevant passage verbatim, and links to the source page in the document viewer.
Drafts a questionnaire of factual questions to ask your client, organised alphabetically by legal topic. Such as Corporate Structure and Relationships, Training Data Acquisition, or Copyright Ownership. Each section contains numbered questions scoped to your client's role. The number of sections and questions scales with the complexity of the complaint. Vincent asks which party you represent before generating output.
Identifies all named parties to the action. Output is a three-column table: full legal entity name, procedural role (such as Plaintiff or Defendant), and corporate structure, ownership chain, and relationships to other named parties, with inline page citations to the complaint.
Identifies every individual, organisation, and entity referenced anywhere in the complaint, including non-parties. Output is a seven-column table: sequential entry number, entity name, functional role, detected aliases, short description of involvement, associated documents, and linked source citations.
Note: Parties and Dramatis Personae serve different but complementary scopes. Parties covers named parties only. Dramatis Personae covers everyone referenced in the complaint.
Summarises all relief sought in the complaint. Output is a bulleted list covering damages, injunctions, statutory penalties, attorneys' fees, and other remedies, with pinpoint citations to the relevant paragraphs.
Maps factual allegations by topic to the corresponding cause of action. Topics are drawn from the complaint's specific subject matter.
Note: The Allegations Table requires the complaint to be uploaded before Vincent generates output. If prompted, resubmit the complaint to proceed.
Jurisdiction-specific tasks generate research memos based on the complaint's claims and governing law. These tasks vary by matter and do not appear for every complaint. Examples include UCL standing, fiduciary duties, or contract formation requirements.
Each memo is organised into the following sections:
- Short response
- Summary
- Background and relevant law
- Detailed analysis
- Exceptions and caveats
- Conclusion
- Legal authorities: Includes source extracts, relevance scores, and citations, filterable by case, statute, regulation, administrative decision, and secondary source
Work with the results
Navigate to source allegations
Select any linked page number in the source citation to open the exact location in the complaint. Verify context before relying on output in a motion, brief, or client communication.
Save to Legal Pad
Select the Legal Pad icon in the response footer to save output to Legal Pad. From Legal Pad, you can edit, annotate, and save content directly to Clio Manage.
Add more tasks
Scroll to the top of your conversation and select Add More Tasks to run additional analyses without re-uploading the document.
Continue the conversation
Use the Ask any follow-up question text box to request additional analysis or ask Vincent questions about the complaint. For example:
- Which claims are most vulnerable to a 12(b)(6) motion?
- Draft a list of third-party discovery targets based on the Dramatis Personae output.
- Summarise the relief sought in plain language for a client update.
Up Next
- Build your litigation strategy: see Build Arguments in Clio Work to develop a structured legal position from the claims and defenses identified here
- Deposition preparation: see Analyze Depositions in Clio Work to match complaint claims to witness testimony
- Research the law: see Ask Research Questions in Clio Work to go deeper on any jurisdiction-specific legal question surfaced during analysis