Speaker and advisory agreements are the highest-volume contract type most life sciences compliance functions handle. A mid-size commercial organisation may execute several thousand in a year, each one small in value, each one broadly similar, and each one carrying obligations that a reviewer can test individually.
That combination is what makes the category difficult. Volume pushes the work toward templates and delegated signing authority, which is sensible. Scrutiny pulls it toward documented approvals and retained evidence, which is also sensible. Where the two are not reconciled in the operating model, the outcome is a large population of executed agreements whose supporting evidence lives in email threads and event folders.
The agreements themselves are usually well drafted. Legal teams have refined this template for two decades and the clauses are rarely the weak point. What fails is the surrounding record, which is the same pattern seen in quality agreement obligations that go untracked: a sound document whose commitments nobody converted into work with an owner and a date.
The obligations inside a standard template
A typical speaker agreement creates obligations on both sides. Reading them out of the template and recording them as fields is the step that turns the document into something manageable, because a field can carry a due date, an owner and a status while a paragraph cannot.
- Execution before performance, meaning a fully signed agreement dated before the first engagement rather than countersigned in the week after.
- Fee and expense terms, tied to an approved rate schedule with defined caps on travel, accommodation and meals.
- Content control, requiring the use of approved materials only, with no off-label discussion and no speaker-generated slides.
- Engagement limits, capping the number of programmes and the aggregate annual payment to a single healthcare professional.
- Disclosure and reporting cooperation, obliging the speaker to accept that payments will be disclosed under applicable transparency rules.
Of these, execution before performance is the one that produces the most findings and the one that is easiest to fix. It fails because the commercial calendar runs ahead of the contracting cycle: an event is booked, a speaker is confirmed verbally, and the paperwork follows. Making the signed agreement a precondition of event scheduling, enforced in the system that books the event rather than by policy alone, removes the problem at source. The objection is always that it will slow the commercial calendar, and in the first quarter it does. After that the lead time simply moves earlier and the exception volume drops to the handful of genuinely urgent cases, which is where a documented override belongs.
Annual caps fail when each brand team counts its own engagements. The same healthcare professional may speak for three products in a year and sit within the limit for each one while breaching the aggregate. Count at the individual level across every brand, business unit and affiliate.
Building a fair market value position you can defend
Fair market value is the second recurring finding, and it is largely a documentation problem rather than a pricing one. Companies usually pay reasonable rates; they cannot always show how the rate was derived, and a reviewer who cannot follow the derivation treats the figure as unsupported regardless of how reasonable it looks. Five practices make the position defensible.
- Band the rates. Define tiers by credential, specialty, years of practice and delivery format, rather than negotiating a figure per engagement.
- Record the source. Name the benchmark data or internal methodology behind each band, with the date it was adopted and the approver.
- Separate preparation from delivery. Paying distinct rates for preparation hours and delivery time makes the fee traceable to effort.
- Require justification for exceptions. Any rate outside the schedule needs a written rationale and a second approval stored with the agreement.
- Refresh on a fixed cycle. Review the schedule annually so rates do not drift from the market, and retain superseded versions for historical engagements.
A five-step control roadmap
Step 1, Inventory the agreement population
Pull every speaker, advisory board and consulting agreement from the last two years into one register with speaker identity, brand, execution date, first engagement date and total paid. The gap between execution and first engagement is the first metric worth reporting.
Step 2, Load the approved rate schedule
Publish the banded schedule as reference data that the contracting workflow reads, rather than as a document people are expected to consult. Rates then default into the agreement and exceptions become visible as exceptions rather than as ordinary variation.
Step 3, Enforce signature before scheduling
Make a fully executed agreement a system precondition for confirming a speaker on an event. The control has to sit in the event workflow, because that is where the commercial pressure is applied and where a policy reminder is most easily overridden.
Step 4, Aggregate caps at the individual level
Maintain one record per healthcare professional that accumulates engagements and payments across brands and affiliates, and alert the compliance owner as a threshold is approached rather than after it is crossed. This is the control that most often needs a system rather than a process.
Step 5, Reconcile transfers of value at period close
Match the transfer-of-value dataset to the accounts payable ledger every period, investigate differences while the underlying detail is still fresh, and keep the reconciliation as evidence. Corrections made at the close are routine; corrections made after filing are not.
Manage HCP agreements as live obligations
Rate schedules, caps, approvals and transfer-of-value evidence held on the agreement record.
Where the evidence has to live
A review question is rarely about the template. It is about one named healthcare professional, one date, and whether the company can produce the agreement, the rate derivation, the approved materials, the attendance record and the payment entry in a form that ties together. When those artifacts are spread across a contract repository, an event management tool, a medical review system and an expense platform, assembling them takes days per engagement, and the company's answer looks weaker than its underlying compliance actually is. Holding the obligations and their evidence pointers on one record changes the economics of every review, in the same way that it does for GxP supplier qualification evidence.
Obligations, owners and evidence
The table sets out the core obligations with the function that should own each one and the artifact that closes it. Owners are deliberately split between commercial, compliance and finance, because concentrating them in compliance alone removes the ability to act.
| Obligation | Control point | Owner | Closing evidence |
|---|---|---|---|
| Agreement executed before engagement | Event scheduling gate | Commercial operations | Executed agreement with both dates |
| Fee within approved schedule | Contract creation | Compliance | Rate band reference or exception approval |
| Approved materials only | Medical and legal review | Medical affairs | Approval record and material version |
| Annual engagement and payment caps | Individual speaker record | Compliance | Running totals across brands |
| Transfer-of-value reporting | Period close reconciliation | Finance | Reconciliation between dataset and ledger |
None of this reduces the volume of agreements, and it is not meant to. The objective is that each one leaves behind a complete record as a by-product of being executed, so the compliance function spends its time on the engagements that look unusual rather than on reassembling the ones that do not. Programmes that reach that state typically report a sharp fall in the hours spent preparing for internal audit, and a smaller but more useful effect, which is that commercial teams stop treating the compliance step as a negotiation.
For related guidance, see The quality leader’s guide to quality agreement management, The quality leader’s guide to CDMO quality agreements and The sponsor’s guide to CRO master service agreements.
