How to Implement Document Control

document control

For engineering projects, document control is a big deal.  Nobody has time to rework a design or report because a reviewer received the wrong copy, or document versioning wasn’t kept up to date.

At Roseke Engineering, besides using ProjectEngineer to manage our projects, we have a physical document control system in place.  It resides in the project management binder and keeps track of all of the project deliverables.  The basics of a good document control system are three fold:

  1. Planning
  2. Tracking
  3. Review

Planning

When a new project is won, each deliverable should be identified and a tracking system put in place.  If your project deliverables change you can update the tracking system.  The document owner should be identified as well as the document reviewers.

Tracking

Whenever a document is complete and submitted for review, even internally, a new document version number should be issued.  This ensures that there are no overlaps and it is clear which document version is being talked about.

Review

In the engineering world, documents need review.  It is important to track who has reviewed each document, when they reviewed it, and what the comments were.  At Roseke Engineering our project management binder contains a sheet for each project document and a place to enter review comments.

You can download the [download id=”1221″] and adjust it as you see fit.

About Bernie Roseke, P.Eng., PMP

Bernie Roseke, P.Eng., PMP, is the president of Roseke Engineering. As a bridge engineer and project manager, he manages projects ranging from small, local bridges to multi-million dollar projects. He is also the technical brains behind ProjectEngineer, the online project management system for engineers. He is a licensed professional engineer, certified project manager, and six sigma black belt. He lives in Lethbridge, Alberta, Canada, with his wife and two kids.

View all posts by Bernie Roseke, P.Eng., PMP

Leave a Reply

Your email address will not be published. Required fields are marked *

*