EYT Experiences · Operator resources
Manage Guest Applications and Approval

A Guest application is a request for review; approval is an authorized Company decision.
- Receive application
- Add recommendation
- Company review
- Communicate outcome
The operating decision
A Guest application is a request for review; approval is an authorized Company decision.
A workable process
Choose whether the Party is invite-only or accepts applications. State the process before asking for information.
Collect only information needed for the decision. Separate a Creator recommendation from the Company approval state.
Communicate the next action clearly after review. Explain what remains subject to provider confirmation and avoid exposing internal review notes to Guests.
Illustrative scenario, not an EYT case study
A hypothetical Host recommends a Guest for an applications-open evening. The Company reviews the application under its own criteria; the recommendation does not reserve a place or bypass capacity limits.
Make the pending state understandable
Applicants need to know whether they should wait, supply information or contact an organizer. Do not leave a submission receipt looking like approval. Tell the team who owns the review queue and how stale applications are resolved before the Party. When capacity or the experience changes, review pending applications against the updated scope rather than leaving contradictory expectations in place.
Limit recommendations to context
A Creator recommendation can explain why someone may fit an experience, but it should not expose unrelated personal information or imply that the Creator controls admission. Keep internal assessment separate from the Guest message. Record the authorized reviewer and outcome so that a later Host can distinguish a declined application, an unanswered invitation and an approved participant without reading private deliberations.
Choose the information the decision needs
An application form should ask for information that supports the stated review, not every detail the team might someday find interesting. Explain required fields and keep sensitive context away from roles that do not need it. A Company may need to distinguish the booking contact from attending Guests, but that does not justify exposing all applicant details to every Host. Confirm the supported visibility and review capabilities in the controlled Partner workflow before relying on them operationally.
Make review ownership visible
Define who reviews new applications, who can request clarification and who may approve or decline. Agree what happens when the reviewer is unavailable close to the Party. A Creator can recommend a Guest or provide relevant context without becoming the final decision maker. Keep a recommendation state separate from an approved state. When the application process changes, review pending submissions rather than assuming the old and new criteria produce equivalent outcomes. Communicate the Guest’s next step clearly after the authorized decision.
Test application and invitation paths separately
Invite-only and applications-open Parties can create different expectations. Check what an invited Guest sees, what a new applicant sees and what a person with a forwarded link can do. Test incomplete submissions, duplicate identities and responses after the review deadline. The receipt message should not imply a reservation or guaranteed admission. If the provider must still confirm capacity or service conditions, keep that boundary visible. Review the process from the Guest’s perspective as well as from the administrative queue.
Review the closing message
After review, the Guest should know whether they are approved, declined, waiting for a decision or being asked for information. Do not use one generic confirmation message for all four states. Keep internal review reasoning restricted to appropriate roles and share the practical next step. If the experience changes after approval, the Company should assess the consequences under its process and provider terms. An approval record is not a guarantee that capacity, venue requirements or every requested service can never change. Keep those boundaries visible without overwhelming the applicant with internal operations.
Operating framework
| Decision or measure | Definition / action | Interpretation boundary |
|---|---|---|
| Application | Request submitted | Not a reservation |
| Recommendation | Creator context | Not Company approval |
| Approval | Authorized review outcome | Still subject to relevant terms |
Questions operators ask
Does this require replacing our existing systems?
No. Start with clear ownership and consistent states. EYT can sit alongside booking, CRM and payment systems; no automatic technical integration is implied.
Who controls Guest information and commercial decisions?
The responsible Company sets permitted access and retains commercial authority. Give Hosts and Guests the information relevant to their role; a shared Party is not unrestricted access to Company records.
Is a Creator recommendation the same as approval?
No. A recommendation supplies context; the authorized Company reviewer makes the approval decision under the applicable process.