Running a multi-day CLE institute on bindro today

What does bindro actually support for a multi-day institute?

A single registration can cover several sessions: one order with one line per session, both pools decremented, and a per-session roster on each. Every attorney gets a credential per session, and that credential admits at its own session and is unknown at the others.

That is exactly the behaviour an institute needs for credit, because it makes attendance per session a fact rather than an inference. Credits are then issued session by session from those scans, so an attorney who skipped day two receives day one's hours and nothing else.

Orders of this shape are placed through the public JSON API, and there is a limit on how many sessions one order may carry, so a very long agenda is split across orders.

What cannot I do in the hosted checkout yet?

Pick several sessions in one go. The hosted registration page sells one session per order today — the multi-line agenda is on the API — so an attorney building their own three-session itinerary through the public page does it as three registrations.

This is recorded honestly in the platform's own capability ledger rather than glossed in marketing, and it is the single most important thing to know before committing to bindro for an institute.

It is a real constraint, not a preference. If your institute depends on an attorney self-selecting a personal agenda in one checkout, either plan to drive the API yourself or wait for the hosted picker.

How should I structure the programme around that?

Sell each session as its own registration and let attorneys register for the ones they want. It is more clicks for them and it is completely exact for you: every session has its own capacity, its own door list and its own credit issuance.

Alternatively sell the institute as a small number of blocks — a full-day track, a half-day workshop — each of which is one session. Fewer registrations, and credit still lands per block, provided the blocks match the credit boundaries.

Whichever you choose, keep sessions aligned to credit blocks rather than to the room timetable. The hours awarded come from the session's own start and end.

• One session per credit block, always.
• Separate ethics sessions — categories are not modelled, so structure carries it.
• Capacity is per session, so a popular workshop fills without closing the institute.
• Firms can block-book a track and name attorneys afterwards.

How does the door work across several days?

Per session, with devices that keep working offline. Each device syncs a signed manifest for the session it is on, validates scans locally, and uploads the log afterwards; scan counters reset per session, so a device running all week does not carry yesterday's state into today.

A credential presented at the wrong session is unknown rather than admitted — the behaviour that makes per-session credit trustworthy in the first place.

Conflicts, if you run several doors, queue for review rather than resolving themselves, which is what you want on a programme where the same attorney is legitimately scanned many times across several days.