KENYA · GUIDE 0577 · EDITION 4.2
Conference registration support in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Administer conference registrations from an approved attendee list, agreeing ticket categories, delegate details, substitutions, payment authority, confirmation routing, and the separation between registration completion and the organizer's own attendance, refund, or admission decisions under the actual published event terms supplied to delegates before booking.
The operating sequence for this offer is:
- Agree required attendee fields, event rules and lawful access, then test the registration form and confirmation process using fictional data.
- Monitor registrations for duplicates or errors, handle authorized corrections and prepare a restricted check-in list without publishing personal contact information.
- Reconcile attendance and outstanding issues with the organizer, transfer the approved records and apply the agreed retention and deletion instructions.
Put acceptance into the job record
Attendee counts reconcile and personal data is not exposed on public lists.
Ask the client to reconcile registered delegates with organizer confirmations, checking spelling, session selections, duplicate entries, dietary information handling where necessary, and substitutions that require the organizer's approval rather than simply changing a name in an internal attendee spreadsheet after the original ticket was issued.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Administer conference registrations from an approved attendee list, agreeing ticket categories, delegate details, substitutions, payment authority, confirmation routing, and the separation between registration completion and the organizer's own attendance, refund, or admission decisions under the actual published event terms supplied to delegates before booking. |
| During delivery | Monitor registrations for duplicates or errors, handle authorized corrections and prepare a restricted check-in list without publishing personal contact information. |
| At acceptance | Ask the client to reconcile registered delegates with organizer confirmations, checking spelling, session selections, duplicate entries, dietary information handling where necessary, and substitutions that require the organizer's approval rather than simply changing a name in an internal attendee spreadsheet after the original ticket was issued. |
| At the pilot review | Record attendee approvals, registration categories, organizer references, payment status supplied by the client, confirmation delivery, substitution requests, unresolved form errors, and final delegate reconciliation so the business can distinguish prepared submissions from registrations genuinely confirmed by the conference organizer under the selected booking category. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
A registration appears complete internally while the delegate remains unregistered if payment did not match the organizer's reference or confirmation went to an unattended address, leaving the traveller without the practical evidence required when arriving at the conference's actual registration desk on the event day.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Ask organiser which statuses permit admission and who decides exceptions. | A form submission or payment screenshot is not automatically a confirmed ticket. |
| 2 | Assign unique references and verify spelling/duplicates with organiser. | Two people sharing a surname remain distinct; cancelled entries do not generate live badges. |
| 3 | Print only approved display name, organisation and category where appropriate. | Do not expose phone numbers, email, medical or meal details on public badges. |
| 4 | Use organiser-approved app/register and practise valid, duplicate, cancelled and not-found cases. | If using QR tools, confirm actual platform behaviour and an offline/failure process before event day. |
| 5 | Keep registered, checked-in, no-show and exception counts separate and return unused badges. | Fifty registrations do not imply fifty arrivals; organiser receives unresolved cases without private data in public reports. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| Attendee appears twice | Compare unique reference and actual registration evidence. | Ask organiser to resolve duplicates before badge printing. |
| QR scans already checked in | Follow the organiser's duplicate-admission rule. | Refer to authorised exception staff rather than admitting automatically. |
| Badge exposes private request | Inspect badge data fields. | Remove sensitive field and route privately to authorised staff. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.