Batch Processing
For cases with many documents, batch processing lets you analyze and redact multiple files efficiently.
When to Use Batch Processing
Batch processing is ideal when:
- A case has 5+ documents requiring redaction
- You need to process similar document types
- Time is limited and automation helps
- You want consistent redaction across documents
Starting Batch Processing
Select Documents
- Open the case with multiple documents
- Navigate to the Batch Processing section
- Check the documents you want to process
- Click Start Batch Analysis
Document Selection Tips
- Select documents of similar types for best results
- Review document quality before batch processing
- Large batches may take several minutes
Batch Analysis
How It Works
The system processes documents in parallel:
- Multiple documents analyzed simultaneously
- Progress shown for each document
- Individual results available as they complete
- Overall batch progress indicator
Monitoring Progress
The progress view shows:
- Documents queued
- Documents in progress
- Documents completed
- Any errors encountered
Timeout Handling
Documents have a processing timeout:
- Complex documents may take longer
- Very large files may timeout
- Retry individual documents if needed
Reviewing Batch Results
Summary View
After batch completion:
- Total documents processed
- Total PII entities detected
- Documents requiring attention
- Quick statistics
Per-Document Review
For each document:
- Click to view detected entities
- Review and confirm detections
- Reject false positives
- Add missed items manually
Batch Actions
Confirm All High-Confidence Accept all detections above 90% confidence automatically.
Reject All Low-Confidence Remove detections below threshold from redaction list.
Apply Common Rules Apply the same decision to matching entities across documents.
Batch Redaction
Preview All Redactions
Before applying:
- Click Preview Batch Redaction
- Review each document’s redactions
- Make final adjustments
- Confirm readiness
Apply Redactions
- Click Apply All Redactions
- Confirm the operation
- Wait for processing to complete
- Download redacted documents
Output Options
Individual Files Each document saved separately with “_redacted” suffix.
ZIP Archive All redacted documents bundled for easy download.
Batch Processing Sessions
Session Tracking
Each batch operation creates a session:
- Session ID for reference
- Start/end timestamps
- Documents included
- Processing status
- Results summary
Resuming Interrupted Sessions
If batch processing is interrupted:
- Session state is preserved
- Incomplete documents can be retried
- Completed documents are saved
- Resume from where you left off
Performance Considerations
Document Limits
| Aspect | Limit |
|---|---|
| Documents per batch | 50 |
| Max document size | 50 MB |
Processing Time Estimates
| Document Type | Typical Time |
|---|---|
| Text PDF (1-10 pages) | 10-30 seconds |
| Scanned PDF (requires OCR) | 30-60 seconds |
| Word document (.docx) | 15-30 seconds |
| Excel spreadsheet (.xlsx) | 20-45 seconds |
| Image file (.png, .jpg, etc.) | 20-40 seconds |
| Email file (.eml, .msg) | 10-25 seconds |
| Text file (.txt, .csv, .json, etc.) | 5-15 seconds |
Optimizing Batch Performance
- Group similar documents - Similar types process more predictably
- Smaller batches for urgent work - Start with priority documents
- Check during processing - Review completed docs while others process
- Retry failures separately - Don’t re-run entire batch for one failure
Best Practices
Before Starting
- Review documents to ensure they need processing
- Remove duplicates from the batch
- Ensure documents meet quality requirements
During Processing
- Don’t close the browser during batch operations
- Monitor for errors
- Review completed documents as they finish
After Completion
- Review all detections before applying redactions
- Check edge cases manually
- Verify redacted outputs before sending
Quality Control
- Spot-check a sample of redacted documents
- Verify critical documents individually
- Document any manual adjustments
Error Handling
Common Errors
“Document extraction failed”
- File may be corrupted
- Password protection present
- Unsupported format variant
“Analysis timeout”
- Document too complex
- Try single document processing
- Check document size
“Redaction failed”
- Coordinate mapping issue
- Try re-analyzing the document
- Manual redaction as fallback
Retrying Failed Documents
- View error details
- Address the issue if possible
- Remove from batch or retry
- Process manually if needed
Audit Trail
All batch operations are logged:
- Batch session details
- Documents processed
- Detections made
- Redactions applied
- User who performed the operation
- Timestamps for all actions