How should a BD rep work a life science conference?

This is the on-site part of the conference playbook: turn a pre-booked calendar into a workable route, protect meeting quality, use target-account sessions as live research, coordinate booth and floor coverage, and reset the team before the next morning. Pre-show targeting and post-show follow-up are covered in their own guides.

7 min readUpdated Jul 20, 2026

Pre-show targeting gets the right meetings onto the calendar, and post-show follow-up turns them into pipeline. This field guide covers the part between those two: running the days on-site without losing priority conversations to venue geography, booth confusion, or a schedule that looked plausible only from a desk.

Map the day to the venue
A conference calendar is not yet an executable day. Put booked meetings, booth shifts, and target-account sessions on one view, then translate each item into an exact place: hall, room, booth, hotel lobby, or partnering table. Group the route by venue zone where possible, record a mobile contact for off-floor meetings, and choose a fallback point for any location described only as "near the entrance."
This guide begins when the doors open. Building the target list and booking meetings belong in selling around life science conferences; use the conference calendar for the supported US event pages and planning details.
Protect transitions and meeting quality
Venue geography can wreck a good calendar. Leave real walking time between halls and nearby hotels, and keep a small buffer around the conversations that matter most. Before one meeting ends, check the next location and contact. End on the agreed time unless both sides explicitly choose to continue.
Decide in advance what gives when the day slips. A general session can move; a meeting with a priority account should not disappear because every item was treated as equally fixed. Notify the next contact before the start time, not after they are already waiting, and update the shared schedule so the rest of the team is not working from stale plans.
Use sessions as live account research
A target-account talk is useful because it supplies current language and context. Listen for the program or product discussed, the operating constraint the speaker names, and what appears to be changing. Those three details are more useful to a rep than a page of general session notes.
If an introduction after the talk is appropriate, reference one specific point and keep the exchange short. The goal is to establish relevance and ask for a better setting to continue, not to force a discovery call into the podium queue. Share the useful account detail with the account owner even when no conversation happens.
Run booth and floor coverage as a team
Booth duty and account work compete for the same hours, so use explicit shifts and a shared handoff channel. When a priority visitor arrives, route them to the rep who owns the account or understands the workflow. When that rep is away, capture the reason for the visit and the best way to reconnect instead of making the prospect repeat everything later.
Treat badge scans as records, not verdicts. Add enough context to distinguish a relevant account conversation from a giveaway stop: company, role, topic, fit, and owner. On the floor, ask a short qualifying question before giving the full company story. That keeps the booth useful to both the visitor and the team waiting behind them.
Reset the operation before the next morning
Finish each day with a short team reset. Reconcile which meetings happened, which moved, what was promised, and what new account context should change tomorrow's route. Assign one owner to every commitment and update the shared record while names, locations, and conversations are still clear.
Keep this reset operational. The full prioritization and outreach sequence after the show belongs in how to turn a conference into pipeline. On-site, the job is to leave the team with accurate context, explicit owners, and a schedule that is ready for the next morning.

On-site checklist

Exact meeting points, contact methods, booth shifts, and target sessions on one schedule.
Venue route grouped by zone, with walking time and priority-meeting buffers protected.
Target-account sessions captured as three facts: program, operating problem, and language used.
Booth handoff channel active, with an owner and context attached to every priority visitor.
End-of-day reset completed: commitments assigned, account notes reconciled, next-day route updated.

Where Arcova fits: Arcova tracks which of your fit-qualified accounts and contacts are exhibiting, presenting, or attending across supported events on its US life science conference calendar. On-site, that context helps a team protect target-account sessions, route priority booth visitors, and spend limited floor time on accounts it already wanted to meet.

Frequently asked questions

How many meetings should I try to book for a show?

There is no useful universal number because venue size, meeting format, booth duty, and travel between locations vary. Build a day you can actually execute: protect priority conversations, include transition time, and leave enough capacity to absorb a delay without sacrificing every meeting that follows.

Should I spend time attending talks, or is that time better spent on meetings?

Attend selectively as account research. A talk by a target contact or about a relevant program can reveal current priorities and the language the team uses. A general session with no connection to your accounts or workflow should not displace a useful meeting.

What is the best way to approach a speaker after their talk?

Keep it brief and specific. Reference one point from the talk, introduce your relevance in a sentence, and ask whether a later conversation would be useful. The queue at the podium is not the place for a full pitch.

How should I split time between booth duty and working the show?

Agree on shifts before the floor opens and protect each rep's booked meetings and target sessions. Use a shared channel for priority visitor handoffs, and designate who can leave the booth when a target account appears elsewhere in the venue.

Are badge scans worth collecting?

Yes, as a capture mechanism rather than a qualification decision. Add the minimum context while the person is present: account fit, reason for stopping, topic discussed, and owner. A scan without context should not outrank a fit-qualified conversation.

What should I do when the schedule starts slipping?

Protect the highest-priority meeting, notify the next contact early, and move or drop the lowest-priority session rather than arriving late to everything. Keep a short list of nearby fallback locations and make one person responsible for updating the team calendar.