open-legal-products proposed moving Mike's large uploads out of the bottleneck
The unmerged plan would send file bytes straight to storage, so completed documents could begin processing before the rest of a batch arrives.
The proposal is less about a new upload button than making document intake behave better under real workloads. Each file would have its own tracked upload and processing path, retaining who submitted it for the audit trail while allowing some files to succeed if others fail.
- Direct browser and Word add-in uploads to storage, reducing pressure on the application service.
- Per-file processing, retries and progress checks, so completed files need not wait for a whole batch.
- Familiar mixed file and folder selection, download and deletion, with immediate visual feedback.
- Streaming downloads and processing with size limits, reducing memory risk for large folders and files.
The work did not land, but it signals the scale and reliability improvements worth watching in Mike's document workflow.
So what Legal teams handling larger matter files should care because smoother uploads and safer bulk downloads are foundational to dependable document operations.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?