Collecting licences and disclosures before anyone pays

Why collect the compliance material at registration rather than afterwards?

Because chasing it afterwards is what actually fails. A disclosure request sent after the fact competes with a physician's clinic list and loses, and the records you are missing at audit are always the ones that were somebody's follow-up task.

Making them blocking parts of the form moves the work to the one moment the participant is definitely paying attention. The refusal happens on the money path, so an incomplete registration is not a paid registration with a gap in it — there is no order to chase.

What is collected on a CME registration by default?

The vertical's field set is configured for accredited education rather than assembled by you from scratch, and the mandated fields render as locked so they cannot be quietly removed from a form.

• NPI or licence number, and the employer.
• A copy of the medical licence, uploaded as a file against the order.
• A financial-disclosure answer per participant, with "none" as a valid answer.
• Society membership number, where a member rate applies.
• Dietary and accessibility requirements for the catering and the room.

How does the disclosure question actually behave?

It is attendee-scope, which is the important detail: the answer belongs to the person attending, not to the person paying. On a group booking, each place carries its own disclosure, and a place filled in later by the person taking it collects theirs at that point rather than inheriting the co-ordinator's.

Follow-up questions can be made conditional on an earlier answer, so a participant who declares a relationship sees the detail box and a participant who writes "none" does not. Conditional visibility is evaluated on the server as well as in the page, so a hidden question is genuinely not required rather than merely invisible.

How are licence documents stored and retrieved?

The file is uploaded against the live booking and claimed onto the order at the moment payment is confirmed. A reference that does not resolve to that booking's own upload is refused on the money path — you cannot attach somebody else's document to your registration, and an invented reference does not confirm an order.

Documents are held per registration with a size limit, and downloaded from the console roster by staff with the right role. They are order-scope by design, so the control renders once per booking rather than once per person.

What does bindro deliberately not do with a disclosure?

It does not review one. Nobody at bindro reads what participants disclose, no rule scores it, nothing blocks a registration based on its content, and there is no mitigation workflow. The relevant-financial-relationship review your accreditation requires is yours, and it happens wherever it happens today.

It also does not model faculty. Planners, presenters and reviewers are not a separate population here with their own disclosure cycle — everybody on the roster is a participant. If your faculty disclosures are managed in a CME office system, they stay there, and that is a reasonable reason to run both.