YACHT WEEK HOST

1. Role Summary

As a Host you run the galley and the onboard hospitality on a single yacht and co-shepherd a crew of around 8 to 10 paying guests through the week alongside the skipper. You own the food, the hosting, the meal plan and budget, the kitty handling on your yacht, and the warmth and cleanliness of the interior. You are second in command of the social side of the yacht; the skipper holds command of the yacht.

You are supplied to Yacht Week by Quarterdeck (QD). YW is the customer, QD is the supplier. Conduct, fitness for role, performance management and replacements all sit with QD; the QD Code of Excellence is the governing document for how you behave on duty.

For the week you report to your Lead Host, or to the Host Manager (HM) where no Lead is assigned. Quarterdeck (QD) management handles performance and conduct decisions where the HM escalates. Where a Lead Host is assigned to your route, they sit under the HM as a support layer. Use the Lead Host for cooking and provisioning coaching, advice on difficult guests, and admin, finance and policy questions. They create your group within the QD WhatsApp Community, reach out early in the week, and check in through it to coach and support rather than control. They have no authority over the skipper team or yacht command.

In one sentence: you are responsible for your galley and your share of your crew; the HM supports and coaches the host team; the EM leads the event.

Reporting & Working Relationships

Reports to: the Lead Host operationally for the assigned week. Where no Lead Host is assigned, you report to the Host Manager (HM).
Quarterdeck (QD) management decides on performance, conduct, offboarding, and role-level matters, acting where the HM escalates.
Works alongside: the Skipper on your yacht, your half of the partnership for the week.
Support your skipper: help with lines, sails and deck work when needed, and keep the shared spaces tidy.
Supported by: Lead Host, sitting under the HM.
Liaises with: the wider host team across the route via the Lead Host's group within the QD WhatsApp Community; the Route Medic on any allergy, dietary or medical incident.
Out of scope: yacht command; financial settlements with the charter company; any guest comms once a complaint is in.

2. Role Ownership Across the Team

These pages sit alongside the rest of the 2026 event-team manuals. Use this glossary so you know who owns what when you need to surface something. Hosts and skippers are the people closest to the guests; the rest of the Event Team and the YW central functions are the support and decision layers behind you.

Operational Management for all Routes (land based)

Head of Operations (HOO): heads operations across all destinations and the season; owns partner-venue contracts and cross-destination escalation; final point on vendor, contract and reputational matters.
Operations Coordinator (OC): cross-destination operations; supplies pre-week intelligence and the budget for each EM; operationalises HOO-level contract requirements at route level.

Event Management Team (on the crew yacht)

Event Manager (EM): route lead; manages the Event Team and the event, and owns the budget.
Guest Experience Manager (GEM): owns the guest experience, guest relationships, and complaint handling.
Event Coordinator (EC): the EM's right hand; keeps the YW App schedule, app comms and message updates current, is on-site POC for the Media and DJ teams, and helps wherever needed.
Route Manager (RM): coordinates route operations and supports and coaches the skipper team; supplied by Quarterdeck (QD).
Host Manager (HM): coordinates and supports the host team and supports the onboard guest experience; supplied by Quarterdeck (QD).

Skipper & Host Management Roles

Lead Skipper: route-level skipper-support role assigned to selected skippers; sits under the RM. Advisory and coordination only, no command authority over any other yacht.
Lead Host: route-level host-support role assigned to selected hosts; sits under the HM. Advisory and coordination only, no authority over skipper teams or yacht command.
Route Medic: assigned skipper, host, or event crew member with medical credentials; provides route-level medical response and health-and-safety support.
Lead Tech: route-level technical-support role assigned to selected skippers with strong yacht-systems experience; sits under the RM as a support function. Advisory and coordination only, does not replace charter-company technicians or formal repair channels.

Other Functions

Quarterdeck (QD): Yacht Week's external service provider for the skipper and host crews (including RM, HM, and the Route Medic). YW is the customer; QD supplies the people. Skipper-side and host-side performance, offboarding, and replacement decisions sit with QD. The QD Code of Excellence is the umbrella conduct framework: https://www.quarterdeck.co/code-of-excellence/
YW Customer Service (CS): owns the guest relationship after the week, and during the week from the moment a complaint is in. All post-complaint guest comms route through CS.
YW Commercial Team: owns charter-company contact, and any settlement coordination with Finance and CS.
YW Finance: executes settlements, refunds, and partial credits on Commercial's instruction.

3. Pre-event Preparation

Saturday onboarding rhythm is owned by the Event Team; the destination Event Guide carries the destination specifics. Your job in the days before the week starts is to come in prepared so the Event Team is briefing you on edge cases, not basics.

Before guests arrive, confirm:

Assignment read end-to-end. Per-guest view and guest summary both.
Guest summary review. Cabin type preferences, holiday budget, table-reservation interest, swimming ability, party-mood indicators, dietary and allergy summary.
Top-dish list review. Up to date and limited to dishes you can actually source in this destination's supermarkets.
Provisioning plan, mapped to local supermarkets and the kitty figure.
Day 1 meal plan and budget drafted, ready to share with the group.
Kitty plan. Built off the kitty baseline posted on the guest assignment in the QD Admin.
First-time-in-destination self-flag to the HM at first meeting if these waters are new to you.
Allergy and dietary data live for every guest on your yacht. Anaphylactic guests confirmed by name and severity.
Galley shopping list and supermarket plan; coins or change for the supermarket cart; receipts in mind.

Saturday morning execution. All crew on the marina by midday. Pre-arrange a fixed meeting point with your crew and stick to it; guests should not be wandering the marina looking for you. Underpromise and overdeliver on yacht-ready times: if the charter office says the yacht will be ready at 16:00, tell your crew 17:00. Encourage guests to spend the day exploring rather than waiting at the marina, especially where marina facilities are limited. The destination Event Guide carries the marina-by-marina specifics.

Uniform. One YW shirt, one cap and one wristband, issued at the crew meeting on Saturday. Replacements only on wear-and-tear damage. Lock down kit at end-of-week so it makes it back to QD.

4. On Event

On event the majority of the responsibility to manage and mitigate sits with the host and skipper directly, on the yacht, in real time. The Lead Host, the HM, and the wider Event Team follow up and support; they do not replace your judgement at the supermarket, in the galley, or with a difficult guest. The sections below cover what that looks like across an event week.

4.1 The YW experience and service mindset

Yacht Week is, ultimately, about the people you meet and the friends you make. The yacht, the sea and the sun are the setting; the experience is built by the skippers and hosts on each yacht. What guests come back for is the week itself, and what we bring to the table is delivering it safely, warmly and with care.

Service mindset is anticipating what your crew needs before they ask, reading who is feeling great, who is tired, who is anxious about something they will not say out loud, and acting on what you read. Putting the guest first is the discipline: no matter how good a moment is for you, your enjoyment should never conflict with your crew’s experience.

Your mindset should be the same as the guests’. We are here to explore, to enjoy the sea and the places we go to, and to make friends along the way. This is not an ordinary job; it is the grey zone between work and the best time of your life. The skippers and hosts who get the most out of YW treat each week as part of the adventure, not a shift to get through.

Look after yourself first. If you are not enjoying the week, it usually traces to one of the basics: sleep, rest, time alone, food, hydration. Address whichever is missing before anything else. You cannot deliver the experience or be your best self if you are running on empty, and the cost of pretending otherwise lands on the crew within a day or two.

Before your guests leave, tell them in person how valuable their feedback is to Yacht Week. A warm, genuine mention on Friday or Saturday morning lifts the response rate and helps the whole team, so keep it friendly and never pushy.

4.2 Galley, hospitality, guest care

Your goal is to make the guests feel comfortable and at ease around you, and to give them food they want to eat. Taste, presentation, timing, food handling and customer service all matter; so does your own pacing across a long week. A clean, organised galley is the foundation. A spotless galley signals to guests that you are organised and in control, and stops you getting overwhelmed when the day gets busy.

Cleanliness, hygiene and food safety are non-negotiable. Wash hands often, keep hair tied back, change cutting boards between raw meat and produce, refrigerate promptly, follow safe internal cooking temperatures. “When in doubt, throw it out” is the rule.

You are solely responsible for what you provision, cook and serve, including every allergen and food-safety call on your yacht. A Lead Host or the HM can coach and advise, but their input is support only: it never takes over your judgement and never shifts that responsibility to them, to QD or to the Company.

Personal pacing matters. The first weeks are the hardest. Burnout is real and shows up in the food first. Sleep, rest and the occasional quiet hour are part of doing the job well, not a luxury.

The week belongs to the guests. They choose where to eat, when to swim, and which activities to opt into. Surface what is available, advise on trade-offs, and let them decide. Guests should never feel pressured to do or buy anything, and they are always free to opt in or out at any point.

4.3 Brand voice and conduct with guests

Yacht Week brand voice is warm, confident, energetic, never defensive. Hold it under pressure. Never disparage the product, the yacht, the destination or the team to a guest. Negative commentary about the team, budget, scheduling or any other internal matter lands on a paying guest as a brand failure. Where something is genuinely unfit for what was sold, surface it through signal flow, not through commentary to the guest.

Flag early rather than handling it quietly onboard. If you try to absorb a difficult dynamic instead of flagging it, the Event Team has no chance to help before it escalates. Raise a concern as soon as you can, even when it feels manageable and even when you believe you have it under control: flagging it early, while it is still a small “yellow” signal, is how the Event Team can act before it becomes a real “red” problem. For example, a Day 1 supermarket confrontation between a host and a guest is worth flagging the same day, even when it ends in your favour.

Once a guest complaint is in, all guest contact stops (including WhatsApp, in person, and social channels) and Customer Service takes over; refer the guest back to CS if they reach out. See 5.2.

Sexual misconduct in any form, guest-on-crew, crew-on-guest, crew-on-crew or guest-on-guest, sits at zero tolerance. The full Quarterdeck Sexual Misconduct Policy, the expected community behaviours, the consent framework and the disclosure-response standard are set out at: https://www.quarterdeck.co/sexual-misconduct-policy/. If you witness or experience misconduct, raise it the same operational day via the Event Team chain. Trained First Responders are designated each event to receive disclosures, and confidentiality is maintained as far as possible. Retaliation against anyone reporting or reported is not tolerated.

4.4 Guest communication channels

The YW App is the first point of contact with guests. Treat it as the primary channel for everything except real-time logistics inside a single day. Guests get push notifications, route info, schedule, the in-app feedback channel and your top-dish list through the App. If guests initiate WhatsApp with you, move into WhatsApp for that thread, but do not move the whole crew off the App by default.

On cabin and solo bookings the App matters more, not less, because it is the one place the individual guests on the yacht meet each other before the week starts. When you are running a cabin or solo yacht, your top-dish list and the in-app conversation are how the group decides what they want to eat together.

4.5 Reading the guest assignment in the admin system

Your assignment in the admin system holds what you need to prepare, and exactly what appears may change over time. Broadly it covers the work-assignment details (yacht, dates, start and end marina, charter company, who you are working with, and guest count); the crew and their check-in status; a per-guest breakdown, where you click a name to see what that guest has shared (for example allergies, dietary needs and food selections, swimming ability, activity interests, music preferences, special occasions, and any medical or health-consent flags); and a Check-in Data Summary that totals those responses across the whole crew, for example how many guests share a given allergy or picked a given dish. Read it all before guests arrive: the summary gives you the shape of the yacht, the per-guest view tells you who needs what.

Guests will mark which of your top dishes they prefer. The standardised top-dishes list you keep on your profile is the indicator of what the group wants to eat. Always keep your top dishes up to date, and only list food you can actually source in the local supermarkets where you are assigned. Listing dishes you cannot reliably make in the destination is one of the cleanest paths to a Day 1 complaint.

Allergy and severe-allergy data is live data, not a one-off read. Re-read it on Day 1 with guests on board; double-check anything that could touch a high-severity flag. Anaphylaxis is the highest-severity risk we carry, and a missed allergy on Day 1 can become a life-threatening event by mid-week.

4.6 Daily rhythm with the Event Team

Run a short daily check-in with your Lead Host, or with the HM where no Lead is assigned. The bar is to flag yellow even when it does not feel red yet: a difficult guest dynamic at the table, a host wellbeing concern, a galley or yacht condition issue, a logistics bump from arrival day. Yellow flags are how the Event Team gets a chance to support before things go red.

Do not wait for the daily check if something material happens. Surface to the HM as soon as you can. The Event Team flow is: host or skipper into the Lead, or directly to the HM or RM, then to the EM, then to the Operations Coordinator (OC). The OC may involve the Head of Operations (HOO) on Critical-severity items. Vendor or guest confrontations follow the same chain: surface, do not absorb. Hosts are not the dispute interface with vendors; the HM and EM resolve on the route.

4.7 Working with the skipper

Together with the skipper you co-shepherd a yacht of around 8 to 10 guests through the week. There is no rigid division of tasks. Guests do not care who gets the job done; they expect an exceptional experience. That means at times the skipper needs a hand washing dishes, taking out the trash, picking up items at the market or with food prep, and you may need a hand throwing a line, raising sails or cleaning the deck. Communicate and coordinate so meal times and provisioning track the itinerary, and reservations and activities can be booked at the right times.

Treat the skipper as a teammate. Back them up in front of guests, and sort any disagreement in private. Look out for each other: regardless of role, gender, or age, anyone who would rather not be alone late at night, in an unfamiliar or remote place, or around unfamiliar guests, should be accompanied; offer that, and ask for it yourself if you would prefer not to be alone. The skipper is responsible for the safe operating condition of the yacht 24/7; you are not directly responsible for the yacht but treat it with care and take responsibility for any damage caused by carelessness, just like the guests.

4.8 Provisioning, kitty, and budget

The Day 1 meal plan and budget shared with the group is yours. Share it before provisioning, ideally in the App. The skipper supports, especially on cabin and solo bookings where you may not be onboard. The Day 1 meal plan and budget heads off the most common provisioning friction: group disagreement at the supermarket, a host who feels unbacked, guests who feel they are paying for something they did not agree to.

The kitty baseline for the week is posted on the guest assignment in the QD Admin; that figure is what the guests saw when they booked. Increasing the kitty “to be on the safe side” is one of the biggest sources of complaints we see; it does not buy comfort, it buys distrust. The discipline is to land within the baseline figure, and if it really is not enough, ask for more in-week and explain why afterwards. Transparency is the over-delivery.

Run the kitty closeout in front of the group at the end of the week: opening balance, expenses with receipts, closing balance, any distribution. The host or skipper runs the closeout; the Lead Host or Lead Skipper verifies via the WhatsApp group, a direct message, or a check-in. Report all receipts on the final day. A kitty that closes without a visible reconciliation is a pattern we now treat as a route-team issue, not a personality issue.

Receipts. Every expenditure made from the kitty or company card needs an itemised VAT receipt. Take a photo as soon as you receive it and upload it to the company expense app the same day. Card slips on their own are not acceptable. Without receipts the company cannot comply with tax and accounting law and you may be personally liable for missing amounts.

4.9 What's included in a Yacht Week booking

Knowing what is in the YW package keeps you from accidentally selling guests on paid add-ons that are already covered. The YW booking covers the yacht charter, your skipper or host services, the route programme and the events along it, the Event Team support, the YW App and route comms, and the standard kit on every yacht. What the kit includes, and any pre-paid extras such as mooring fees or partner-venue dinners shown on the guest profile, vary by destination and change over time, so check the destination Event Guide for the current per-destination list.

Selling or recommending services and products outside the YW offer

Recurring complaints in this area come from skippers or hosts recommending paid add-ons in good faith. Once lawyers and insurance are involved, everything looks different. Think downstream before suggesting anything that sits outside what YW already provides.

Speaker rental. Do not promote or sell speaker-rental services from third-party companies that lack proper registration or insurance. If something goes wrong (battery, fire, injury) you may carry personal legal exposure. YW cannot recommend or be connected to companies that do not comply with local regulations.
Alcohol purchases. Same legal-exposure logic. Do not get involved in advising on or arranging supply that could be illegal sales or distribution.
Activity recommendations. Be cautious about activity providers where insurance status is unclear. In legal claims, the company's insurance will look for whoever stepped outside the Code of Conduct.
Cooler boxes and included kit. Offer what the destination includes rather than reselling third-party hire; the destination Event Guide lists the current per-yacht kit.

Tipping

Tipping is a gesture of appreciation, not an expectation, and entirely at the guest’s discretion. No asking, no hinting, no pressure, in conversation, in jokes, or in any other way. Respect that tipping varies by culture, and stay just as professional whether or not a guest tips. If a guest does tip, accept it with appreciation, never expectation. The full Tipping Policy is in the Code of Excellence: https://www.quarterdeck.co/code-of-excellence/

4.10 Yacht handover at start and end of charter

The skipper leads the yacht handover at the start and end of charter. You support on the linen and consumables side: counts, condition, and what was used or lost, and co-sign the handover record with the skipper so heads, linen, sound, dinghy fuel and ice are covered, not just engine and hull.

Friday: checkout starts in earnest on the Friday, not Saturday morning. Prompt guests to start packing on Friday afternoon and to throw out leftover food they no longer want.
Saturday morning: strip beds, leave linen and towels in the saloon, empty cupboards, and bag and sort waste (transparent garbage bags where required). Half-used food binned; unopened food can be left as a gratuity for the cleaners.
Galley: left clean, ovens, stoves and fridges wiped down, dishes done and put away.
Integrity: lack of integrity at end-of-charter on damage or inventory is treated seriously by QD and YW.
Sign-off: stay close to the skipper through final inspection.

If you damage guest property, intentionally or by accident, tell the guest the same day. Same-day report to the HM via the Lead. Late or quiet handling on damage to guest property is one of the patterns that turns a recoverable situation into a complaint and an insurance issue.

The week runs Saturday to Saturday. Your assignment begins when your guests arrive on the Saturday, typically around lunchtime but varying with their travel; adapt to when they turn up and to their reasonable requests.

On Friday night, stay in service. You are hired for the full week, so keep looking after your guests through Friday and help them off the yacht on Saturday morning. Guests should never be left alone on the yacht overnight: where a yacht has both a skipper and a host, at most one of you may leave on the Friday night (for example a transfer between countries or a personal flight), and only if the other stays with the guests. If all your guests leave the yacht themselves, you may leave too. Do not initiate leaving yourself, and leave earlier only if the guests ask you to; any complaint about it reflects badly on you.

Friday is a full day at sea, not a rush back to the marina; support the plan to stay out and return in good time for check-out, so guests get the most from their last day. Guests are encouraged to stay onboard on the Friday night. Anyone who wants a lie-in on the Saturday morning can be advised to book a hotel room for the Friday night and move their luggage off the yacht then, so they can enjoy their Saturday without holding up the clear-out.

On Saturday morning the yacht must be cleared out on time, with 9am the safe general target though it can vary by destination (check the Event Guide). Making sure your guests clear out on time is a shared responsibility with the skipper. Late departures hold up the marina and delay the maintenance and cleaning teams. If you are not sleeping onboard on the Friday night, appoint someone to make sure the yacht is cleared out on time in your place; the responsibility for guests complying still sits with you.

4.11 Damage, incident, safety

Safety first, always. Report any accident, near-miss or incident the same day, to the skipper and through the QD report form, not at end of week (see Section 5). Allergy near-misses are same-day reports without exception.

Personal safety, for everyone regardless of role, gender, or age: as a standing norm, no team member is left alone with venue staff late at night, and anyone heading back late does so with a companion.

Vendor confrontation does not land on you. Surface to the HM and EM; they resolve on the route.

Yacht security alongside the skipper: yacht locked when unattended, hatches closed against rain downpours, dinghy back on board every night. Waters at most destinations are safe but yacht-security discipline is the bar regardless.

Brief guests on the conditions of the destination at the start of the week: sun and UV exposure (multi-method protection where the sun is strong), seasickness on longer crossings (advise guests to come prepared with patches, wristbands or other prevention), and treatment of grazes and coral cuts (treat immediately and surface to the Route Medic; warm water and iodine is the standing first response).

4.12 First-time-in-destination

If you have not hosted in those waters before, self-flag at the first meeting with your Lead Host, or with the HM where no Lead is assigned. First-time-in-destination is a separate flag from first-week-of-season; it captures experienced hosts who are new to a particular destination. The Event Guide for your destination (see 4.14) is the starting point for local knowledge, including supermarkets, produce sources and partner venues, in the days before you fly in. The Lead Host and HM pay extra attention through the week and provide support on anything you have not encountered before. Self-flagging is the lighter, quicker option than the Event Team learning during the week.

4.13 QD Community on WhatsApp

The QD Community is the umbrella for the many WhatsApp groups that get spun up across a season. Only join the groups where you are assigned. Privacy works the same as any WhatsApp group you create yourself: admins cannot see or access content in groups created within the QD Community, not even retroactively, and admins cannot join groups they are not members of. The Community exists as one place to find the jungle of groups created during a season, not as a surveillance layer over them.

For privacy and GDPR reasons the company manages these groups and deletes them after each event. They are official, professional channels for event comms only, and are not to be used for anything that conflicts with Quarterdeck or Yacht Week. Quarterdeck’s core business is training and supplying crew to companies and individuals who need them; if you ever need crew yourself, QD can help.

4.14 Event Guide for your destination

The Event Guide is the operational reference for your route. It carries the destination-specific detail that this manual deliberately does not: local supermarkets and where to source produce, partner venues and any history with each, transfer logistics, charter office contacts, route layout and weather notes, and common local situations and how the Event Team has handled them before. The Event Guide is owned by the Operations team and is the single source for anything route-specific. Start there in the days before you fly in, and surface any gap or out-of-date item to the HM via the Lead Host so OC can keep the guide current.

4.15 Partner reservations and dinners

Partner-venue dinners and activities run on advance reservations. The booking channel varies by item and by destination. Some dinners are pre-paid through the guest’s YW booking account; other dinners are reserved directly with the venue (mention “Yacht Week” when booking). For activities not listed on the guest profile, YW may set up a registration channel for the destination, typically a Google Form or Eventbrite. Share what is available with your guests early in the week and let them decide. The destination Event Guide lists which channel applies for each dinner and activity, the deadlines, and the venue contacts.

5. Complaint and Incident Handling

Every guest complaint and operational incident on your yacht follows the same flow: Listen, Acknowledge, Assess severity, Route, Act, Close, Log. Severity decides authority; authority decides who acts and who escalates. You are the role with the relationship for guests on your yacht; you hold the guest POC through resolution unless and until a complaint is in, at which point CS holds the guest relationship.

Yacht issues and accidents are reported through the QD report form (https://www.quarterdeck.co/report-form/), choosing “yacht issue” or “accident”, as soon as they happen. The form goes automatically to the YW Commercial Team, the HOO, and QD Management, so each report is actioned and logged, which also builds a record if the same yacht has the issue again.

5.1 Escalation chain

Host to Lead Host or directly to HM, then to EM, then to OC, then to HOO. Get it onto that chain the same operational day on serious items; the Event Team and OC handle the formal documentation from there. When in doubt, escalate one level higher.

Low: schedule confusion, dietary tweak, lost item, minor venue gripe. Resolve onboard. Log at end of day.
Medium: repeat complaint, partner-venue conflict, missed transfer, group dissatisfaction with one event, minor conduct flag, Day 1 supermarket confrontation. Surface to the HM same day.
High: safety incident, medical issue, allergy near-miss, refund request, conduct incident, social-media-bound complaint, repeated host-skipper failure on the yacht. Stop. Notify HM immediately.
Critical: injury, missing person, criminal incident, yacht emergency, anaphylaxis, regulatory issue. Safety protocols first. The HOO owns the response, supported by OC, EM, Route Medic and the Event Team. Capture facts and times for the Event Team and OC.

5.2 Post-event guest communications

Once the week is over, or once a guest complaint is in during the week, Customer Service holds the guest relationship and owns all guest-facing communication. The Event Team, YW Operations & Management and QD Management feed input through CS and act on guest comms only at CS’s request. If a guest reaches out directly after the week, or after a complaint is in, the response is to refer them back to CS rather than reply. Skipper, Host and Event Team contact with the guest stops the moment a complaint is in, including via WhatsApp or social channels. The matter is escalated to the Route Manager, the Host Manager and the Event Manager.

6. Reporting Lines and Accountability

The Lead Host, where assigned, sits under the HM as a support layer and does not carry authority over the skipper team or yacht command.

The HM and the Lead Host do not rate you. They give you feedback when there is something to address, in person and early, with documented examples that go to QD via the EM. Anything that touches conduct, safety or repeat issues is reported to QD by that route. The QD Code of Excellence is the governing standard for conduct and is available on the QD admin: https://www.quarterdeck.co/code-of-excellence/

Guest ratings matter, but they do not override the day-to-day priorities of safety and conduct. Management reads poor ratings and assesses whether they are valid; removal of a rating happens rarely and only in very clear cases. Recurring issues are tracked over time so patterns can be reviewed.

A high average rating does not on its own increase your likelihood of further assignments. A high rating combined with poor feedback from teammates or management is directly negative. Quality delivered together, by the whole Event Team and by the skipper-host pair on each yacht, is the bar.

A high rating where guests later mention they were prompted or asked to leave a high rating is significantly more damaging than a low rating. We are a close team and know over time who plays well with others and consistently delivers happy and safe guests.

Where instructed by QD management, the Event Team supports formal actions including removal from duty, reassignment, or offboarding. Cover and redistribution decisions for mid-week dropouts sit with QD via the standby pool, not with the HM.