The operating problem
A tidy folder is not useful if the file belongs to another client. Prioritize identity and access checks over cosmetic naming. A deterministic naming rule should use opaque references where a filename could be exposed.
Use your own working copy
The free workbook for this process opens in a browser and works offline after download. It includes editable checks and notes, a text export, and a print view. It is a planning resource: it does not send messages, read account data, or run actions in business systems. No vendor account is needed to use the workbook.
Map the process
1. Quarantine incoming files
Validate actual MIME type, extension, size, and malware scanning status. Reject suspicious payloads before routing.
2. Resolve the destination
Match stable client and engagement IDs against an approved mapping. A missing mapping requires staff input.
3. Create a safe filename
Remove path separators, control characters, and unexpected Unicode. Use an approved opaque ID and document category.
4. Move with verification
Check destination permissions and checksum after transfer. Preserve the original until the retention policy permits cleanup.
5. Record a restricted manifest
Store source reference, destination reference, checksum, and approval. Keep document contents out of alerts.
Information to check
These reference fields describe the process. Use invented values while planning. Keep real records in an appropriate private system; the public website does not need them.
| Reference field | Working record | Check before progressing |
|---|---|---|
| file_sha256 | dedupe_key | Verify after transfer |
| client_id | destination_mapping | Stable approved identifier |
| mime_type | allowed_type | Inspect content as well as extension |
| storage_reference | destination_reference | No publicly readable files |
| original_filename | restricted_manifest | Sanitize the routed name |
Acceptance checks
- A path-traversal filename cannot escape the destination.
- A client without a mapping enters quarantine.
- A checksum mismatch blocks completion.
- A file with a misleading extension is rejected.
Walk through a successful example, a duplicate, a missing item, an incorrect match, and an interrupted handoff with synthetic records. Record the expected result, observed result, owner, and recovery action. Checklists record your work; checking a box does not establish that an external action happened.
Ownership and review
Name the person responsible for the process and the person who can resolve an exception. Define which decisions require qualified professional review. Use stable references, limit access to private records, and document when work must stop. Educational material does not establish legal, accounting, tax, security, or regulatory compliance.
Run a measured pilot
Choose a small, reversible sample. Measure handling time, waiting time, review, rework, and errors before changing the process. Include the effort of maintaining the new method. Expand only when the observed result meets your acceptance criteria; a longer checklist is not proof of improved performance.
Use the free workflow planner to define your next step, or compare the assumptions in the opportunity calculator.