Record Control - Why must I control these records?

A

Angelika

I agree, blank forms need to be issue controlled, records need 'looking after' e.g. fling, protecting from damage or loss, have retention periods defined, be retrievable etc, as described in 4.2.4

I absolutely agree.

A document contains the "input requirement", e.g. a form used in production may lead you through the working and inspection steps and "force" you to write down the work you have performed and/or its results.

Once a form is filled in, it is no more a document, but a record.

The record is the proof that the work has been done i.a.w. the requirements.

Records cannot be revised whereas documents are controlled via the revision level or date.

Examples for documents are: Regulations, handbook, procedures, forms, standards, Directives from the Aviation Authorities etc.

Examples for records are: Work Reports, Test Reports, Audit Reports, Training Records, Supplier Assessment Reports and so on.

I remember a thread from this forum (sorry, I can't remember which one it was) where somebody explained the difference between document and records with

Do = document (= requirement)
done = record (= showing of compliance with the requirement)


Hope this helps!

Angelika
 
Top Bottom