In-depth IYS permission management

If commercial communication consent is obtained in the registration form but forgotten during dispatch, the compliance chain breaks. IYS consent management maintains the same chain from registration to dispatch.

If every dispatch isn't secure, campaign speed creates risk.

Breaking Points

• Consent in the form, not in the dispatch
• Channel-based consent confusion
• Opt-out/withdrawal delay
• Lack of evidence in audit

Chain Steps

1. Collection: Explicit consent in the form.
2. Registration: Reflection to IYS.
3. Control: Pre-submission query.
4. Update: Rejection processing.
5. Trace: Log and proof.

Frequently asked questions

Is it the same as KVKK?

Different layers; managed together.

Transactional?

Purpose distinction must be clear.

SMS/email?

Channel-based permission.

Error?

Stop submission, correct.

Module?

Marketing automation.

Make permission the gateway to submission

IYS is the backbone, not an afterthought checkbox.

Explore QEMENT features or contact us.

The most common mistake teams make in IYS permission management is setting up the tool but failing to document the process. If questions like who enters the data, who approves it, who makes it available to visitors, and who manages exceptions on the fair day are not clear, the operation will remain disorganized even if the system is populated. Therefore, a one-page responsibility matrix should be updated at the beginning of each season.

IYS permission management cannot be improved without measurement. Take a baseline before the season; monitor with the same definitions during the season; and write three concrete actions at the end of the season. Instead of saying 'It got better,' talk about rates, durations, and volumes. The next team should be able to read the same numbers.

Changes on the exhibition day are inevitable. What's critical is which record the change is applied to and who is informed. Verbal updates alone are not enough; if the relevant profile, map, notification, or request record is not updated simultaneously, the field and office will become disconnected.

Use consistent language in exhibitor and visitor communication. Explaining the same rule differently on the portal and in emails increases the support load. Short help texts, screenshot guides, and a deadline calendar should work together.

Even on an integrated platform, Excel backups don't completely disappear; the problem is when the backup is declared the 'primary source'. Keep the official source in one place, use exports for reporting purposes. Otherwise, the debate over which file is correct will reopen in two days.

As your international exhibitor and visitor rates increase, language, time zone, and permission rules become part of the same process. Leaving translations until the last day weakens the registration and discovery funnel. Set a target of at least two languages for critical areas at the beginning of the season.

Checklist

• Process owner and backup owner are documented.
• Mandatory fields and publishing rules are clear.
• Pre-fair rehearsal or sample registration test has been conducted.
• Exhibition day exception channel (who, what time) is defined.
• End-of-season metrics and action list are stored.
• Roadmap features are not confused with live promises.

This checklist should not be reinvented for every event. It is embedded in a folder or season template; a new team member sees the same list in their first week. Maturity emerges in repeatability, more than in the number of tools.

Small touches that reduce the support burden

Half of the questions received by the info desk and call center are actually “where do I find / how do I do it” questions. A help page, in-portal tips, and timely short SMS/e-mails cut this burden. The same content base feeds assistants or AI features when they arrive; an assistant built on an empty knowledge base generates frustration.

Finally: you don't have to activate every new feature at once. First, fix the three workflows that generate the most tickets, measure, then move on to the next package. Disciplined simplicity in fair operations yields faster results than a pile of features.

In the seasonal review, records related to IYS permission management are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed into rule and template improvements, not personal criticism. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to IYS permission management are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed into rule and template improvements, not personal criticism. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to IYS permission management are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed into rule and template improvements, not personal criticism. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to IYS permission management are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed into rule and template improvements, not personal criticism. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to IYS permission management are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed into rule and template improvements, not personal criticism. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to IYS permission management are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed into rule and template improvements, not personal criticism. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to IYS permission management are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed into rule and template improvements, not personal criticism. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.

In the seasonal review, records related to IYS permission management are sampled and checked. In twenty randomly selected records, field integrity, publication status, and stakeholder visibility are examined. Found errors are transformed into rule and template improvements, not personal criticism. This sampling habit catches quality issues lost in large lists early and reduces hidden debt carried over to the next event. Sampling notes are stored in the folder; comparisons can be made when the same check is repeated a year later.