Lab protocols

Most practical modules in your curriculum require that you write a lab protocol at the end of your project. This lab protocol is your proof of achievement, and thus must be taken seriously, independent of whether it is graded or not. Please find below some information that should give you an idea of what to consider when writing a protocol.

Before writing a lab protocol, you should ask yourself not only why your are writing a lab protocol, but much more what you want to achieve with the lab protocol. The answer is considerably simple: You write the lab protocol for

• yourself. It should bring you in the position to easily repeat your analysis - or parts of it - somewhen in the future, and probably at a time point where you can no longer do it from the back of your head¹⁾
• for any other person that comes after you, such that this person has a chance to understand
  • what you did
  • why you did it
  • and how you did it

With the help of your protocol, any person should be able to quickly reproduce your analysis. If you keep this objective in mind, then you should already have a good idea of how to write a protocol.

It happens often that people have no clear idea of how to write a protocol. We have, therefore, compiled a short guideline of what to take into account when writing a protocol.

1. A protocol is a scientific text, and thus the same rules apply
2. A protocol is typically written for a short term project. Its focus is more on the technical part and the results, and less on answering a particular scientific question²⁾
3. A protocol is meant to provide

   1. all data
   2. all programs
   3. all analysis steps

   that are required to reproduce your analysis

Follow this LINK to get some additional ideas of how to write a good report

It is a good idea to carefully read the Guidelines of how to write scientific text

Below, we have compiled a collection of points that you should check before writing a protocol, and afterwards as well

• Try sticking to the standard structure

  • Introduction
  • Material & Methods
  • Results
  • Discussion
  • Bibliography

  Don't mix up the contents of the main sections! In particular, there is always the danger to write results in the discussion section, or vice versa!

• Figures
  • each figure has
    • a figure number. Figure numbers must occur in the correct order in the main text
    • a short, informative title
    • a description that reflects the message of the figure. Make sure that the figure description does not end up in the main text
  • each figure should be interpretable on its own. It is generally a bad idea to refer to other figures (other than supplementary figures) in the figure caption
  • Screenshots als Abbildungen sind ok, allerdings muss die Bildauflösung ausreichend hoch sein. Verpixelte Abbildungen haben in einem Protokoll nichts zu suchen
• Tables
  • Each table has an informative title. Table columns can be explained in the table footnotes
• Methods
  • provide references for the programs you use, the URL from where you have downloaded it, and provide the program version together with the relevant parameter settings
• References
  • Wikipedia cannot serve as a reference for scientific text, because it is a source of information that is subject to change over time
  • Make sure that references in the text, and your bibliography is correctly and consistently formatted
• Abbreviations
  • Abbreviations, that cannot safely be considered common knowledge, have to be explicitly introduced. For example you can write “We used the Quest for Orthologs (QfO) set of reference proteomes…
  • Species names have to be given in full length, before you start abbreviating them. For example you should write: ”(…) we extracted all ribosome biogenesis factors from yeast (Saccharomyces cerevisiae)“. Later in the text, you can then abbreviate the species name to S. cerevisiae.
• Spelling
  • Most editors provide a spell checker. Make sure to use this!
• Headings
  • Headings should be concise and informative. Something like ‘Getting an idea (of) how to use HaMStR…’ should be avoided. This could be reformulated to ‘Establishing the HaMStR Workflow for …'
• Miscellaneous
  • Use standards whenever possible
  • briefly introduce relevant methods such that you - as well as any other person - comes into the position to understand what kind of analysis you are actually doing.
  • Avoid lab jargon. For example, to blast is not the appropriate verb for performing a Blast search
  • Avoid group-internal abbreviations such as DROME as an abbreviation for Drosophila melanogaster
• Datensets
  • Introduce data sets that you use in your analysis in the Materials section, and make sure to explain where the data is located

You will find some general guidelines for writing a project report, or in general scientific text here

• How to write a Labreport
• How to write scientific text