Prerequisites, age limits and the bookings a training centre should refuse before the money moves

How do I stop an unqualified trainee booking a seat?

Safety training asks for the prerequisite certificate as a required file on the booking, so the upload is part of checkout rather than a follow-up email. The booking cannot be completed without it, and the file is attached to the whole booking rather than to each person on it.

The upload is tied to the live booking and claimed onto the order when it confirms. A reference that belongs to somebody else's checkout, or to a booking that has since lapsed, is refused on the money path rather than accepted and orphaned — which is what stops an uploaded document being attached to the wrong trainee.

The awarding body's own wording appears under the field: evidence of the prerequisite is required before a place can be confirmed. Employers read that before they book, which cuts down the number of people who arrive on the day without a card.

• One document per booking, up to five megabytes, uploaded during checkout.
• Photographs and scans are both fine — this is evidence, not a form.
• The file cannot be claimed by another order, and a lapsed hold releases it.
• For a block booking, that document covers the booking rather than each trainee.

What does the age rule actually refuse?

Sixteen is a hard floor on the date of birth across safety training, and it is a rule rather than an attestation. The check runs inside the confirm transaction: a younger trainee is refused with the rule named and the error anchored to the date field, no order exists afterwards and nothing is charged.

A garbage date is refused too, which sounds obvious and is not — a rule that can be bypassed by typing nonsense into the field is not a rule. There is no path through the hosted form or the JSON API that reaches payment with an unparseable date of birth.

Where it stops is the course-specific floor. Powered-equipment courses whose awarding body sets a higher age than sixteen are not modelled, so that check stays with your enrolment process. Publish the requirement on the course description and check it against the prerequisite document you collected.

• The floor is sixteen and applies to every course in this vertical.
• Refusals happen before any payment intent exists.
• Higher, awarding-body-specific age limits are yours to enforce.
• Date of birth is stored as personal data under your retention rules.

Can I ask different questions depending on the answers?

Yes, and it is the right tool for the branches a safety course actually has: ask about a respirator fit test only of the people doing the confined-space module, or about a licence category only where the answer to an earlier question makes it relevant.

The condition is declared on the field itself rather than scripted, so the same rule governs the hosted booking form and the public JSON API. A field that is hidden is genuinely not required, and a field that is visible cannot be skipped by posting past the form — the enforcement is on the money path, not in the browser.

Answers are stored against the trainee where the question is asked per person, and against the booking where it is asked once. Anything classed as health data is anonymised on a shorter retention clock than ordinary personal data.

• Conditional fields need no scripting and work with JavaScript switched off.
• Hidden fields are not enforced; visible ones cannot be bypassed.
• Ask per-trainee questions at attendee scope and commercial ones at booking scope.
• Health-classed answers have a shorter retention life than the rest of the record.

What does bindro not check?

The contents of anything you collected. Bindro stores the prerequisite certificate and shows it to you; no rule reads it, no rule judges whether the qualification it shows satisfies your awarding body, and nothing expires it. A trainee who uploads a photograph of a bus ticket completes the booking.

Nor does it check identity. The name on the booking is the name typed into the booking, and the door register matches names — nobody's document is verified and no verification service exists anywhere in the platform. If your awarding body requires photographic identification, that check happens in your classroom.

And it does not track certification currency. There is no record that a trainee's existing card expires next March, so nothing can refuse a booking on that basis or remind anybody about it.

• Uploaded documents are stored and never assessed.
• No identity or document verification service is integrated anywhere.
• Existing certification expiry is not recorded and cannot gate a booking.
• The judgement that a prerequisite is genuinely satisfied stays with your enrolment team.