Certificates from the register, not the sale: what bindro issues and what it will never send

Where do a certificate's contact hours come from?

From the session, not from the sale and not from the register. A session scheduled from nine until five is eight contact hours, and every certificate issued for it carries eight hours regardless of who arrived late. Bindro records that a trainee was marked in, not how long they stayed.

That is worth designing around. If your awarding body cares about partial attendance, split the day into sessions on the boundaries it cares about, because the session is the unit that both attendance and hours are counted against.

It also means the schedule you publish is the schedule you certify. A course that over-ran by an hour still issues the hours it was scheduled for; a session edited after the fact changes what future certificates say, not the ones already issued.

• Contact hours are the session's scheduled duration, to one decimal place.
• Structure sessions on the boundaries you need to certify against.
• Lateness and early departure are not modelled anywhere.
• Already-issued certificates are immutable records with their own serial.

How do I issue certificates after a course has run?

Open Credits in the console. Every delivered session is listed with its contact hours, how many trainees were verified as present and how many certificates have been issued so far. Press "Issue certificates" against the session and bindro mints one for each trainee with a check-in record.

Three refusals are built into that action, and each of them exists because an auditor would ask. A session that has not ended yet is refused outright. A trainee who paid and never arrived gets nothing, because issuance reads the register rather than the sale. And pressing the button twice issues nothing the second time — the constraint is on the trainee and the session together, so re-issuing after a late check-in picks up only the people who were missing.

It is not automatic, and the vertical's own most-asked question uses the word "automatically". Nothing fires on its own: a person decides the session is complete and the register is right, and then issues. Given what a certificate is used for, that is the correct place to put a human.

• Issuing needs the event-write grant; a read-only role sees the counts and no button.
• A session that has not finished is refused with the reason named.
• Re-issuing is safe and never duplicates a trainee's certificate.
• Fix the register first — a missing check-in means a missing certificate.

What does the certificate say, and what does it not say?

It is a printable page headed "Certificate of completion": your training centre certifies that the named trainee completed the named course on the date it ran, earning a stated number of contact hours of verified attendance, with a serial and the date it was issued. Anyone holding it can quote the serial back to you to check it is real.

What it is not is a card. There is no awarding-body number on it, no expiry date, no scheme logo and no wallet card, because bindro is not an awarding body and does not pretend to be one. If your obligation is to produce a DOL card, an eCard or a scheme certificate, you produce it exactly as you do today and this is the attendance record underneath it.

Certificates are not emailed to trainees either. They live in your console, one page per certificate, and you send them the way you send them now.

• Your training centre's name is the certifying name on the page.
• No expiry, renewal date or awarding-body identifier is recorded.
• Nothing is emailed automatically and there is no bulk export of certificates.
• The serial is the verification mechanism, and it points back at you.

Does bindro report credits to OSHA or an awarding body?

No, and this is the single most important sentence on the page. No agency, scheme or regulator is integrated anywhere in the platform. Nothing is transmitted to OSHA, to a DOL outreach programme, to the American Heart Association or to any other awarding body, and no submission file is produced for one.

A training centre that reads "certificate issuance" as "the reporting is handled" would stop doing something they are accredited to do, on our word. So: you report, you file, you issue the card. Bindro gives you a defensible attendance record with serials behind it, and that is the whole of the claim.

The accreditation acknowledgement on the booking form is the same shape. It is a record that the requirement was acknowledged; it is not enforced on the money path and a booking completes whether or not the box is ticked.

• Nothing is sent to any awarding body, in any format, at any point.
• No eCard, card or scheme submission is produced.
• The accreditation acknowledgement is advisory, not a blocking check.
• Use the attendee export if you need to build a submission of your own.