35 lines
No EOL
1.4 KiB
ReStructuredText
35 lines
No EOL
1.4 KiB
ReStructuredText
Procedure Management Procedure
|
|
------------------------------
|
|
|
|
.. impl:: Write and maintain written procedures describing how work is done
|
|
:links: R_APPB_22
|
|
|
|
This procedure governs how procedures are created and maintained.
|
|
|
|
.. impl:: Require that each procedure include acceptance criteria
|
|
:links: R_APPB_44
|
|
|
|
Each procedure shall include appropriate quantitative or qualitative
|
|
acceptance criteria for determining that important activities have been
|
|
satisfactorily accomplished.
|
|
|
|
.. impl:: Keep forms/records/document types synchronized with
|
|
the Document management plan
|
|
:links: R_APPB_45, R_APPB_43
|
|
|
|
If procedures are precise about what record/document types to use,
|
|
people will be more likely to put in the appropriate and expected
|
|
information, maintaining document control.
|
|
|
|
Whenever a record or document is dictated by a procedure, the procedure shall
|
|
clearly specify with record/document type from the list in :ref:`rmdc-doctypes`
|
|
is to be used. If a new record or document type is needed for the procedure,
|
|
ensure it is defined and added to the list in :ref:`rmdc-doctypes`.
|
|
|
|
Procedure review checklist
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
A new or revised procedure should be checked to have the following characteristics:
|
|
|
|
* It includes acceptance criteria
|
|
* Record/documents generated throughout the procedure are identified
|
|
clearly, including with type |