Recurring schedules
Weekly, fortnightly or on your own pattern. Change the series and every future occurrence follows.
Set an event up once and it repeats, books its rooms and expects the right people. Tickets go to every attendee, the doors are run from a phone, and every visit lands on the person's record.
No credit card. Qikbot is included.
Why it's different
A ticketing site knows who paid. Qik also knows who they are, who is expected, which room is free, who is rostered on and who has gone home, because it all sits on the same records as everything else.
Copy last week's event and fix the dates by hand.
Set the pattern once. Each occurrence is created for you with its rooms booked, and any room that's already taken is flagged instead of double-booked.
One ticket per order, in the buyer's name.
One named ticket for every person on the registration, each linked to their own record and emailed to them. At the door you can see who collected it, and when.
A list of whoever bought a ticket.
Describe who's expected, like every Year 3 family or the whole under 12s squad, and see who has arrived, who hasn't and who never showed.
A paper sign-in sheet at the front desk.
Check-in by staff or a parent, a printed name label with the note that matters, like a peanut allergy, and a matching code or PIN to check them out again.
How it works
Dates, rooms, sessions, the registration form and who's expected. Make it repeat and every future occurrence is ready.
On your own website. Each person gets a named ticket, and the team on the roster gets their reminders.
Check people in and out, print their labels and watch arrivals against who's expected. Attendance is on every record afterwards.
On the day
Everyone you expect is already on the list. Check them in from any device, print their label and see the room fill up in real time. When it's over, every visit is on their record.
The basics, covered
The planning, the people and the paperwork that usually live in five different tools.
Weekly, fortnightly or on your own pattern. Change the series and every future occurrence follows.
Book halls, rooms and courts by venue. A clash is caught before it happens, and Qik can find you a free room.
A conference day or a camp with several streams, each with its own rooms and its own check-in.
Attach a form to the event, with prices, questions that adapt and payment taken on the page.
Every person on a registration gets their own ticket, and you can send it again in a click.
Check-in opens before the start and closes after the end, so late arrivals still count.
Mark a period when nothing runs, so it shows on the calendar without anyone being expected.
Who came last term, who has missed three weeks, how numbers compare. Ask Qikbot and get the list.
Each registration, ticket and check-in sits on their timeline next to their forms, payments and messages.
The team behind it
The people who make the day happen are on the same records as the people who come to it.
Fill each position for each event, with suggestions for who's available and suits the role.
People mark the dates they're away, and clashes are flagged before anyone is rostered on.
Rostered people are reminded ahead of time, can accept or decline, and a swap keeps the roster full.
A minute-by-minute plan for the event, in sections with your own columns, started from a template.
Helpers and leaders check in alongside everyone else, so you know who's on site.
Make this event repeat every Thursday in a free room, or roster the usual team for next month. It sets it up for you.
Start today
Start a free trial and tell Qikbot what you need, or talk to the people who build it. Either way you begin with something that works.
No credit card. Your data stays yours, and you can export it any time.