Planning compliance briefings for different practitioner levels
A compliance forum often seats first-year officers beside heads of function, and one briefing rarely works for both.
The short answer
Decide the levels you will serve (for example foundation, practitioner and senior), write one sentence on what a delegate at each level should be able to do afterwards, and assign each briefing to one level. Label every session on the programme and in registration so delegates choose for themselves.
The content of any briefing, and whether it counts towards a professional body's recognition scheme, is for the speaker and the relevant body to confirm. The organiser plans the structure and asks the questions.
Why mixed levels go wrong
Senior delegates leave when a session explains basics, and newer delegates stay silent when it assumes long professional background. Both groups then rate the forum as not for them.
Labelling levels honestly is cheaper than building more sessions.
Define the levels in plain terms
| Level | Who it is for | What the session should help them do | Format that tends to suit |
|---|---|---|---|
| Foundation | People new to compliance or new to the sector. | Follow the vocabulary and know where to look things up. | Short briefing with a glossary and time for basic questions. |
| Practitioner | Working officers handling day-to-day cases and reviews. | Compare approaches and test their own procedures. | Case walk-throughs, small-group discussion, templates. |
| Senior | Heads of compliance, risk and legal. | Weigh trade-offs, resource decisions and reporting lines. | Peer roundtable or closed panel with limited places. |
| Cross-level | Everyone, including board or business representatives. | Share a common update. | One plenary with a clear, non-technical summary. |
Decisions in order
- Pick the levels from your registration data or last year's feedback, not from guesswork. Ask what roles delegates hold.
- Write the one-sentence outcome for each level and share it with speakers as their brief.
- Decide how many parallel sessions each level needs and how many people each room should seat, based on expected registrations per level.
- Set a rule for moving between levels: delegates may sit anywhere, or senior sessions require a role check.
- Plan transitions: breaks long enough for delegates to change rooms, and signs that state the level.
- Agree materials per level: a glossary for foundation, templates for practitioner, a discussion paper for senior sessions.
- Ask each speaker to confirm in writing the level they are pitching to and the assumed prior knowledge.
Questions for the competent party
- To each speaker or their organisation: is the briefing content cleared for the audience level and for any recording or circulation?
- To the relevant professional body, if recognition is wanted: what is required for a session to be considered, and by when must the application be made? Do not state any recognition in promotion until it is confirmed in writing.
- To your own adviser: are there topics where the forum should add a note that briefings are informational and not advice?
- To the venue: can rooms be sized and reset between sessions so that level-specific rooms do not overflow?
Common pitfalls
- Labelling by job title alone, so a new manager in a senior session feels out of place.
- Putting all senior content in one slot, so heads of function cannot attend both topics they came for.
- Printing level names that sound ranked, such as beginner, without telling delegates what the level covers.
- Leaving the cross-level plenary to the last speaker with no time left for questions.
Worked example · Fictional example
A fictional compliance forum with three levels
Fictional organisation and figures, for illustration only.
The fictional Persatuan Pegawai Pematuhan Contoh expects about 180 delegates. Registration data suggests roughly 70 foundation, 80 practitioner and 30 senior delegates.
The committee runs two parallel tracks in the afternoon. The foundation briefing runs in the larger room and the practitioner case sessions in a medium room. The senior roundtable is limited to 30 places and uses a role check at registration. A cross-level plenary opens the day with a short non-technical update.
Speakers receive a one-sentence outcome per level, and delegates see level labels and prior-knowledge notes on the programme. The committee asks the professional body whether any session can be considered for recognition, and promotes nothing until it receives a written reply.
Use this yourself
Briefing track planner
Copy one row per briefing. Fill it in with each speaker and use it to check that every level has a session in each time slot.
| Session and slot | Level | Outcome in one sentence | Assumed prior knowledge | Expected delegates and room | Materials | Content clearance owner |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- One or two levels in the audience and a single track.
- Speakers are members of your committee and know the audience.
- No external recognition scheme is involved.
Outside planning help earns its fee when
- Three or more levels with parallel tracks and room-sizing questions.
- Speakers come from several organisations with separate clearance routes.
- You need a person to chase speakers, check outcomes against the brief and handle recognition enquiries.
Need help turning one briefing into level-based tracks?
A conference project lead can analyse your registration data with you, draft the level definitions and track planner, brief each speaker on the outcome for their level, size rooms with the venue and track speaker clearances. Content and recognition questions stay with your speakers, their organisations and the relevant body. Send the expected audience mix and date to scope the work.
Questions organisers ask
How many levels should a forum have?
Two or three is usually enough. More levels create too many small rooms and make the programme hard to read.
Should senior sessions be invitation-only?
That is a committee decision. A role check at registration is a lighter option, and the rule should appear on the programme.
Can we promise professional recognition points?
Only after the relevant body confirms in writing. Until then, say that you have asked.
What if most delegates are mid-level?
Give that level the most sessions and keep foundation and senior tracks smaller. Use registration data to set the balance.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.