Allowing multiple people to edit the same Microsoft Project file simultaneously - Imagine this scenario: two or more schedulers want to make adjustments to different parts of the same Microsoft Project file. Because there is no way to have multiple people edit the same Microsoft Project file at once, the team would have to take turns making adjustments to their respective sections. With SSI's Change Tracking tools, the same copy of the schedule file can be given to team members, who can go and record the changes they make to the copy. The Tracked Changes file (.tcs) that is outputted by the Change Recorder tool can then automatically replicate the changes made into the "live" or "real" file using the Change Importer tool.

  Making changes to an "unlinked" Master Project when working in a Multi-Project Environment - Teams working in a Multi-Project environment will be working with a collection of Subprojects that come together to create a Master Project. SSI's recommends teams integrate "unlinked" Subprojects on a regular basis to create a temporary "unlinked" Master Project. Changes made in an "unlinked" Master Project file will not be automatically reflected in Subproject files, so SSI recommends teams treat this file as read-only. However, it is often the case that teams will find it necessary and unavoidable to make live changes on the fly to an "unlinked" Master Project. Changes such as dependency changes, duration changes, changes to fields, etc. In the past, these changes would just need to noted and the information passed down to the Subproject Owners to recreate the changes in their Subproject files manually. Now with SSI's Change Tracking tools, Teams can record changes made into the "unlinked" Master Project and flow the Tracked Changes file (.tcs) that is outputted by the Change Recorder tool down to the Subproject Owners. Subproject Owners can then automatically replicate changes that affect their Subproject file using the Change Importer tool.

  Training Support - For many organizations, allowing someone who is new to Microsoft Project or still learning the organizations internal scheduling processes is not an option. Because of the significant performance management and deliverable requirements of the schedule, allowing someone new to Project edit the live schedule before they have learned all the nuances of the tool is usually a recipe for disaster. Microsoft Project is complex and requires a lot of training to master after all! Because of this, many organizations' training process will involve junior level schedulers shadowing more senior level schedulers to just watch what they do, but not actually be able to get that hands on Microsoft Project experience. SSI's Change Tracking Tools allow team members to independently make changes to a real schedule for training purposes. These changes can be reviewed step by step, offering a practical learning experience in managing and updating a Microsoft Project file.