![]() But sometimes because they also (wrongly) think you have to have a way to keep track or have a very rigid interpretation of the particular clause/requirement. Sometimes because they're just testing your system - they ask a question, and see how you respond. (How many people ever actually use it? Very, very, very few - if any - I'd warrant in many cases.) If you have a reasonable way of communicating this to your readers (and that could be as simple as the supervisor telling people, the QM/Doc Controller or whoever sending out an email to advise what changed, or even using automated methods such as Track Changes or the history available in SharePointPortal), then you definitely don't need to do it via a 'Revision History'. Often in IT system specifications.īut in other cases, often they're not exactly earth-shattering - a minor change to a procedure for example. They are in contracts, for example,and legal docs. My view is: keep track of changes only IF it's necessary, eg, they're vital. In your system and in your environment, what's the risk if you don't? Or the consequences? Click to expand.Sometimes because they're just testing your system - they ask a question, and see how you respond.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |