Waalikwaby Protend
Sign in
Conferences and multi-day events

Three days, one delegate list, three different turnouts.

A bank's leadership week is not one event repeated. The same 130 people are invited to all of it, the opening day fills the hall, the middle day scatters into parallel workshops, and the awards dinner pulls them back again. One attendance figure for the week hides all three of those facts.

Create your workspaceStart planning for free.
An agenda written against each dayOne badge, admitted to every sittingTurnout counted day by day
The turnout-by-sitting chart for a three-day summit, with a tall bar for day one, a much shorter bar for day two and a middling bar for the awards dinner.

Turnout

Who came on Tuesday is a different question from who came.

Every sitting counts its own admissions, so the week reads as a shape rather than a total. The dip on day two is not a failure — it is the day the delegates split across three workshop rooms and half of them went to a client instead. You only know that if the report tells you which day is which.

  • Every sitting counted separately, in running order
  • A sitting nobody attended keeps its bar rather than vanishing
  • The same delegate counted once per day they actually came
The reports screen for a multi-day conference, showing turnout for each of the three days alongside the arrivals chart.

Agenda

What happens on the day, written on the day.

Each sitting carries its own description — the running order, which rooms are in use, whether lunch is provided, whether partners are welcome. It is the difference between a calendar entry that says "Day 2" and one that tells a delegate whether to turn up.

  • Rich text against every sitting, not one description for the week
  • Shown to the delegate on their own invitation, not buried in a settings screen
  • Written once, read by everyone who opens the link
The three-day programme as a delegate sees it on their phone, each day listing its times, sessions and rooms.

Delegates

One list, invited to the whole week.

Nobody is invited to Tuesday specifically. The delegate list is the delegate list, every badge admits one person, and which days they actually came is something the gate records rather than something you decide in advance.

  • One badge per delegate, valid all week
  • Admitted separately at each day's gate
  • Search by name, phone or badge code
A conference delegate list of a hundred and thirty single entries, each admitting one place.

The week

A client engagement that spans the calendar.

Three consecutive days read as three linked sittings of one event rather than three unrelated entries, so a planner running several clients can see whose week is whose without opening anything.

  • Consecutive days as sittings of a single event
  • Colour-coded by status alongside every other client
  • Read by day, week, month or year
The Waalikwa calendar in month view, with a multi-day conference running across consecutive days alongside other events.

A different kind of event

Weddings

Family blocks holding four, five and six seats, three sittings in a day, and a michango ledger behind it.

Weddings

Road races

Several hundred single entries arriving inside one hour, checked in at the gate from a phone.

Road races

Birthdays

One person, one afternoon, about thirty-five guests — and no committee anywhere in sight.

Birthdays

Set the days, write the agenda, hand out the badges.

The turnout report builds itself out of what the gate records, so the week is documented by the time it ends.

Create your workspace