Module 8 of 13 · Platform Walkthrough

Manage Attendee Priorities

After delegates pick partners (Module 5) and sponsors pick delegates (Module 6), the platform aggregates every selection into a single Attendee Priorities view — and lets the administrator override it. This is the human-in-the-loop step before matchmaking runs: re-rank a priority, manually add a pairing, spot one-sided picks that may not be worth scheduling.

Audience: Event Administrators Surface: Attendee Priorities (event sidebar) Prerequisite: Both delegate and sponsor selections submitted

1. Why Administrators Override Priorities 00:00 – 00:21

The matchmaking engine is good — but the organizer always knows things the engine doesn't.

Narrator · 00:00 – 00:21 In this session we look at how we manage attendee priorities and what we can do in that area. After the selections are finished, as an administrator, you can go into this Attendee Priorities section on the left-hand menu.

This module is the administrator's last chance to shape the matching outcome before the engine actually runs. Delegates have submitted who they want to meet (Module 5), sponsors have submitted who they want to meet (Module 6). Now the operations team can:

Re-rank a priority a delegate or sponsor submitted (move from 2 → 1 if it really matters).
Add a priority that nobody picked but you know should happen (e.g., a strategic intro the organizer is brokering).
Spot conflicts and one-sided picks that probably shouldn't be scheduled at all.

2. Getting There — The Attendee Priorities Page 00:00 – 00:21

Live with the agenda left rail. Open Attendee Priorities.

Session Agenda calendar with the agenda left rail visible — Event Agenda highlighted, with Master Scheduler, Matching Plan, Attendee Priorities, Company Priorities, Itinerary Setup, No Show Delegates, Push Notifications, Removed Meetings underneath — **Where to find it.** The video opens on the Session Agenda calendar (Module 4). The agenda left rail holds Event Agenda, Master Scheduler, Matching Plan, **Attendee Priorities**, Company Priorities, Itinerary Setup, No Show Delegates, Push Notifications, Removed Meetings. Click *Attendee Priorities* to open the page covered in §3.

3. Anatomy of the Priorities Table 00:21 – 00:39

One row per (selecting attendee → ranked attendee) pairing, grouped by who's doing the selecting.

Narrator · 00:21 – 00:39 From here you can see all of the selections that were given into the system. You can see how many matches there were and the reasons why. For each of these given attendees, you can see their company, their priority, and if they have provided a reason.

Attendee Priorities page with three filter dropdowns at the top, a Set Priority button, then a table grouped by 'Attendee Ranking: [name/table]' sections, each listing ranked attendees with company, priority and reason columns and per-row edit/delete buttons — **Attendee Priorities.** Three filters at the top: *Source attendee type*, *Source attendee*, *Target attendee type* — narrow the table to a specific selecting party or target. *Set Priority* button on the right. Below, a table grouped by *Attendee Ranking: [name / table]* — each group is one selecting attendee or sponsor table, listing the ranked attendees with their company, the assigned priority number, an optional reason, and per-row pencil-edit and delete controls.

Column / control	What it shows / does
Source attendee type	Filter the table to selections coming from a particular attendee type.
Source attendee	Filter to a specific selecting attendee (e.g., one delegate or one sponsor table).
Target attendee type	Filter to a particular kind of recipient (e.g., only delegate-as-target rows).
Set Priority	Open a dialog to manually add a new priority pairing (covered in §5).
Attendee Ranking group header	Identifies the selector and, for sponsors, the specific table (e.g., Amazon Web Services Asia Table A: 1).
Ranked Attendee / Company	The selected counterpart with their company.
Priority	The numeric rank the selector gave them (1 is highest).
Reason	Optional free-text justification (carried over from the client panel).
Edit (pencil) / Delete (×)	Override or remove an individual priority row.

4. Editing an Existing Priority 00:39 – 00:58

Move a Priority 2 to a Priority 1 — or anything else — with one click.

Narrator · 00:39 – 00:58 As an administrator, you have the full power to override any of these selections. If you click the edit button on the right, you can go in and change the priority for a given match. For example, if you want to move a priority from two to one, you can just do it from here.

The pencil icon at the end of each row opens the row for inline editing. The most common change is bumping a priority number, but the same control also lets the administrator re-target the row or update the reason text.

5. Manually Adding a Priority 00:58 – 01:21

Force-create a pairing the engine wouldn't otherwise see.

Narrator · 00:58 – 01:21 You also have a way to manually add a priority. If you think two attendees should meet but they haven't selected each other, you can go in and add that priority for them. Once you do that, the matching algorithm will take it into account when running the final scheduling.

The Set Priority button (top right) opens a dialog where the administrator picks the source attendee, the target attendee, the priority tier, and optionally a reason. Once saved, the new priority becomes part of the input the matching engine reads — so the resulting itinerary will reflect that override even though neither party clicked it themselves on their client panel.

Use case

A common reason to do this: the organizer is brokering a strategic introduction (e.g., a sponsor's CEO wants a particular delegate at the table) that wasn't surfaced through the normal selection flow. Manually adding a Priority 1 makes the engine treat it as if both parties had requested it.

6. Spotting Conflicts & One-Sided Picks 01:21 – 02:00

Use the same view to find pairings that might not be worth scheduling.

Narrator · 01:21 – 01:45 From here you can also see if there are any conflicts. For example, if two attendees have selected each other as a priority one, that's a perfect match. But if one has selected the other as a priority one and the other hasn't selected them at all, you might want to look into that and see if it's still worth scheduling that meeting.

The same Attendee Priorities table is the right place to spot mismatches. Filter by source attendee, then look across to whether the target reciprocally picked the source. The narrator's mental model:

Both sides Priority 1 — perfect mutual match. Schedule it.
One side Priority 1, other side hasn't picked — soft signal. Worth a human judgement call before scheduling.
Both sides Priority 2 or lower — weaker mutual signal. Schedule if there's room; deprioritize if not.

Narrator · 01:45 – 02:00 So this section really gives you that fine-grained control over the matching process to make sure that the meetings being scheduled are the most relevant and valuable for all of the participants involved in the event.

7. Essence & Takeaways

The one-paragraph version

The Attendee Priorities page is the administrator's last touch on the matching input before the engine runs. It surfaces every priority anyone submitted — delegates picking partners (Module 5), sponsors picking delegates (Module 6) — grouped by selector and table, with company, priority tier, and reason on each row. Three filters narrow the view by source attendee type, source attendee, or target attendee type. Per-row controls let the administrator edit a priority (bump from 2 → 1) or delete it; a Set Priority button lets the administrator manually add a pairing the parties didn't pick themselves (e.g., a brokered introduction). The same view is the place to spot conflicts and one-sided picks — perfectly mutual Priority-1 ↔ Priority-1 pairings are guaranteed schedules, while one-sided picks may not be worth running. The result is a hand-curated input set that drives the next step: matchmaking and itinerary generation.

Use this page as the basis for…

An ops runbook for the "between selections deadline and matchmaking run" window.
A reference for whoever onboards new event coordinators on managing the matching pipeline.
A QA checklist before running matchmaking — every brokered intro must be reflected in this table.

8. Full Transcript

Verbatim narration provided alongside the video.

Show / hide transcript

00:00 – 00:21

In this session, we are going to look into how we manage the attendee priorities and what actually we can do into that area. So after the selections are finished, as an administrator, you can go into this Attendee Priorities section on the left-hand menu.

00:21 – 00:39

And from here, you can see all of the selections that were given into the system. You can see how many matches there were and also the reasons why. So for each of these given attendees, you can see their company, their priority, and if they have provided a reason.

00:39 – 00:58

As an administrator, you have the full power to actually override any of these selections. So if you click the edit button on the right, you can actually go in and change the priority for a given match. For example, if you would like to move a priority from two to one, you can just do it from here.

00:58 – 01:21

You also have a way to manually add a priority. So if you think that two attendees should meet but they haven't selected each other, you can actually go in and add that priority for them. And once you do that, the matching algorithm will take that into account when it's running the final scheduling.

01:21 – 01:45

So from here you can also see if there are any conflicts. For example, if two attendees have selected each other as a priority one, that's a perfect match. But if one has selected the other as a priority one and the other hasn't selected them at all, you might want to look into that and see if it's still worth scheduling that meeting.

01:45 – 02:00

So this section really gives you that fine-grained control over the matching process to make sure that the meetings that are being scheduled are the most relevant and valuable for all of the participants involved in the event.