You do not need to set everything up before anyone can use CrewByte. The fastest way to get real value is to get one site running one checklist on an actual shift — then improve and expand from there.
Trying to launch with every checklist, every person, and every feature on day one usually creates confusion and slows adoption. Keep the first hour focused and practical.
Goal for the first hour
By the end of this session you should have:
- One location correctly set up
- Your key temperature equipment added
- One working checklist (opening or closing)
- Two or three people who can log in and complete it
- A clear plan to run it on the next real shift
Step-by-step (in order)
1. Check your site details
Go to Settings → Locations.
The two most important fields are:
- Timezone
- Trading day cutoff
These control which calendar day a late-night closing check belongs to. Getting this wrong is one of the most common early frustrations, so set it correctly now.
While you’re here, confirm the site name is exactly how you want it to appear on reports and exports.
2. Add your appliances
Go to Settings → Equipment.
Add every fridge, freezer, walk-in, and hot-holding unit that you temperature-check. For each one, set a realistic target range.
This step usually takes 8–12 minutes and is what turns temperature logging from a list of numbers into something useful. You can always add more equipment later.
3. Choose your first checklist
Pick either Opening or Closing — not both.
We strongly recommend starting with whichever one is currently most painful or most likely to be missed on paper. Build it properly, get people using it, then add the second checklist a few days later.
If you already have a laminated sheet or paper version, send it to us. We will turn it into your first digital checklist so you’re editing something familiar instead of starting from a blank screen.
4. Add only the people who will use it this week
Go to Team.
Invite two or three people who are actually working the next few shifts. Do not invite the whole team yet. Early adoption works better with a small group who can give you quick feedback.
Make sure at least one Manager/Owner account and one Team Member account are set up so you can test both experiences.
5. Do a dry run, then run it live
Before the real shift, get one person to walk through the checklist on their phone. Fix any wording, missing items, or awkward steps immediately.
Then run it on an actual shift. Afterwards, spend ten minutes with the person who completed it and ask:
- What felt slow?
- What was unclear?
- What did you normally do on paper that is missing?
Make those small changes the same day.
What to deliberately leave until week two
- Training modules — useful, but they distract from getting the daily checks running.
- Mock audits — far more valuable once you have a week or two of real data.
- Custom roles & permissions — the default Owner, Manager and Team Member roles are enough for almost every site at the beginning.
- Multiple checklists — master one before you roll out more.
- Multi-site setup — get one site working smoothly first.
Quick tips for a smooth first week
- Keep the first checklist short. You can always add more items later.
- Make critical food-safety items required (temperature + photo or corrective action).
- Tell the team this is a trial and you want their honest feedback.
- Check the “Outstanding” view yourself at the end of each shift for the first few days.
- If something feels clunky, change it immediately — don’t wait.
If you are moving from paper, bring us the laminated sheet. We will build your first checklists from it so you are editing something familiar rather than starting at a blank screen.
The aim of the first hour is simple: One site. One checklist. Real use on a real shift. Everything else can follow once that is working.