workflows

How to automate client document collection without losing the status of each file

A privacy-aware collection workflow with item-level states, validation, reminders, and safe handoff.

A folder containing files is not a completed client packet. The workflow must know which requested item arrived, whether it is usable, and who decides an exception.

Short answer

Track each requested item separately. Confirm receipt, validate only objective constraints automatically, route uncertain content to a person, stop reminders for resolved items, and delete or restrict files according to an approved retention rule.

Item-level contract

{
  "case_id": "known engagement",
  "item_id": "requested document type",
  "purpose": "why it is needed",
  "status": "requested|received|invalid|accepted|waived|expired",
  "storage_reference": "restricted location",
  "reviewer": "accountable person"
}

Google Forms can restrict file type, count, and size, and stores uploads in Drive. It also requires responders to sign in to a Google Account and does not support file-upload questions when the form is in a shared drive. Those limits matter when choosing a collection channel.

Safe state flow

requested → received → accepted
                 ↘ invalid → requested
requested → waived (human reason)
accepted → expired (when validity matters)

Do not infer document truth from filename, OCR confidence, or upload success. A reminder reads the item state immediately before sending and names only missing items; sensitive categories should not appear in notification subjects.

Reversible pilot

Use synthetic files for wrong type, excessive size, duplicate upload, unreadable content, late arrival, waived item, revoked access, and a client without a Google account. Pass only when no real personal document is collected, resolved items stop reminders, access is least-privilege, and the fallback channel is documented.

Measure accepted-on-first-review rate, invalid items, time to complete a packet, reminders after resolution, orphaned files, access exceptions, and retention deletions. Connect the handoff to turning forms into tasks without treating file arrival as task completion.

Sources