AI Event Registration Administrator / Australia

Attendee records.
Ready to review.

Cleo prepares attendee records, missing-field lists and confirmation drafts from your event exports. Your organiser controls bookings, payments and every attendee message.

  • Human approval
  • One event first
  • No attendee sending

[ THE REGISTRATION DESK ]

Every row traceable.
Every unresolved booking visible.

For Australian adult business event organisers who can provide an export and review each batch. This is preparation for a human-run event desk.

01

Attendee records

Approved fields in a working copy, with event and registration IDs beside every row.

02

Missing fields

Gaps and conflicting rows listed for your organiser, without guessed identities.

03

Confirmation drafts

Your template and recorded preferences, ready for internal recipient review.

04

Session summary

Recorded rows grouped by your session codes, without allocating seats.

05

Review pack

A dated list of prepared drafts, held items and documented organiser decisions.

Children, sensitive information, payment processing and event-day support are excluded. Your team handles dietary and accessibility requests directly. Ongoing membership records stay with Darcy; reception and intake stay with Harper.

[ START WITH ONE EVENT ]

Choose the preparation your desk needs.

CSV or spreadsheet exports are enough to assess a first batch. Platform integration requires separate assessment.

WORKFLOW / 01RECORDS

Prepare the working attendee list

Arrange the approved fields from your event export without changing the live platform.

START
A redacted export and agreed field dictionary
DONE
Source-linked rows plus a gap and conflict list
HUMAN
Resolves conflicting IDs and controls the official record
WORKFLOW / 02DRAFTS

Prepare the confirmation review queue

Use the approved template and recorded preferences; hold unresolved recipients aside.

START
Your template and recorded contact preferences
DONE
Confirmation drafts with proposed recipients
HUMAN
Checks each recipient and sends every message
WORKFLOW / 03HANDOFF

Close the registration review loop

Group recorded rows by supplied session codes and list decisions still needed.

START
Working rows and documented organiser decisions
DONE
A dated review pack with held items and named decision owners
HUMAN
Decides bookings, waitlists and every ticket issue

[ THE APPROVAL LANES ]

What Cleo prepares.
What your organiser decides.

Internal working copies and drafts only. Approval can change the agreed preparation scope; it cannot grant an excluded decision, platform write or attendee send.

GREEN

DOES-IT-ALONE

Internal preparation in the agreed private workspace.

  • Prepare a working attendee list from the approved fields in your registration export
  • List missing fields and conflicting registration rows without resolving identity
  • Group recorded registrations by the session codes your organiser supplies
  • Prepare confirmation drafts using your approved template and recorded contact preferences
  • Record organiser decisions already documented in the internal working copy
  • Compile the weekly registration review pack with unresolved items held aside
AMBER

APPROVE

A named person reviews these handoffs and scope changes.

  • Hand confirmation drafts and proposed recipients to your nominated internal reviewer
  • Prepare proposed attendee-field corrections for your organiser to check
  • Change the working fields or draft template only after your named approver agrees
RED

NEVER

These actions stay outside this service, even with approval.

  • Accept or reject a booking, allocate a place, move a waitlist or decide admission
  • Issue tickets, change prices, authorise refunds, take payment or move money
  • Send attendee messages, publish attendee lists or disclose records outside your nominated review team
  • Write to the live registration platform or delete its records
  • Verify identity, award attendance credit or certify participation
  • Process records about children, health, accessibility needs, dietary needs or other sensitive information
  • Plan event safety, interpret permit duties, book travel or commit a venue or supplier
  • Run prospecting, sponsor lead sharing or marketing campaigns

[ THE DELIVERY AGREEMENT ]

A reviewable pack.
A named organiser at the end.

These examples are fictional output shapes, not customer results. Turnaround and volume are confirmed before live work.

Example output — fictional registration E-104
Confirmation draft prepared; recipient and wording awaiting organiser review
Example output — fictional registration E-208
Conflicting session codes in two source rows; held for organiser decision
Weekly measures
Rows prepared; missing fields; conflicts unresolved; drafts awaiting review
Proposed turnaround
Next-business-day handoff for one complete agreed batch before the confirmed cutoff, subject to written onboarding agreement
Human review
Named organiser checks every proposed recipient and controls the live registration list
CONTROL / 01ONBOARDING

Confirm the fields and reviewer

Bring a redacted export, event and registration IDs, session codes, recorded contact preferences and approved template. Name an organiser and escalation contact. Test a conflicting ID and missing field before accepting live records.

CONTROL / 02CAPACITY

Agree a batch limit before work starts

The delivery team agrees a maximum number of rows and drafts per batch, working hours, cutoff and review slot in writing. Excess work waits for reprioritisation or separately agreed capacity. There is no real-time, event-day or unlimited-volume promise.

CONTROL / 03ESCALATION

Hold the affected rows

List the source, conflicting field and decision needed at the agreed handoff. Unknown contact permission or conflicting IDs stay held. Unexpected sensitive data pauses the affected workflow and immediately alerts your named contact via the agreed route.

CONTROL / 04DATA HANDLING

Keep the export narrow

Use the minimum approved fields in client-approved storage with named access and retention and deletion instructions. Exclude sensitive fields before transfer. No sponsor sharing, public attendee directory, cross-client reuse or model training on attendee records.

No assumed registration-platform integration, autonomous sending or live-platform write access. Your organiser owns all booking, admission, capacity, refund and safety decisions. A load audit scopes one workflow; it does not promise a ready-made connector.

[ FROM AUDIT TO TRACKED WORK ]

One event.
Your organiser in control.

Agree the first delivery before live work.

STEP 1

Map the desk

Choose attendee records or confirmation drafts with a redacted export.

STEP 2

Agree access

Confirm minimum fields, private storage, working hours and the batch limit.

STEP 3

Test fictional records

Check a conflicting registration ID and a row missing its session code.

STEP 4

Review the first batch

Your organiser checks the pack and confirms the ongoing review slot.

[ BEFORE THE FIRST EXPORT ]

The registration desk, explained.

Does Cleo send confirmations or tickets?

No. Cleo prepares confirmation drafts and proposed recipients in your private review workspace. Your organiser checks each draft and sends it using your own platform. There is no automatic sending. Ticket issue, booking acceptance and admission stay with your people.

Which events fit this workflow?

Adult business workshops, conferences and networking events with an organiser who can review each batch. Start with one event and a registration export. Events whose attendance reveals sensitive information, children's events and live event-day support are outside this offer.

What files and tools are needed?

Bring a CSV or spreadsheet export with stable registration and event IDs, the approved field list, session codes, recorded contact preferences and a confirmed message template. Work stays in an agreed private workspace. No live registration connector or platform write access is assumed.

Can Cleo handle dietary or accessibility requests?

No. Keep dietary, accessibility, health and other sensitive fields out of the export. Your authorised event staff handle these directly. If unexpected sensitive data arrives, Cleo pauses the affected workflow and alerts your named contact through the agreed route.

Who owns the live attendee record?

Your organiser owns the registration platform and all booking decisions. Cleo prepares an internal working copy with source references. A conflicting or missing ID is held for your organiser; it is never treated as an identity match or a confirmed place.

How is this different from membership or front-office administration?

Darcy prepares ongoing member records and renewal drafts. Harper owns reception and intake paperwork. Cleo prepares a separate event-specific registration review pack. Membership status, general reception, event promotion and event-day operations are outside this workflow.

When will the first review pack arrive?

During onboarding we agree working hours, cutoff, maximum rows and drafts per batch, the first delivery date and the review slot. The proposed starting target is a next-business-day handoff for one complete agreed batch before the confirmed cutoff. It becomes a commitment only after written delivery-team confirmation. No real-time or event-day cover is promised.

What is in the review pack?

A dated working attendee list, missing-field and conflict list, confirmation drafts with proposed recipients, and a summary by the session codes you supplied. Counts describe recorded rows rather than seats available, attendance or capacity compliance. Your organiser resolves every held item and controls the live list.

[ ONE EVENT WORKFLOW ]

A clear pack for the next review.

Choose the registration records and confirmation drafts your organiser needs prepared.

Book the Registration Load Audit Direct with the founder