Legal Document Processing Template (law.gbai) 🟡 BETA

A General Bots template for legal case management, document analysis, and AI-powered legal Q&A.

Overview

The Law template enables legal professionals to load case documents, query case information using natural language, and get AI-assisted analysis of legal materials. It’s designed for law firms, legal departments, and compliance teams who need efficient document-based legal research.

Features

Case Document Loading - Load and index PDF case files by case number
Document Q&A - Ask questions about loaded legal documents
Context-Aware Responses - AI responses grounded in actual case content
Case Summarization - Generate summaries of case documents
Multi-Document Support - Work with multiple cases simultaneously
Audit Trail - Track all document access and queries

Package Structure

law.gbai/
├── law.gbdialog/
│   └── case.bas           # Case loading and query handler
├── law.gbdrive/           # Case document storage
│   └── (case-*.pdf)       # Case PDF files
├── law.gbkb/              # Knowledge base for legal reference
└── law.gbot/
    └── config.csv         # Bot configuration

Scripts

File	Description
`case.bas`	Loads case documents by number and enables document-based Q&A

How It Works

Case Loading Flow

User provides a case number (e.g., “12345”)
Bot searches for case-12345.pdf in the drive
Document content is extracted and set as context
Answer mode switches to “document” for grounded responses
User can ask questions about the loaded case

Code Example

PARAM cod AS STRING LIKE "12345" DESCRIPTION "Case number to load and query"

DESCRIPTION "Load a legal case document by case number for Q&A and analysis"

text = GET "case-" + cod + ".pdf"

IF text THEN
    SET CONTEXT "Based on this document, answer the person's questions:\n\n" + text
    SET ANSWER MODE "document"
    TALK "Case ${cod} loaded. Ask me anything about the case or request a summary."
ELSE
    TALK "Case not found. Please check the case number."
END IF

Configuration

Configure in law.gbot/config.csv:

Parameter	Description	Example
`Answer Mode`	Response grounding mode	`document`
`Theme Color`	UI accent color	`navy`
`LLM Provider`	AI provider	`openai`
`Document Retention`	Days to keep loaded docs	`30`
`Require Authentication`	Require user login	`true`

Sample Conversation

User: Load case 12345

Bot:  Case 12345 loaded. Ask me anything about the case 
      or request a summary.

User: What are the main claims in this case?

Bot:  Based on the document, the main claims are:
      
      1. Breach of contract regarding the delivery terms 
         in Section 3.2
      2. Failure to meet quality standards as specified 
         in Exhibit A
      3. Request for damages in the amount of $250,000
      
      📄 Source: Case 12345, Pages 3-5

User: Summarize the defendant's response

Bot:  The defendant argues that:
      
      • Delivery delays were caused by force majeure events 
        (documented in Exhibit C)
      • Quality standards were met according to third-party 
        inspection report
      • Damages claimed are excessive and not substantiated 
        by evidence
      
      📄 Source: Case 12345, Pages 12-18

User: What are the key dates mentioned?

Bot:  Key dates from the case file:
      
      📅 Contract signed: January 15, 2024
      📅 Delivery due date: March 30, 2024
      📅 Actual delivery: April 22, 2024
      📅 Complaint filed: May 10, 2024
      📅 Response deadline: June 15, 2024
      
      📄 Source: Case 12345, Pages 1-2

Document Naming Convention

Case documents should follow this naming pattern:

case-{case_number}.pdf

Examples:

case-12345.pdf
case-2024-CV-0001.pdf
case-APPEAL-789.pdf

Customization

Adding Case Search

' search-cases.bas
PARAM query AS STRING DESCRIPTION "Search term for finding cases"

DESCRIPTION "Search for cases by party name, date, or keywords"

cases = FIND "case_index.csv", "content LIKE '%" + query + "%'"

IF UBOUND(cases) > 0 THEN
    TALK "Found " + UBOUND(cases) + " matching cases:"
    
    FOR EACH c IN cases
        TALK "- Case " + c.case_number + ": " + c.title
    NEXT
ELSE
    TALK "No cases found matching: " + query
END IF

Case Summarization

' summarize-case.bas
PARAM cod AS STRING DESCRIPTION "Case number to summarize"

DESCRIPTION "Generate an executive summary of a legal case"

text = GET "case-" + cod + ".pdf"

IF text THEN
    summary = LLM "As a legal professional, provide an executive summary of this case including: 
                   1. Parties involved
                   2. Key facts
                   3. Legal issues
                   4. Current status
                   5. Next steps
                   
                   Document: " + text
    
    TALK "## Case " + cod + " Summary\n\n" + summary
    
    ' Save summary for future reference
    SAVE "case_summaries.csv", cod, summary, NOW()
ELSE
    TALK "Case not found."
END IF

Supporting Multiple Document Types

' load-document.bas
PARAM doc_type AS STRING LIKE "contract" DESCRIPTION "Type: case, contract, brief, motion"
PARAM doc_id AS STRING DESCRIPTION "Document identifier"

DESCRIPTION "Load various legal document types"

filename = doc_type + "-" + doc_id + ".pdf"
text = GET filename

IF text THEN
    SET CONTEXT "This is a legal " + doc_type + ". Answer questions based on its content:\n\n" + text
    SET ANSWER MODE "document"
    TALK "Loaded " + doc_type + " " + doc_id + ". Ready for questions."
ELSE
    TALK "Document not found: " + filename
END IF

Compliance Logging

' Add audit logging to case.bas
IF text THEN
    ' Log access for compliance
    WITH audit_entry
        timestamp = NOW()
        user = GET SESSION "user_email"
        case_number = cod
        action = "document_access"
        ip_address = GET SESSION "client_ip"
    END WITH
    
    SAVE "legal_audit_log.csv", audit_entry
    
    SET CONTEXT "Based on this document..." + text
END IF

Integration Examples

With Calendar

' Schedule case deadlines
deadline = LLM "Extract the next deadline date from this case: " + text

IF deadline THEN
    CREATE CALENDAR EVENT "Case " + cod + " Deadline", deadline
    TALK "Deadline added to calendar: " + deadline
END IF

With Email

' Email case summary to team
summary = LLM "Summarize the key points of this case in 3 paragraphs: " + text

SEND MAIL "legal-team@firm.com", "Case " + cod + " Summary", summary, []
TALK "Summary sent to legal team."

With Document Generation

' Generate response document
response = LLM "Draft a formal response letter addressing the claims in this case: " + text

CREATE DRAFT response, "Response to Case " + cod
TALK "Draft response created. Review in your documents."

Security Considerations

Access Control - Implement role-based access for sensitive cases
Audit Logging - Log all document access for compliance
Data Encryption - Enable encryption for stored documents
Session Timeout - Configure appropriate session timeouts
Authentication - Require strong authentication for legal systems
Data Retention - Follow legal data retention requirements

Best Practices

Organize documents - Use consistent naming conventions
Index cases - Maintain a searchable case index
Regular backups - Back up case documents frequently
Version control - Track document versions
Clear context - Clear previous case context before loading new cases
Verify AI responses - Always verify AI-generated legal content

Troubleshooting

Issue	Cause	Solution
Case not found	Wrong filename	Check naming convention
Empty responses	Document not parsed	Verify PDF is text-based
Slow loading	Large document	Consider document chunking
Context errors	Multiple cases loaded	Clear context between cases
Access denied	Missing permissions	Check user authentication

Limitations

PDF documents must be text-based (not scanned images)
Very large documents may require chunking
Complex legal analysis should be verified by professionals
AI responses are assistive, not legal advice

Use Cases

Case Research - Quickly find relevant information in case files
Document Review - AI-assisted document analysis
Client Communication - Generate case status summaries
Deadline Tracking - Extract and track important dates
Knowledge Management - Build searchable legal knowledge bases

Disclaimer

This template provides AI-assisted document analysis tools. It does not constitute legal advice. All AI-generated content should be reviewed by qualified legal professionals. Users are responsible for ensuring compliance with applicable legal and ethical standards.

General Bots Documentation