A briefing is the pre-event walkthrough every driver completes online: safety rules, flags, the circuit, what to expect. Doing it before arrival means less to cover at the gate and a record that each driver actually went through it.
Modules and templates
Briefings are built from two pieces, under Content → Briefings:
- Modules are reusable blocks: a video, a block of text, or a short form. You write them once and they can be circuit-specific or general.
- Templates chain modules into a flow (for example "Beginner flow" or "Nürburgring flow"). You attach a template to an event, and drivers step through it during registration.
Reuse across events
Build your modules once and combine them per circuit or level. Most organisers end up with a handful of templates that cover everything, so a new event is a one-click attach rather than writing from scratch.
Writing a module
Text in a module accepts basic markdown, so **bold** reaches drivers as bold. That works in the body of a text module and in the individual lines of an icon list or a flag list, which is handy for the part of a rule you want to stand out.
Each module also has a Key. It is an internal label for your own list, drivers never see it, and renaming it breaks nothing: templates and events reference the module itself, not its key. Leave it blank and Lapvio builds one from the title.
Previewing
Use Preview to step through the exact flow a driver sees before you attach it. It's worth doing once per template so the order and wording read the way you intend.
Inactive blocks reach nobody
Every module has an active/inactive switch. An inactive module is skipped in the driver's briefing even when it sits in the flow, so a briefing whose blocks are all inactive shows drivers nothing. The builder flags inactive blocks in the list and refuses to publish a briefing with no active block, but it's worth a glance before you publish.
A completed briefing is one of the things that marks a driver "ready" for check-in, alongside a signed waiver.