Logbook

Aim

To ensure that important decisions, problems or solutions can be retrieved.

 

Requirements

  • An up-to-date logbook containing important decisions, problems and solutions throughout the project.

 

Documentation

A logbook in an electronic format.

 

Responsibilities

Executing researcher: Keep an up-to-date logbook containing all important decisions, problems and solutions.
Project leaders: Occasionally check whether the logbook is accessible and up-to-date.
Research assistant: N.a.

 

How To

The idea behind maintaining a logbook is that it can be used to investigate how the study has progressed, and why certain choices or decisions were made. This is useful to you, but it is essential for others who may have to continue your work.
Logbooks are required for recording issues, such as problems and solutions chosen during the data collection and input process; which research assistant worked on this; which controls were carried out and what the results of the controls were; etc. A logbook is also essential for recording important decisions during the study, such as which questionnaires were chosen and, most importantly, why.
A logbook should at least contain the date, description and reference of important moments, decisions, problems and solutions.

 

Date
Description
Reference
15-01-2014
SF35 questionnaire chosen
Notes December 15, 2013
20-01-2014
Telephone discussion with Herman (statistician) about randomization. Group randomization instead of individual randomization was chosen, given the people play football in teams.
January 20, 2014
16-02-2014
Research assistant … starts work
Notes February 15, 2014
18-02-2014
Database tested described in Specs database.doc
In C:\project football\ Preparation\ database setup.doc
13-03-2014
Questionnaire modified! Pilot study showed question 13 was misunderstood
C:\project football\ Preparation\ pilot.doc

 

Examples of logbooks:

 

Audit questions

  1. Is a logbook kept up to date, including date, agreements and (path to) notes?

 

V2.0: 13 May 2015: Revision format
V1.2: 1 Jan 2010: Translation into English
V1.1: Sept 2006: Minor textual amendments