
A guide to the iGEM DNA construct workflow
How an iGEM team runs its DNA construct workflow: pick a part standard, choose an assembly method, order DNA, document builds for the wiki and learn each cycle.
Updated October 2026.
Picture a team in August: a part was ordered with the wrong overhang, the plasmid map lives on one student's laptop, and by wiki freeze nobody can say which construct was tested. Settling the workflow before the first order prevents all three.
What does an iGEM DNA construct workflow look like from start to finish?
An iGEM DNA construct workflow is a loop of four stages: design the construct, build it, document what you did, and test it so the result shapes the next design. Most teams run it several times per project.
- Design. Decide the parts, their order and the junctions between them.
- Build. Choose an assembly method, get the DNA, assemble and verify it.
- Document. Record every design, reaction and result in a form a teammate (or a judge) can follow.
- Test and learn. Measure the construct, record the outcome next to the design, and decide what to change.
This is the design-build-test-learn cycle (DBTL) used across synthetic biology, and iGEM judges look for it directly. The Engineering Success criterion for a Silver medal asks a team to go through at least one iteration of the engineering design cycle on a technical part of its project, so a written record of each pass is evidence, not overhead.
What lab software do iGEM teams use to design and document DNA constructs?
iGEM teams use a sequence editor to design constructs, an electronic lab notebook to record the work and the team wiki to publish it, and TeselaGen Community puts the editor, a shared parts library and the notebook in one free workspace. You need each of these jobs covered:
- A sequence editor to view plasmid maps, annotate features, search for restriction sites and simulate digests or assemblies.
- An electronic lab notebook (ELN) for protocols, reaction records, gel images and results, with a history of who changed what.
- A parts and sequence library so every student works from the same, current sequences instead of emailed files.
- The team wiki, where the polished version is published.
What decides the setup is whether a design, its assembly steps and its results stay linked. Every handoff between separate tools (map to spreadsheet, spreadsheet to notebook, notebook to wiki) is a place where a version goes missing. Read more about DNA construct design for iGEM teams.
How should you design parts and choose a standard?
Pick a part standard early, because it fixes how every junction in the project will look. BioBrick RFC10 and iGEM Type IIS (RFC1000) are the iGEM Registry's de facto assembly standards, and any part you want considered for medals or awards must be compatible with one of them, whatever method you use to build it.
- BioBrick (RFC10). Each part sits between a fixed prefix and suffix of restriction sites (EcoRI and XbaI before, SpeI and PstI after), so any two parts join through the same cut-and-ligate steps. The trade-off is a short scar sequence at every joint, which matters inside coding regions.
- iGEM Type IIS (RFC1000). Built on Golden Gate and following the MoClo and Loop standards. Type IIS enzymes cut outside their recognition site, so the site leaves the product. Level 0 parts are released with BsaI, which leaves a 4-base overhang at each junction, and Level 1 transcription units are flanked by SapI, which leaves a 3-base overhang for the next level. iGEM's DNA Distribution kits are now mostly Type IIS Level 0 parts, so a new team gets the most reuse from this standard.
- Overlap-based design (Gibson). Fragments carry matching ends and need no grammar, which suits one-off constructs. A part you build this way still has to be RFC10 or RFC1000 compatible to count toward medals and awards.
Whatever you choose, apply the same habits. Keep each part a clean, annotated sequence with a defined start and end. Remove internal sites the standard rules out: an RFC1000 part must not contain BsaI or SapI sites (this is called domestication). Keep a single naming scheme from day one, because renaming parts after the wiki is half-written is a painful afternoon. For the part-level detail, read our guide to designing a Golden Gate assembly.
Which assembly method should a beginner team choose?
Choose Golden Gate when you have standardized parts and several fragments, and choose Gibson assembly when you have a few longer fragments you want to join without a standard. A beginner team can start with one method and add the second later.
- Golden Gate (iGEM Type IIS) suits a project built from a part library: promoters, coding sequences, terminators and backbones that you will recombine many times. It also matches the parts in the Distribution kit.
- Gibson assembly suits a small number of long fragments, a one-time edit to an existing plasmid, or a junction that must match your sequence exactly without designing around fixed overhangs.
- BioBrick assembly joins two parts per step and leaves scars, but RFC10 is still one of the Registry's two standards, so many existing parts and their documentation use it.
The methods also combine, for example Golden Gate for transcription units and Gibson to join larger modules. Our guides to designing a Gibson assembly and designing a Golden Gate assembly cover each method step by step.
How do you get the DNA: order it, amplify it, or both?
Order synthetic fragments for sequence you have no template for, and PCR-amplify the pieces you already have. Synthesis is the route for new DNA, such as a codon-optimized coding sequence, so check each synthesized design against the vendor's sequence rules on repeats and GC content. PCR is cheaper and faster for existing parts, and the primers add the overhangs your assembly needs.
In 2026, IDT offered teams that registered with it up to 40 kb of free gene fragments, and Twist offered every team 20 kb of free DNA as gene fragments or clonal genes. Both 2026 offers closed in October: IDT's last order day was October 12 (US time) and Twist's last claim day was October 20. Plan your largest fragments around next season's vendor offers, if they return, and claim them once registration opens.
Each primer needs an annealing region that matches the template, plus any tail that carries a restriction site or overlap. Write the tail layout down once, reuse it, and check melting temperatures before ordering. Our guide to designing PCR primers for cloning walks through the rules.
Finally, plan verification before you build. Decide which colony PCR, diagnostic digest or sequencing reads will confirm each construct, and note them in the design. A construct that was never verified is a hypothesis, not a part.
How do you document builds so they are ready for the wiki?
Document at the moment of the work, in the same place as the design, using a fixed record for each construct. A wiki assembled from clean records takes hours rather than days.
A useful construct record holds:
- The final annotated sequence and map, with the version that was actually built.
- Each part and its source.
- The assembly method, the enzyme or master mix, and the date and person who ran it.
- The primers and fragments used, linked to their order records.
- Verification results, such as gel images and sequencing alignments, including failures.
Registry Contributions (new parts, collections, documentation or characterization added to the iGEM Registry) are one of the 2026 competition deliverables, and documenting a part in the Registry is one way to meet the Bronze criterion of a useful contribution for future teams. Keep your own parts in a registry-style table from the start, with a stable ID, a one-line function, the sequence and a link to the characterization data, and check RFC10 or RFC1000 compatibility while you design each part rather than at submission time. Keep failed attempts too, with the reason you think they failed.
What is a simple checklist for a first iGEM construct?
A first construct needs nine checks, run before each new construct and again before your wiki freeze:
- State the question the construct answers, in one sentence.
- Pick the part standard and assembly method for the whole project.
- Annotate every part and remove the internal sites your standard rules out.
- Simulate the assembly and read each junction in the result.
- Check any synthesized fragment against the vendor's sequence rules.
- Design primers with the same tail layout every time.
- Plan the verification step, such as a diagnostic digest or sequencing.
- Record the construct, its map and its results together in the notebook.
- Update the parts table and the wiki draft the same week.
How do you design and document iGEM constructs in TeselaGen Community (free)?
You design constructs, prepare DNA orders and document builds in one workspace in TeselaGen Community, the free edition for individual researchers, academic labs and small teams. It includes the sequence editor and parts library, Gibson and Golden Gate assembly design with an assembly protocol for each design, primer design, the ELN and the TeselaGen CoScientist AI assistant.
PCR, USER and other assembly methods, multi-level (hierarchical) designs, inventory, workflow management, lab automation and the Discover machine learning modules are Enterprise only.
- Invite your team and add your parts. Invite teammates to your workspace, then import or create sequences in the library, annotate them, and use the sequence editor to find cut sites such as BsaI or SapI before a part goes further.
- Build a design. Lay out the positions of your construct, add the parts for each, and pick Gibson or Golden Gate. For Golden Gate, choose the Type IIS enzyme; TeselaGen designs the junction overhangs, and you can specify them for parts prepared by digest. If a position has several candidates, add them as options for that position.
- Validate and submit. TeselaGen checks the design, then generates an assembly protocol that lists the oligos, PCR reactions, assembly pieces and finished constructs.
- Order. Build orders for IDT (oligos and double-stranded DNA fragments) and Twist (DNA fragments and clonal genes) in TeselaGen, then submit them to the vendor.
- Record the build. Write the work in a notebook entry linked to the design, and export entries as PDF for the wiki.
Start in the free Community edition.
How do you test and learn from each cycle?
Close the loop by writing the result beside the design, then asking what the data changes. Compare the construct you intended with the one you verified, then the measured behavior with your prediction. If a result is surprising, check the build record first, since a wrong junction or a mixed-up plasmid explains many odd results before biology does.
Keep each cycle small. One change per construct makes the outcome interpretable, and keep the raw files with the construct record. By the third cycle, a team with tidy records reuses its own parts, primers and notebook templates, and has its Engineering Success evidence already written.