exploreAIExplore
How to Use CoCounsel for Issue spotting checklists
Learn CoCounsel issue spotting checklists with step by step workflows, realistic examples, and verified plan notes.
CoCounsel works well for issue spotting checklists when you run it like production work: locked brief, SOURCE facts, then review before publish. CoCounsel is Thomson Reuters generative AI assistant for legal professionals covering research, document review, deposition prep, and contract analysis. Confirm firm policy before uploading client documents; verify citations in official legal databases. Start at /explore/cocounsel.
This guide focuses on issue spotting checklists in detail. Related CoCounsel articles: /blog/how-to-use-cocounsel-for-legal-research-drafts, /blog/how-to-use-cocounsel-for-document-review-workflows, /blog/how-to-use-cocounsel-for-deposition-prep-outlines.
When this workflow is the right job
Use issue spotting checklists when the deliverable is specifically this CoCounsel job. Switch to legal research drafts when that workflow already owns the asset.
Step by step workflow
1. Brief Issue spotting checklists
Write what must stay true for issue spotting checklists in CoCounsel before settings or spend.
Brief: Issue spotting checklists Keep: verified SOURCE facts only Avoid: invented pricing or features Success: one reviewable output
2. Open CoCounsel for Issue spotting checklists
Use the CoCounsel surface that owns issue spotting checklists. Do not mix a neighboring workflow in the same pass.
Surface: Issue spotting checklists Start: pilot with one representative input Plans: www.thomsonreuters.com/en/cocounsel.html
3. Pilot Issue spotting checklists
Run a single issue spotting checklists pilot. Score clarity, grounding, and whether the output is reviewable.
Pilot: Issue spotting checklists [ ] SOURCE facts match [ ] Output reviewable [ ] Settings logged
4. Refine Issue spotting checklists
Change one issue spotting checklists dimension only. Save a template from the best run.
Refine: Issue spotting checklists Change: one control only Keep: SOURCE and success criteria
Practical issue spotting checklists examples
Material deviation
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Material deviation". Objective: Extract structured terms for Material deviation with human validation gates. Inputs: - Document type for Material deviation - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Material deviation → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Material deviation with citations/page refs and validation status.
Portfolio summary
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Portfolio summary". Objective: Extract structured terms for Portfolio summary with human validation gates. Inputs: - Document type for Portfolio summary - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Portfolio summary → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Portfolio summary with citations/page refs and validation status.
Demo prep brief
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Demo prep brief". Objective: Extract structured terms for Demo prep brief with human validation gates. Inputs: - Document type for Demo prep brief - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Demo prep brief → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Demo prep brief with citations/page refs and validation status.
Expert validation
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Expert validation". Objective: Extract structured terms for Expert validation with human validation gates. Inputs: - Document type for Expert validation - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Expert validation → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Expert validation with citations/page refs and validation status.
Covenant list
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Covenant list". Objective: Extract structured terms for Covenant list with human validation gates. Inputs: - Document type for Covenant list - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Covenant list → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Covenant list with citations/page refs and validation status.
Pricing grid
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Pricing grid". Objective: Extract structured terms for Pricing grid with human validation gates. Inputs: - Document type for Pricing grid - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Pricing grid → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Pricing grid with citations/page refs and validation status.
Collateral note
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Collateral note". Objective: Extract structured terms for Collateral note with human validation gates. Inputs: - Document type for Collateral note - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Collateral note → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Collateral note with citations/page refs and validation status.
Maturity date
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Maturity date". Objective: Extract structured terms for Maturity date with human validation gates. Inputs: - Document type for Maturity date - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Maturity date → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Maturity date with citations/page refs and validation status.
Interest mechanics
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Interest mechanics". Objective: Extract structured terms for Interest mechanics with human validation gates. Inputs: - Document type for Interest mechanics - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Interest mechanics → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Interest mechanics with citations/page refs and validation status.
Reporting cadence
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Reporting cadence". Objective: Extract structured terms for Reporting cadence with human validation gates. Inputs: - Document type for Reporting cadence - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Reporting cadence → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Reporting cadence with citations/page refs and validation status.
Default triggers
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Default triggers". Objective: Extract structured terms for Default triggers with human validation gates. Inputs: - Document type for Default triggers - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Default triggers → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Default triggers with citations/page refs and validation status.
Amendment history
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Amendment history". Objective: Extract structured terms for Amendment history with human validation gates. Inputs: - Document type for Amendment history - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Amendment history → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Amendment history with citations/page refs and validation status.
Party names lock
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Party names lock". Objective: Extract structured terms for Party names lock with human validation gates. Inputs: - Document type for Party names lock - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Party names lock → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Party names lock with citations/page refs and validation status.
Page cite quotes
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Page cite quotes". Objective: Extract structured terms for Page cite quotes with human validation gates. Inputs: - Document type for Page cite quotes - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Page cite quotes → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Page cite quotes with citations/page refs and validation status.
Unsure markers
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Unsure markers". Objective: Extract structured terms for Unsure markers with human validation gates. Inputs: - Document type for Unsure markers - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Unsure markers → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Unsure markers with citations/page refs and validation status.
Counsel review gate
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Counsel review gate". Objective: Extract structured terms for Counsel review gate with human validation gates. Inputs: - Document type for Counsel review gate - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Counsel review gate → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Counsel review gate with citations/page refs and validation status.
Export structured
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Export structured". Objective: Extract structured terms for Export structured with human validation gates. Inputs: - Document type for Export structured - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Export structured → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Export structured with citations/page refs and validation status.
Term grid extract
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Term grid extract". Objective: Extract structured terms for Term grid extract with human validation gates. Inputs: - Document type for Term grid extract - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Term grid extract → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Term grid extract with citations/page refs and validation status.
Credit agreement PDF
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Credit agreement PDF". Objective: Extract structured terms for Credit agreement PDF with human validation gates. Inputs: - Document type for Credit agreement PDF - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Credit agreement PDF → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Credit agreement PDF with citations/page refs and validation status.
Diligence checklist
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Diligence checklist". Objective: Extract structured terms for Diligence checklist with human validation gates. Inputs: - Document type for Diligence checklist - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Diligence checklist → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Diligence checklist with citations/page refs and validation status.
Prior deal diff
Scenario: A private credit analyst uses CoCounsel for Issue spotting checklists on document set "Prior deal diff". Objective: Extract structured terms for Prior deal diff with human validation gates. Inputs: - Document type for Prior deal diff - Desired output fields - Prior deal reference if comparing - Expert reviewer Workflow: Upload/connect docs → Run Issue spotting checklists → Review structured grid for Prior deal diff → Mark UNSURE → Counsel validates Requirements: - Stay within verified CoCounsel capabilities; do not invent features. - Confirm live plan notes on www.thomsonreuters.com/en/cocounsel.html before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Human expert validation before reliance. Expected output: A structured term summary for Prior deal diff with citations/page refs and validation status.
How to improve issue spotting checklists
Cut noise from issue spotting checklists by removing extra adjectives while preserving SOURCE facts in CoCounsel.
Raise quality by insisting on a single success check before debating style.
Make review easier by labeling fields that must never change.
Speed iteration by cloning the last good run and altering only one control.
Stabilize outputs by pinning settings after the pilot is approved.
Reduce rework by rejecting drafts that invent claims.
Improve handoffs by recording which control produced the best result.
Harden the workflow by testing an incomplete input before trusting defaults.
Prompting and usage guidance
Name the issue spotting checklists job, audience, and success check before opening CoCounsel.
Paste only verified facts under SOURCE so CoCounsel cannot invent details.
Specify the deliverable shape up front.
Call out fixed details versus flexible style choices.
Ask CoCounsel to flag unsupported claims before you accept the draft.
Limitations to respect
Check CoCounsel plan gates for issue spotting checklists on www.thomsonreuters.com/en/cocounsel.html before you promise timelines.
Keep drafts unpublished until a human confirms SOURCE facts.
CoCounsel can be wrong. Treat issue spotting checklists as provisional until review.
If documentation is silent on a claim, leave it out rather than guessing.
Practical tips for this workflow
Pilot once before batching issue spotting checklists in CoCounsel.
Keep a reusable template with variables for issue spotting checklists.
Separate creative instructions from SOURCE facts.
Log settings from the best run.
Common mistakes
- Skipping the pilot run before scaling volume
- Inventing pricing, quotas, or features not on official pages
- Mixing unrelated workflows in one session
- Publishing without a human review gate
Treat issue spotting checklists in CoCounsel as a production workflow: brief, pilot, refine, then ship with review. Related reading: /blog/how-to-use-cocounsel-for-legal-research-drafts, /blog/how-to-use-cocounsel-for-document-review-workflows, /blog/how-to-use-cocounsel-for-deposition-prep-outlines.