Supplier specifications
What an event registration vendor brief should say
Registration is about to open, and the vendor will only deliver what the brief says it must.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A registration vendor brief covers the registration form and categories, how payment and invoices work, who owns the attendee data, what check-in looks like on the day, what reports you receive and when, and how you will test it before opening.
Personal data handling and payment compliance are for the vendor and your own legal or finance advisers to confirm. The brief should ask the questions and record the answers rather than assume them.
What the brief has to settle
| Item | What to write | Acceptance test |
|---|---|---|
| Registration categories | Member, non-member, speaker, guest, sponsor delegate, with the fields each must give. | Test registration for each category produces the right form and confirmation. |
| Payment and invoicing | Payment methods wanted, who issues receipts or invoices, and refund and transfer rules owned by the organiser. | Test payment, receipt and a refund request are walked through once. |
| Data ownership and access | Who is the data owner, who may see and export it, and what happens to it after the event. | Vendor states this in writing in its terms and answers the privacy question pack. |
| Confirmation and reminders | Wording owner, languages, sending dates and who approves changes. | Sample emails approved before opening. |
| On-site check-in | Counters, scanning or name lookup, badge printing, walk-ins and what happens if connectivity fails. | Rehearsal check-in with a sample list on the day before. |
| Reports and exports | Daily counts by category, final list for catering and seating, dietary needs. | Sample report received in the agreed format before opening. |
| Support during registration | Who answers attendee queries, in which hours and languages. | Escalation contact named on both sides. |
Privacy and payment questions for the competent party
Registration collects personal data, and sometimes payment details. The organiser's own legal adviser or data protection lead decides what the form may ask and how long data is kept. The vendor should be asked to describe its practice, not to decide it for you.
- Where is attendee data stored, and who at the vendor can access it?
- How are consent wording and opt-outs recorded on the form?
- Is payment handled by a separate payment provider, and who is the merchant of record?
- How is data returned or deleted after the event, and by when?
- What incident notification arrangement does the vendor offer?
Dependencies
Registration data feeds catering numbers (catering scope), badge and signage production, and the event digital platform if one is used. Agree which system is the master list and who reconciles changes before each cut-off.
Common gaps
- The form asks for fields nobody will use, which lowers completion.
- Refund and transfer rules are decided after registrations have opened.
- The final list for catering and badges comes from two different spreadsheets.
- Check-in has no fallback if the internet is slow.
Worked example · Fictional example
A fictional professional body opens registration
Fictional organisation and figures, used only to show the level of detail.
The Malaysian Institute of Fictional Accountants plans a two-day congress for about 400 people. Two vendors quote: one includes badge printing and on-site staff, the other provides software only.
The secretariat writes the brief with five categories, names the membership manager as data owner, sets a test registration for every category before opening, and asks both vendors to answer the same privacy questions in writing.
Use this yourself
Registration vendor brief template
Copy into a document and send with your event brief. Mark unknowns Not decided with owner and date.
- Event, dates, venue, expected registrations and categories:
- Fields per category and which are mandatory:
- Payment methods, receipts or invoices, and refund and transfer rules (organiser decision):
- Data owner, access list, export rights, retention and deletion request:
- Privacy and payment questions sent to vendor, with date answered:
- Confirmation and reminder emails: wording owner, languages, approver:
- Cut-off dates for catering, badges and seating lists:
- On-site check-in: counters, method, badge printing, walk-ins, offline fallback:
- Reports and exports: content, format, frequency:
- Support hours, languages, escalation contacts:
- Price basis: set-up, per-registration fees, on-site staff, equipment:
- Acceptance: test registrations, sample reports, check-in rehearsal, sign-off by:
Handle it in-house, or bring in help?
Your team can usually handle this when
- A single category and a simple form with offline payment.
- The vendor is already known and the process is repeated from last year.
- One person owns the registration list.
Outside planning help earns its fee when
- Several categories, payment types, languages or sponsor delegate quotas are involved.
- Registration data feeds catering, badges and a digital platform at once.
- The privacy and payment questions need coordinating with advisers and the vendor.
Want registration briefed alongside the rest of your suppliers?
An Event Blueprint can set registration requirements next to catering, signage and platform briefs, and list the cut-off dates between them. A project lead can then coordinate the vendor's test runs and the written answers to your adviser's questions.
Questions organisers ask
Who owns the attendee data?
This is for your own legal or data protection adviser to confirm. Write the intended position in the brief and ask the vendor to confirm in writing that its terms match.
Should we choose the vendor on price per registration?
Compare the full price basis: set-up, per-registration fees, on-site staff, equipment and reports. Use the same rows for each quote.
What if check-in software fails on the day?
Ask the vendor for a fallback, such as a printed list by surname and a manual badge process, and rehearse it.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.