Purpose

A checksheet is a data recording form that tells how many times something has happened. Checksheets can, therefore be used in every project stage that includes data collection.

Checksheets should be simple to use, and display the data in a format that will allow patterns and trends to be identified easily.

How does it do it ?

• Builds, with each observation, a clearer picture of the facts, as opposed to the opinions of the team members.
• Makes patterns in the data become obvious quickly.
• Forces agreement on the definition of each event. Everyone is then looking for the same thing.

Method

1. Decide what data is needed.
   • If events or conditions are being monitored, agree on the definition of the event or condition. (It is important that everyone has the same interpretation.)
2. Confirm who will collect the data, over what period and from what sources.
   • The data can be from a sample or entire populations.
   • Ensure sufficient time is available to collect the data.
   • The time period for data collection should be long enough for the results to represent a 'typical' period.
   • All data must be recorded - 'bad news' must not be filtered out.
3. Designing a Check Sheet - it must be clear, complete and easy to use.
   • All of the relevant information should be considered.
   
   

   Reason for Check		Event or Condition being checked					Dates - From/To
   	Dates
   	3/7	4/7	5/7	6/7	7/7	10/7	11/7	Total
   Condition A
   Condition B
   Condition C
   Condition D
   Total


A good practise is to have the checksheet tested before it is used, preferably by someone who wasn't involved with the design. Make improvements if necessary.
4. Data collection
   • Make sure all entries are written clearly and the information is accurate.
   
   
   Example:
   
   

   Will not assemble		Spline form and Condition			Dates -12 -16/7/97
   	Date
   	12/7	13/7	14/7	15/7	16/7	Total
   Oversize Diameter	II	I	II	II	I	8
   Undersize Groove	I	III	II		I	7
   Damage	III	IIII	III	II	IIII	16
   Total	6	8	7	4	6	31