Cross Function Process Map for Document Control

[Moldmaker1]

Looking for example process maps on doc control (creating, updating, control of documented information, etc.). Re-doing some of my procedures into process maps (attached simple Visio example of my format). Any help or links to any examples would be appreciated! This is my first post, hopefully I'm doing this right.

 

[normzone]

Not exactly what you're looking for, but it should go something like this (serial numbers sanded off and repainted, from ISO 9001:2015)

When creating and updating documented information, how is this information identified and described?

What formats for documentation are appropriate?

How is documented information reviewed for suitability and adequacy?
How is documented information approved for suitability and adequacy?

How is documented information required by the management system controlled so that it is available and suitable for use, where and when it is needed?

How is documented information required by the management system stored and preserved, including preservation of legibility?

How is documented information required by the management system controlled to ensure control of changes?

 

[Pancho]

IMHO, document control is a collection of related short tasks that are not so well suited for a single linear flow chart or process map.

But if you must draw one, you may need to show unconnected separate boxes, as listed. I'd omit the arrows, as task execution is not necessarily linear.

1. Composing new documents
2. Publishing documents
3. Updating documents
4. Reviewing, approving and re-approving documents
5. Monitoring documents
6. Identifying changes

Here is a sample document control procedure.

 

[Marc]

From the mid-1990's I have used flow charts/process maps quite a lot. In the "early days" they were simple, not like process maps of today. When ISO 9001:2000 came out I did a .ppt presentation for clients at the time which had some simple flow charts for some systems, including document control. Looking at it now, it's pretty basic, and there are few changes I should make, but it was mostly something I used to one-on-one mostly in small companies to teach them the basic requirements for some systems of which document control was one.

It's not great, it's simple, it was originally made for teaching some basics one-on-one, and it's old, but it may give you some "food for thought" - Flowcharts for 2000 - Most of the basic requirements haven't significantly changed.