Trying this attachment again, not sure it's opening in the original...
Good day dwells
I have been in both sqf & brc and use a list of changes at the bottom of each and found that works better, at least for me. You do have to change revision number at each review or change to doc and add the new dates. I also add the version number in the title. Here is an example
We use an excel spreadsheet to maintain our revision control. Yours looks like it could basically do the same thing.
1. Your spreadsheet (if you maintain the spreadsheet and not a history of amendments on the document itself) should be more of an archiving system; meaning that you should track the document each time it is changed; not just once. - Your headings should be something like this: Document Name, Amendment, Reason for Amendment, New Issue Date, Old Issue Date
2. In place of the spreadsheet, you could keep all of the issue information and history of amendments on the document itself. For example, you could have your documents all list "Document name, Date created, Revision Date, Document Creator, Change to the document, Who made the change." as you stated, then you could add your history of amendments to the bottom of the document. This will make some of your documents fairly lengthy if you make frequent changes.
3. You should have an archival system - The old issued (obsolete) documents should not be deleted, but they should go into an archive folder, so that you can keep track of those documents even though they aren't in use. Those documents should not be able to be accessed by anyone outside of QA so that document control is maintained and older versions aren't being distributed for some reason. We've found that our archive has been useful to us at times.
Our SOPs are in a somewhat similar format as GFDoucette's. We have the version, issue date, person completing, etc. Our history of amendments are located at the bottom of the documents. We use our spreadsheet mostly for production related documents, since a history of amendments isn't practical when you've gone through 5-6 versions and you need that space for record keeping.