ClubPilot guided walkthrough

Welcome to ClubPilot. We are in a fictional 10-club workspace for Peakline Fitness Group. The names, clubs, jobs, and figures are examples. In this walkthrough, you will see the actual demo being operated, from a club manager creating work, to a leader reviewing it and closing it. The View as control lets us switch roles in the same browser tab. Each role sees the work it needs while owners have a broader picture across the group. We start on the owner dashboard. It is a place to notice what needs a decision. Maintenance, approvals, checklists, local marketing and other work across the clubs. A headline number is a starting point. Open the underlying record to see the club, owner, status and next step. In a live rollout, set up your locations and people first, then check that each manager sees the right clubs. That access design matters because too much noise can hide urgent work. Now I am switching to Olivia, the club manager at Brisbane City. We will build a local area marketing plan for October. The LAM plan centre keeps outreach, events, budgets, targets and follow-up together. Olivia starts a new monthly plan, selects the month and enters an offer for former members. She records the channels, a measurable reactivation target and the action that follows. These fields are useful when they tell the team what to do, not simply because they are filled in. Next, Olivia adds a Brisbane Open Day. We put in the date, who it is for, the requested budget and a lead target. The plan can include more event setup and promotion detail as needed. She saves the draft. Notice that saving and submitting are separate decisions. The draft is still hers to edit. Because the event has a requested spend, she requests a budget review before submitting the whole plan. The budget now shows requested. She submits the plan for review and its status changes to submitted. Now we move to maintenance. Olivia opens the maintenance log and chooses new request. She selects the club, names Spin Bike 12 and describes the fault in plain language. The pedal bearing is grinding and slipping under load, so she marks the priority high. The club, item and issue are enough to create a job. Photos, supplier details and a due date may be added when they are useful, but the first report should be quick. She creates the job and ClubPilot gives it a job number. The original report is now a record that can be found and followed, not a message somebody must remember to forward. We switch to Marcus, the area manager. He can inspect the plan for his assigned club. He sees the audience, activity, target and event rather than a loose email attachment. He first approves the requested event budget. Only then can the full plan be approved. That separation makes the spending decision visible in the same record as the activity it supports. Marcus approves the plan. Returning to Olivia shows the decision from the manager's side. The approved dates can feed the plan calendar, and both people can see what was proposed and decided. If the plan needed work, the reviewer could request changes with notes instead. That is the handoff we want. A club manager proposes, an authorised reviewer decides, and the club can act on the approved plan. Watch the role switch. Amelia, the business owner, sees the new issue on the group dashboard and in the maintenance queue. Opening the job shows the fault, location, priority, status and history. The same item is visible to the people responsible for acting on it. Amelia moves it to in progress and adds an update that the facilities team has booked an inspection and parts check. In a real business this is where you would assign the right owner, set a sensible due date and record any quote or approval required. The update matters because the club manager can see what is happening without chasing a separate conversation. When the repair is actually finished, Amelia marks the job completed. The status and history remain with the job. For safety critical equipment, your team should agree what evidence and verification is required before closing the issue. A completed button is only useful when it reflects a real outcome. You can filter completed jobs later to review what happened and how long it took. That provides a better basis for weekly operating meetings than scattered calls and spreadsheets. The same pattern extends to the rest of ClubPilot. Monthly checklists give recurring duties a clear owner and completion state. ClubWalk inspections let managers capture observations at a location. Alerts and approvals bring decisions to the right person. Staff onboarding keeps required steps visible, while reports help leaders spot exceptions across clubs. Start with one workflow that your people already struggle to track. Put a few real examples through from start to finish. Check the role permissions and adjust the process with the team. The fictional demo can be reset and explored again at clubpilot.au/demo. Thank you for watching.