CPD recording for medical conferences: what the AV scope has to deliver

At most corporate conferences, recording is a nice-to-have. Someone in marketing will clip the keynote, maybe post the highlight reel. Whether the recording exists at all is not a compliance question.

At a medical conference, it is. The RACGP, RACP, ACRRM, ANZCA, and the AMA’s CPD Home all operate frameworks in which educational activity has to be documented. The recording of a scientific session is evidence of that activity. It sits in an educational record, not a content library. That changes what the AV team has to produce and how they have to produce it.

This piece focuses on the recording scope specifically. For the broader production picture (Medicines Australia Code, panel-heavy session formats, hybrid attendance), see the medical and pharma conference production overview.

Why the recording is an educational record

Australia’s major medical colleges overhauled CPD requirements in 2023, with the frameworks continuing into 2026 broadly unchanged. All of them now require fellows to record a minimum of 50 hours of CPD activity per year across three categories: Educational Activities (minimum 12.5 hours), Reviewing Performance, and Measuring Outcomes. The 2026 RACP CPD framework matches this structure, as does RACGP, ACRRM, and ANZCA’s January 2026 program handbook.

What this means for a conference organiser: delegates attending your scientific sessions are collecting CPD hours, and they need documentation to log those hours. The recording of the session is part of that documentation trail. Some colleges auto-populate CPD records when an accredited event is registered, but attendees still need access to session content for later review and audit purposes. The Medical Board of Australia’s CPD registration standard requires practitioners to keep CPD records for three years, and ANZCA explicitly recommends the same retention period.

When the recording is going to sit in an educational record for up to three years, the quality bar rises. A video file that works fine for a social media clip does not necessarily meet the requirement of a usable educational resource. Audio intelligibility matters. The slides have to be readable. The file has to be deliverable to a spec that the CPD administrator can actually use.

The recording and post-production scope for a medical conference is built around these requirements, not around marketing deliverables.

What “every session” actually means

The most common gap in medical conference AV scoping is room coverage. An organiser briefs “recording” and pictures the main plenary. The AV vendor quotes accordingly. On the day, delegates are logging CPD hours in four concurrent breakouts that were never wired for ISO recording.

Every room running accredited scientific content has to be recorded independently. That is not a production preference, it follows directly from the CPD framework. If a fellow attends a workshop in Breakout 3 for two hours, they need evidence of that attendance and access to that session’s content. If the session was not recorded, or was captured only on a single camera with ambient audio picked up from the room, neither the organiser nor the delegate has a clean record.

In practice, for a mid-size medical society annual meeting, this means:

• One main plenary room, often with multi-camera direction and a separate broadcast feed
• Four to six concurrent breakouts, each with at least one fixed camera, dedicated audio feed taken from the room’s mixing desk, and an isolated recording that runs independently of the plenary workflow
• Any additional workshop or special interest group sessions, even where attendance is small

The ISO recording feed (a clean, unprocessed audio and video file for each room) is the baseline. Anything cut or processed for broadcast is a separate deliverable. The archive record has to be the uncut room feed so that post-production has complete material and the CPD administrator has an unambiguous record of what was presented and for how long.

A typical multi-room conference day generates eight to twelve hours of scientific content per room. Across five concurrent spaces over a three-day meeting, the raw archive reaches several terabytes. The storage and workflow plan for that volume has to exist before bump-in, not after.

Attendance and verification

Recording the session is one requirement. Verifying who attended is a related but separate one.

Some CPD home platforms, including ACRRM’s CPD Home portal and AMA CPD Home, require education providers to upload attendance data within one week of the event. ACRRM’s guidelines for education providers specify the use of a standard attendance sheet template uploaded through the provider’s event portal. If attendance is not confirmed on time, the hours may not be auto-verified and delegates have to self-record with supporting evidence.

The AV team’s involvement in attendance tracking varies. At smaller conferences, the organiser handles registration scanning at room entry with a separate system. At larger meetings, RFID lanyards or QR check-in at room level are increasingly common, and the AV team may be asked to confirm session start and end times to cross-reference against badge scan data.

What the AV team always contributes is the timestamp record. A clean ISO recording with accurate timecode is the production equivalent of an attendance log. If a delegate’s check-in scan shows entry at 09:14 and the session recording confirms the session ran from 09:00 to 10:30, the CPD administrator has a verifiable record. If the recording has no timecode, or if the file metadata is stripped on export, that verification becomes harder.

This is not a complicated technical requirement. It is a workflow discipline requirement. The post-production team has to know the convention before they export, not after.

Delivery to spec

CPD administrators do not want a Dropbox link to a folder of unlabelled MP4 files. They need files they can manage, distribute, and archive. The delivery spec should be agreed before the event, not negotiated afterwards when the raw files are already sitting on a drive.

A workable delivery spec for medical CPD content typically includes:

File naming. Each file identified by date, room, session title, and presenter name where possible. “Day2_Breakout3_PediatricUpdate_DrSmith.mp4” is a usable archive. “Camera3_final_v2.mp4” is not.

Format. H.264 MP4 is the broadest-compatible format for distribution and playback. Some college platforms require specific bitrate ranges. Check before encoding.

Captioning. Increasingly a requirement rather than an option. For CPD content, accuracy on technical terminology matters. A cardiology session includes drug names, anatomical references, and clinical terminology that AI captioning frequently misreads. Human CART captioning during the live event produces a clean transcript that can be used for post-event access. AI captioning with a medical vocabulary supplement is a workable fallback, but the transcript needs quality review before it becomes the permanent record.

Timeline. Some colleges require content to be available to delegates within a set period of the event. A three-month post-production timeline is too slow. Many medical conference organisers expect content available within two to four weeks of the event close.

Access control. CPD content is usually restricted to registered delegates, not public. The delivery method has to support access control, whether that is a password-protected portal, a college LMS, or a purpose-built post-event platform.

All of this is scoped and agreed before bump-in. Discovering on week three of post-production that the college requires a specific subtitle format adds time and cost that the budget did not allow for.

Where this goes wrong

The points of failure in CPD recording at medical conferences are well-established. They are rarely technical surprises. They are almost always scoping gaps.

Breakouts not in scope. As above. If the brief only says “record the keynote” and the organiser expected everything to be covered, the gap surfaces on the day when it cannot be fixed affordably.

Audio from the wrong feed. A room mix that works for in-room listening is not necessarily clean on record. If the room mix includes reverb from the space, or if the mix engineer compensates for the room acoustics in a way that sounds fine in the room but harsh on playback, the archive recording carries that processing permanently. The ISO recording should come from a clean pre-effects send, or at minimum a dedicated mix position configured for the archive feed.

No redundancy plan. A single recording device per room with no backup is a single point of failure at a compliance-critical event. The consequence is not just a missing highlight. It is a gap in an educational record that CPD administrators and delegates have a legitimate claim to. Dual-redundant recording per room is the standard at medical conferences, not a premium option.

Post-production handed to the wrong team. A video editor who is experienced with corporate brand films may not have a workflow for managing 80 hours of multi-room scientific content to a CPD archive spec. The post-production team assigned to a medical conference needs experience with high-volume structured archive work, not just edit craft.

No delivery spec confirmed. This one comes up constantly. A well-recorded event still produces a usable archive only if the delivery format, naming convention, access method, and timeline are confirmed in advance. The AV team cannot know what the college or organiser needs without being told explicitly.

For a more complete picture of the planning scope, the AV for medical and pharma conferences guide covers the Medicines Australia Code, hybrid attendance, panel session formats, and venue selection alongside the recording considerations.

If you are producing a medical conference and need an AV team that understands the CPD recording requirement from the brief stage, send us the details. We scope the recording layer to the educational record standard from day one, not as an afterthought.