Create a Master Schedule |
![]() |
|
|||||||
| What is the best way to implement a system that combines different users' Milestones Professional schedules into a single "master schedule?" This is a popular question with more than one valid answer. This paper poses a "best practices" method for implementing a master scheduling system. | |||||||
| What is a master schedule? | |||||||
| A Milestones Professional master schedule is a compilation of separate Milestones Professional schedules (sub-schedules). Usually, the sub-schedules are each maintained by different people, each responsible for one project. Thus, the master schedule gives a view of all projects. | |||||||
| Changes to data in the sub-schedules appear in the master schedule. Any changes to the master schedule will not appear in the sub-schedules. | |||||||
|
|||||||
| Projects 1 and 2 in master schedule | |||||||
![]() |
|||||||
Things to consider before creating a master schedule
system
|
|||||||
|
|||||||
| Create a common format using a template or blank chart | |||||||
| By creating a schedule template or
blank chart, and using it for all sub-schedules, the format is consistent
and ensures that sub-schedules will merge successfully into the master
schedule. Distribute a copy of the template or blank chart to each person
entering project data into a sub-schedule.
Learn more about the differences between a chart and a template. |
|||||||
Format a schedule to meet your
needs. Focus especially on these areas:
|
|||||||
|
|||||||
Why is a common format so important? If one sub-schedule contains columns of duration values, percents complete, and end dates, and another sub-schedule contains columns of baseline dates and task names, then the master schedule will not know which columns to display. Thus, all schedules should have columns of the same format and placement. |
|||||||
| In this example, all sub-schedules and the master schedule would have this basic format: | |||||||
![]() |
|||||||
| After each person populates his sub-schedule, it's recommended that the schedule be saved to a shared network folder and that the name of the sub-schedule is passed along to the keeper of the master schedule. | |||||||
| Create the master schedule | |||||||
|
|||||||
| Common questions | |||||||
| In my sub-schedule, I want to track additional column data, not included in the master schedule merge. Can I do this? | |||||||
| Yes. Just be sure to add the additional columns to the far left or far right, outside the standard columns which will be merged into the master schedule. The master schedule will ignore those extra columns. | |||||||
| My master schedule serves as a "Friday Report" to management. How can I keep a historical record of each week's report? | |||||||
| Each week, save the schedule under a new name, for example "Projects Report 11 March 03.ml7". Then choose File | Master Schedule and uncheck Treat the Current Schedule as a Master Schedule. That way, your original master schedule will be updated, yet the newly named "historical" schedule for that week will not be updated. | |||||||
| Now that we have distributed the schedule format, we want to change the format. How can we do that? | |||||||
| Save the new format as a template.
Have each person apply that template to his current sub-schedule. But
first, have them back-up the schedule in case the template makes
unwanted changes to the schedule.
NOTE: This can only be done if the template changes are minor. For example, extensive column properties and column ordering changes which are saved in the new template and then applied to an existing schedule may have adverse effects on the existing schedule. In another example, if the template changes are made to the Toolbox symbology, this new template can be applied to the sub-schedules without adversely affecting the schedule data. |
|||||||





