Site turn checklists
Pitch steps in a fixed order, with a photo where damage needs recording.
SIZ Group designs and builds a campground staff app that assigns site turns, grounds work, checklists and photos to each team member, so the seasonal crew can pick up a shift without a briefing from the office.
The operations manager signs off when the morning walk round the grounds can be replaced by a screen. Each site due for a turn should show as cleaned and checked, each restroom and shower block should show its last cleaning time, and each fire ring and water point should show as inspected.
The second test is the seasonal crew. Many campgrounds hire students and short-term staff for the summer, and they arrive with no history. The app must give a new person the same list the veteran sees, in order, without needing to remember which loop is which.
The third test is the weather. A storm can flatten a tent pitch or cut a water line. The manager should be able to add an urgent job to every affected team member in one step, then see who has picked it up.
The first release covers site turns, grounds checklists with photos and a shift note feed. A site turn is a checklist for each pitch: clear the fire ring, check the water and electric hookups, sweep the pad and photograph anything damaged. Steps close in order, and a damaged item opens a repair task.
Grounds checklists cover recurring work such as mowing the loop, emptying bins, checking the dump station and refilling firewood racks. Each one has a due time and an owner, so the crew can see the next job at a glance.
Shift notes carry anything still open, such as a leaking tap or a camper's request for an extra towel, to the next shift. Scheduling, payroll and inventory links can wait until the crew trusts the basic routine.
Before the build, the campground supplies its site list with loop names and hookup types, the turn standard for each site type and the grounds schedule by season. A simple map of the loops helps everyone, including the new crew, find the right pitch on the first day.
Content should be specific. A fire ring check reads better as three named checks with a photo than as a line saying keep the site safe. Some crews speak more than one language, and the content may need translating before the season opens.
On access, the manager sees the whole park, loop leads see their own loops, and seasonal staff see only the tasks for their shift. The owner decides how long photos are kept and who can export them.
Pitch steps in a fixed order, with a photo where damage needs recording.
Recurring loop work with due times, owners and the next job visible to the crew.
A damaged hookup or fire ring opens a repair task the lead can track to completion.
Open items carried to the next shift, from a leaking tap to a camper's request.
The first mistake is writing the task list at the office desk. The people who clean the pitches know the real steps, such as which tap drips or which loop floods after rain. We would build the first checklist with a lead who walks the loops, then test it on a real turn.
The second is turning the app into a second job. If a crew member must log every walk round the grounds, the app will be ignored by midsummer. Each task should take a few taps, and only the steps that matter should be required.
The third is ignoring the seasonal cycle. A list built in July may be wrong in October, when the crew changes and the grounds shift to winter work. The owner should plan to review the templates at each season change.
Start with a short briefing on the first day of the season, led by the lead rather than the office. Show the crew the phone screen, one site turn and where the photos go. Five minutes at the start beats a long manual.
Give everyone a printed card with a QR code and one plain instruction for the most common task. Pair new staff with a veteran for their first two turns, so the habit forms on the real ground.
We would pilot with one loop before opening the whole park. The lead can check that tasks close properly and that photos show what the standard asks for, then widen the app to the rest of the grounds.
Use the operations numbers the park already keeps: how many sites are turned by a set time, how many repairs are reported in the first week and how often a pitch is found unready at check-in. Capture those figures before launch as a baseline.
Watch the crew too. Many tasks closed without photos may mean the standard is unclear, while many tasks left open at the end of a shift point to too many jobs for the crew size.
Give the owner a weekly comparison against the same weeks last year and against the pre-launch baseline, so the season's own patterns are not mistaken for the app's effect.
Yes, and that is the case it is built for. Each person sees their own list in order, with steps written in plain language. Pairing a new hire with a veteran for the first turns helps more than a long training session.
The lead marks the site as blocked and gives a reason. A repair task opens if one is needed, and the site stays blocked until someone clears it.
Yes. Each completed step, photo and note is time stamped and tied to a person and a site, so the lead can review the day or answer a question about a pitch weeks later.
Not always. Many parks use a few shared phones or tablets kept at the maintenance shed, and the app can be limited to crew tasks on those devices. We would confirm the devices before the build.
The owner sets how long they are kept. Photos can be archived or deleted, and the owner decides who can export them, so the record matches the park's own policy.
Walk the loops with us during the scoping call, then agree the site turn list and the first release in writing.