L
Another simple rule for 4.2 vs 4.3.
Documents specify requirements (SOPs, WIs, Forms). They require approval prior to release (for most folks this means a signature on the cover page or via their change control process).
Records demonstrate conformance to the requirements in the documents. They only require signature when specified by your documents or in certain cases (more limited than most people think) by the standard or regulation (e.g. nonconformance reports are records that require approval (i.e. signature), same with acceptance records). Many records require identification of the individual but this does not mean legal signature, just printed name is sufficient.
Documents specify requirements (SOPs, WIs, Forms). They require approval prior to release (for most folks this means a signature on the cover page or via their change control process).
Records demonstrate conformance to the requirements in the documents. They only require signature when specified by your documents or in certain cases (more limited than most people think) by the standard or regulation (e.g. nonconformance reports are records that require approval (i.e. signature), same with acceptance records). Many records require identification of the individual but this does not mean legal signature, just printed name is sufficient.
Well, our problem with records and documents having no signature is a systematic problem. Purchase Orders, Engineering Designs, and other important documents and records are being approved but no signature to prove that it is approved prior to use (This is I think clear to violate 4.2.3 a of the standard). I'd just use the time card as a sample because it is a record (since the time of the employees are recorded there) and we have confusions if what clause we can call it. Time card is stated in our Quality Manual as an Input to our Human Resource management process.
and as much as possible, he wants our report to be accurate.