Attached is a procedure for writing documents

[energy]

Document for Creating Documents

Attached is a procedure for writing documents. I pulled it from my achives as an example of a ludicrous document. Believe it or not, this is real. I changed a few things to protect the innocent. Can you imagine auditing to this? Some people have just too much times on their hands. I would immediately cite the inappropriate use of the terms Header and Footers.

 

[CarolX]

Re: Document for Creating Documents

When I first came to work at this company over 9 years ago, I found something similar written by the ISO "Consultant". What a bunch of garbage!!!! Straight to the shredder it went....on it's merry way!



Carol

 

[Al Rosen]

Re: Document for Creating Documents

Attached is a procedure for writing documents. I pulled it from my achives as an example of a ludicrous document. Believe it or not, this is real. I changed a few things to protect the innocent. Can you imagine auditing to this? Some people have just too much times on their hands. I would immediately cite the inappropriate use of the terms Header and Footers.

Energy, it seems reasonable to me except I like having the revision history in the front of the document.

 

[Wes Bucey]

Re: Document for Creating Documents

Attached is a procedure for writing documents. I pulled it from my achives as an example of a ludicrous document. Believe it or not, this is real. I changed a few things to protect the innocent. Can you imagine auditing to this? Some people have just too much times on their hands. I would immediately cite the inappropriate use of the terms Header and Footers.

It may be ludicrous in Energy's opinion and mine, but I can attest that I have seen very similar wording and document length for a "document creation procedure" at dozens of companies.

Some time ago, I recall threads and comments about bloated Quality Manuals versus briefer ones. Laura even has a Landmark one that consists of two sides of one sheet of paper.

One company ($1 billion plus in sales) that had a "document creation procedure" similar to energy's had a 1,000 page QM PLUS thousands of pages of Procedures. (I have no idea how many "work instructions")

When the Configuration Manager of that company showed me the QM, he BRAGGED about how "cool" it was with absolutely no irony or sarcasm whatever. The "Procedure for Identifying Wires and Cables" ran close to 200 pages! I could only conclude someone in the organization had stock in all the paper companies and forests where pulp was harvested.

 

[Craig H.]

Re: Document for Creating Documents

Aaaarrrrgh!!!!

 

[Mike S.]

Re: Document for Creating Documents

Attached is a procedure for writing documents. I pulled it from my achives as an example of a ludicrous document. Believe it or not, this is real. I changed a few things to protect the innocent. Can you imagine auditing to this? Some people have just too much times on their hands. I would immediately cite the inappropriate use of the terms Header and Footers.

I agree that the posted procedure is nuts -- waaaay too detailed and full of ... stuff. However, I have for several years always had a basic WI regarding minimum requirements for QA documents. Call it a procedure for writing procedures, or a WI for creating WIs. Whatever. It helped us.

 

[Laura M]

Re: Document for Creating Documents

The closest I've come is referring to a template (form) for all procedures in the document control procedure.

Did this company ever acheive ISO?

 

[energy]

Re: Document for Creating Documents

The closest I've come is referring to a template (form) for all procedures in the document control procedure.

I've attached a template. I'm for uniformity, otherwise we'd have documents all structured differently and "personalized".

Did this company ever acheive ISO?

No!

 

[Rob Nix]

Re: Document for Creating Documents

After reading the procedure in energy's post, all I can say is, WOW!

Like Wes, I have seen many like it, having come into organizations and inherited those monsters. And like Laura, I almost always provide a simple template instead.

I did get a kick out of the statement at 5.4.6 that said in effect, "make the procedure steps concise", although this procedure (the model for making procedures) was six pages of the nine!!!

My guess is that nobody but the procedure writer has ever read that document. If fact the procedure writer probably doesn't follow it, but, instead, takes an old procedure or a template - deletes non-applicable information, and adds the new. We (my company) do not even have a procedure for making procedures, and we seem to get along fine.

 

[energy]

Re: Document for Creating Documents

When I first came to work at this company over 9 years ago, I found something similar written by the ISO "Consultant". What a bunch of garbage!!!! Straight to the shredder it went....on it's merry way!



Carol

Was it something like *****tek?