1.1 Overview

1. Please upload a photo or two of your lab to the iGEM 2018 server (include your team name in the file name), preferably showing the relevant safety features and paste the link here:

2. Describe the goal of your project: what is your engineered organism supposed to do? Please include specific technical details and names of important parts.

(Even though your project might change, please describe the main project idea you are working on right now. See the example answers for help.)

Describe your project
This part of the form is for you to tell us about your primary project idea, what organisms and parts you will use and what your project will do. We know that iGEM teams often change project topics during the competition. When you change your primary project idea, please update this form to tell us about your new idea! If you are still working on multiple project ideas by June 29, you may choose one to describe on this form. If there are major changes to your project after June 29, please contact the Safety and Security Committee by emailing safety AT igem DOT org.
How will your project work?

1.2 Identifying possible risks

iGEM has developed a Risk Assessment Tool to help you identify possible risks to you, your colleagues, communities, or the environment. We encourage you to use this tool before filling in this part of the form. What are you using / planning to use? Some organisms and parts present risks beyond what is ordinary for lab work in synthetic biology. As your project progresses, you should consider the risks presented by each organism and part you plan to use.

3. Which whole organisms, including viruses, are you planning to use or using in your project?

Please provide as much detail as possible (such as strain information). If you are not using an organism, please note this.

4. What risks could these organisms pose to you or your colleagues, or to your community or the environment if they escape the lab?

If you are not using an organism, please note this.

5. Check all species you are using as a chassis in your project.

What is your chassis organism?
For the purposes of iGEM, a chassis is the organism in which you are putting your parts, or which you are modifying in your project. Many teams will use a common lab organism as a chassis. Some teams may use a more exotic organism. Some project may not involve a chassis.

• Escherichia coli (give names of all strains you are using)
• Yeast (Saccharomyces cerevisiae)
• Lactobacillus spp.
• Bacillus subtilis
• Others (give species names)
• No chassis organism (please comment)

Comments:

6. What risks could your chassis pose to you or your colleagues, or to your community or the environment if they escape the lab?

If not using a chassis organism, please note this.

What parts are you making or planning to make?
This part of the of the form is for you to tell us about the parts you are planning to make or have developed during your project. It summarises information that might already have been submitted through Check-in forms. If you submitted a Check-In form for an organism or part, you should still include it in this section. You may omit non-protein-coding parts (except if they are known virulence or anti-microbial factors – you should undertake a literature search to determine if they are), and you may omit parts that were already in the Registry if you are using them without significant modifications. For more information on virulence factors see the Safety Policy page and the White List. If there are major changes to your project after June 29, please contact the Safety and Security Committee by emailing safety AT igem DOT org.

7. As part of your project, are you are planning to make / have made new parts or substantively changed existing parts in the Registry.

• Yes (All relevant new or revised parts should be described on a spreadsheet)
• No

8. Part information is submitted in a spreadsheet.

Please visit this page to download a blank copy of the spreadsheet for this question. (If you need a CSV version instead of XLSX, visit this page.)

Instructions for parts spreadsheet: Remember to change the filename of your spreadsheet! Put your team's name in place of "TeamName".

A. Species name (including strain): For an organism, give the scientific name of the species. Include a strain name or number (such as "K-12" for E. coli K-12) if there is one. For a part, give the name and strain of the organism that the part originally came from.

B. Risk Group: Give the Risk Group of the organism in column A. You may use a categorization according to your home country, according to the USA, or according to the WHO. If the organism falls into an 'in-between' or special category such as 2+ or 2-Agricultural, explain this category in the Notes column. If you cannot find any Risk Group categorization for this organism, write "N/A" and explain in the Notes column. (Multicellular organisms generally do not have a Risk Group.)

C. Risk Group Source: Cite the source from which you obtained the Risk Group information. See Risk Group Guide for recommended sources. If you got the information from the Canadian PSDS, from the NIH Guidelines, or from the DSMZ catalogue, you may simply write "PSDS", "NIH", or "DSMZ". Otherwise, please give a web link or a full citation for your source.

D. Disease risk to humans: Does this organism cause any disease in humans? If yes, what disease does it cause?

E. Disease or other risks to the environment: Does the organism cause plant or animal diseases or would in any other way pose a risk to the environment if accidentally released?

F. Part number/name:For a part: If it has a Registry part number (like BBa_XXXXX), write that number. If it has no Registry part number, give a short name for the part. (For example: "Actin", "Alcohol Dehydrogenase".) For a whole organism, leave this column blank.

G. Natural function of part: For a part: Briefly describe what the part does in its parent organism. (If it is an enzyme, what reaction does it catalyze? If it is a receptor, what molecules does it bind to? Etc.) For a whole organism, leave this column blank.

H.How did you acquire it: Describe how you acquired the organism/part. If you have not acquired it yet, describe how you plan to acquire it. (For example: did you receive the part DNA from another lab? Did you order the part DNA from a synthesis company? Did you use PCR to isolate the part from genomic DNA of its parent organism? Did you order the cell line from a company?)

I. How will you use it: Describe how you are using the organism/part in the lab. (For example: "This organism is our chassis." "This part senses when the cells are exposed to glucose." "This organism is the source for a part that we are isolating by PCR." "This part produces the toxin which our bio-sensor is designed to detect.")

J. Notes: Use this column to give any additional information that is necessary.

Upload Spreadsheet Please do not change the "Destination Filename"! [File:TeamName Safety2018 Spreadsheet.xls] You may upload multiple versions of your spreadsheet, using the same Destination Filename. The wiki software will keep track of different versions, and list them in chronological order.

9. What experiments will you do with your organisms and parts?

Please explain briefly. Please include the names of species / cell lines / strains. This includes the origins of parts taken from other organisms, even if they are being synthesized rather than isolated from nature – you need not include any parts already in the registry. We are particularly keen to understand the boundaries or scope of your project. If you are not conducting any experiments, especially on grounds of safety, security or as a responsible scientist / engineer, please note this. Examples might include, making sure you only use non-pathogenic strains of an organism, deciding that animal use experiments are not yet warranted, or avoiding plant infection experiments because the affected plant is found in your country.

Example answers
"Our bacteria is meant to live on plant leaves, so we will test them on tobacco (Nicotiana benthamiana) in a lab greenhouse."
"We want to use a protein from ants, but its sequence is unknown. So we will capture ants (Camponotus spp.) to extract DNA and RNA to find the sequence of the protein we want."
"Our bacteria need to interact with human cells for a medical application. We will test them in human cell culture using the HEK293 cell line."
“We are interested in a RNA-binding protein expressed in Kluyveromyces lactis. We have found the sequence in a paper and will have it synthesized by a provider.”

10. What risks could arise from these experiments?

For example, could they produce aerosols making it more likely that you could inhale something? Or are you using needles and could accidentally stick yourself? Could you produce something that is not inactivated using standard lab protocols? If you are not conducting any experiments, please note this.

11. Imagine that your project was fully developed into a real product that real people could use. How would people use it?

What risks would there be is your project was fully developed?
Check all appropriate boxes and expand in the comments section. (Note: iGEM teams should not release modified organisms into the natural environment but you could imagine such a release if your project was fully developed.)

• Our project is foundational / we do not have a specific real-world application in mind (Examples: library of standardized promoters, system for communication between cells)
• Only in the lab (Examples: reporter strain for measuring the strength of promoters)
• In a factory (Examples: cells that make a flavor chemical for food, cells that make biofuel)
• In a consumer product that ordinary people buy (Examples: cells that clean your clothes, bread made with engineered yeast)
• In agriculture / on a farm (Examples: cells that guard against pests, engineered rice plants, cells that promote growth of crop plants)
• In a small enclosed device (Examples: a bio-sensing strip with cells that detect arsenic)
• In the natural environment (Examples: cells that remove pollution from lakes, engineered forest trees that can resist drought)
• To be used in the human body, or in food (Examples: anti-cancer bacteria, bread made with engineered yeast, engineered rice plants)
• Other (Examples: bacteria that live on Mars, or a software project)

12. What safety, security or ethical risks would be involved with such a use?

It is possible that software projects could also pose relevant risks.

1.3 Managing the risks you have identified

It is impossible to remove all risk from any biological activity. Instead, we attempt to manage these risks - to reduce them to an acceptable level. In this section, you should outline what steps have been taken (or you are planning to take) to reduce any risks you identified in the first part of the form.

13. How will experts overseeing your project help to manage any of the risks you identified in this form?

Oversight by experts For example, who is responsible for the safety and security of biology labs at your institution? What role has any institutional biosafety officer played in reviewing your work? What skills do these experts have that might help? For example, do they have a long history of working with an organism or part that might pose a risk? How familiar are they with the experimental procedures and practices you will be, or are, using?

14. What rules or guidance cover your work which could help to manage any of the risks you identified in the last section?

Rules and guidance For example: In your country / region, what are the laws and regulations that govern biosafety or biosecurity in research laboratories? Please give a link to these regulations, or briefly describe them if you cannot give a link. What are the guidelines for laboratory biosafety and biosecurity? Please give a link to these guidelines, or briefly describe them if you cannot give a link.

15. Have your team members received any safety training yet?

Training For the purposes of iGEM, biosafety and biosecurity training covers the procedures and practices used to manage risks from accidents or deliberate misuse of your projects to your team, colleagues, communities and the environment. All team members are expected to be aware of these risks and to work to manage them.

• Yes, we have already received safety and security training.
• We plan to receive safety and security training in the future. Please specify approximately when:
• We will not have safety and security training. Please explain in detail how team members will be aware of and manage risks to the team, colleagues, communities, and the environment in the absence of training. If it is not relevant because there is no lab component to your project, please note this:

16. Please select the topics that you learned about (or will learn about) in your safety training.

• Lab access and rules (including appropriate clothing, eating and drinking, etc.)
• Responsible individuals (such as lab or departmental specialist or institutional biosafety officer)
• Differences between biosafety levels
• Biosafety equipment (such as biosafety cabinets)
• Good microbial technique (such as lab practices)
• Disinfection and sterilization
• Emergency procedures
• Transport rules
• Physical biosecurity
• Personnel biosecurity
• Data biosecurity
• Chemicals, fire and electrical safety
• We will not have safety training

17. Which work areas do you use / are you using to handle biological materials?

Containment Please check all that apply. If you are using more than one space please check all that apply and note this in the other work area box.

• No lab work (e.g. software project)
• Open bench
• Biosafety cabinet (please note there are important differences between biosafety cabinets and laminar flow hoods / clean benches. iGEM encourages the use of biosafety cabinets but discourages the use of laminar flow hoods or clean benches)
• Specialist greenhouse
• Specialist animal house
• Specialist insect facility
• Other work area. Please describe:
• Unknown. Please comment:

18. What is the biosafety Level of your lab?

Help about Risk Groups and Safety Levels

• Not applicable as we have no lab component
• Level 1 (low risk)
• Level 2 (moderate risk)
• Level 3 (high risk)
• Level 4 (extreme risk)
• Other biosafety level. Please describe:
• We have several different lab spaces with different biosafety Levels. Please describe:

Note: iGEM teams should not use Risk Group 3 or 4 organisms, and they should not work in Safety Level 3 or 4 labs. If you are planning to work at Safety Level 3 or 4, contact safety (AT) igem (DOT) org right away!!

19. How will the rules, training, containment and other procedures and practices help to manage any of the risks you identified in the last section?

Please also consider waste treatment – how will you know that any waste produced in your project will be successfully activated?

1.3 Compliance with iGEM’s rules and policies

20. Are you planning / have released any organism or product derived from your project?

For the purposes of iGEM, release includes putting any engineered organism or product from one into the environment, yourselves or volunteers (including by eating or drinking), or into a device that will be placed in the environment.

• No
• Yes
  STOP: Release is not allowed in iGEM. For more information see the policy page. Please contact the Safety and Security Committee by emailing safety AT igem DOT org

21. Are you planning to make / or have made a gene drives?

For the purposes of iGEM, a gene drive includes Cas9 (and other endonucleases, such as dCas9 and Cpf1) integrated into the genome (including through the use of gRNA) of a sexually reproducing eukaryotic organisms (including organisms that reproduce both sexually and asexually, such as yeast) and/or the use of a drive to impact the progeny.

• No
• Yes
  STOP: Gene Drives are not allowed in iGEM projects without a special exception from the Safety and Security Committee. For more information see the policy page and the White List. Please contact the Safety and Security Committee by emailing safety AT igem DOT org

22. Are you planning / have used resistance factors (or associated sequences) for critically or highly clinically important antimicrobials, as listed by the World Health Organization?

For the current list of these antimicrobials see the table on p10 of this report. You need NOT include any resistance factors included in iGEM’s distribution kit.

• No
• Yes
  STOP: Before you acquire or use resistance factors and associated sequences for critically or highly clinically important antimicrobials, you must - submit a Check-In form. Check-Ins allow the iGEM Safety and Security Committee to help you ensure that you will work safely with these riskier organisms/parts. The Safety and Security Committee will base its review on the information you provide – please provide as much information as possible and use references as appropriate.

23. Are you planning to use, or using any animals (including insects and invertebrates) not on the Whitelist?

• No
• Yes
  STOP: Before you acquire or use any animal NOT on the Whitelist, you must - submit a Check-In form. Check-Ins allow the iGEM Safety and Security Committee to help you ensure that you will work safely and responsible with these organisms. The Safety and Security Committee will base its review on the information you provide – please provide as much information as possible and use references as appropriate.

24. Are you planning to use / have used any vertebrate (such as rats, mice, guinea pigs, hamsters, fish, etc.)?

• No
• Yes
  STOP: Before you acquire or use any vertebrate you must submit an Animal Use form. The use of animals is not allowed in iGEM projects without a special exception from the Safety and Security Committee. For more information see the policy page and the White List. Please contact the Safety and Security Committee by emailing safety AT igem DOT org

25. Are you planning to use, or using any parts not on the Whitelist?

• No
• Yes
  STOP: Before you acquire or use any part that is NOT on the Whitelist, you must - submit a Check-In form. Check-Ins allow the iGEM Safety and Security Committee to help you ensure that you will work safely with these riskier parts. The Safety and Security Committee will base its review on the information you provide – please provide as much information as possible and use references as appropriate.

26. Are you planning to use, or using any parts or organisms obtained from outside the lab or regular suppliers?

• No
• Yes
  STOP: Before you acquire or use any organism/part that has come from outside the lab or regular suppliers, you must - submit a Check-In form. Check-Ins allow the iGEM Safety and Security Committee to help you ensure that you will work safely with these riskier organisms/parts. The Safety and Security Committee will base its review on the information you provide – please provide as much information as possible and use references as appropriate.

27. What else can you tell us about any risks associated with your project, how you are managing them, or your compliance with iGEM’s safety and security rules and policies?

This can include any improvements you would like to see to our safety and security efforts, or anything that has not been sufficiently clear, or where additional guidance would be useful, or where you see important uncertainties.

1.4 Sign off

Only a team Instructor or PI may submit the Safety and Security Form. Instructors/PIs, please read the form you are submitting, and confirm that all its information is correct. By checking the "I Agree" box and clicking the "Submit" button, you are agreeing that the Safety and Security Form accurately describes the activities of your team and that they have complied with all relevant institutional, national or regional laws, rules and regulations. We are using the "I Agree" box in lieu of a signature with paper and pen.

I Agree