The Principles of Document Control By Dave Baldwin



Similar documents
Risk-Based Approach to 21 CFR Part 11

Approved by: Vice President, Human Resources & Corporate Resources and Vice President, Treasury & Compliance Date: October 14, 2009

COLORADO COMMUNITY COLLEGE SYSTEM SYSTEM PRESIDENT S PROCEDURE ELECTRONIC COMMUNICATIONS MANAGEMENT AND RETENTION PROCEDURES

Electronic Documents: is any electronic media content that is intended to be used in either an electronic form or as printed output.

Document Management in the FIPPA Era

Life Cycle of Records

Records and Information Management. General Manager Corporate Services

Creating an Electronic Filing Structure

RUTGERS POLICY. Approval Authority: Executive Vice President for Academic Affairs and Senior Vice President for Administration

TERRITORY RECORDS OFFICE BUSINESS SYSTEMS AND DIGITAL RECORDKEEPING FUNCTIONALITY ASSESSMENT TOOL

INFORMATION GOVERNANCE STRATEGY NO.CG02

TRANSPORT CANADA MARINE SAFETY PLEASURE CRAFT OPERATOR COMPETENCY PROGRAM QUALITY MANAGEMENT SYSTEM FOR ACCREDITATION

Legal billing and predictive coding A fresh way to assess your legal spend

Classifying Correspondence. General, Administrative, Project/Case, and Transitory

The Next Frontier. for Records Managers. Retention and Disposition of Structured Data:

Manual of Accounting and Financial Reporting for Pennsylvania Public Schools CHAPTER 11 TABLE OF CONTENTS 11.A. Chapter

Basic Records Management Practices for Saskatchewan Government*

Gatekeeper PKI Framework. February Registration Authority Operations Manual Review Criteria

UserLock vs Microsoft CConnect

Table of Contents. Chapter No. 1. Introduction Objective Use Compliance Definitions Roles and Responsibilities 2

TERMS and CONDITIONS OF USE - NextSTEPS TM

State Records Office Guideline. Management of Digital Records

Understanding the Software Contracts Process

This interpretation of the revised Annex

ADRI. Statement on the Application of Digital Rights Management Technology to Public Records. ADRI v1.0

Working with Versioning. SharePoint Services

ISO/IEC QUALITY MANUAL

Data Governance Policy. Staff Only Students Only Staff and Students. Vice-Chancellor

Records Management Policy.doc

Council Policy. Records & Information Management

Information Management: A common approach

HOME TRUST COMPANY PRIVACY NOTICE/PRIVACY CODE for Creditworx/Home Owner Merchant Express

RECORDS MANAGEMENT POLICY

Government records findings--recognition of public policy.

Business Administration. Level 2 Diploma in Business Administration (QCF) 2014 Skills CFA B&A units L1 Page 1

Compliance Management Systems

Chapter RECORDS MANAGEMENT Sections:

September Tsawwassen First Nation Policy for Records and Information Management

Corporate Records Management Policy

Records Management Policy

RECORDS AND INFORMATION MANAGEMENT AND RETENTION

Information Management Policy

Implementing an Electronic Document and Records Management System. Key Considerations

RECORDS MANAGEMENT MANUAL

Strategies for Developing a Document Imaging & Electronic Retention Program

Document Control in an ISO Environment

INSTITUTE OF TECHNOLOGY TALLAGHT RECORD MANAGEMENT & RETENTION POLICY

Digital Continuity Plan

Retention & Disposition in the Cloud Do you really have control?

The Manitowoc Company, Inc.

1. What is PRINCE2? Projects In a Controlled Environment. Structured project management method. Generic based on proven principles

Archiving, Backup, and Recovery for Complete the Promise of Virtualization

Chapter 1. Database Systems. Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel

IDERA WHITEPAPER. The paper will cover the following ten areas: Monitoring Management. WRITTEN BY Greg Robidoux

University of Sunderland Business Assurance Information Security Policy

Integrated archiving: streamlining compliance and discovery through content and business process management

Polices and Procedures

UNIVERSITY OF ROCHESTER INFORMATION TECHNOLOGY POLICY

POLICY FOR PRESERVATION / ARCHIVAL OF DOCUMENTS

Netskope Cloud Report. Report Highlights. cloud report. Three of the top 10 cloud apps are Storage, and enterprises use an average of 26 such apps

Access Control BUSINESS REQUIREMENTS FOR ACCESS CONTROL

Guidelines and Procedures for Project Management

OFFICE OF TEMPORARY AND DISABILITY ASSISTANCE NATIONAL DIRECTORY OF NEW HIRES DATA SECURITY. Report 2008-S-49 OFFICE OF THE NEW YORK STATE COMPTROLLER

Bridging People and Process. Bridging People and Process. Bridging People and Process. Bridging People and Process

Improving database development. Recommendations for solving development problems using Red Gate tools

The Paper Medical Record

E-Discovery Quagmires An Ounce of Prevention is Worth a Pound of Cure Rebecca Herold, CISSP, CISA, CISM, FLMI Final Draft for February 2007 CSI Alert

DOCUMENT AND RECORDS CONTROL PROCEDURE

Electronic Palliative Care Co-Ordination Systems: Information Governance Guidance

Management: A Guide For Harvard Administrators

5 FAM 440 ELECTRONIC RECORDS, FACSIMILE RECORDS, AND ELECTRONIC MAIL RECORDS

Utica College. Information Security Plan

United Cerebral Palsy of Greater Chicago Records and Information Management Policy and Procedures Manual, December 12, 2008

Southern Law Center Law Center Policy #IT0004. Title: Policy

Records Disposal Schedule Anti-Discrimination Services Northern Territory Anti-Discrimination Commission

Procedures on Data Security Breach Management Version Control Date Version Reason Owner Author 16/09/2009 Draft 1 Outline Draft Jackie Groom

Space Project Management

EUROLAB Cook Book Doc No. 13 ELECTRONIC RECORDS

Information and Compliance Management Information Management Policy

Guide 4 Keeping records to meet corporate requirements

HCAOG Records Retention Policies & Procedures

REVIEWED BY Q&S COMMITTEE ON THE 4 TH JUNE Social Media Policy

Introduction to Business Planning

Draft Information Technology Policy

Transcription:

The Principles of Document Control By Dave Baldwin The Out of Control Syndrome Organizations create documents daily. They are used to convey new ideas, provide direction, give instructions, describe processes, define specifications, and a host of other purposes. Often documents are generated in an ad hoc environment without thought to how they will eventually be used or by whom. Documents are often created in a casual manner and then stored on someone's hard drive. They are passed around in printed form, or attached to e-mails, and end up being thrown away or deleted when they no longer seem relevant to the issues of the day. Realizing the Importance of Documents This undisciplined approach to document creation and distribution overlooks the importance documents may likely have to the organization in the long term. Individually, documents are pieces, or snippets, of the organization's intellectual capital. They each contain information that represents a small part of what the organization knows. Taken together, over time, documents become a significant part of the intelligence of the organization. The importance of documents to the organization and, perhaps, its very survival, calls for a thoughtful approach to understanding the role documents play in the day-to-day functioning of the organization. Once this is understood, the need for a rational and consistent means of creating and managing documents becomes clear. A Practical Approach to Document Management Effective document management requires an underlying philosophy and strategy. It should be tailored to the needs of the organization that must use it. It should be practical and it should be written. No document management strategy can be useful if it is not explicitly documented and made part of the daily routine. In organizations with the proper understanding of the significance of document management, this documented philosophy and strategy becomes a document management policy. Once this policy is defined, it should be 2012 David A. Baldwin www.davebaldwinconsulting.com 1 of 5

followed with a document management process that explains how to put the policy into use. The document management policy and process become the organization's method of document control. In broad terms, document control provides a means of managing the development, approval, issue, change, distribution, maintenance, use, storage, security, and disposal of documents. The Purpose of Document Control The purpose of document control is not to create extra work or build a bureaucracy. Instead, it is put in place to protect the value of the content of documents and to enhance the usefulness of that content to the people in the organization who need to use it. Document control provides a framework for thinking about how information is created in the organization and how it should be managed once created. The purpose of a document control method is to ensure: Documents fulfill a useful purpose Resources are not wasted on the distribution of unimportant or useless information Only valid information is published Information is kept up to date Information is provided in a form that can be used by the people who need it Classified, confidential, or proprietary information is restricted to the people who have a real need to use it Information is retained that could help solve a problem, improve opportunities, avoid costly errors, or deflect potential litigation Document Control Procedures The document management process put in place to support the policy should include procedures that define the development of documents. While these procedures should not be cumbersome, they should be explicit and detailed enough to provide clear direction as to how documents should be prepared. The procedures may include topics such as: How to plan new documents; authorization, funding, establishing need, etc. How to prepare new documents; who prepares them, how they are drafted, how drafts are maintained 2012 David A. Baldwin www.davebaldwinconsulting.com 2 of 5

Standards for the format and content of documents, forms, diagrams, etc. Document identification conventions Version control conventions Dating conventions; date of review, date of approval, date of issue, date of distribution, date of revision Document review procedures; who reviews, evidence of review Document approval; who approves, evidence of approval Publication; what constitutes publishing a document Printing; who prints a document, restrictions to printing Distribution; how is a document distributed, who does it, who checks it Use of documents; limitations, unauthorized copying, access to files, marking printed copy Revisions; identifying a need; who makes revisions, review and approval process, how are changes marked Amending issued documents; who creates amendments, review and approval process, identification of amendments Storing documents; determining location, security, access and prevention of unauthorized changes, indexing, retrieval by users, restrictions concerning paper documents vs. electronic documents, authorized and unauthorized external distribution and republishing A System Tailored to the Environment While many of these processes can be automated with a document management tool, the organization must not allow a purchased software application to dictate its document management policy and process. To work effectively, a document control method must be adopted that makes sense for the organization's environment and culture. Implementing a Document Control Process Prior to implementing a document control process, an organization should prepare a document control policy that explicitly explains how the system is to work. This document should describe with precision the rules for how documents are to be created, reviewed, published, stored, and used, as well as any other details as suggested in Document Control Procedures above. A relatively simple way to implement document control is to use a master list as the control mechanism. This is the approach taken by the ISO 9000 2012 David A. Baldwin www.davebaldwinconsulting.com 3 of 5

series of quality standards. The master list contains the same document control elements as does each document. The master list, however, is the governing instrument for the process. If the master list is changed, affected documents must be changed to correspond to the master list. In such a system, the master list is a particularly sensitive document once document control information is recorded and must be protected accordingly. The document control policy may include instructions for how the master list is to be managed. In actual practice, a document is created, its document control elements populated, and the master list is used to record the document coming under the control process. If the system is audited, the master list is the source used to check the control of individual documents. Document revisions are done in a similar fashion. Document content is changed as required, the document control elements are updated, along with the revision history page of the document, and the master list is updated to correspond to the document information. Document Control Elements At a minimum, the recurring control elements of a document include the document name, revision number, issue/revision date, the current page number and the document s total number of pages. This is the same basic set of information that is included on the master list. Other information, such as the name of the author or editor, the name of the person authorizing the document, and document reviewer identification may also be included. It is a good idea to include all such information you choose to record and track on the revision history page of the document as well. Again, the document control policy should spell out what information about each document will be maintained. The document control elements should be consistently placed on each page of the document, normally in the header and footer. Other information, such as classification of information (confidential, proprietary, etc.) or copyright notices may be required by your organization as well. Organizations usually publish these requirements for employee use. 2012 David A. Baldwin www.davebaldwinconsulting.com 4 of 5

Once the required control elements are placed within the document, an entry in the document control master list should be made. Going forward, for the document to be considered controlled, its document control elements must always match those on the master list. Between the document and the master list, should control information get out of sync, the document is no longer considered controlled. References Robitaille, Denise. Document Control: A Simple Guide to Managing Documentation. Chico, California: Paton Press LLC, 2005. Dick, David & Kathy Bine. Documentation Management for Dummies. The Nor easter (July/August 2003). 2012 David A. Baldwin www.davebaldwinconsulting.com 5 of 5