Exhibitor Team Registration: Roles, Data and Access

A practical framework for an exhibiting company: who maintains the register of stand staff, what data to collect, how to handle replacements and pass a confirmed status through to accreditation.

Exhibitor team registration often starts with a shared spreadsheet. It gets forwarded to marketing, HR, the stand manager and the organiser. After a few edits it is already hard to work out the final line-up, see a replacement for a sick employee or check the data for a badge. The error surfaces late: a person is scheduled for a shift, but their entry is still a draft.

At Aventura we start with the exhibiting company's internal register. It has a data owner, each employee's working role, required fields, a verification status and a replacement history. Only the confirmed version goes to the external portal or access control system. This approach does not replace the rules of a specific exhibition, but it stops them from getting mixed up with the company's internal arrangements.

What counts as a completed exhibitor team registration?

A completed registration means that the employee is included in the approved roster, their mandatory data has been verified, a work role has been assigned, and the status has been passed to the relevant external system. A filled-in form only shows that data has been entered. It does not yet confirm admission, badge printing or access to the stand's working tools.

It is convenient to distinguish four states:

1. Draft. The employee has been added, but the mandatory fields or role have not yet been verified.
2. Confirmed by the company. The registry owner has checked the data and included the person in the working roster.
3. Submitted for admission. The confirmed record has been sent to the organiser, the venue or the registration system.
4. Admission confirmed. The external system has accepted the record or returned a status that allows the employee to obtain a pass under the rules of the specific event.

Cvent separately describes the exhibitor portal, stand staff registration, tasks and profiles. OnArrival links the entry process with participant lookup, on-site registration, badge printing and attendance tracking. These functions show a useful boundary: team management begins inside the company, while physical entry is confirmed by a separate process.

For the general entry logic, you can use our guide to event participant registration. Here the focus is narrower: the staff of a specific stand, their functions and the transfer of status.

Data owner and single registry

A single data owner is responsible for the final version of the list, the completion rules and any transfer to external parties. They do not have to collect every form themselves. Their job is to set the fields, assign deadlines for internal checks, approve changes and stop records with incomplete data from being sent. After an edit, it is they who tell the team the number of the current version.

Most often this function is taken on by the participation coordinator from marketing or the event team. HR confirms the employment data, the stand manager determines the composition and roles, the security service checks its own requirements, and the administrator of the external portal uploads the records. The decision on which version is considered final stays with one owner.

If there are many participants, it is useful to separate form collection from approval. An employee or department head fills in the record, the data owner checks it, the stand manager confirms participation, and the administrator transfers the data. An event responsibility matrix is suitable for allocating decisions.

What roles does a stand team need?

A role shows why an employee is at the stand, which shift they work and what work permissions they need. Physical accreditation does not answer these questions. A person may have a badge but not work with a contact scanner, not change the exhibitor profile and not present the technical part of the product.

The minimum set of roles depends on the purpose of participation. We use functional names rather than job titles from the staffing table:

Cvent Exhibitor Management allows administrators to manage the portal, tasks, profiles and employee calendar. LeadCapture supports scanning and qualifying contacts. This does not mean that every stand employee should receive all functions. The company first assigns a role, then grants only the necessary permissions.

We link roles, registration and the work scenario in organising exhibitions and stands. This helps keep the list of people connected to the programme of meetings, demonstrations and shifts.

Required fields without unnecessary data

The form should collect the data needed for identification, contact, role and transfer for access approval. Fields collected "just in case" increase the volume of personal data and the number of errors. Article 5 of Federal Law No. 152-FZ requires that data be consistent with the purpose of processing, not excessive, accurate and up to date.

Divide the fields into three groups:

The specific set of identification fields is set by the organiser or the venue. Within the company, do not copy passport data, home address, personal phone number or other details into a shared file if they are not needed for the stated purpose. If the external party requires a sensitive field, transfer it through an approved secure channel and do not duplicate it in the working shift spreadsheet.

For each field, record four properties:

1. Purpose: why the field is needed.
2. Source: who confirms the value.
3. Recipient: who the field is transferred to.
4. Term: when the record is updated, archived or deleted.

Such a field passport helps to spot anything unnecessary before the form goes live. It also makes corrections easier: the data owner knows where the primary source is and which systems have received the old value.

How do you gather employees and check completeness?

Gathering happens by role and shift, not with a single email saying "send us a list." Department heads first confirm the required functions, then name the primary employees and the reserve. The data owner checks the mandatory fields and only then changes the record status. This order reveals unfilled functions before any names are shared externally.

The workflow looks like this:

1. The stand manager approves the functions and the number of people per shift without personal data.
2. Department heads propose primary employees and a reserve for each function.
3. Employees fill in only the approved fields.
4. HR or another designated source verifies the official data if the company's process requires it.
5. The stand manager confirms the role and shift.
6. The data owner checks completeness and records the version of the register.
7. The administrator passes the confirmed records to the external environment.
8. Returns and corrections go into the same register, not into a separate email thread.

Completeness checking does more than answer the question "are all the cells filled in?" It compares the roster against the stand plan. If three consultants are assigned to the second shift but there is no shift manager or technical specialist, the register is formally complete, yet the team is not ready to work.

Two cross-checks are needed: by people and by functions. The first looks for empty fields, duplicates and unconfirmed records. The second shows unfilled roles, shifts without a reserve, and employees with conflicting tasks.

Substitutions, cancellations and reserve staffing

A substitution should update a single record and all related statuses. A new employee is not added alongside the old one without a link. The register records whom they replace, which function they take over, what data has already been transferred, and whether the old access pass needs to be revoked. The shift supervisor sees the substitution only after its internal confirmation.

The change card contains:

• the ID of the main record;
• the type of change: substitution, cancellation, role or shift change;
• the previous and new value;
• the initiator;
• confirmation by the stand supervisor;
• the status of transfer to the external system;
• the result of the external check.

It is better to assign reserves by function. The wording "there are two people for cover" is of little help if one can give a demonstration and the other is only responsible for meetings. In the register, specify which role the reserve employee can take on and which shift they are available for.

The old record cannot simply be deleted before the change is confirmed. Otherwise the history is lost: who was registered, what had been transferred, and which access pass needs to be revoked. Once the process is complete, the work history is stored according to company rules and the stated purpose of data processing.

How to transfer status to the access control system?

Only an approved selection is transferred to the external system, not the entire internal register. It retains the fields needed by the organiser or venue, the record ID and the current status. The shift, reserve function and internal comments remain inside unless the external process requests them. This way internal working information does not proliferate across external systems.

The transfer follows clear steps:

1. The data owner completes the internal version check.
2. The administrator generates the selection using the agreed template.
3. The number of records and IDs are reconciled with the register.
4. The data is uploaded or transferred via the standard channel.
5. The import result, returns or statuses are written back.
6. Errors are corrected in the primary register, then the record is transferred again.
7. The final status is visible to the stand supervisor and the access coordinator.

Cvent OnArrival allows searching for a participant by name, email, company and confirmation, and also supports check-in and badge printing. This is an example of why identification fields must be agreed in advance. Different spellings of a name or an outdated email can split one record into two versions.

If participation includes a business programme, meetings and separate guest streams, stand team registration should be coordinated with the overall organisation of the business event. At the same time, exhibitor employees remain a separate category with their own roles and data owner.

Status Matrix Before Opening

Statuses must trigger a clear action. The phrase "in progress" does not show who is working on the record or whether the employee can be scheduled for a shift. We use a short set of states with an owner for the next step. The stand manager needs an unambiguous answer: the person is ready, awaiting correction, or removed from participation.

A status applies to a specific version of the record. If the surname, email or role changes after confirmation, the data owner creates a new version and returns it for review. The old green status is not carried over automatically.

Work rights also have their own separate track. Access to the exhibitor portal, calendars, materials or contact collection is confirmed separately from the badge. This way the stand manager sees two readiness states: the person can log in, and the person can perform the assigned function.

What to check in the final reconciliation

The reconciliation compares the final roster, shifts, roles and external status. It is carried out against the latest version of the register, not against emails and local copies. Every discrepancy gets an owner and a decision: fix, replace, remove from the shift, or keep with an explicitly recorded limitation.

Go through the list in order:

1. Every function at the stand has a primary staff member.
2. Critical functions have a suitable backup assigned.
3. Every staff member has a role and a shift specified.
4. Required fields are filled in from a confirmed source.
5. Duplicates by email, phone or ID have been resolved.
6. Cancelled staff members are excluded from the final roster.
7. All active records have been transferred to the external system.
8. Returns have been corrected and the resubmission has been recorded.
9. Admission has been confirmed in the wording of the specific organiser or venue.
10. Work access rights match the role and are not left with cancelled staff members.
11. Shift supervisors have received only the operational version of the list they need.
12. The emergency replacement procedure is known to the data owner and the stand manager.

Related questions about structures, packaging and reassembly are covered in the article on the reusable exhibition stand. They should not be added to the team register: the installation plan and staff data serve different purposes.

Exhibitor responsibility boundaries

The exhibitor company is responsible for its own team, the accuracy of the data it submits, internal roles, replacements and timely responses to returns. The organiser or venue sets its own admission format and confirms external status. These areas must connect through a single version of the data, but must not substitute for one another.

We do not carry the rules of one exhibition over to another. The set of fields, deadlines and badge issuance procedures vary. What stays stable is the internal framework: a single registry owner, roles defined before names are collected, a minimum data set, a change history, and transfer of only the confirmed version.

Sources

• Cvent: Exhibitor Management
• Cvent Support: Using the Exhibitor Portal
• Cvent: Onsite Solutions
• Cvent: OnArrival Event Check-in Software
• Cvent: LeadCapture
• ConsultantPlus: principles of personal data processing in Federal Law No. 152-FZ