Creating a Booking – Administrate Documentation and Support

Purpose: This article explains how to create a booking in Administrate and what to review before confirming a learner onto training. A booking connects a student to an event or course instance and becomes the record that tracks their status, participation, and any related financial activity.

You will typically create a booking when a learner is being enrolled manually by an administrator, when operational teams are adjusting enrollment directly in the platform, or when you need to understand what information is required before registration is complete.

For a concept-level explanation of how bookings work overall, see Bookings Overview. For the broader operational guide to the booking lifecycle, see Managing Bookings.

Before you create a booking

Before creating a booking, confirm the following:

The student record already exists, or you know how the learner will be added.
The correct event or training instance exists and is open for registration.
You understand whether the booking should create or connect to any financial records, such as invoices or payments.
You know whether the learner should be placed directly into a confirmed status or whether your process uses a more provisional or approval-based approach.
You have reviewed any internal rules around pricing, discounts, portals, online registration, or approval workflows that may affect the booking.

These checks matter because booking creation is not only about adding a learner to an event. It can also trigger downstream operational and financial activity depending on how your account is configured.

Where bookings are usually created

Bookings are commonly created from one of these places in Administrate:

From the event, by adding a learner from the event’s student-related area
From the student record, when registering the learner onto a specific event
Through online registration tools such as WebLink or portal workflows
Through integrations, imports, or automated business processes

This article focuses on the manual administrative workflow. If bookings are being created through online registration, portal, or WebLink activity, you should also review the relevant learner-access and registration documentation.

How to create a booking

Open the correct event or learner record, depending on your team’s preferred workflow.
Choose the option to add, register, or book the learner onto the event.
Select the correct student.
Review the event details carefully to make sure the learner is being placed onto the correct delivery.
Complete any required booking fields, such as status, pricing, or other enrollment information used by your account configuration.
Save or confirm the booking.

Once saved, the learner will have a booking record connecting them to that event. From there, the booking can be managed operationally through status changes, edits, cancellation, and finance-related actions.

What to check immediately after creation

After creating a booking, review the booking carefully before moving on.

Confirm the learner was added to the correct event.
Confirm the booking is in the correct status.
Check whether any financial records were created or attached as expected.
Review whether the learner should now receive any communication, portal access, or follow-up actions based on your internal process.
Make sure the booking appears where operational teams expect to find it.

This quick validation step catches the most common enrollment mistakes early, before they affect attendance tracking, learner communication, or billing.

Choosing the correct booking status

When creating a booking, the booking status matters because it affects how the learner is treated operationally.

For example, your team may use different statuses to distinguish between:

tentative or provisional registrations
confirmed enrollments
cancelled bookings
post-delivery attendance outcomes

If you are unsure how status should be used in your account, review Managing Booking Status before making large numbers of manual bookings.

Financial considerations when creating a booking

Depending on your configuration, creating a booking may have financial implications. In some setups, a booking can create or connect to invoices, orders, or payment-related records as part of the registration workflow.

Before creating or confirming a booking, make sure you understand:

whether the learner or organization should be billed
whether pricing has been applied correctly
whether any discounts, tokens, passes, or agreements should affect the booking
whether creating the booking will trigger immediate finance activity

For more on how bookings relate to invoices and payments, see Booking Payments and Invoices.

Common reasons booking creation goes wrong

Most issues during booking creation fall into a few patterns:

The wrong learner is added to the event.
The learner is booked onto the wrong event or date.
The booking is created in the wrong status.
Expected finance records are missing, duplicated, or incorrect.
The learner should have used a portal or online registration process instead of manual booking.

When this happens, the next step depends on the type of problem. Some issues are solved by editing the booking, while others require cancellation, rebooking, or finance review.

Use these follow-up articles as needed:

When not to create a booking manually

Manual booking is useful for administrative control, but it is not always the best option.

You may want to avoid manual creation when:

learners are expected to self-register online
approval workflows should control enrollment
portal or WebLink processes are intended to create bookings automatically
integrations or imports are already responsible for enrollment creation

In those cases, manual creation can introduce duplicate registrations or bypass the intended commercial or approval flow.

After a booking is created

Once a booking exists, the next task usually falls into one of these categories:

reviewing or updating booking status
editing learner or enrollment details
cancelling the learner’s participation
reviewing invoices and payments
troubleshooting unexpected behavior

Continue with the next appropriate article: