The rep walks into a GP's practice, asks for Dr. Patel at the front desk, and the receptionist says he moved to another location three months ago. Nobody updated the record. The visit — forty-five minutes of driving, parking, and waiting — delivers zero value because the last person who came through didn't log the change.
That's the core failure mode in medical BD. Not bad relationships. Not poor territory coverage. Bad data hygiene on practice-level changes.
When the Referrer Record Fails You at the Door
Healthcare referrer management has one uniquely brutal characteristic: the data decays fast. Practices merge, GPs take locum positions, physiotherapists shift clinics. The referrer who sent you eight patients last quarter might now be working two suburbs away, and if nobody flagged that on the record, you're farming dead ground.
The usCBR referrers template is built as the second half of a two-library system — the referrer (practitioner-level) record linked into the practice-level library. That relationship matters more than it looks. A single GP can be associated with multiple practices, and each practice visit has its own cadence. If you're tracking visits at the practitioner level only, you're missing the site-specific context that determines whether a visit landed anything.
The Visited1 and Visited2 date fields aren't redundant — they're a primitive timeline. In a single-database system without full date-range logging, two visit timestamps let you calculate rough visit frequency without building a separate log. Combined with the FollowUp by field, you get a triage mechanism: filter by FollowUp by overdue, sorted by Amount referred descending, and you have your immediate call list.
The Fields That Separate Tracking From Intelligence
The Amount referred rating field (max 3) is deliberately coarse, and that's correct. You don't need a precise referral count here — you need a tier. High/medium/low volume tells you where to weight your time. Trying to maintain exact referral counts in a mobile CRM invites inaccuracy; a three-point scale that gets updated consistently beats a precise number that's three months out of date.
The Our impression rating (max 5) captures something that no referral count reflects: whether this practitioner is actually engaged or just occasionally cooperative. A GP who rates 4/5 on impression but 1/3 on Amount referred is a warm lead who hasn't converted yet. A 2/5 impression with 3/3 referral volume is a volume source you should protect but won't deepen. Those combinations drive different conversation strategies.
NeedsDoctorVisit as a boolean is the triage flag you set when the rep visit isn't enough. Some referral relationships require a clinical peer conversation — a company doctor having a face-to-face with the referring GP, discussing patient outcomes or clinical pathways. When you flip that flag, it surfaces in any filtered view and prevents that practitioner from falling through the cracks until the right-level visit happens.
The Deliver multichoice field — Printable, A5, Business card Iain, Personalised — is unglamorous but operationally important. When you're running a practice visit schedule across a territory, knowing what collateral each location prefers means you walk in prepared rather than handing a GP a stack of A4 leave-behinds they'll immediately recycle.
What a 200-Entry Database Tells You That 20 Doesn't
At small scale, referrer CRM is mostly memory with a backup. You know the names, you remember who sent what, you track it loosely. The system earns its value when the territory is handed over, when a second BD rep comes on board, or when the database crosses 150-200 active referrers.
At that scale, the linked practice library becomes essential. Filtering by Location lets you build route-optimised visit schedules. Filtering by NeedsDoctorVisit true gives clinical leadership an exact list for their next swing through the territory. Filtering by FollowUp by within the next 14 days, cross-referenced with Amount referred, tells you which visits actually move volume and which are relationship maintenance.
The Buscard image field pulls surprisingly heavy weight in handover scenarios. A photo of the physical business card, captured during the first visit, anchors the contact details with a visual reference. When a rep who's been working a territory for two years leaves, the incoming person can look at that card image and immediately understand the professional context — subspecialty, clinic branding, direct line — without a week of phone calls to reconstruct what should already be documented.