Attendee records
Approved fields in a working copy, with event and registration IDs beside every row.
AI Event Registration Administrator / Australia
Cleo prepares attendee records, missing-field lists and confirmation drafts from your event exports. Your organiser controls bookings, payments and every attendee message.
[ THE REGISTRATION DESK ]
For Australian adult business event organisers who can provide an export and review each batch. This is preparation for a human-run event desk.
Approved fields in a working copy, with event and registration IDs beside every row.
Gaps and conflicting rows listed for your organiser, without guessed identities.
Your template and recorded preferences, ready for internal recipient review.
Recorded rows grouped by your session codes, without allocating seats.
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.
[ THE APPROVAL LANES ]
Internal working copies and drafts only. Approval can change the agreed preparation scope; it cannot grant an excluded decision, platform write or attendee send.
Internal preparation in the agreed private workspace.
A named person reviews these handoffs and scope changes.
These actions stay outside this service, even with approval.
[ THE DELIVERY AGREEMENT ]
These examples are fictional output shapes, not customer results. Turnaround and volume are confirmed before live work.
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.
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.
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.
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 ]
Agree the first delivery before live work.
Choose attendee records or confirmation drafts with a redacted export.
Confirm minimum fields, private storage, working hours and the batch limit.
Check a conflicting registration ID and a row missing its session code.
Your organiser checks the pack and confirms the ongoing review slot.
[ BEFORE THE FIRST EXPORT ]
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.
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.
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.
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.
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.
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.
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.
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 ]
Choose the registration records and confirmation drafts your organiser needs prepared.
Book the Registration Load Audit Direct with the founder