Three dates, three separate handoffs
Original fictional meal-support reading copy, not a MealTrain.com export, booking page or recipient record. No actual invitation address or delivery has been supplied.
Requested delivery dates
3 requested dates · 2 recorded fictional offers · 1 date with no offer
M01 · November 9, 2026
Ellis has offered a meal in this fictional record.
Proposed delivery window: 5:00-6:00 p.m.
Actual local time zone, dish and handoff arrangement: __________
M02 · November 11, 2026
No offer recorded. This date remains open in the exercise.
Actual contributor, meal and delivery details: __________
M03 · November 13, 2026
Rowan has offered a meal in this fictional record.
Dish and actual delivery details are not supplied: __________
One contribution per date is this exercise's plan. These counts are dates, not portions, people fed, actual bookings or completed deliveries. Household size and recipient acknowledgment are not supplied.
Confirm before inviting participants
- Recipient-approved dates, time zone and delivery windows.
- Actual household size and recipient-supplied preferences or requirements.
- Recipient-approved drop-off instructions and permitted audience.
- The maintained invitation page and actual coordinator's contact route.
Actual booking invitation / coordinator route: __________
Use the organizer's actual invitation to sign up. This reading copy has no Volunteer, Submit, Donate, confirmation or send button and cannot reserve a date.
Participant reply format
Date / contribution I am offering: __________ Meal details requested by the recipient: __________ Actual delivery arrangement I can make: __________ Question to resolve with the coordinator: __________ Recorded through the real calendar / coordinator: __________
Leave that last line blank until the real arrangement is recorded. Do not treat an offer as a delivered meal or certify dietary suitability from a calendar.
Return to the requested dates