NestPoint
Start free trial

← All features

Operations · Events & Trips

The bus leaves at nine. Everyone on it is on your list.

Publish the trip, take sign-ups and the fare, lay out where everyone will be at two o'clock, and check people aboard from the same record.

Try NestPoint free for 21 daysSee pricing

What it helps with

What your team can do here.

Sign-ups

The seat and the fare, in one step.

Members sign up from the portal or at the desk, and pay the fare there. Set the capacity, decide whether a waitlist forms behind it, and choose whether a signup needs a staff yes first. Members can pull out themselves up to the cutoff you set, after which it comes to you, which is roughly when you want to hear about it anyway.

  • Registration opens and closes on the dates you set
  • Fare paid at signup, or owed and settled at the desk
  • Self-cancel up to your cutoff, then it becomes your call

Itinerary

Where everyone is at two o'clock.

Build the day in order: the time, the place, and what is happening there. Members see it in the portal before they go, so the questions get asked in the week beforehand instead of in the coach park. Departure and return times and places sit on the trip itself, where nobody has to hunt for them.

  • Ordered stops with a time, a place, and a note
  • Visible to members in the portal before the day
  • Departure and return points on the trip record

The manifest

Who is actually on the bus.

The roster is the list of people who signed up, and boarding is a separate mark, because those are not the same thing and the difference matters when you are counting heads on a kerb. Check people aboard as they climb on, and mark the rest as no-shows in one action rather than one at a time.

  • Boarding recorded per person, with who marked it
  • Everyone still unmarked set to no-show in one action
  • The count is of people aboard, not people who meant to be

Afterwards

Thank the people who came.

Attendance is recorded per person, so a follow-up can go to the people who came, the people who did not, or the ones still on the waitlist when the coach pulled away. Each member's trip history stays on their record, which is how you notice who has been on nine of them and who has never been on one.

  • Follow-up split by who actually boarded
  • Every member's trip history on their record
  • Attendance and fares collected, in reports

A typical workflow

Set it up in the morning. Take sign-ups by lunch.

One record carries the trip from the day you think of it to the report that mentions it.

  1. Set up the trip. Destination, dates, the fare, the cap, and where the coach leaves from and comes back to.

  2. Publish it. Put it in the portal with an intro note, or keep it staff-only and take the sign-ups yourself.

  3. Fill the seats. Sign-ups come in, the waitlist queues behind the cap, and the fares are collected as they go.

  4. Board the coach. Check people aboard, mark the ones who never turned up, and go.

  5. Close it out. Thank the people who came, and put the numbers where the board can find them.

Connected work

Keep the next step connected.

Works with

Other parts of NestPoint that share this information.

Especially useful for

Teams that often use this part of NestPoint.

Common questions

What teams ask before getting started.

The gala, the retreat, the pancake breakfast.

See how a trip, a fare, an itinerary, and a headcount on the kerb all run off one record.

Try NestPoint free for 21 daysSee pricing

Card required. Cancel anytime.