Anti-Doping Case Management Software: When Chain of Custody Has to Survive a Hearing Panel

Why anti-doping programmes break the tools they are given

The moment that decides whether your programme is credible happens two years after the test. A hearing panel is asked whether the sample in question was collected, sealed, stored and transported in a way that leaves no room for doubt. Your evidence is a paper doping control form, a courier tracking number in an email, a temperature log that someone photographed, and a chaperone's recollection of how long the athlete was observed before the notification was signed. If any link in that chain is missing, the science stops mattering.

ADAMS is the system of record for whereabouts filings, test results and results management data exchange, and it does that job because the Code requires it. What it is not is an operations platform for your organization. It does not plan your test distribution against a risk model you own, it does not schedule your doping control officers or pay them, it does not hold your intelligence with proper separation from case handling, and it does not assemble the evidence bundle you hand a panel. So programmes fill the gap with spreadsheets, a shared drive, WhatsApp for mission coordination, and a compliance manager who is the only person who understands how it all connects.

Across compliance and evidence heavy projects we have delivered, the failure pattern in this domain is consistent. Missions planned in a spreadsheet that nobody can reconstruct six months later. Whereabouts strikes issued late because a filing failure was noticed at quarter end. And an arbitration file assembled by hand over three weeks, from four sources, by the one person who cannot be replaced.

Problem 1: the test distribution plan is a risk model kept in a spreadsheet

Under the International Standard for Testing and Investigations, testing has to be planned rather than random, informed by an assessment of the doping risks in each sport and discipline. Which means somewhere in your organization there is a model: physiological demands of the discipline, competition calendar, historical adverse findings, athlete performance progression, intelligence, and the mix of in competition and out of competition, urine and blood, standard menu and specific analysis.

That model almost always lives in a spreadsheet built by a single analyst. It cannot be queried, it cannot be audited, and the reason a particular athlete was tested three times in a quarter while another was not tested at all exists only as a memory. When your programme is reviewed, or when an athlete's counsel asks whether the testing was targeted improperly, a spreadsheet is a weak answer.

What a build should include is the plan as a governed object. Risk factors are named and weighted, athletes carry a computed risk score with the inputs visible, coverage is tracked against plan by sport, discipline, testing pool and analysis type, and every deviation from the plan is recorded with a reason and an approver. Then a quarter's testing can be explained, on a screen, in a sentence. It also lets you see the thing spreadsheets hide, which is systematic under coverage: the discipline nobody has tested out of competition in 14 months because it never came up in a planning meeting.

Problem 2: whereabouts strikes are a legal clock, and you have to prove notice

Athletes in a registered testing pool file whereabouts including a daily 60 minute time slot, and under the Code three whereabouts failures within a 12 month period, whether filing failures or missed tests, constitute an anti-doping rule violation. That is a career level consequence built out of administrative steps, and every one of those steps has to be provable.

The proof burden is what software usually ignores. A missed test is not just a doping control officer reporting that nobody answered the door. It is the attempt itself, with time, location and what the officer did during the slot, followed by a notice to the athlete, an opportunity to respond, a review by someone who was not the officer, and a decision with reasons. The 12 month window rolls, so a strike expiring next Tuesday changes the athlete's status without anyone doing anything.

What a build must include: an attempt record captured in the field with a timestamp that the officer cannot backdate, a notification workflow with delivery evidence, a response window with a countdown, a reviewer separate from the collector, and a rolling window calculation that shows each athlete's live strike position and what expires when. Filing failures should be detected automatically at the deadline rather than found during a quarterly sweep. Every one of those artefacts is what makes the strike stand up later, and assembling them retrospectively from email is how strikes get abandoned.

Problem 3: chain of custody is evidence, and a log is not evidence

Between the athlete sealing a sample and the laboratory logging it in, the bottle passes through a collection officer, a transport container, a courier, sometimes a border, and a receiving desk. Each handover is a fact you may need to prove. Most programmes prove it with a paper form, a courier tracking screenshot and good faith.

The distinction that matters is between a log you can edit and a record you cannot. If a chain of custody entry can be amended without trace, opposing counsel will say so, and they will be right to. What the build needs is append only capture: each custody event written once with the actor, the timestamp, the location and the sealed kit codes, corrections made as new entries that supersede rather than overwrite, and the whole chain hashed so any alteration is detectable. Kit code and sample code scanning rather than typing, because a transposed digit is the kind of error that ends a case. Temperature and integrity observations captured at handover with photographic evidence attached to the event, not to a folder.

The payoff is concrete. When a hearing asks for the custody record, you produce a single sequence for that sample code, generated in seconds, with attachments in place. Programmes that can do this settle arguments that programmes with a folder of scans have to fight.

Problem 4: a testing mission is field logistics with a contract workforce

A no advance notice mission at an athlete's home at 6am is a small operation. Someone assigns an officer with the right accreditation and gender requirements for the collection, checks conflicts of interest with that athlete's club or region, gets the kit inventory to the right place, arranges a chaperone if the sport needs one, and confirms the officer actually went. Afterwards the officer submits expenses and gets paid, usually as a contractor, sometimes across borders.

This is workforce management with compliance attached, and it is normally run by email and phone. What it costs you is not only administration. It is coverage: the mission that did not happen because the only available officer was six hours away and nobody saw it in time to reassign.

A build should hold officer accreditation with expiry, sport and language capability, geographic base, conflict declarations, availability, and kit stock by location with lot numbers so a recall on a collection kit lot can be traced to every sample it touched. Assignment then respects constraints rather than relying on the coordinator remembering them. Officers work from a mobile interface that functions with no signal in a stairwell, because 6am at a residential address is exactly where connectivity fails, and the doping control form has to be completable and signable offline with sync afterwards.

Problem 5: intelligence and results management must be separated by design

Programmes increasingly act on information: a whistleblower, a customs referral, a pattern in an athlete biological passport, a tip from another organization. That material is sensitive, sometimes attributable to a person at real risk, and it must not leak into the case file of an unrelated athlete or into the hands of staff who have no need to see it.

A single shared case management inbox cannot express that. What is needed is compartmentalisation as a design feature: intelligence records held separately with their own access control and source protection, a controlled path by which intelligence informs the test distribution plan without exposing the source, and a results management workspace where only the case handlers, the reviewing panel and the athlete's disclosed material live. Access logging that shows who opened what, permanently, protects your staff as much as the athlete.

Therapeutic use exemptions belong in the same conversation. They contain medical records, they are decided by a panel that must be independent of the testing operation, and they have to be retrievable at the moment a laboratory reports a finding for the substance in question. A shared drive of PDFs fails that test in every direction.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this shape prices as follows. A focused first release covering the test distribution plan with risk scoring, mission assignment and officer management, offline field capture of the doping control form, and append only chain of custody through to laboratory dispatch runs $80,000 to $170,000 and ships in 14 to 20 weeks. A full platform adding an athlete whereabouts application, officer scheduling and payment, therapeutic use exemption workflow with panel review, intelligence handling with compartmentalisation, results management through to hearing, and reporting into global systems runs $200,000 to $500,000 phased over 8 to 14 months.

What drives cost up in anti-doping specifically: multi jurisdiction operation, because sanction rules, privacy law and language requirements multiply. Integration and data exchange with global reporting systems, which is a specification exercise with a testing calendar you do not control. Laboratory interfaces, since each accredited laboratory has its own result delivery format. Athlete biological passport data handling, which is a different analytical shape from pass or fail results. And the athlete facing app, which sounds simple and is not, because whereabouts filing is the most legally consequential form your athletes will ever complete on a phone.

What keeps cost down: building the operations core first and leaving the athlete app to phase two, since athletes can continue filing in the mandated system while your internal workflow gets fixed.

Build versus buy, and when buying is the right call

Do not build if your programme is small. A federation testing a few dozen athletes a year, using an external service provider for collections, working almost entirely in competition, should operate inside ADAMS and a well kept set of procedures. The money buys more tests, and more tests is a better anti-doping programme than better software.

Build when two or more of these are true. You plan and justify your own test distribution rather than executing someone else's. You manage a network of collection personnel directly, with accreditation, conflicts and payment to control. You handle results management through to hearing and have had a case turn on documentation rather than science. You receive and act on intelligence and currently have no structural separation between that material and general case handling. Or you operate across sports and jurisdictions where rules genuinely differ and a single process cannot express both.

The tipping point is evidentiary. A programme whose credibility rests on paper forms and one person's institutional memory is carrying a risk that grows with every case it brings. That is the argument for a build, and it is a board level argument, not an IT one.

How to choose a developer

Ask them how they would make a custody record tamper evident. You want to hear append only storage, superseding corrections rather than edits, hashing, and a rendering that a non technical panel can read. If they describe an audit table that an administrator can update, they have not built evidence systems and your case file will be attackable.

Ask them to model the rolling 12 month whereabouts window on a whiteboard, including what happens when a strike expires overnight and when an athlete moves between testing pools. It is a small piece of logic that exposes immediately whether they understand the domain or are pattern matching on generic case management.

Ask what they have shipped that works offline with a signature and a photograph, and what happens when the device is lost before sync. A doping control officer at 6am has no tolerance for a spinning icon and neither does the eventual hearing.

Ask how they will separate intelligence from case handling in the permission model, and how source protection is enforced rather than promised. If the answer is user roles, keep looking.

Ask who owns the code and settle it in writing before kickoff. You should hold the repository, the hosting accounts and the right to bring in another firm. At Digital Heroes the client owns the code from the first commit, and for an organization whose independence is the product, being unable to leave a vendor is a governance problem, not just a commercial one.