Before an outbreak has a curve, a map, or a hypothesis, it usually has a line list — a running, case-by-case table that a field team builds and updates by hand, often in nothing more sophisticated than a spreadsheet. It is easy to overlook because it looks so plain next to a case report form or a laboratory database, but in field epidemiology it does something neither of those tools does well: it lets a small team see the whole outbreak, one row at a time, as it is still unfolding.
What a Line List Actually Is
A line list is organized the opposite way from most medical records. Instead of one detailed file per patient, it puts every case on its own row and every variable of interest in its own column, so the entire outbreak can be read across the sheet rather than dug out file by file. Each new row is a new case; each new column, if the investigation needs it, is a new question the team wants answered about all of them at once. That structure is what makes a line list useful for something a case report form is not built for: scanning dozens or hundreds of cases at a glance to see who is getting sick, where, and when.
The Variables That Belong in It
Guidance from WHO and CDC field epidemiology training converges on the same underlying logic: a line list should describe each case in terms of person, place, and time, plus enough administrative and laboratory detail to keep the record usable as the investigation matures. In practice that means a working line list typically carries:
- Administrative fields — a unique case ID, interviewer name, questionnaire status, and a case-classification field (suspect, probable, confirmed, or ruled out).
- Person — age, sex, and residence or camp/settlement location.
- Time — date of symptom onset, date of report, date of specimen collection, and date of outcome.
- Clinical course — presenting symptoms (often one column per symptom, marked present or absent), hospitalization status, and outcome (recovered, died, still under care).
- Laboratory data — pathogen or organism, specimen type, and result, added as confirmation comes back.
- Exposure fields — whatever the emerging hypothesis calls for: a water source, a market stall, an index-case contact, a specific ward or shift.
- A free-text notes column for anything that does not fit a fixed field but might matter later.
None of this is fixed. A line list is deliberately built and rebuilt as the investigation’s questions change — a column for a suspected food exposure gets added once a foodborne hypothesis emerges, and a column that turns out not to discriminate between cases gets dropped. That flexibility is a feature, not a gap in rigor.
Line List or Case Report Form? Different Jobs
The two tools are often confused because they capture overlapping information, but they serve different purposes. A case report form is a detailed, standardized questionnaire completed once per patient — the depth needed to generate and test a hypothesis about what caused the outbreak. A line list is the summarized, constantly updated view across every case at once, built for speed rather than depth. WHO field guidance treats these as complementary rather than competing: teams are expected to use standardized case investigation forms for depth on individual cases, and a line list to keep a real-time view of the outbreak as a whole.
Why It Matters More, Not Less, in Low-Resource Settings
In a well-resourced surveillance system, much of this aggregation happens automatically inside a case-management database. A field team working an outbreak in a low-resource setting rarely has that luxury, and the line list becomes the substitute for it. Built in an ordinary spreadsheet on a laptop that may not have reliable power or connectivity, it is the tool a small team can actually maintain under field conditions: fast to update after a day of interviews, easy to review by anyone on the team without special training, and immediately usable for the two things an investigation needs earliest — a rough epidemic curve and a first read on who is affected. The tradeoff is discipline. A line list with inconsistent date formats, duplicate case IDs, or fields left blank because no one owned data entry stops being a summary and starts being noise, right at the point in an outbreak when a clear signal matters most.
Reading the List, Not Just Keeping It
A line list earns its place in an investigation only if someone is actually reading it as it grows — sorting by onset date to watch the curve take shape, filtering by location to see whether cases are clustering, checking for the missing values that mean a field interviewer needs a follow-up call. Used that way, it is less a record than a working instrument: the plainest tool in field epidemiology, and often the one that tells a team, before the laboratory results or the formal report ever arrive, what kind of outbreak it is actually looking at.