Every sector has a version of the argument that meetings need better records, and in most of them the case for managing them as one programme has to be made from the beginning. In healthcare and pharmaceutical organisations that argument is usually already won. The compliance function has documented expectations about hospitality and engagement with external healthcare audiences, those expectations apply to meetings whether or not anyone thinks of meetings as a category, and the organisation knows it may have to evidence what happened.
What is often missing is the operational apparatus to satisfy it reliably. Requirements arrive from medical affairs, commercial teams, market access, clinical operations and communications — each with its own way of organising a meeting, its own agency relationships and its own records. The standard is shared; the process delivering against it is not.
So the framing here is narrower than elsewhere. The programme is not introduced to create governance. It exists to make an existing, externally shaped standard operationally repeatable.
What makes the meeting activity distinctive
- Mixed internal and external audiences. Ordinary internal training and meetings involving external healthcare audiences carry very different documentation expectations.
- Advisory and expert engagement. Meetings convened to gather clinical or scientific input involve contracting, attendance records and reporting defined by the compliance function.
- Congress and symposium activity. Presence around major scientific congresses generates accommodation, hospitality and logistics commitments across several teams at once.
- Investigator and study-related meetings. Clinical operations activity with its own timelines, budget holders and record-keeping requirements.
- Long retention horizons. Records may need to be retrievable years later, by people who were not involved at the time.
- Multiple agencies in play. Medical communications, congress and event agencies working alongside each other, each holding part of the record.
Why fragmentation is more expensive here
Fragmented meetings activity costs money anywhere — duplicated sourcing, unused leverage, inconsistent terms — and reducing fragmented event spend covers that.
The additional cost here is evidential. Where five teams hold their own records in their own formats, answering a question about what the organisation did, for whom and under what authorisation becomes a reconstruction exercise — slow, incomplete and happening at exactly the moment the organisation least wants to be doing it.
A single data standard applied at the point of booking is the practical answer. Not because it satisfies any particular code, which is not something a meetings programme can assert, but because the record then exists in one retrievable form whatever the compliance function needs from it. Meetings data and reporting sets out how that is built.
Design implications
Data capture
- What the environment demands
- A defined field set — purpose, audience type, attendees, authorising person — recorded at booking rather than assembled later.
- Reference
- Meetings data and reporting
Approvals
- What the environment demands
- A route reflecting whatever compliance requires for meetings involving external audiences, with the decision and decision-maker recorded.
- Reference
- Approval process
Supplier standards
- What the environment demands
- Consistent contracting and data-handling expectations rather than case-by-case negotiation.
- Reference
- Supplier management
Contracting
- What the environment demands
- Standard positions on cancellation, attrition and liability, with legal involvement defined in advance.
- Reference
- Meetings governance
Retrievability
- What the environment demands
- Records held centrally and indexed so someone who was not there can find them.
- Reference
- Meetings compliance
Duty of care
- What the environment demands
- A current answer to where attendees are, particularly for international congress activity.
- Reference
- Duty of care
| Component | What the environment demands | Reference |
|---|---|---|
| Data capture | A defined field set — purpose, audience type, attendees, authorising person — recorded at booking rather than assembled later. | Meetings data and reporting |
| Approvals | A route reflecting whatever compliance requires for meetings involving external audiences, with the decision and decision-maker recorded. | Approval process |
| Supplier standards | Consistent contracting and data-handling expectations rather than case-by-case negotiation. | Supplier management |
| Contracting | Standard positions on cancellation, attrition and liability, with legal involvement defined in advance. | Meetings governance |
| Retrievability | Records held centrally and indexed so someone who was not there can find them. | Meetings compliance |
| Duty of care | A current answer to where attendees are, particularly for international congress activity. | Duty of care |
Where sourcing still adds commercial value
It would be easy to read the above as though the whole question here is compliance. It is not. Underneath the documentation layer sits ordinary commercial activity — venues, accommodation, catering, production — bought repeatedly by teams that rarely compare notes.
The buying disciplines apply unchanged: aggregate the requirement, negotiate against the volume, hold suppliers to agreed terms, measure what was delivered. Meetings procurement and venue procurement describe that work, and none of it conflicts with a compliance framework. It simply has to operate inside one. An SMM Review is the usual way to establish what is currently happening across both layers.
Frequently asked questions
01Can you advise us on what our industry code requires for meetings?
No. We are not compliance advisers and we do not hold ourselves out as having expertise in any specific industry code. Those questions belong with your compliance and legal teams.
What we can do is design a meetings programme that records, routes and reports whatever they specify, consistently and at the point of booking.
02Our compliance team already reviews meetings. Does a programme duplicate that?
It should reduce their workload rather than duplicate it. Much compliance review time is spent chasing incomplete information from organisers; if the required fields are captured as part of the booking route, the review starts with a complete record.
03We use several agencies already. Does this replace them?
Not necessarily. A programme is a framework — one route in, one data standard, one reporting view — and specialist agencies deliver within it. What changes is that the organisation, rather than each agency, holds the consolidated record. Outsourced meetings management covers the options.
04How should meetings involving external healthcare audiences be handled differently?
As a distinct category within the programme with its own recorded fields and its own approval route, rather than as exceptions handled outside the process. Exactly which fields and which route is a question for your compliance function; the programme’s job is to apply their answer consistently.
05What about record retention?
Retention periods, data protection obligations and disclosure requirements are set by your own legal, compliance and information governance teams. The programme should meet whatever period they specify, which in practice means storing records centrally rather than in individual mailboxes.
Related reading
- 01GovernanceMeetings complianceWhat a meetings programme can evidence — and the limits of what it can claim.
- 02GovernanceMeetings risk managementContractual, financial and operational risk across a meetings portfolio.
- 03The data modelMeetings data and reportingThe field set, the reporting cycle, and capture at the point of booking.
- 04Sector noteFinancial servicesThe other environment where evidence and approval culture shape the design.