BIOTECHNOLOGY INNOVATION

COMPETITION PROJECT DETAIL REPORT

Project Name:
Team Name:
Team ID:
Application ID:
 CONTENTS

1.TEAM STRUCTURE.............................................................................3
2. PROJECT SUMMARY.........................................................................3
3. DETECTED PROBLEM.......................................................................3
4.METHOD...............................................................................................4
5.INNOVATIVE ASPECT.........................................................................5
6.APPLICABILITY....................................................................................6
7.COST AND TIME PLANNING...............................................................6
8.TARGET AUDIENCE............................................................................7
9.RISKS....................................................................................................7
10.SUMMARY..........................................................................................8
11.ADDS..................................................................................................9

2
1. TEAM STRUCTURE

The team structure should be prepared to meet the distribution of tasks and planning
needs. The table below shows the roles undertaken by the team members. The team
should have members from different disciplines who meet the planning needs.
Personal information (name, surname, Turkish ID number, contact information,
photo, etc.) should not be added to the table. Advisor information must also be
included. Table rows can be changed as necessary.

Team Task Description - Roles - Planning

Consuler
Team Captain
Team Member 1
Team Member 2 …

2. PROJECT SUMMARY

In this section, you are expected to summarize the general idea of your project briefly
and clearly. The purpose, goal and the problem it solves should be clearly stated.
The summary should also generally address the technical aspects of the project such
as design, experimentation, installation and assembly. If available, you can add a
diagram, drawing or sketch visual that describes your project. However, the visual
you add must belong to you or, if it is a quote, it must be stated in the references and
the date of access must be added. This section serves as a short but comprehensive
introduction that allows the evaluator to understand your project at first glance. Since
the technical details will be explained in detail in the following sections, it is important
to provide a clear, simple and striking summary here.

3. DETECTED PROBLEM

In this section, you should explain the problem your project aims to solve in a clear
and simple language. You are expected to not only define the problem, but also
explain why it is important and why it has not been sufficiently solved to date. If this
problem has been solved by other methods before, please state why these existing

3
solutions are insufficient. Explain in general terms how your project will improve this
issue.

If the problem addressed by the project is complex or involves more than one
subsystem, it will be more understandable to explain this large problem by dividing it
into subheadings or subproblems.
To support your explanation:
• You can use your own visuals.
• Simple diagrams, presentations prepared with icons or infographic-style
explanations will also increase comprehensibility.
• If you are going to use quoted visuals, you must definitely indicate their source and
access date.

4. METHOD

In this section, you are expected to explain the path you followed while implementing
your project in clear and detailed manner. You should clearly state which scientific
principles your project is based on and which technological applications you use.

You should also state which technological readiness level (THS/TRL) you were at
when you started your project and which level you reached as a result of the project.
For example: “TRL was at level 1 at the beginning of the project, TRL 4 was reached
since the prototype was developed.”

If you have developed a prototype:

• You should clearly explain the content of the experiments you conducted.
• You can present the data you obtained with graphs or tables.
• You should evaluate whether your project created a solution by interpreting the
results.
• You can use 2D or 3D drawings,
• Process visuals,
• Prototype photographs, BioRender drawings or CAD views to support this section.
• If you use visuals, it is recommended that they belong to you. If you have obtained
them from another source, the source and access date must be stated. If you have
produced them with artificial intelligence, this must also be stated.

4
5. INNOVATIVE ASPECT

In this section, you should clearly explain the innovative and original aspects of your
project. You are expected to state the main features that distinguish your project from
similar products or projects.
Answering the following questions clearly and simply will make this section stronger:
• Are there previously developed solutions for this problem on the market or in the
literature?
• If so, in what ways are these solutions lacking or different from your solution?
• How does your solution approach this issue differently?
You should explain the aspects of your project that are unique to you in terms of
biotechnology in this section. The following points can guide you:
• Is the microorganism, cell line, enzyme or biological system used unique?
• How does your method differ from others in applications such as genetic
engineering, protein engineering, tissue culture, biosensors?
• Is your application more cost-effective, environmentally friendly, more efficient or
faster?
If you have developed a laboratory process:
• Which reagents, biological materials, methods were used?
• Have the process steps been optimized in a unique way?
• How does the biotechnological method used (e.g. PCR, ELISA, fermentation,
CRISPR, etc.) differ from the applications in the literature?
If the system you developed includes a biosensor, algorithm, or bioinformatics tool:
• What this system does, how it works,
• What biological data it analyzes,
• In what ways it differs from similar systems should be explained.

Also as a suggestion:
• Examining existing patents and similar projects and comparing them with your own
work will add strength to this section.

5
Remember: Innovation is not limited to just being a “new idea”; making an existing
solution simpler, more efficient, accessible, or lower cost is also considered
innovation.

6. APPLICABILITY

In this section, you should explain how the project you developed can be
implemented in real life. Can your project become a product, system or service when
completed? In which areas can it be used? For example: health, agriculture,
environment, industry, education, etc.
You are also expected to evaluate whether your project has the potential to become
a commercial product. When making this evaluation, you can consider issues such
as cost, manufacturability, sustainability and target user.
The technological readiness level (THS/TRL) that you mentioned in the method
section should be used again here:
• What level were you at when you started the project?
• What level did you reach at the end of the project?
• How long did this progress take or is it expected to take?
Adding a schedule or roadmap that briefly summarizes the steps in which the
application will be implemented will make the feasibility of your project concrete

7. COST AND TIME PLANNING

This section should explain the estimated cost of your project and how it will progress
over time.
Cost Planning:
• The list of materials to be used in the project (number, unit price, total cost) should
be given in a table. A table format is not provided, you are expected to create it
yourself.
• Expenses for each of the steps such as design, production, testing and
improvement that will occur during the product development process should be
specified.
• When the expenses will be made should be shown on the time axis as a periodic
spending plan (e.g. weekly or monthly).
• If there are similar products or projects in the market, a comparison should be made
in terms of cost. If there is no cost advantage, competitive advantages such as time,

6
environmentally friendly approach, user convenience, sustainability should be clearly
stated.
Time Planning:
• The entire process of the project should be divided into stages such as design -
production - testing - result, and these stages should be shown in a simple way on a
timeline (e.g. Gantt chart, workflow diagram, mind map especially for the idea
category).
• Work package, work description and estimated time should be specified for each
stage.
• This plan should not be complicated; however, it should help the reader easily
understand the project process visually.
It is of great importance in terms of showing that your project is realistic and
applicable. Keeping your budget low may be advantageous; however, more
important than low cost is using the budget effectively and in a planned manner. The
budget of the idea or experimental study to be carried out is also an important
criterion. For example, if the cost and usage of market-based gelatin are to be stated
instead of gelatin purchased from a chemical manufacturer, it should be clearly
stated that it will not make a difference in the study or will yield better results.

8. TARGET AUDIENCE

In this section, you should clearly state who will use your project and who it is aimed
at. It should include information such as who is experiencing the problem your project
is solving, what age, profession or social characteristics this group has. Providing
brief information about the size of the target audience will help understand the scope
of your project. It would be useful to distinguish and explain the people who will use
the project and the groups that will indirectly benefit from it.

9. RISKS

This section should describe the possible problems that may be encountered during
the implementation of the project, namely the risks. An assessment should be made
considering the probability of each risk occurring and its impact on your project, and
alternative solutions (plan B) should definitely be specified for high-risk situations.
Too many risks should not be written unnecessarily; however, realistic, important and
manageable risks should be included. Thinking in advance about the technical,
logistical, financial or environmental obstacles that you may encounter during the
implementation of the project will ensure that your project has a more solid structure.
If you wish, you can also provide a short SWOT analysis in this section, including the
strengths and weaknesses, opportunities and threats of your project idea.
7
 10. SUMMARY

This section should include all sources you have used while preparing your project.
These can be articles, books, websites, forums or product pages. The access date
should be stated especially in web addresses. In case the web site is closed or out of
service, if available, a source can be given via the Internet Archive
(https://archive.org/). For scientific sources, one of the standards such as APA, IEEE,
MLA or Chicago should be chosen and all sources should be written in accordance
with this format. The chosen format should be consistent and only the sources that
are actually used should be included. This section shows the reliability of your work
both scientifically and ethically.

IMPORTANT NOTES ABOUT REPORTS:

 Everything in the 10 articles, including the “Table of Contents” above, will be explained
in a maximum of 15 (fifteen) pages.
 A maximum of 2 (two) pages of visuals can be uploaded as an attachment to the
report. The attachment must be referenced in the report text. There will be a maximum
of 15+2 pages, including the cover, description and visual attachments.
 All reports must be written in accordance with this report template and technical
specifications..
 The report must include a cover page. No information other than the relevant headings
should be written or removed from the cover page.
 Explanatory texts, including this table, must be deleted from your project report. If they
remain, they will result in a negative evaluation.
 Font: Arial, Point: 12, Line Spacing: 1.15, justified, page margins top-bottom-right-left
should be 2.5 cm. Gutter margin is not required..
 Sentences in the report should not be the same or repetitive..
 Sentences and expressions taken from sources must have the adaptations of the
project report writer. Sentences taken directly with “copy-paste” should not be
included. If it is necessary, it should be quoted in “double quotes” and the source
should be mentioned in the text..
 In case of using artificial intelligence, it should not be directly “copy-pasted” from the

8
AI writing format, it should be edited by the report author. In case of using an image
produced with artificial intelligence, it should be stated which AI language model is
used under the image and in the references.

11. ADDS

This section should include materials such as additional documents, drawings,

tables, graphs, calculations, code snippets, survey results, permission letters, etc.
that are referred to in the report or support the report. Any document that would make
the narrative difficult due to detail can be presented here if included in the main text.