Professional Documents
Culture Documents
SST DocControlProcedureA
SST DocControlProcedureA
SST DocControlProcedureA
Revision History
Date of Last Review Comments
Original document created.
[Date]
[Company Name]
Prepared by:
Summit Safety Technologies
www.SafetyProgramNow.com
310-940-1394
(COMPANY NAME) Document Control Procedure
1. Introduction & Purpose
Documentation is critical in the success of any organization’s Management System. It allows for consistency
and uniformity in the application of procedures and specification in the workplace. The purpose of this
procedure is to provide a standard method for controlling documents that support the operation of the
(Company Name) Management System.
(COMPANY NAME) relies heavily on it’s intranet for the storing and availability of documents used in the
management system. This allows for one controlled source to be available for the Company and eliminates
the need for multiple controlled copies of manuals to be kept. In doing so, this means that any printed
version of a document or record is ‘un-controlled’ and should be checked against the intranet for its status.
2. Scope/Application
This procedure applies to the documents created as part of the (COMPANY NAME) Management System. This
includes policies, procedures, manuals, training materials, articles, newsletters, guidelines and fact sheets.
3. Responsibilities
3.1 (COMPANY NAME) President
The (COMPANY NAME) President has the overall responsibility for the (COMPANY NAME) document
control system. This includes the development and evaluation of this procedure. The (COMPANY
NAME) President also has direct responsibility for all centrally produced documentation.
3.2 Department Senior Management
Department Senior Management is responsible for ensuring the implementation of procedures and
guidelines created within their department are implemented and controlled in accordance with this
guideline.
3.4 Local Document Controllers
All Department Senior Management will nominate a document controller/s to ensure all document
control requirements are met. The following individuals are assigned as Document Controllers for their
group:
4. Implementation
4.1 Document Control Register
Each document created as part of the (COMPANY NAME) Document Management System will be
recorded on the Document Control Register [See Document Control Register in Appendix A]. This
may be accomplished by listing the document details (document number, current version, title,
creation date, last review date, next review date and comments) directly into the (COMPANY NAME)
Document Control Register, or by inserting a single link in the (COMPANY NAME) Document Control
Register that points to a detailed Register in another Network location.
While the recommended review period for controlled documents is 1 year, each department may establish
the review period for their documents. For example, the steps and processes in many equipment
maintenance procedures might remain constant and may not require an annual review. The department
owning the document may choose to establish a review period of more than 1 year based on the
department’s needs. This decision should be made by the Approval Authority for the particular document in
question, and must be indicated in the Date of Next Review located in the document control header.
Review frequency
may be established by
each department.
Recommendation is 1
year.
A disclaimer using one of the formats below will be placed as a header on uncontrolled documents.
a. For uncontrolled copies of controlled documents that are maintained electronically, the header should
read:
For documents maintained on the Internet/Intranet:
“This is an UNCONTROLLED DOCUMENT printed for reference only (date). The controlled document
is located on-line at the address shown at the bottom of this page.”
For documents maintained on a locally accessed file:
“This is an UNCONTROLLED DOCUMENT printed for reference only (date). The controlled document
is located (state where, e.g. I-Drive, file name)”
b. Uncontrolled copies of hard copy controlled documents should have the following format:
“This is an UNCONTROLLED DOCUMENT for reference only. The controlled copy (or copies, if more
than one) is (are) located (state where, e.g., file cabinet in a specific shop office or room number)”
Following completion of any review, the program will be revised or updated in order to correct any
deficiencies. Any changes to the program will be reviewed by the appropriate Senior Staff members, and
approved by the (COMPANY NAME) President.
Changes to Documents
To request a change to a document, the (COMPANY NAME) Document Change Request Form should be
completed and routed per the instructions in the Form below. As with the Document Approval Process Flow
(see Section 4.7 of this document), the change control process may be customized as necessary to meet the
needs of each department.
1-1. Originator: 1-2. Date (m/d/yy): 1-3. Phone Number: ( ) Ext:
1-4. Document Type: 1-5. Type of Action Requested:
1-6. Document Number: Version
1-7. Document Title: Note1
1-11. Send Form to: (Select Name of Responsible Manager):
Factory Support: Other:
1-8. Other Documents Affected: Field Ops: Other:
Finance/Admin: Other:
1-9. Summary of Requested Change: Product Marketing/Engineering: Other:
1-10. Recommendation (include rationale for change: Sales/Sales Support Other:
SBU: Other:
Note1
To send, select File, Send To, Mail Recipient – email fields will appear at top of page. Click Address Book Icon ()
near “To…” field (top of page), select Name of Responsible Manager. Type in any text you wish as comment or
explanation in “Introduction:” field. Select Send a Copy to email the form.
2. Responsible Manager (Initial Review & Approval): Complete Section 2 & send Note1 to Assigned Author (see Block 2-2)
2-1. Approval 2-2. Assigned Author: 2-3. Date: (m/d/yy)
2-4. Not Approved Reason: If Not Approved, return to Originator (Name in Block 1-1)
3. Author (Assigned by Responsible Manager): Complete Section 3 and return to Responsible Manager via email Note1
4. Responsible Manager (Final Review and Approval): Complete Section 4 , send Note1 to Dept. Document Controller.
Approval:
Not Approved Reason: If Not Approved, return to Assigned Author and include instructions.
Responsible Manager Name: Date: (m/d/yy)
6. (COMPANY NAME) Document Control Administrator – Final Release: Assign Doc Cont Req#, post revised document on
(Company Name)Web.
Document # Level I, Document Title Created Date; Last Review Date; Comments
II, III, or (C) = (COMPANY NAME) Owner Next Review Date
IV Confidential
Programs, Policies, & Plans
Doc-P-001 (COMPANY NAME) Document 4/06; M. Lawrence
Control Procedure
Doc-P-002 (COMPANY NAME) Employee ; HR
Handbook
Doc-P-003 (COMPANY NAME) Policy Manual ; HR
Manuals
Doc-M-001
Forms
Doc-F-001 Job Description Questionnaire
Training Materials
Doc-TM-001
Document Levels:
Level I consists of a quality manual that outlines what the company plans to achieve and outlines the policies it plans
to implement to achieve its goal.
Level II outlines procedures the company will follow, what workers will do, in what order, by whom, and with what
results, structured to reflect the process flow of events.
Level III consists of detailed work instructions—specific written information on how to do a particular task—available
centrally and locally.
Level IV consists of reference material and information not in other categories. This information may include quality
records, forms, and so forth.
Originating Office
Revision History
Date of Last Review Description of Changes
See (COMPANY NAME) Document control procedure ((COMPANY NAME)-ALL-P-001 A) for full details.
2. Scope/Application
2.1. Detail the scope of the document here (who it affects, which region/toolset/etc.)
4. Implementation
4.1. Details of steps in procedure/policy/etc. here.