Back to docs
Getting Started

How Uploads Work

Understand the end-to-end flow from creating a request to receiving files from clients.

Understanding how the upload flow works helps you troubleshoot issues and set client expectations. Here's the complete lifecycle of a file upload.

The upload flow

  1. Client opens the upload link — No login required. They see your branded checklist with descriptions and due dates.
  2. Client previews and drops files — Files are previewed locally before upload so clients can verify they selected the right document.
  3. Direct-to-storage upload — Files are uploaded directly to secure cloud storage using signed URLs. This bypasses server size limits and supports files up to 50 MB each.
  4. Upload confirmation — After the file reaches storage, the system records metadata (file name, size, type) and updates the checklist item status.
  5. Notifications sent — You receive an email (and optional SMS) notification for each uploaded file. Your client sees a progress indicator.
  6. Auto-completion — When all checklist items are uploaded or skipped, the request is marked complete and a thank-you email is sent to your client.

File types supported

By default, the following file types are accepted:

  • Documents: PDF, DOC, DOCX, TXT, PPT, PPTX
  • Spreadsheets: XLS, XLSX, CSV
  • Images: JPG, JPEG, PNG, HEIC, TIF, TIFF
  • Email files: MSG, EML
  • Archives: ZIP

You can customize allowed file types per checklist item when creating a request.

File size limits

  • Maximum file size: 50 MB per file
  • No limit on number of files per checklist item
  • Storage limits depend on your plan (Free: 2 GB, Pro: 50 GB)

Security

All files are encrypted in transit (TLS 1.2+) and at rest. Only you (the requester) can access uploaded files. Clients cannot see files uploaded by other clients, and upload links are unique per request.

Version history

When a client uploads a replacement file for the same checklist item, the previous version is preserved in the version history. You can access all versions from the request detail page.