Technical Deep Dive: Multiplex PCR and Capillary Electrophoresis Accuracy

Accuracy in short tandem repeat profiling is more than a single number. For QA and QC leaders, it means your multiplex PCR is balanced across loci, your capillary electrophoresis sizing is precise, your allele calling is consistent, and your reporting tells a true and reproducible story. This article is a practical, audit‑ready guide to STR multiplex PCR accuracy and capillary electrophoresis, written for technical directors, lab managers, and quality leads who need reliable operations and clean, defensible results.

We emphasize concepts rather than blanket numeric cutoffs. Where a representative value helps, we'll note it as an example and recommend local validation under your ISO/IEC 17025 framework. Along the way, we point to authoritative standards and validation documents so your SOPs and reports stay aligned with expectations from SWGDAM, OSAC/NIST, NIH, and ANSI/ATCC.

---

1. What Accuracy Means in STR Work

Accuracy in STR work is a system property. It is demonstrated when the workflow—from DNA input through amplification, separation, detection, analysis, and reporting—produces concordant allele calls within known uncertainty bounds and meets acceptance criteria defined during internal validation.

1.1 Repeatability, reproducibility, and allele calling consistency

• Repeatability: Within‑run and same‑day consistency under identical conditions. In practice, this appears as stable peak heights and reproducible sizing for replicate injections on the same instrument.
• Reproducibility: Between‑run, between‑day, and cross‑instrument consistency. A robust method will yield concordant allele calls across analysts and instruments after spectral calibration and maintenance.
• Sizing precision and resolution: Precision is the standard deviation around measured fragment size; resolution is the ability to separate very close fragments and observe microvariants without crosstalk. Together, they determine whether close alleles and microvariants can be reliably distinguished.
• Allele calling consistency: Rules for analytical and stochastic thresholds, stutter handling, and heterozygote balance are applied consistently and documented in the SOP. Standards emphasize that thresholds are empirically derived for each lab and platform, not copied from kits or papers.

1.2 Where errors come from

Errors creep in at every stage:

• PCR artifacts such as stutter and occasional non‑specific products
• Sizing variance from polymer aging, temperature drift, or suboptimal internal size standard performance
• Spectral overlap and pull‑up from overloaded or poorly calibrated dye channels
• Thresholding decisions that treat noise as signal or dismiss legitimate minor alleles

These issues are well framed in OSAC/NIST validation guidance and in vendor support notes that describe common failure modes and mitigations. Standards call for determining an input window and instrument settings that minimize the combined risk of dropout, pull‑up, elevated stutter, and off‑scale saturation.

Figure 1. Sources of error across the STR workflow from sample input to reporting. Green stage boxes mark Input, Amplification, Separation, Detection, Analysis, and Reporting; blue callouts list typical risk points such as inhibitors, stutter, sizing drift, spectral overlap, and thresholding choices.

1.3 How multiplexing changes the failure modes

Multiplexing increases locus count and dye channels, raising the odds of locus imbalance, cumulative stutter burden, and spectral bleed. The method is also more sensitive to small variations in injection conditions and DNA quantity. Practically, that means your validation must characterize acceptable ranges for input mass, cycle number, injection time/voltage, and polymer condition—and your routine QC must verify that runs are inside that validated space.

---

2. Multiplex PCR Primer Design, Balance, and Artifact Control

Multiplex PCR is where accuracy is either made easy or made hard. Good primer design and locus compatibility produce clean, balanced profiles. Poorly matched loci and dyes force downstream triage and rework.

2.1 Locus selection and compatibility

Design starts with the locus set and how amplicons distribute across dye channels and size ranges. Objectives include:

• Avoiding size overlap within channels to reduce ambiguous bins and peak crowding
• Limiting secondary structures and extreme GC content that suppress amplification
• Ensuring compatibility with the intended internal size standard so the model can interpolate accurately across the STR size range

Vendor validations often show how modern kits separate loci by channel and size to preserve resolution while enabling high‑plex assays. Your internal validation confirms that this design performs on your instruments and matrices.

2.2 Balance metrics in practice

Balance has two layers:

• Inter‑locus and inter‑channel balance: No single locus or channel should consistently dominate signal or fall below interpretability across the validated input range.
• Heterozygote balance: Peak height ratio for heterozygous alleles should generally cluster within an empirically determined window across inputs and instruments. Rather than adopt universal cutoffs, validate your expected ratio distributions via replicate studies and dilution series, and set acceptance criteria accordingly.

2.3 Common artifacts you must plan for

• Stutter: The most common artifact, driven by polymerase slippage, typically appears as n−1 back stutter and less frequently as +1. Its ratio to the parent allele varies by locus and allele length.
• Pull‑up: Overloaded dye channels or poor spectral calibration create artificial peaks in neighboring channels. Reducing injection and keeping calibration current are primary mitigations.
• Non‑specific peaks: Primer‑dimers or off‑target products that may appear near the analytical threshold; robust AT selection and repeat‑analysis rules help distinguish them from true alleles.

See real‑world examples of artifacts (stutter vs true alleles) in this interpretation guide: CD Genomics' "Choosing the Right STR Profiling Partner" guide.

2.4 Automation considerations for batch‑scale accuracy

High‑throughput operations succeed on design and discipline, not heroics. Recommended practices include:

• Plate layout controls: Include positive control, negative control, and reagent blank per plate. Randomize sample positions to minimize location bias.
• Replicate strategy: Place technical replicates across plates or positions to reveal batch effects.
• LIMS logging: Record kit lot, cycle count, input quantitation, injection parameters, polymer batch, and analyst. These metadata make trend analysis and audits straightforward.

---

3. Capillary Electrophoresis and STR Multiplex PCR Accuracy: Sizing Precision and Peak Calling

Capillary electrophoresis translates fragment mixture into measurable peaks. Accuracy here hinges on the internal size standard, instrument state, injection parameters, and the rules you use to separate noise from signal.

3.1 Why the internal size standard matters

The internal size standard anchors size‑to‑migration calibration on each injection. If ISS peaks are off‑scale, distorted, or missing in segments, size calling drifts or fails. Make it routine to examine ISS peak morphology and signal range before interpreting alleles. If the ISS is not healthy, stop and re‑run—no amount of clever analysis will fix bad calibration.

Figure 2. Capillary electrophoresis workflow for STR fragment analysis. The schematic highlights injection settings, polymer matrix, the detection window, and an electropherogram inset with multicolor peaks and a size standard track.

3.2 Resolution limits and microvariants

Two questions guide resolution:

• Can the system separate close alleles and microvariants at typical signal‑to‑noise ratios?
• How stable is sizing precision across the fragment range and over routine instrument maintenance intervals?

A pragmatic way to answer both during internal validation is to design a small but informative study matrix. For example, select a panel of samples with known microvariants (or construct them via synthesized controls) that occupy crowded regions of your allele ladders. Run these across a range of validated injection times and DNA input levels, ideally capturing at least two polymer ages (fresh and near end‑of‑life). For each run, compute within‑run and between‑run size SD for those crowded regions, and record the minimum resolved base‑pair difference at acceptable SNR. If you operate multiple instruments, include cross‑instrument replicates—this often exposes subtle differences in capillary performance or oven temperature behavior.

Microvariant handling benefits from disciplined bin management. Keep your allele bins anchored to the ladder and your observed data, and document exceptions in report notes. When a peak consistently lands between bins but is reproducible and supported by ISS health and balanced peak morphology, label it as a microvariant with an explanatory note rather than force‑fitting it. Reviewers and auditors respond well to explicit, reasoned judgment calls backed by data.

Finally, remember that resolution is not a fixed constant; it's contingent on signal range, polymer condition, and thermal stability. Your validation should therefore recommend re‑injection at lower conditions when off‑scale peaks or pull‑up appear, and re‑running on a fresh polymer or after maintenance if size SDs drift beyond your acceptance envelope.

3.3 Peak detection thresholds and calling rules

Analytical and stochastic thresholds are the backbone of consistent calling. In concept:

• Analytical threshold separates noise from candidate peaks. It is derived empirically per instrument and dye channel based on baseline noise characterization.
• Stochastic threshold is set high enough that heterozygote dropout is unlikely for single‑source samples. It is derived from dilution and replicate studies.

In practice, pair these thresholds with supporting logic:

• A repeat‑analysis rule for just‑above‑AT minor peaks in crowded regions (re‑inject once before excluding or calling).
• A heterozygote‑balance review step for peaks straddling ST (examine PHR across loci, not just at the suspect locus).
• A stutter‑model check where software or SOPs compute whether a minor peak's height and position are consistent with expected stutter rather than a true allele.

Document how you determine thresholds, and ensure your report template exposes any exceptions or analyst overrides with justifications. Many labs now complement fixed thresholds with probabilistic genotyping or semi‑continuous models that incorporate stutter and dropout probabilities—especially for mixtures and challenging matrices—while keeping single‑source authentication workflows simple and transparent.

---

4. Quality Controls and Reporting Outputs That QC Teams Want

Accuracy becomes defensible when QC signals are clear and reports are complete. The controls you run and the way you summarize outcomes determine how quickly you can accept a run—or detect and correct a problem.

4.1 Controls that anchor each batch

• Positive control: Verifies amplification, separation, and calling rules under known conditions.
• Negative control and reagent blank: Detect contamination introduced during setup or reagents.
• Ladder and ISS integrity checks: Confirm proper channel separation and sizing performance.

4.2 Run‑level checks before you interpret results

• Signal window: Peaks should sit within the validated range—neither so low that stochastic effects dominate nor so high that pull‑up and off‑scale distortion appear.
• Off‑scale monitoring: If ladder or ISS peaks clip, expect downstream sizing or bleed issues; re‑inject at lower conditions.
• Spectral calibration currency: Calibration must be current and verified; otherwise, channel bleed will masquerade as alleles.

Figure 3. Run‑level QC acceptance checklist for CE‑STR workflows. Key items include controls passing, healthy signal window, no off‑scale ISS/ladder, current spectral calibration, expected heterozygote balance, modeled stutter bounds, clean negatives, and complete report metadata.

4.3 Report outputs that speed review and audits

A concise report structure improves trust and throughput. Consider including the following fields in your standard output table and summary notes.

Two short examples illustrate how this helps in practice:

• Example 1—Borderline minor peak: Report shows a 60 RFU peak at a known stutter position with modeled expectation of 65±20 RFU given the parent height. The narrative notes that a re‑injection produced the same minor peak within bounds; the call remains an artifact and is excluded. This is immediately auditable and reproducible.
• Example 2—Microvariant near bin edge: Report documents consistent sizing at 0.6 bp above the common allele, healthy ISS, and balanced heterozygote peaks. The allele table labels a microvariant and includes a brief note; reviewers can trace decisions without additional emails.

If you prepare grant‑facing or journal‑facing summaries, align wording with NIH reproducibility expectations and ANSI/ATCC authentication practices so reviewers recognize that your STR methods are validated, documented, and repeatable.

---

5. When Results Look Wrong A Troubleshooting Playbook

The moment something looks off—a flat locus, a forest of minor peaks, or a microvariant that refuses to size correctly—speed matters. Here's a structured way to decide whether to re‑inject, re‑amplify, or go back to extraction.

5.1 Weak signal or apparent dropout

First, confirm quantitation and inhibition. If inputs are low or inhibitors are suspected, dilute and re‑amplify within your validated cycle and input ranges. Check injection parameters; a small increase in injection time or voltage, still within your validated window, can restore interpretable peaks. Inspect heterozygote ratios across loci: widespread imbalance points to input or polymer issues rather than a single problematic locus.

5.2 Overloaded signal or saturated peaks

If peaks are off‑scale or bleed into other channels, lower injection time or concentration. Confirm that spectral calibration is current. Look closely at the internal size standard and ladder—if either shows clipping, re‑inject at lower conditions before interpreting sample profiles. Pull‑up should subside in the repeat if overload was the root cause.

5.3 Unexpected alleles and how to respond

Refer to NIH and ANSI/ATCC guidance on authentication and reporting for contamination/drift diagnosis steps: Refer to NIH and ANSI/ATCC guidance on authentication and reporting for contamination/drift diagnosis steps.

Differentiate among three categories quickly:

• Artifact: A minor peak at a known stutter position that fits your modeled expectations. Check stutter ratios and confirm with replicate analysis when the decision affects reporting.
• Contamination or mixture: Non‑stutter extra alleles across multiple loci, often at variable heights and inconsistent with single‑source expectations. Negative controls become decisive here.
• Sample swap: A clean, strong profile that does not match expectation or prior records. Trace via LIMS metadata and re‑run confirmed aliquots.

Document the decision path in your report notes, including any re‑runs performed and acceptance criteria used.

5.4 Re‑extract, re‑amplify, or re‑run CE

A simple decision path works well under audit. Think of it like a traffic‑light system:

• Red—Calibration or ladder/ISS failure: Stop interpretation. Re‑inject at lower parameters if off‑scale, or re‑run after restoring spectral calibration or replacing polymer/capillary.
• Yellow—Low signal or imbalance: Consider re‑amplification with adjusted input or cycles within your validated bounds, or a cleanup/dilution step to relieve inhibition. Re‑inject at a slightly higher time/voltage if your validation matrix supports it.
• Green—Artifact‑consistent profile with clean controls: Proceed with reporting but include narrative notes about stutter modeling or microvariant handling. If a decision hinges on a borderline peak, perform one confirmatory re‑injection to lock down repeatability.

Tie each color to your SOP page numbers and validation study sections so analysts can cite the exact rule when documenting corrective actions.

---

A practical note on services and workflow fit

In many labs, authentication and contamination checks run alongside other characterization assays. When outsourcing portions of the workflow, choose partners who publish acceptance criteria, share validation summaries, and return analyzable data with full metadata. For example, a service provider that performs multiplex STR amplification with capillary electrophoresis and provides allele tables, peak heights, and interpretation notes aligned to recognized standards can slot into your traceability model with minimal friction. For direct service details, see CD Genomics — Cell Line Identification by STR and consult the sample submission guidelines for packaging and minimum input requirements before onboarding.

---

Author

Yang H. — Senior Scientist, CD Genomics; University of Florida.

Yang is a genomics researcher with over 10 years of research experience in genetics, molecular and cellular biology, sequencing workflows, and bioinformatic analysis. Skilled in both laboratory techniques and data interpretation, Yang supports RUO study design and NGS‑based projects.

References:

1. Ludeman MJ, Koen J, Budowle B, et al. Developmental validation of GlobalFiler PCR amplification kit. Forensic Science International: Genetics. 2018;35:173–182. DOI: 10.1016/j.fsigen.2018.10.002. Open access summary: Developmental validation of GlobalFiler PCR amplification kit
2. Scientific Working Group on DNA Analysis Methods (SWGDAM). Interpretation Guidelines for Autosomal STR Typing by Forensic DNA Testing Laboratories. 2017. Accessible via the official publications index: SWGDAM Publications
3. OSAC/NIST. Best Practice Recommendations for the Internal Validation of Human STR Profiling on Capillary Electrophoresis Platforms. Draft document, accessed 2026. Best Practice Recommendations for Internal Validation of Human STR Profiling on CE Platforms
4. NIST. OSAC 2021‑S‑0003 Standards for Determining Analytical and Stochastic Thresholds and Their Application. 2023. OSAC 2021‑S‑0003 standard page
5. Thermo Fisher Scientific. Fragment Analysis Support and Troubleshooting for CE Platforms. Accessed 2026. Fragment Analysis Support Center
6. National Institutes of Health (NIH). Authentication of Key Biological and/or Chemical Resources. Notice NOT‑OD‑17‑068. 2017. NIH Grant Notice NOT‑OD‑17‑068
7. ANSI/ATCC. Overview of ASN‑0002 Standard for Human Cell Line Authentication by STR. Accessed 2026. ANSI/ATCC ASN‑0002 overview
8. ATCC. Standards and Controls Portal. Accessed 2026. ATCC standards and controls
9. NIST. DNA Mixture Interpretation Scientific Foundation Review. NIST IR 8351. 2024. NIST IR 8351 PDF

Related Services

• Cell Line Identification by STR
• Microsatellite Genotyping Service
• Multiplex PCR Sequencing
• Genomic Data Analysis
• Next Generation Sequencing
• Bioinformatics Services
• Sanger Sequencing