Going back to difference between instruction and procdures, I'll add one more point of view
. I agree with the previous opinions that the best disctinction is that procedures answer the question: who / what? and instructions: how? It's generally up to you how you name your documents but here's the reason why we decided to transfer that logic into our procedures..
When deciding what should be the disctinction between procedures and instructions we used only one criterion. It was: the way that the want a document to be approved and controlled.
Defining employees responsibilities is very important subject. Therefore, the documents that establish or change rights and obligations for employees should be approved by the top management. In practice, these are the documents that answer the question: "who does what?". And - according to our control over documents procedure - these documents are called procedures.
The documents explaining the way of performing some task, without (or "almost without") establishing any new obligations are called instructions (in practice they answer the question "how?") - and these are approved by a process owner (there is no need for these documents to get "higher" approval, since they doesn't change the distribution of responsibilities in the company).
The documents that determine the form of preparing a records are called "forms". These are approved by process owner (in simplified way).
- the document that states: 1. quality controller performs the control and records its results, according to the control plan, then 2. warehouse worker transports the material to the warehouse, then: 3. quality controller marks the material with label and color (ref. to material marking instruction) - is procedure.
- the document that states how material should be marked (1. use orange paint for material A, blue for B, 2. put a label on the top of the containter in a visible place etc.) - is instruction.
If all of these matters were put into one document (document explaining "who, what and how?") - it would still be called a procedure because it should be approved by the top management. But I avoid mixing these subjects in one document because then any technical change in the way of performing a task would require approval on a higher level which is unnecessary. It's better to have a reference to instruction.
Therefore, I think that you should decide what should be the way of control over various documents in your company. Which criterion, which document attribute determines that the control should be different? Then, make the distinction between them. It is unnecessary to have 2 kinds of documents controlled in the same way or one kind controlled in 2 different ways.