What a week takes from you.
Before, during and after, with the part that is genuinely yours named in each one. It is a shorter list than people expect, and knowing which items are on it is most of what planning a first year involves.
Before your dates.
Most of it is decisions you have already made.
The two developer accounts are the only part measured in weeks rather than days, so they go first. They are opened in your organization’s name, we guide you through it, and it happens once.
Everything after that is decisions and a little writing, and most of it you have either already made or already have.
What actually lands on your desk:
- Your roster and your dates. The Restaurants taking part, where each of their Locations is, and the Food Item on offer at each. Everything else waits on this, which makes it the thing worth locking first rather than last.
- Three branding decisions. One color, one of three Themes, and your own word for the food, each of which reaches further into the app than it sounds like it should. Your logo and the artwork for the icon are a fourth thing we need.
- The words. Your ground rules, your home page copy, your how-it-works page, and the line that asks somebody to sign up. None of it is hard and all of it is yours, which is exactly why it is worth starting before the week you wanted to be live.
- How it is sorted and filtered. The tags people filter by, whether those are dietary flags or neighborhoods or something only your city would recognize, and the order items appear in before anybody sorts or searches. Both are yours to set.
- Your sponsors. A logo and a link each, on your event.
The week itself.
Three things you can handle while the week runs.
You are already in the admin, because it is the same app you hand your diners. Same email address, same six-digit code, and a Manage entry appears in the menu. You see your own organization and nothing else.
Most of a week is watching it happen. The rest is these three, and what each one costs is the whole argument for not being on paper.
- A venue drops out. Switch it off rather than delete it. It leaves the guide and the map, and the Stamps people already collected there stay on their Passports.
- Something sells out. Mark it at that one Location and leave the others alone. Sold out is set as an expiry rather than a switch, so it clears itself at the time you choose instead of waiting for somebody to remember.
- Somebody missed a Stamp. They ate somewhere on Monday and only found the app on Wednesday, or they were sitting right there and never opened it. Their stamp history is on the event’s Users tab with when and where each one came from, and the one they missed can be added by hand.
None of the three is a reprint, and none of them needs a new download. You change it and it is true from then on: the next time somebody opens the app, they have all the updates.
The rest of the week is the numbers moving. Which item is winning, which venues are getting missed, and who is worth sending a notification to while it still matters.
After the last day.
The counting is already done.
Stamping runs through your Event’s dates. There is nothing to collect at the end of it and nothing to add up.
What happens to the numbers is a decision rather than a task. There is a one-page recap for each Restaurant and a set of exports covering everyone who took part, and nothing reaches a venue unless you send it.
A second year is a new Event on the App you already have. A different week entirely, a Pizza Week beside a Burger Week, is a second App under the same Organization.
Next step
Tell us when your week runs
Send us your dates and roughly how many venues, and we will walk you through what lands on your desk and when.