Module 9 of 13 · Platform Walkthrough

Event Scheduling Automation

The matching engine — what runs once delegate priorities (Module 5), sponsor priorities (Module 6) and admin overrides (Module 8) are all in. This module covers the Setup Matching Plan UI (drag-and-drop ordering of session types, per-type settings, attendee-type weighting), running and re-running the plan, the statistics the run produces, the run history with rollback, and the per-attendee Matching Review where administrators can delete or manually add individual meetings.

Audience: Event Administrators, Operations Surface: Matching Plan (event sidebar) Prerequisite: Delegate & sponsor selections submitted (Modules 5–6) and reviewed (Module 8)

1. From Selections to Schedule 00:00 – 00:54

Every selection in the system feeds the matching engine. The engine produces a meeting calendar.

Narrator · 00:00 – 00:26 In this portion we review the automated matching and scheduling engine and how it looks from an administrator point of view. As soon as everyone has provided their preferences — delegates and sponsors — you have a full overview of what the priorities are. For example, you can choose a sponsor or partner and then you see their selections.
Narrator · 00:26 – 00:54 For each, you see their priority — they have assigned priority 1, priority 2, or priority 3. Once you have all this gathered, you move to the matching plan. The matching plan is where you actually define the logic of how the system is about to schedule these meetings. You define what sections or meeting types you want to have scheduled.
1
Selections collected
Delegates pick partners (Module 5); sponsors pick delegates (Module 6).
2
Admin reviews / overrides
Attendee Priorities (Module 8) — bump, delete, or manually add priorities.
3
Matching plan defined
Order of session types + per-type rules, set in this module.
4
Plan runs → schedule
Engine produces a complete itinerary; admin reviews, edits, applies.

2. Setup Matching Plan — Drag & Drop Order 00:54 – 01:11

A numbered list of session types — the order is the order the engine fills them in.

Narrator · 00:54 – 01:11 You can use — as you have probably noted — drag and drop to define the priorities. That means the system will first try to schedule the workshops; after they're finished it will move to roundtables; after that is finished it will move to 1-to-1.
Setup Matching Plan page with a numbered drag-and-drop list of session types — Blocked Session, Breakfast/Lunch/Dinner, Free Activities, General Session, Informal meeting type, Keynote (with 'Delegate, Delegate / Speaker' attendee types), POD, RoundTable (with 'Delegate / Speaker, Delegate'), Speaker Session, Staff Informal Meeting, Workshop, then a series of Single Meeting variants (Mutual, Spartners→Delegate, Spartners→Speaker, Delegate→Spartners, Delegate→Speaker, etc.)
Setup Matching Plan. The page is titled "SETUP MATCHING ORDER USING DRAG AND DROP". Items 1-11 are pre-scheduled session types (Blocked Session, Keynote, RoundTable, Workshop, etc.). From item 12 onward come the Single Meeting variants — (Mutual), (Spartners → Delegate), (Spartners → Speaker), (Delegate → Spartners), (Delegate → Speaker), (Speaker → Spartners), etc. — one per directed pair of attendee types, each with its own Index (min) weighting.

Each row carries:

3. Per-Session-Type Settings 01:11 – 01:54

For roundtables: min/max attendees and who can attend. For 1-to-1s: how heavily it weights the schedule.

Narrator · 01:11 – 01:54 It is important to know that for each of these, there are settings. For roundtables you say what is the minimum and maximum amount of participants, and you can select the attendee types taking part in the roundtable. For 1-to-1s, you can define how much that meeting is weighting into the whole session.
Matching Plan list scrolled to show all 11 pre-scheduled types and many directed Single Meeting variants with Index (min) inputs
Matching Plan — full list. Scrolling reveals every directed Single Meeting variant: (Mutual), (Spartners → Delegate), (Spartners → Speaker), (Delegate → Spartners), (Delegate → Speaker), (Speaker → Spartners), (Speaker → Delegate), (Speaker → Delegate / Speaker), (Delegate / Speaker → Spartners), (Delegate / Speaker → Delegate), etc. Each gets its own Index (min) — the lower bound on match score required for the engine to even consider scheduling that pairing.
Per-row settingWhat it does
Attendee types (Keynote, RoundTable, etc.)Which attendee types can attend this session-type slot. Driven by the rules defined in Module 4 §7.
Max (%)Upper cap on how full each slot of this type can get (a percentage of capacity).
Index (min) for Single MeetingsMinimum match-score threshold. A 1-to-1 pairing below this index is excluded from auto-placement.
Show Hidden Steps toggleReveal entries you've previously hidden so you can re-include them.
Why directional Single Meeting variants?
A Spartners → Delegate 1-to-1 is not the same as a Delegate → Spartners 1-to-1. The first is a sponsor selecting a delegate (the canonical hosted-buyer pattern); the second is a delegate selecting a sponsor. By giving each direction its own row in the matching plan, the administrator can weight, throttle or even disable any direction independently.

4. Running the Plan 01:54 – 02:22

Give it a name; click Run; come back in a few minutes for the result.

Narrator · 01:54 – 02:22 As soon as you define all of these, you can proceed to running the matching plan. When you run the matching plan, you just give it a name and then you click Run. After several minutes, the system gives you a full overview of what has been scheduled.

The Run dialog has three controls:

5. Run Output — Statistics & Coverage 02:22 – 02:54

Once the run finishes, three views show what got scheduled and how well it covers your attendees.

Post-run statistics: 1-1 Meeting Generated Statistics pie (Total 43 / Mutual 7 / Spartners Lead 36); Matches panel with 35% of all attendees broken down by attendee type (Delegate 34% 69 attendees, Delegate/Speaker 38% 6 attendees, Guest 17% 2, Partner 24% 2, Partner/Speaker 22% 2, Spartners 24% 42, Speaker 20% 5, Staff 100% 10, Ticket Delegate 0%); Generated panel with 156 sessions broken down by type (RoundTable 25, Single Meeting 43, General Session 0, Keynote 37)
Run statistics. Three panels per run: (a) the 1-1 Meeting Generated Statistics pie — Total 43, Mutual 7, Spartners-led 36; (b) the Matches panel showing match coverage by attendee type — Staff at 100%, Delegate at 34%, etc.; (c) the Generated panel listing sessions by type — 25 RoundTables, 43 Single Meetings, 37 Keynote sessions.
Narrator · 02:22 – 02:54 Most delegates have between 8 and 10 sessions in the event. It's the same for partners — 24 partners have more than 10 sessions scheduled. So that's very important to see — that everyone is busy and everyone has a good amount of meetings.
Sessions Generated (Cumulative) line chart showing scheduled sessions ramping from ~13 to 156 across the run; Attendees Statistics pie (Free participants 72, Matched participants 66); Matched Attendees by Type pie (Delegate 89, Spartners 42, Delegate/Speaker 6, Speaker 5, Staff 10, Partner/Speaker 2); History table of past runs
Sessions Generated (cumulative) chart, attendee pies, and run history. The line chart shows total scheduled sessions over the course of the run. Two pies summarise coverage: how many participants have any meeting at all (66 matched / 72 free), and the breakdown of matched participants by attendee type.

6. Run History & Apply 02:54 – 03:19

Every previous run is kept. Compare them, then apply the one you like.

Narrator · 02:54 – 03:19 As soon as this is done, you can also have a look at the history of what has been run. From here you can see all previous matching runs, and for each you can see the results. If you find a suitable matching run, you can just click Apply and that will be assigned to the attendees — they will be able to see it in their client panel or on the mobile app.
History columnWhat it shows
No.Sequence number of the run.
NoteThe label the administrator gave the run when starting it (e.g., "w1 - all RTs @ 50", "W6 Sp => Del @ 40%") — useful for parameter sweeps.
Run dateTimestamp.
Run byWhich administrator triggered it.
No. of meetingsHow many meetings the run produced.
RollbackRevert to a previous state.
View detailsOpen the full run output for inspection or to Apply.
Workflow — parameter sweep
The example history shows runs with names like "W6 Sp → Del @ 40%", "W7 - Sp → Del @ 30%", "W8 - Sp → Del @ 20%" — same plan, different per-type weighting. This is how you tune: run a sweep of parameter combinations, compare the statistics, then Apply the run that best balances coverage vs match quality.

7. Matching Review — Per-Attendee Schedule 03:19 – 03:52

Inspect what the engine scheduled for each attendee, one at a time.

Narrator · 03:19 – 03:52 What you can do from here as an administrator is review the meetings. If I click on Matching Review, the system gives me a full overview of what has been scheduled. For each delegate or each sponsor, I can see what is being scheduled into their itinerary — for example, for this person on Monday they have roundtable sessions, single meetings, and I can see with whom they are meeting.
Matching Review page with three filters (Attendee type, Attendee, Meeting type), Individual View / Meeting View tabs, and per-attendee group rows listing scheduled sessions with date, title/type, P1/P2 columns, second attendee, table, seat, index, Is approved toggle
Matching Review. Top: Back to plan, Approve selected meetings, Delete selected meetings action buttons. Three filters: Attendee type, Attendee, Meeting type. Individual View / Meeting View tabs. Each attendee gets a green group header (e.g., Alan Goh — Jones Lang LaSalle Singapore (3)) followed by their scheduled meetings: date, time, title/type, second attendee, table, seat, index score, and an Is approved toggle per row.

Two views on the same data: Individual View groups by attendee (one card per person showing their full day), Meeting View groups by meeting (showing all attendees in each session). Use whichever fits the question you're answering.

8. Manual Edits — Delete or Add a Meeting 03:52 – 04:22

The engine does the heavy lifting; the admin retains the final say.

Narrator · 03:52 – 04:16 As an administrator, you have full flexibility — you can delete a meeting if you think it's not suitable, or you can add a meeting manually if you find that there is a need for that. You just click Add Meeting, select the person, and the system will give you the available slots where this person is free.

Two override paths from the Matching Review:

Narrator · 04:16 – 04:22 So that's how you manage and run the automated scheduling on the platform.

9. Essence & Takeaways

The one-paragraph version

Setup Matching Plan is a numbered drag-and-drop list of session types — pre-scheduled types (Workshop, Keynote, RoundTable, etc.) with Max % caps and attendee-type rules; then directed Single Meeting variants (Spartners→Delegate, Delegate→Spartners, Speaker→Delegate / Speaker, etc.) with Index (min) match-score thresholds. The order in the list is the order the engine fills slots. Click Run with a label and the engine produces a run; come back to a stats screen with a 1-to-1 pie (Total / Mutual / Spartners-Lead), a Matches panel showing match-coverage % per attendee type, a Generated panel of session counts by type, and a cumulative-sessions chart. Every run is kept in a history table with note, date, owner, meeting count, rollback and View details — Apply the run you like and attendees see it in their client panel and mobile app. Matching Review exposes the per-attendee schedule with filters by attendee type / attendee / meeting type, and an Individual View / Meeting View toggle. From there, administrators can delete any auto-scheduled meeting or manually add one (the platform shows free slots), giving them final say over the engine's output.

Use this page as the basis for…
  • An ops runbook for "how do we run scheduling for event X" — including the parameter-sweep workflow.
  • A reference for whoever tunes match thresholds (Index min, Max %) for a new event format.
  • A QA list before applying a run — coverage by attendee type, meeting count per attendee, mutual-vs-lead 1-to-1 ratio.
  • A naming convention for run notes ("W6 Sp → Del @ 40%") so the history table stays readable across many sweeps.

10. Full Transcript

Verbatim narration provided alongside the video.

Show / hide transcript
00:00 – 00:26
In this portion, we are about to review the automated matching and scheduling engine and how that looks like from an administrator point of view. So as soon as everyone has provided their preferences—delegates and sponsors—from here you have a full overview of what the priorities are. For example, you can choose a sponsor or partner and then you see their selections.
00:26 – 00:54
For each of these, you see their priority. So they have assigned like priority 1 or priority 2 or priority 3. So as soon as you have all this gathered, you move to the matching plan. The matching plan is where you actually define the logic of how the system is about to schedule these meetings. So you defined what are the sections or meeting types you would like to have scheduled.
00:54 – 01:21
And you can use—as you have probably noted—drag and drop in order to define the priorities. So that means that the system will first try to schedule the workshops, and after they're finished, then it will move to roundtables, and after that is finished, then it will move to 1-to-1. It is important to know that for each of these, there are settings. So for roundtables, you say what is the minimum and maximum amount of participants.
01:21 – 01:54
And also you can select the attendee types who are taking part into this roundtable. So by defining that, and for 1-to-1s, you can define how much that meeting is weighting into the whole session. So as soon as you define all of these, you can proceed to running the matching plan. When you run the matching plan, you just give it a name and then you click "Run."
01:54 – 02:22
So after several minutes, the system will give you a full overview of what has been scheduled. So for example, in this case, we have generated 1,732 meetings out of possible selections. It says that for roundtables we have 25 sessions, single meetings we have 43, 67 keynote sessions and similar. And here you have also the statistics on how many delegates have been matched and how many of them have—for example—how many sessions.
02:22 – 02:54
So you can see that delegates, most of them have between 8 and 10 sessions into the event. It's the same for partners. You can see 24 partners have more than 10 sessions scheduled. So that is very important to see that everyone is busy and everyone has a good amount of meetings. So as soon as this is done, you can also have a look at the history of what has been run.
02:54 – 03:19
So from here you can see all previous matching runs, and for each of them you can see the results. If you find a suitable matching run, you can just click on "Apply" and then that will be assigned to the attendees and they will be able to see that into their client panel or on the mobile app.
03:19 – 03:52
Also, what you can do from here as an administrator is you can review the meetings. So if I click on "Matching Review," the system gives me a full overview of what has been scheduled. So for each delegate or for each sponsor, I can see what is being scheduled into their itinerary. So for example, for this person, I can see that on Monday they have roundtable sessions, they have single meetings, and I can see with whom they are meeting.
03:52 – 04:16
From here, as an administrator, you have full flexibility—you can delete a meeting if you think that's not suitable, or you can even add a meeting manually if you find that there is a need for that. You just click "Add Meeting," select the person, and then the system will give you the available slots where this person is free.
04:16 – 04:22
So that's how you manage and run the automated scheduling on the platform.