Product documentation

Bookings Overview

Purpose: This article explains how bookings work in Administrate. A booking represents a learner’s enrollment in an event or course, but it is also part of the…

Purpose: This article explains how bookings work in Administrate. A booking represents a learner’s enrollment in an event or course, but it is also part of the wider workflow that connects learners, events, pricing, financial records, and operational progress from registration through completion.

Understanding bookings is important because they sit at the center of the training management workflow. Every learner attending an event has a booking record that tracks status, financial obligations, participation, and the operational history of what has happened to that registration.

In this article

What is a Booking?

A booking is created whenever a student is registered onto an event or course. The booking record stores the operational and financial information related to that student’s participation.

A booking connects:

  • The student attending the training
  • The event or course instance
  • The pricing structure applied to the booking
  • Any invoices or payments associated with the registration
  • The student’s attendance and completion status

Bookings are typically created in one of several ways:

  • Manually by administrators
  • Through online registration via WebLink or portals
  • Via integrations or imports
  • Automatically through automation rules

Why Bookings Matter

Bookings are more than a simple registration record. They are the operational link between demand, scheduling, learner participation, and revenue.

They provide a single place to track what has been booked, what stage a learner is in, what actions still need to happen, and what financial or operational activity has already taken place.

For many teams, bookings replace fragmented processes that would otherwise live across spreadsheets, emails, and disconnected systems.

Bookings, Pipeline, and Workflow

In many Administrate implementations, bookings are part of a broader process that begins before a learner is fully enrolled. This can include lead capture, applications, approvals, or sales activity.

Because of this, bookings are often used as a pipeline management tool, not just a final registration record.

Bookings can be tracked through a structured workflow made up of:

  • Stages – high-level states such as open, won, lost, or archived
  • Steps – the phases within your process (for example: lead, proposal, booking)
  • Transitions – the rules that control how a booking moves between steps

This structure allows teams to:

  • Track registrations that are still in progress
  • Enforce required operational steps before confirmation
  • Maintain consistency across staff
  • Improve visibility into pipeline performance

In some configurations, bookings can also support forecasting by tracking values, probabilities, and conversion rates across the pipeline, helping teams understand expected revenue and performance trends.

To understand configuration options, see:

The Booking Lifecycle

Bookings move through a lifecycle as a learner progresses from registration through course completion.

Typical booking statuses include:

  • Provisional – a tentative registration awaiting confirmation
  • Confirmed – the learner has a confirmed seat
  • Cancelled – the booking has been cancelled
  • Completed – the learner has attended successfully
  • No Show – the learner did not attend

Administrators manage booking statuses as part of event management and attendance tracking.

Creating Bookings

Bookings can be created directly or automatically through registration systems.

  • Adding a student to an event
  • Creating from a student record
  • Online registration via WebLink or portals
  • Imports or API integrations

See:

Managing Existing Bookings

Once created, bookings can be updated throughout their lifecycle.

  • Edit booking details
  • Change booking status
  • Transfer bookings between events
  • Cancel bookings
  • Add notes and track history

Each booking also maintains a historical record of activity, including updates, communications, and related operational actions, helping teams understand what has happened and why.

See:

Payments and Financial Records

Bookings are closely tied to the financial lifecycle of a registration.

Depending on configuration, a booking may generate:

  • Invoices
  • Sales orders
  • Payment records
  • Credit notes

In many workflows, financial records are created automatically when a booking reaches a specific stage (such as confirmation or completion).

Online Registration and Portals

Administrate supports automated booking creation through:

  • WebLink storefronts
  • Student Portal
  • Approval workflows
  • LMS integrations

These tools allow learners or organizations to create bookings without manual intervention, while still following your configured workflow and rules.

Getting Started

If you are new to bookings, a recommended path is:

  1. Read this overview
  2. Review Bookings Workflow
  3. Review Bookings Layout
  4. Use task-based guides for daily operations

Troubleshooting Bookings

Common issues include:

  • Bookings not appearing on events
  • Duplicate registrations
  • Payment mismatches
  • Status inconsistencies

See: