Yes, we look after the New Zealand wide system - so have a failrly comprehensive array of change tracking mechanisms and service action request process where changesa re allocated a sequential number and date. We schedule changes on a shared Resource calendar, and usually supplement the supplied change documentation with details of local customisations and in-cycle fixes. Making use of categories for different types of changes is handy to differentiate e.g. a Map roll forma product fix. We also have issue tracking solutions in place so we can internally mark an issue as fixed by a particular update or change.
Changes are raised with rollback steps as well so it is possible to remove a change and a change usually has enough detail to break down the parts or components and verfiy they are working with user and system testing.
It is quite useful to have details of historic updates and dates in calendar form and One Note is good at combining multiple types of documents into a comprehensive whole, along with checklists.
I wish you well in your moves in that direction.
-Jo.
