Food Donation Pickup Scheduling
Design a coordinated pickup flow that matches surplus food with recipient capacity, handling rules, courier availability, and changing quantities.
The brief
Understand the problem
Background
Restaurants and grocers often know surplus quantity only near closing. Recipient organizations need food type, allergens, storage condition, quantity, and arrival time before accepting, while volunteer couriers need realistic pickup instructions.
User context
A bakery expects forty-eight unsold sandwiches and pastries at 20:30. A nearby shelter can accept chilled items only before 21:15, and the assigned volunteer has limited cargo space.
Product problem
The three parties need a shared plan that protects food handling requirements and adapts when quantity, capacity, or timing changes.
Objective
Create donation offer, recipient match, pickup coordination, and exception resolution states for a same-evening collection.
What to design
Define the experience
Required experience
- Describe the food, quantity range, handling, and pickup window
- Review a recipient's capacity and acceptance conditions
- Assign a courier with suitable transport and timing
- Confirm custody or recover from a delay or quantity change
Screens and states
- Donation offer
- Recipient match and acceptance
- Courier pickup plan
- Handoff and exception resolution
Core user flow
Follow the critical path
- 01
The bakery posts an estimated donation with chilled and ambient items separated
- 02
The shelter accepts the sandwiches but limits pastries to twenty units
- 03
A courier with insulated storage confirms the pickup window
- 04
The final count drops, all parties receive the update, and the handoff records condition and time
Product rules
Requirements and constraints
Requirements
- Capture food type, allergens, preparation time, storage state, quantity range, and latest pickup
- Match only recipients whose declared capacity and rules fit
- Show donor, recipient, and courier responsibilities separately
- Require acknowledgement when quantity or timing changes
- Record pickup, condition, custody, and receipt without overstating safety
Constraints
- Food outside the declared handling policy cannot be scheduled
- The platform cannot certify food safety from self-reported data alone
- Recipient locations and client information require limited disclosure
Reality check
States worth considering
Ready-to-use content
Mock data
Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.
Donation offer
- 36 to 48 chilled sandwiches
- 20 to 30 ambient pastries
- Prepared between 15:00 and 17:00
- Pickup: 20:30 to 20:50
- Recipient cutoff: 21:15
Finish line
What to deliver
- Four responsive screens covering a changed final quantity
- A three-party responsibility and notification model
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.