| Sequencing method | Which method will you use for my plasmid, and why? | Sanger sequencing can provide targeted reads, often around 600–900 high-quality bases per read. Short-read sequencing commonly uses reads of roughly 150–300 bases. Long-read sequencing can span longer regions; a hybrid approach combines complementary read types. | Method suitability depends on plasmid size, repeated regions, and the level of sequence confirmation required. |
| Full-length coverage | Will the report cover the complete plasmid, including the backbone? | Confirm that coverage includes the entire construct—not only the insert—and ask how gaps, low-confidence regions, and circular-plasmid junctions are handled. | Insert-only checks can miss changes elsewhere in the plasmid. |
| Depth and consensus | What minimum read depth and consensus criteria do you apply? | Ask for the guaranteed or typical depth, the consensus-generation method, and the thresholds used to flag uncertain bases. Depth targets vary by method and provider; request the actual acceptance criteria. | A stated pass/fail standard makes results easier to interpret and compare. |
| Variant detection | Can you detect small variants and mixed plasmid populations? | Confirm whether substitutions and small insertions or deletions are reported, and ask about the validated detection limit for minor variants. Do not assume a consensus sequence identifies low-frequency variants. | Detection sensitivity is distinct from producing a consensus sequence. |
| Assembly and repeats | How do you resolve repeats, homopolymers, or other difficult regions? | Ask whether the workflow uses long reads, complementary reads, or targeted follow-up sequencing when a region cannot be resolved confidently. | Repeated or low-complexity sequence can complicate read mapping and assembly. |
| Sample requirements | What DNA quantity, concentration, purity, and format do you accept? | Request written submission specifications, accepted purification methods, shipping conditions, and guidance for samples with low yield or contamination. | Clear requirements reduce delays and failed runs. |
| Turnaround and reruns | What is the current turnaround time, and what happens if a sample fails? | Get the estimated time from sample receipt to report, whether weekends or shipping are included, and the policy for no-calls, reruns, or resubmission. Timing varies with method and workload. | A quoted schedule is useful only when failure and repeat scenarios are clear. |
| Deliverables and comparison | Which files and analysis results will I receive? | Confirm whether deliverables include a consensus sequence, read files, coverage or quality information, and a comparison against a reference sequence you provide. | A reference-based comparison helps identify and review sequence differences. |
| Data handling | How are sequence data stored, shared, and retained? | Ask about access controls, data retention and deletion periods, file-transfer security, and whether data are used for purposes beyond completing the order. | These terms matter when constructs or sequence information are confidential. |
| Pricing and scope | What is included in the quoted price? | Check whether analysis, reference comparison, data delivery, shipping, and repeat sequencing are included or charged separately. | Comparing the full scope avoids relying on headline prices alone. |