Collect
The right file. In the right place.
A document checklist that lets suppliers upload the exact files a project needs.
- Role
- Designed and built, start to finish
- Status
- Concept
- Area
- Ownership
47s · 5 beats
The problem
External file requests become email chains. A received PDF rarely says which requirement it satisfies, or whether it replaces an earlier version.
The idea
Give each requested document an identity before a file exists, then accept uploads against that request.
How it is built
Upload permission is scoped to one requested item, and a document is marked received only once storage confirms it.
Read the diagram as text
A supplier uploads against one requested item. Permission and file format are checked, then the submitted version is saved to customer storage. Only once the file is safely stored does the checklist mark that version received; if storage is unavailable the upload stays pending and any previous version is kept.
Diamonds are decisions. Indigo marks the path that matters. Scroll across to see all of it.
Scope
A design proposal with a fictional project, supplier and document; no file is uploaded. Received means saved to its request — the contents still need a person. Upload permission grants no folder browsing and no sight of other submissions.