I guess it all depends on how much work you want to do.
A couple of assumptions:
1) you have one document format with a document number
You have 300 specifications that are all "Document #: 184.108.40.206 Product Specification" (because they are all the same format), because you don't want to do "Document #: 220.127.116.11 - 18.104.22.1680.
2) But the actual document title is "22.214.171.124 Product Specification Widget"
I would make that particular document Revision # 2.1. Because the format of the document has not changed, some minor data has.
3) I would put the following in the document revision log: Your document revision log format, of course applies:
Doc #: 126.96.36.199 "Product Specification" Revision: 2.1 Date of Change: xx/xx/xxxx Reason For Change: "Changed Product Specification for Widget per Customer to include 275 doohickeys in box vice 300".
If that makes sense.
Of course you have to make sure that the most recent document is in use and that any training about the changes has taken place and is documented.
There are of course all sorts of "rules" about document revision out there. But if the standard you are audited against does not specify one of those rules, make it easy, ensure the document in use is the correct one and have that documented.
I have roughly 400 SSOP's that all have the exact same document format. I'm not going to change revision numbers on all of them if I decide to change a cleaning practice on one piece of equipment.
MarshallGo to the full post