Fragment Length Analysis Requirements: Best Practices for Success

Reliable fragment length analysis is built long before a sample reaches the detector. It depends on meeting a set of concrete requirements spanning sample quality, instrument calibration, reagent integrity, and documentation. This guide lays out those requirements as best practices, framing each as a condition you must satisfy for sizing results to be accurate, reproducible, and defensible. The distinction matters because a requirement is a gate that must be passed, not a recommendation that can be traded away under time pressure. A run that skips one of these gates may still produce numbers, but those numbers carry hidden uncertainty that only surfaces later, often after downstream decisions have already been made on them. Treating each requirement as non-negotiable is what makes the difference between a result you can defend and one you merely hope is correct.

Want expert help putting this into practice? FragmentMorphology can guide you through it.

Sample requirements: quantity and quality

The single most common cause of failed runs is a sample that falls outside the usable window. Fragment length analysis requires DNA that is intact, appropriately concentrated, and free of inhibitors. Too little material produces weak signal and unreliable sizing; too much saturates the detector, distorts peak shape, and shifts apparent size.

• Concentration: measure input before loading. Aim for the linear response range of your platform rather than guessing from a bright band.
• Purity: residual salts, proteins, or organic carryover alter migration and injection. Confirm purity ratios where your quantitation method reports them.
• Integrity: degraded DNA produces smears and dropout of larger fragments. Assess integrity before committing a precious sample.
• Amplicon balance: in multiplexed PCR, unbalanced products cause some peaks to tower while others vanish; normalize inputs where possible.

Calibration and standards requirements

Related: Fragment Length Analysis: Decoding DNA Patterns for Precision.

No sizing is valid without a properly performed calibration. The requirement is an in-range, correctly assigned size standard for every run. For capillary systems this means an internal standard co-injected with each sample and validated peak-by-peak before allele calling. For gels it means a ladder chosen to bracket the expected fragment sizes with adequate resolution in the region of interest.

Best practice is to establish acceptance criteria in advance. Define the minimum number of standard peaks that must be detected, the maximum allowable deviation from expected sizes, and the action to take when the standard fails. A run whose standard is missing a marker or shows split peaks must be rejected, not rescued, because the calibration curve it produces is unreliable across the entire size range.

Instrument and reagent readiness

The platform itself imposes requirements. Capillaries and polymer degrade with use; expired polymer causes resolution loss and migration drift. Running buffer must be fresh, because depleted buffer changes conductivity and shifts every fragment's position. On gels, buffer that has been reused across many runs heats unevenly and distorts bands.

• Track capillary injection counts and replace on schedule, not after failures accumulate.
• Prepare running buffer fresh and to correct concentration; a diluted or concentrated buffer changes field strength.
• Control temperature, since migration is temperature-dependent and uncontrolled gradients skew sizing.
• Keep fluorescent dyes protected from light and within shelf life to preserve signal strength.

Meeting these readiness requirements removes a whole class of intermittent, hard-to-diagnose sizing errors.

Controls that must be present

See also: Fragment Length Analysis Checklist: Essential Best Practices for Success.

A defensible workflow requires controls on every plate or gel, not occasionally. The minimum set is a positive control of known size, a negative or no-template control, and, where the assay demands it, an allelic ladder that defines the reference bins for genotyping.

The positive control validates that the whole system, from separation through sizing software, reproduces a known answer. If it drifts outside tolerance, no sample result from that run is trustworthy. The no-template control catches contamination that would otherwise appear as a spurious fragment. The allelic ladder, in STR analysis, is what turns a raw size in base pairs into a named allele; without it, sizes cannot be binned reliably because slight platform differences shift absolute positions. A subtle but important requirement is that controls must be treated with the same rigor as samples, not run and ignored. A positive control that is glanced at but never checked against its acceptance window provides no protection at all. Build the control review into the workflow so that a failed control halts analysis automatically rather than being noticed only when a sample result looks strange.

Analysis and thresholds

Interpretation has its own requirements, chiefly the thresholds that decide what counts as a real fragment. An analytical threshold defines the minimum signal above baseline noise that a peak must reach to be called at all; anything below is treated as noise. A stochastic threshold, higher, defines the level above which allele dropout is unlikely and heterozygote calls are reliable.

Best practice is to validate these thresholds empirically for your own instrument and chemistry rather than importing numbers from elsewhere, then apply them consistently. Additional analysis requirements include filters for known artifacts:

• Stutter filters that suppress peaks one repeat unit shorter than a true allele.
• Recognition of split peaks caused by incomplete terminal nucleotide addition.
• Pull-up correction for signal bleeding between dye channels when a peak is off-scale.
• Rejection of off-scale, saturated data, which cannot be sized accurately and must be rerun at lower input.

Documentation and reproducibility

The final requirement is a record that lets any result be reconstructed and defended. This means capturing run parameters, standard performance, control outcomes, and the software settings and thresholds applied. Reproducibility is not a bonus; it is the condition that separates a research-grade measurement from an anecdote.

A practical documentation checklist:

• Record instrument, capillary or gel batch, buffer preparation date, and run conditions.
• Log the size standard used and its per-peak assignment for each run.
• Note control results and whether they passed acceptance criteria.
• Save raw data, not just processed calls, so reanalysis is possible.
• Version-control the analysis parameters so a size can always be traced to the settings that produced it.

When a borderline result appears, this record is what lets you distinguish a true finding from an instrument artifact. Treat every requirement above as a gate rather than a guideline, and fragment length analysis delivers sizes you can stand behind. FragmentMorphology's best-practice guides are structured around exactly these gates, so that meeting them becomes routine rather than reactive.