Running a multi-day CME conference on bindro

How should I structure the agenda as inventory?

One session per creditable block. That is the unit capacity is held in, the unit a credential is scoped to, the unit a scan is recorded against and the unit credit is issued from, so anything you might later want to count separately should be its own session from the start.

This is also how you get around credit types not being modelled: a workshop carrying a different kind of credit is a different session, and the per-session records then carry the distinction for you without the engine needing to know what the distinction means.

• Give each session its real capacity — a breakout room's limit is not the plenary's.
• Keep sessions that people can attend independently separate, even if they run back to back.
• Sessions that everyone attends together can be one session with the full capacity.

What is the hosted-checkout limit I need to plan around?

The hosted HTML checkout sells one session per order today. A participant building a three-day personal agenda through the hosted page therefore places one order per session, which is honest but tedious, and worth knowing before you publish a registration link rather than in the week registration opens.

The full agenda and multi-session orders ship on the public JSON API. If you are driving registration from your own conference site — which most providers with a real agenda are — that is the route to build against, and it is the one place where the multi-day model is complete.

How do badges and the door work on the day?

Badges are the primary credential for this vertical. Each participant on the roster has a printable badge page carrying their name, the activity and their registration type, and that badge is what gets scanned at each session.

Re-entry is allowed and multiple door points are supported, so a session with two doors and a plenary with four are both normal. A place on a group booking that nobody has named yet is refused at the door and left off the manifest — an unnamed place is not a person, and admitting one would put an unidentified attendee into a credit record.

What happens when the venue network fails?

Nothing much, if you downloaded the manifests. The signed per-session manifest lets a device validate scans locally with no network call at all, which is the assumption for this vertical rather than a fallback — hotel ballroom wifi is the normal condition, not the exception.

When devices reconnect, each shift log is replayed and applied exactly once however many times it is uploaded. A badge scanned on two devices at the same door lands in a conflict queue for somebody to look at, rather than being resolved silently in a way that would quietly change an attendance record.

What about the exhibit hall and commercial support?

Sponsor packages and sales are recorded on the roster so your staff know who is in the room, and that is the whole of it. No money moves through bindro for them: no charge is taken, no ledger entry is written, no fee applies and nothing is paid out. You invoice supporters off-platform — which is where the separation of commercial support wants that money anyway.

There is no exhibit-hall inventory at all: no floor plan, no booth to sell, no booking. If your annual meeting is really a trade show, that half of it lives somewhere else, and the Cvent comparison is the honest place to start.