My first post! I find this forum most helpful. I am in the process of creating an integrated health, safety, environment and quality management system for a small marine company. There is no intention for 'formalized certification' but that is a possibility in the future (ISM Code/ISO 9001/ISO 14001/OHSAS 18001).

Now, my question may appear rudimentary in nature but what are the main differences between a 'checklist' versus a 'working instruction'. I know a working instruction provides step by step detail for a specific task but fundamentally is there a big difference in application and terminology? Thank you in advance!

Sorry - one more thing. To give you an example, 'start up list for boom boats'

1. Check fuel
2. Check oil in engine
3. Check level of water in engine header tank....etc.

More checklist or 'working instruction'? I am inclined to think working instruction.

Basically a checklist is a list of things to do, whilst a work instruction is how to do something. Usually they are different 'documents', but not necessarily. A checklist could be embedded in a work instruction (or the other way around for that matter). Often a checklist is used to gather data or to record that something was done and thus becomes a record.

In my mind every form or checklist is a work instruction. After it is completed it becomes a record.
This thus saves paper and makes the WI user friendly.
Most WI's are boring and no one reads them, all the information can be in tables, checklists and forms.

Remember that before name or date on a form it is understood that the instruction "Please fill in your" name and everyone acts on it.

KISS_principle

I am currently integrating our Health and Safety and Quality systems. I will be using forms as much as possible to reduce the need to read boring procedures that nobody likes to read.

In most cases they have to fill out the form, so why not design the forms to function as work instructions. It will be a struggle (HR likes to make things easier for the auditors and not easy to use), but, we will get there.

Basically - they aren't necessarily the same, but, I find forms if designed properly can greatly reduce the need for work instructions (or at least reduce their length)

John

I am currently integrating our Health and Safety and Quality systems. I will be using forms as much as possible to reduce the need to read boring procedures that nobody likes to read.

In most cases they have to fill out the form, so why not design the forms to function as work instructions. It will be a struggle (HR likes to make things easier for the auditors and not easy to use), but, we will get there.

Basically - they aren't necessarily the same, but, I find forms if designed properly can greatly reduce the need for work instructions (or at least reduce their length)

John

Great answer........:agree1::applause::yes:;)

In my world, a work instruction tells you how to do something and it may define a specific order for doing those items. A checklist is conformation, yes or no, and possibly data gathered from measurements while doing a certian set of activities. I have often combined work instructions and checklists into one document.

One big difference, a checklist becomes a Quality Record when it is used. A work instruction just remains a document.

One big difference, a checklist becomes a Quality Record when it is used. A work instruction just remains a document.

Exactly so eliminate the middleman.

Lean really applies to bureaucracy

One big difference, a checklist becomes a Quality Record when it is used. A work instruction just remains a document.

May sound good in theory, but not always true. A check list only becomes a record if it's designed to do so, and some kind of marking up occurs. I've seen checklists that were just a short bullet point list ('hey remember this') and never intended to become records.

Also, re an instruction, you could also turn this into a record simply by 'ticking off' or 'marking up' points on it, then initial/sign it off.

I think the distinctions can be a bit artificial, really. I think it's more effective just to determine what they mean and how they will be used in your own system.