The core challenge of forensic molecular biology is not memorizing the extraction-to-electrophoresis pipeline — it is deciding what a DNA profile means when the data are incomplete or ambiguous. Build your D-ABC-MB review around interpretation: classify every peak in a mock electropherogram as allele, stutter, pull-up, or artifact, then justify which statistical framework your assumptions allow. Work paper scenarios the way casework does, and treat thresholds as laboratory-validated values rather than universal constants. This guide gives you two worked scenarios, a peak-reading exercise with a rubric, a decision table, and an adaptable preparation sequence.
Stutter, Pull-Up, and Artifacts: Classify Peaks Before You Interpret
Interpretation begins with classification. Before assigning alleles to any contributor, distinguish true alleles from stutter products, pull-up peaks, dye blobs, and baseline noise, using validated locus-specific thresholds rather than visual impressions.
Learn the signature of each artifact type. Stutter arises from polymerase slippage during PCR and typically appears one repeat unit shorter than its parent peak, at a fairly predictable percentage for each locus and chemistry. Pull-up is spectral bleed-through: an oversized peak in one dye channel pulls a spurious peak into another channel at the same scan number. Dye blobs from unincorporated fluorophore appear as broad, off-ladder peaks in fixed positions. Each has a recognizable fingerprint once you have annotated enough profiles.
Worked scenario: in a duplicate injection, a small peak appears one repeat below a 12,000 rfu parent peak at an STR locus, and the analyst calls it a minor-contributor allele because it reproduced in both injections. The mistake: reproducibility does not override stutter expectations — one repeat below a strong peak is exactly where stutter occurs. The better decision is to calculate the stutter percentage, compare it with the validated stutter threshold for that locus and chemistry, and examine peak morphology. If the ratio falls below threshold, the peak is annotated as stutter, keeping an invented contributor out of what is actually a single-source profile.
- Stutter: one repeat shorter than a parent peak; percentage compared against the laboratory's validated locus-specific threshold.
- Pull-up: same scan number as an oversized peak in a different dye channel; removed by spectral correction or flagged.
- Dye blob: broad, off-ladder, appears near known positions for the chemistry; does not repeat like an allele.
- Noise: low-level irregular peaks without positional consistency across injections or replicates.
From Swab to Profile: Name Every Step and Its Failure Points
Trace the workflow aloud: collection and preservation, extraction, quantitation, PCR amplification of STR loci, capillary electrophoresis, and genotyping. Each stage has distinct failure modes that shape what later interpretation can claim.
Collection and preservation determine what the chemistry receives: wet items degrade DNA and encourage microbial growth, so drying and appropriate storage matter, and documentation of handling underpins the chain of custody. Extraction concentrates and purifies DNA; for sexual assault samples, differential extraction separates sperm cells from epithelial material, and knowing when it was used explains why a fraction is male-dominated. Quantitation with a human-specific assay then reports not just amount but often degradation and inhibition indicators, which forecast amplification problems.
Amplification targets STR loci with fluorescently labeled primers; inhibitors or degraded template produce the classic warning signs — locus dropout, imbalanced heterozygotes, and general signal loss across an electropherogram. Capillary electrophoresis separates fragments by size and the software calls alleles against an allelic ladder. Practice explaining why degraded samples show a declining signal gradient from small to large amplicons, and why inhibited samples may fail at specific loci rather than uniformly. Connecting each failure mode to its upstream cause is what turns a list of steps into working knowledge.
Mixtures: Match the Statistic to Assumptions the Data Support
For mixed profiles, the reported statistic must match the assumptions the data can defend: exclusion probabilities when contributor sets are clear, or likelihood-ratio reasoning when contributor number or dropout is uncertain.
The combined probability of exclusion (CPE) and combined probability of inclusion (CPI) treat the observed alleles at a locus as the complete set against which a random person is compared. That assumption fails when a contributor's alleles may have dropped out: unobserved alleles widen the pool of possible contributors, and an exclusion probability computed anyway overstates the strength of the evidence. Likelihood-ratio frameworks, including validated probabilistic genotyping systems, model dropout and contributor number explicitly instead of assuming them away.
Worked scenario: a two-person assault sample shows a clear major profile and a low-level minor. The analyst computes a CPI across all loci, treating every detected peak as a potential contributor allele — including low-template loci where the minor's alleles plausibly dropped out. The mistake: CPI presumes the profile is complete for the contributors included. The better decision is to restrict the statistic to loci where the minor's profile appears complete under the laboratory's validation, deconvolute and report the major contributor separately, or apply the laboratory's validated probabilistic genotyping system while documenting the assumptions. Why it matters: the number in the report must survive cross-examination about exactly what was assumed.
Drop-In, Drop-Out, and Contamination: Reading What the Data Cannot Show
Stochastic effects at low template amounts cause allelic dropout, while sporadic drop-in alleles appear with no contributing source. Recognizing which loci are affected determines how much of a profile the report can rely on.
Dropout means one or both alleles of a true contributor failed to amplify, most often at low template amounts where stochastic amplification dominates; related indicators are heterozygote imbalance and complete locus loss. Drop-in is the reverse: a spurious allele appears without a corresponding source, typically as an isolated low-level event. Both concepts feed directly into interpretation limits — a heterozygous contributor may look homozygous at a dropout-affected locus, which is precisely why statistics that ignore dropout can misrepresent the evidence. Keep the vocabulary distinct: dropout is missing true signal, drop-in is added false signal.
Controls are how the data reveal what should not be there. Reagent blanks and negative controls monitor for contamination introduced during processing; a positive amplification control confirms the chemistry worked. Practice the reasoning, not just the definitions: if an artifact appears in a blank, the question is which samples in the batch are affected and how the laboratory's procedures require that to be handled and documented. The consistent habit is recording what the control shows and acting within validated procedures — never quietly subtracting an unexplained peak because it is inconvenient for the interpretation.
Validation and QA Vocabulary: Developmental, Internal, and Routine Controls
Distinguish developmental validation, which establishes a method's reliability, from internal validation, where a laboratory demonstrates the method works in its own hands — plus the routine controls that monitor continuing performance.
Developmental validation is the foundational demonstration that a method detects its targets reliably: sensitivity studies across template amounts, precision and accuracy studies, mixture studies, and population studies supporting the statistics. Internal validation is what each laboratory performs before casework use, confirming the method behaves as published on that laboratory's instruments, with its staff and its sample types, and establishing the laboratory's own operational values. The distinction matters because a published kit study does not by itself define what another laboratory's thresholds should be.
Quality assurance then keeps a validated method valid in routine use: reagent lots checked with controls, instrument maintenance and calibration, proficiency testing of analysts, technical review of case files, and corrective action when something drifts. Practice narrating the chain: a validated method produces data, controls confirm the batch behaved, technical review confirms the conclusions follow from the data, and documentation ties every step together. If you can explain why a laboratory's validated threshold cannot simply be borrowed from another laboratory's published number, you understand the framework rather than the vocabulary.
Use the table below to test whether you can place each activity in the right category and state the question it answers.
| Activity | Who performs it | Core question it answers |
|---|---|---|
| Developmental validation | Method developer or originating laboratory | Does the method reliably detect its targets across sensitivity, precision, and mixture conditions? |
| Internal validation | Each laboratory, before casework use | Does the method perform as expected on our instruments, with our staff and sample types? |
| Proficiency testing | Individual analysts, on a recurring basis | Can this analyst produce correct results under test conditions? |
| Reagent blanks and negative controls | Analyst, with each processing batch | Did contamination enter during processing? |
| Technical and administrative review | Second analyst or supervisor | Do the conclusions follow from the data and the laboratory's procedures? |
A Peak-Reading Exercise With a Self-Check Rubric
Practice on paper electropherograms: label every peak, compute stutter percentages and heterozygote balances, and state what each locus supports. Score yourself against a rubric, not a feeling of familiarity.
Construct or obtain mock electropherogram panels from teaching materials, or simulate profiles by assigning allele calls and adding plausible artifacts. For each panel, annotate every peak with a label and a one-line rationale: allele, stutter, pull-up, dye blob, or unexplained. Expected observations to verify: pull-up peaks share a scan number with an oversized peak in another dye; stutter sits one repeat below a parent peak at a modest percentage; dye blobs are broad, off-ladder, and appear near fixed positions for the chemistry; genuine alleles align with the allelic ladder. Then compute heterozygote balance per locus and flag any locus where dropout is plausible for a low-level contributor.
Score the completed work against this rubric and repeat with a fresh panel until the observations hold. A self-check score here is a learning milestone, not a prediction of any exam outcome or a laboratory competency determination — its purpose is to show you whether your classification reasoning is explicit or still improvised.
- Correctly classifies at least 90% of pre-labeled peaks, with a mechanism-based rationale for each.
- Computes stutter percentages and heterozygote balances and compares them with stated, clearly labeled practice thresholds.
- Identifies every locus where dropout is plausible and states its effect on which statistics would be defensible.
- Separates what belongs in a report (supported conclusions) from what belongs in annotations (artifacts and observations).
An Adaptable Eight-Week Sequence and Readiness Checks
Sequence review from fundamentals to interpretation to legal context: two weeks on DNA structure and function, two on the analytical workflow, two on mixtures and statistics, one on QA and validation, one on legal and ethical considerations.
Weeks one and two: DNA structure, replication, and the logic of STR markers, ending with drawing the workflow from memory. Weeks three and four: the analytical pipeline — collection and preservation, extraction including differential extraction, quantitation, PCR, and electrophoresis — with notes on each stage's failure modes. Weeks five and six are the center of gravity: mixture deconvolution and statistics, working repeated paper scenarios like those above until classifying peaks and choosing a defensible framework feel routine. Week seven covers validation categories, controls, and documentation; week eight covers objectivity, ethics, expert testimony foundations, and reporting.
Adapt the proportions to your own background: an experienced analyst may compress the workflow weeks and extend mixtures and validation. Finish by auditing yourself against the readiness checks below; treat unmet items as the map for a second pass. Administrative details of the credential — application, testing arrangements, and recertification — are maintained by the American Board of Criminalistics, so verify current requirements directly with the issuer rather than relying on any summary, including this one.
- You can explain PCR, STR structure, and electrophoretic separation without notes.
- You can classify every artifact type on an unfamiliar paper profile and justify each call.
- Given a scenario with stated assumptions, you can name the defensible statistic and why alternatives overstate or understate the evidence.
- You can distinguish developmental from internal validation and describe what each establishes.
- You can outline how objectivity, documentation, and validated-procedure limits shape a report and testimony.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.