This post is for you to get in touch with me about anything you want (all I ask is it’s in some way related to the Project management System). If you have something to say which isn’t in direct response to something I’ve written about, this is the place to say it, so get commenting 
Change Control:
This is something that I don’t specifically remember seeing throughout the logbook, so correct me if I’m wrong.
If the customer is being allowed to look through the project materials and such as well, you may want to integrate in, the ability to submit change requests within the site. Changes need to go through an approval process, determine their impact to the overall project, and based on the overall impact, if it would be something that the customer was still willing to make happen after new financial quotes had been drawn up to take that change into account. Basically, the ability for the customer to say, “I would like to go back and make ‘this’ change.” The financial side and everything else could be done elsewhere, but it would allow you a way to keep track of them required changes. If the change is eventually approved, mark it as approved in the system, and then allocate new tasks based to the group to make this change happen.
Just an idea.
Hi David, nice to see you visiting again!
This is something that has been touched on a little, but I refer to it as tickets. But you’re right. It would need to tie in much more with the bigger picture, such as the impact on milestones and the financial side.
I’ll be doing a post exploring some of the options with ticketing, what should be involved, some UI sketches, what else is afffected etc, so I’ll be sure to get your input on that one.
Also, I just double checked, and you actually gave some feedback on it in on of the threads here.
I guess I forgot what it was because I was thinking of a ticket as something that needs attention and not a change request.
I think it’s safe to say (unless there’s a huge backlash of people saying they want both) that tickets and change requests are pretty much interchangable so in the sake of keeping the implementation nice and simple, and to avoid cluttering the UI with 2 options, I will just use tickets.
Your ‘Project Trackr’ link in the footer is missing a ‘k’
Just spotted that so I thought I’d tell you.
Hi
thanks for pointing that one out. It took me a while to realise you where on about the actual target instead of justt the text. Fixed it now though