Sample Submission Guidelines
Build edited iPSC clones with sequencing-supported QC from the start
Gene editing in induced pluripotent stem cells can support disease modeling, isogenic control generation, functional genomics, and drug discovery model development. But an edited iPSC project is rarely just an editing task. Your team also needs clone-level validation, sample tracking, sequencing evidence, and a clear QC plan before downstream experiments begin.
Our iPSC gene editing and quality control solution is designed to help you plan the project as one connected workflow. We help you think through the editing goal, target sequence, donor template, screening strategy, target-site validation, optional genome-wide QC, and report-ready deliverables before cells or extracted DNA enter the project.
What this solution helps you answer
- Is my iPSC line suitable for the planned editing goal?
- Should the project use a KO, KI, point mutation, correction, or reporter strategy?
- Is a donor template needed?
- Which clones carry the intended edit?
- Is Sanger confirmation enough, or should amplicon, targeted, or whole-genome sequencing be added?
- What QC outputs are needed before downstream disease modeling, differentiation, or functional studies?
The goal is to help your team move from "we need an edited clone" to "we understand which clone is better supported by sequencing and QC evidence."
Why edited iPSC projects need more than target-site confirmation
Target-site confirmation is important, but it may not be enough for every edited iPSC project. A clone can appear correct by a short PCR or Sanger readout while still requiring deeper review for allele status, larger on-target events, donor insertion structure, copy number changes, or other genome-wide QC signals.
That does not mean every project needs the same QC depth. It means QC should match the purpose of the edited clone. A quick exploratory knockout screen may not need the same evidence package as a high-value isogenic disease model or a clone intended for long-term downstream differentiation studies.
We help you define that QC depth early, so the final results are easier to review and easier to use.
Our service capabilities for edited iPSC projects
We support edited iPSC projects as integrated design, validation, sequencing, QC, and reporting workflows. Depending on project scope, our team can help with editing strategy planning, clone screening logic, target-site validation, sequencing-supported QC, and bioinformatics interpretation.
Editing goals we can help plan
- Gene knock-out for loss-of-function modeling
- Knock-in or reporter insertion
- Point mutation introduction
- Disease-associated mutation correction
- Isogenic control generation
- Donor-template-supported editing
- Clone-level genotype validation
- Sequencing-supported QC before downstream research
For each project, the editing goal should be linked to a validation strategy. A knockout clone may require allele-level indel interpretation, while a knock-in or reporter insertion may require junction validation and donor sequence confirmation.
Clone screening and validation modules
- Candidate clone collection and tracking
- Clone expansion status review
- Target-site genotyping
- Sanger or amplicon sequencing where appropriate
- Targeted sequencing for higher-resolution edit review
- Donor insertion or junction confirmation
- Clone comparison table
- QC flagging and report notes
These modules help your team compare clones in a structured way rather than reviewing scattered files.
Sequencing-supported QC and reporting options
For selected projects, sequencing-supported QC can go beyond the target site. Depending on the study goal, optional add-ons may include off-target candidate review, whole-genome sequencing-supported QC, CNV/SNV/SV analysis, or large on-target event review.
For related services, see our CRISPR Editing Analysis with NGS, CRISPR Off-Target Validation Sequencing, and CRISPR Sequencing pages.
Choose the right editing and QC strategy for your iPSC line
There is no single QC plan that fits every edited iPSC project. The right strategy depends on the editing goal, donor design, clone number, downstream use, and how much genomic context your team needs.
| Strategy | Main Question | Best-Fit Editing Goal | Validation Method | QC Depth | Limitation |
|---|---|---|---|---|---|
| Knockout | Was the target gene disrupted? | Loss-of-function iPSC model | Sanger, amplicon sequencing, or targeted sequencing | Target-site validation and clone comparison | May need allele-level interpretation |
| Knock-in | Was the donor sequence inserted correctly? | Reporter insertion, tag insertion, functional sequence addition | Junction PCR, amplicon sequencing, or targeted sequencing | Donor insertion and junction review | Donor design affects screening complexity |
| Point Mutation | Was the intended base change introduced? | Disease mutation modeling | Amplicon or targeted sequencing | Allele-level confirmation | Low-frequency edits require careful clone screening |
| Mutation Correction | Was the disease-associated variant corrected? | Isogenic control generation | Target-site sequencing and clone comparison | Target-site and allele status review | Additional QC may be needed for high-value clones |
| Reporter Insertion | Was the reporter inserted in-frame and at the correct site? | Reporter iPSC line | Junction validation and sequencing | Target-site plus downstream expression planning | Does not replace cell-state QC |
| WGS-Supported QC | Are broader genomic changes present? | High-value clone review before downstream studies | Whole genome sequencing and bioinformatics | Genome-wide review, CNV/SNV/SV context where applicable | Not always required for every research clone |
For target-site validation, Targeted Region Sequencing may support focused review. For broader genome-wide assessment, Whole Genome Sequencing can be considered when the project requires deeper QC.
Start with the edit you need and the downstream experiment you plan to run. If the edited clone will be used for early exploratory work, target-site validation and clone comparison may be enough. If the clone will support disease modeling, isogenic control studies, or long-term differentiation experiments, a deeper QC package may be useful.
A donor-template project should include donor design review and junction confirmation. A point mutation or correction project may need allele-level sequencing. A clone intended for broader downstream use may need genome-wide QC or off-target candidate review.
We help you choose the level of validation that fits the research goal, without turning every project into an unnecessarily heavy workflow.
Sample-to-report workflow with clone-level QC checkpoints
Our workflow connects editing design, clone screening, sequencing validation, and QC reporting. Each step is designed to reduce uncertainty before the project moves to the next stage.
Step 1: Project intake and editing goal review
We start by reviewing target gene or genomic region, editing type, iPSC source and cell-line background, donor template or construct information where applicable, downstream research use, desired validation depth, number of clones to screen, and expected deliverables.
This step helps us define whether the project needs target-site validation only, clone comparison, off-target candidate review, genome-wide QC, or a combined package.
Step 2: Editing design, guide RNA, and donor template planning
The editing design should match the intended result. Knockout projects may focus on creating frameshift or disruptive indels. Knock-in and reporter projects require donor template planning and junction validation. Point mutation or correction projects require careful sequence-level confirmation.
At this stage, guide RNA, donor template, target sequence, and screening logic are reviewed together. This helps reduce the risk of designing an edit that is technically possible but hard to validate later.
Step 3: Delivery, recovery, and monoclonal screening
The delivery and recovery plan depends on the iPSC line and editing strategy. iPSC lines can be sensitive to editing stress, single-cell handling, and clone expansion. Monoclonal screening helps separate candidate clones and allows each clone to be reviewed independently.
Once clones are available, sample identity, clone labeling, expansion status, and DNA availability become important QC checkpoints.
Step 4: Target-site validation and clone comparison
Target-site validation checks whether the intended edit is present. Depending on the project, this may include Sanger sequencing, amplicon sequencing, targeted sequencing, junction confirmation, allele-level review, or donor insertion support.
Clone comparison brings the results together. Instead of looking at each clone in isolation, your team can compare genotype, edit pattern, zygosity, donor insertion status, QC flags, and sequencing quality in one table.
Step 5: Genome-wide QC, bioinformatics, and final deliverables
For selected projects, additional QC may include whole-genome sequencing-supported review, off-target candidate validation, CNV/SNV/SV analysis, or large on-target event review. Bioinformatics analysis organizes these results into tables, visual summaries, and report notes.
The final deliverables may include edited clone information, sequencing data, QC summaries, clone comparison tables, figures, and analysis notes.
Sample and project information requirements
Sample needs depend on whether your team requests editing design, clone validation, sequencing-only QC, genome-wide review, or a combined package. The table below uses CD Genomics sample submission guidance as the baseline for nucleic acid and cell submissions. Final requirements should be confirmed during project review.
| Input Type | Recommended Material | Quality Check | Container or Format | Shipping or Submission | Notes |
|---|---|---|---|---|---|
| Existing iPSC line or frozen cells | Project-specific; for general cell submission, CD Genomics guidance lists cell input at 1×106 cells | Cell identity, viability, passage history, mycoplasma status if available | Cryovial or approved frozen-cell format | Dry ice | Used for editing feasibility review or DNA/RNA extraction planning |
| Edited iPSC clones / cell pellets | Project-specific; sufficient cells for genomic DNA extraction and clone validation | Clone identity, sample labeling, expansion status, DNA yield after extraction | Cryovial or cell pellet tube | Dry ice | Used for target-site validation, clone comparison, and QC review |
| Extracted genomic DNA for target-site or clone validation | For focused DNA sequencing projects, use the assay-specific requirement; WES/WGS-style short-read inputs commonly start from ≥500 ng gDNA | OD260/280 close to 1.8-2.0; RNase-treated; no obvious degradation or contamination | DNase-free tube; DNase-free water, elution buffer, or 10 mM Tris pH 8.0 | Ice packs | Useful for targeted sequencing, clone validation, or focused QC |
| Extracted genomic DNA for WGS-supported QC | WGS: recommended ≥500 ng, minimum 200 ng, minimum concentration 10 ng/µL; PCR-free WGS: recommended ≥1 µg, minimum 500 ng, minimum concentration 20 ng/µL | Concentration by fluorometry when possible; if using Nanodrop, higher input may be needed | DNase-free tube | Ice packs | Used when broader genome-wide QC is needed |
| Extracted genomic DNA for long-read structural review | PacBio WGS: ≥3 µg, 80 ng/µL; Nanopore WGS: ≥5 µg, 20 ng/µL | High molecular weight DNA, low degradation, adequate purity | DNase-free tube | Ice packs | Consider when long-range structural context is important |
| Purified amplicon for focused validation | Amplicon sequencing: recommended ≥1 µg, minimum 500 ng, minimum concentration 20 ng/µL | Single expected product if applicable; concentration and purity check | Low-bind or DNase-free tube | Ice packs | Useful for target-site, donor junction, or clone-level confirmation |
| Editing design files | Target gene, reference sequence, gRNA, donor template, plasmid map, clone list | Sequence accuracy and sample ID consistency | FASTA, GenBank, spreadsheet, plasmid map, or project sheet | Electronic submission | Needed before method review and reporting setup |
CD Genomics also asks customers to submit a completed sample submission form, keep sample names consistent between the form and sample labels, and provide electronic QC data when available. Samples in 1.5 mL centrifuge tubes should be sealed carefully; cells and frozen samples should be shipped with dry ice.
Bioinformatics analysis and deliverables
Bioinformatics helps turn sequencing data into clone-level QC evidence. It is especially important when your project includes amplicon sequencing, targeted sequencing, off-target candidate validation, WGS-supported QC, or multiple clone comparisons.
Minimum deliverables
- Editing design review notes where included
- Sample and clone-level QC summary
- Target-site validation summary
- Allele or indel profile where applicable
- Clone comparison table
- Sequencing QC summary
- Candidate off-target validation table where included
- Genome-wide QC summary where WGS is included
- CNV/SNV/SV review outputs where applicable
- Final report notes
For custom analysis and reporting, see our Bioinformatics services.
Optional add-ons
- Amplicon sequencing analysis
- Targeted off-target candidate validation
- Whole-genome sequencing-supported QC
- CNV/SNV/SV analysis
- Large on-target deletion or insertion review where suitable
- Donor insertion junction analysis
- Clone ranking or clone selection summary
- Custom figure-ready visualization
- Pipeline parameter record
For broader off-target assessment, see our CRISPR Off-target Discovery and CRISPR Off-Target Validation pages.
A strong report should help your team compare clones, not only archive sequencing files. Useful outputs may include clone-level summary tables, target-site plots, donor junction evidence, off-target candidate tables, genome-wide QC figures, and final interpretation notes.
This is especially helpful when the edited iPSC line will support disease modeling, drug discovery, or long-term downstream experiments.
Application scenarios for iPSC editing and QC
These application scenarios show how edited iPSC clones can support downstream research when editing design, clone screening, and sequencing-supported QC are planned together.
Disease model and isogenic control generation
Edited iPSC lines are often used to model disease-associated variants or generate isogenic controls. In these projects, target-site validation, clone comparison, and optional genome-wide QC can help your team select better-supported clones before differentiation or functional assays.
Drug discovery model development
Drug discovery programs may use edited iPSC-derived models to study disease mechanisms, pathway response, or compound effects. A clear QC package helps reduce uncertainty before the edited line is used in larger screening or assay development work.
Functional genomics and mechanism research
Knockout, knock-in, reporter, and point mutation iPSC models can support functional genomics and mechanism studies. A sequencing-supported validation plan helps ensure that the observed phenotype is linked to the intended edit as much as possible.
Regenerative medicine research support
For regenerative medicine research, edited iPSC lines may need deeper clone-level and genome-wide review before downstream experimental use. We can help plan QC depth based on research goals while keeping the interpretation within a research-service scope.
Demo results: what an edited iPSC QC package may include
Demo results help your team understand what a final QC package may look like. These examples show common output formats when they match the project design.
Demo 1: Target-site editing confirmation
A target-site confirmation output can show whether the intended edit is present. Depending on the method, this may include sequence traces, amplicon sequencing summaries, indel profiles, donor junction evidence, or allele-level edit tables.
This helps your team move beyond "edited or not edited" and review the exact sequence-level result.
Demo 2: Clone screening and genotype comparison
Clone comparison is useful when multiple candidate clones are available. A report may compare clone ID, genotype, allele status, edit pattern, expansion status, donor insertion support, and QC flags.
This makes it easier to decide which clones should move forward into deeper QC or downstream assays.
Demo 3: Genome-wide QC and off-target review summary
For higher-value edited iPSC projects, genome-wide QC or off-target review may be added. A summary may include candidate off-target sites, CNV/SNV/SV findings where applicable, genome-wide QC notes, and figure-ready summaries.
The goal is not to overstate what QC can prove. The goal is to provide a stronger research evidence package for clone review.
FAQ: planning an iPSC gene editing and QC project
1. Can you work with my existing iPSC line?
Yes. We can review your existing iPSC line, editing goal, available cell information, and QC needs before project setup. Useful information includes cell source, passage history, culture status, mycoplasma status if available, and downstream use case.
2. What editing types can this solution support?
This solution can support planning for knockout, knock-in, point mutation, mutation correction, reporter insertion, and isogenic control projects. The exact workflow depends on target sequence, donor template, cell-line condition, and validation goals.
3. Do I need monoclonal screening?
If your team needs a stable edited iPSC clone for downstream studies, monoclonal screening is usually important. It allows individual clones to be genotyped, compared, and selected based on clone-level evidence.
4. Is Sanger sequencing enough for edited iPSC validation?
Sanger sequencing may be useful for initial target-site screening, but it may not be enough for every project. Amplicon sequencing, targeted sequencing, off-target validation, or WGS-supported QC may be useful when allele-level resolution or broader genomic context is needed.
5. When should WGS be added to edited iPSC QC?
WGS may be considered when a clone will support high-value downstream studies, isogenic disease modeling, long-term differentiation, or projects where genome-wide context is important. It is not required for every edited clone.
6. What sample or project information should I provide?
Useful information includes target gene, editing type, iPSC source, donor template, guide RNA information, target sequence, clone list, available gDNA QC data, desired deliverables, and downstream research use.
7. Can you compare multiple edited clones?
Yes. Clone comparison can include genotype, allele status, target-site edit pattern, donor junction support, QC flags, sequencing quality, and report notes. This helps your team decide which clones should move forward.
8. What bioinformatics outputs can be included?
Outputs may include target-site validation summaries, indel or allele profiles, clone comparison tables, candidate off-target validation tables, CNV/SNV/SV review where applicable, genome-wide QC notes, and final report summaries.
9. Can this solution support disease modeling or isogenic control projects?
Yes. Edited iPSC lines are often used in disease modeling and isogenic control research. We can help plan the editing and QC strategy so that clone-level evidence supports downstream research review.
10. What deliverables can be included?
Depending on project scope, deliverables may include edited clone information, sequencing data, target-site validation results, clone comparison tables, bioinformatics outputs, QC summaries, and final report notes.
Case Study: deeper QC can reveal hidden defects in CRISPR-edited iPSCs
Open-access literature case
Journal: Stem Cell Reports
Published: 2022
DOI: 10.1016/j.stemcr.2022.02.008
Background
This open-access study examined a key quality concern in CRISPR-edited iPSC projects. Human iPSC lines are widely used for disease modeling and isogenic control generation, but edited clones can carry unexpected on-target changes that are difficult to detect with short PCR and Sanger sequencing alone.
The study is relevant to this solution because it shows why edited iPSC QC may need more than a simple target-site check, especially when clones will support important downstream experiments.
Methods
The authors evaluated 27 iPSC clones generated after CRISPR/Cas9 editing across 9 genomic loci in 4 genes. These clones had initially appeared correctly edited based on short PCR and Sanger sequencing.
To look deeper, the study used quality control assays including allele copy number quantitative genotyping PCR and sequencing of nearby heterozygous SNPs. The goal was to identify large on-target events and loss-of-heterozygosity patterns that could be missed by standard validation.
Results
The study found that 33% of the edited iPSC clones had acquired large on-target genomic defects, including insertions and loss of heterozygosity. Importantly, all of these defects had escaped standard PCR and Sanger sequencing analysis. The publication reports that 8 out of 27 clones showed lower allele copy number by qgPCR, and one additional clone showed a copy-neutral loss-of-heterozygosity pattern through nearby SNP analysis.
Figure 2 presents allele copy number assessment in edited iPSC clones. It includes the qgPCR assay concept, allele copy number results across 27 clones, nearby SNP analysis, and a donut chart summarizing correctly edited clones versus clones with unwanted monoallelic editing.
Figure 2 from the open-access study shows how allele copy number assessment can reveal edited iPSC clones with hidden on-target defects that escaped standard screening.
Conclusion
This study supports a practical lesson for edited iPSC projects: a clone that looks correct by standard target-site screening may still require deeper QC depending on the research goal.
For a service project, this means the QC plan should be defined early. Target-site validation, clone comparison, off-target review, and genome-wide QC should be selected based on how the edited clone will be used.
Reference
