Just found this site whilst surfing for any online info / examples of a Forward Schedule of Change - what a find !!

I'm currently doing some service improvement work on change / release processes and my client keeps saying they don't like the current FSC, but can't articulate why - only that it isn't that easy to read. I think what they really want is a second version destined for the user community rather than the IT community, so I'm trying to accommodate both.

I use a simple Excel spreadsheet - some colour coding, with keys at the bottom of the page but nothing fancy.

I'm looking for inspiration really - any ideas or examples of how other people format and present the information.

As posted previously we use Sharepoint - it has benefits and drawbacks - take a look - we have in the past used the calendar in Outlook - if you have Exchange then you can share the calendar with whoever.

One way to get what your clients need Jools is to get them involved in designing/modifying an existing schedule. Not necessarily form technical stand point, but spend an hour or two with them going over stuff like elements to be included, layout, colors, etc...

I use a simple Excel spreadsheet - some colour coding, with keys at the bottom of the page but nothing fancy.

My orgaisation uses the same format, extracted directly from our tool via a reporting engine and squirted into Excel; our tool has no inbuilt functionality to deliver this view.

Just now working with the reporting guys to see if we can make this look more like a MS Project Plan layout with serviecs/platforms etc down the side and dates/times across the top.

Changes would be represented by blocks colour coded for type and impact, and any potential conflicts or dependencies (based on a knowledge matrix we maintain) would be highlighted by a linking line (or similar).