My compnay is in the process of implementing Change Management, Release Management and Configuration Mangement all at once. I've been assigned to write the policies for Release Mangagement. I have a list of release management policies, but I'm not sure how detailed they should be.
Should the actual policy detail how the policy should be carried out? For example, the policy for release documentation indicates that all releases should include documentation that outlines the specific components of the release; impact of the release; status of the release at each stage in the release cycle; acceptance criteria, test plans, etc.
Should I also be creating templates for each of these so the data collected is consistant?
Should I tell them where and how these documents should be stored?
Any suggestions regarding policies in general would be greatly appreciated.

having written a general policy for Change Management, you have my sympathies. Not an easy job.

Firstly I would suggest that in the case of documentation, you should write a procedure on how to complete any given document, in detail, giving examples wherever possible, screen shots if appropriate, where to store it, where the templates are to be found, any naming conventions that you require, what kind of evidence you need for testing etc. etc.

Then in your policy refer to the procedure as the guiding light.

In this way you ensure that the detail you want is given and captured. As far as I am concerned your policies should contain all the details that you mention.

It also means that if you change your mind on what you need (inevitable really) all you need to do is change the procedure, not the policy document.

In our general policy document I also detailed the consequences of non-compliance i.e. that anyone disregarding the policy was likely to be subject to disciplinary processes, and got it signed by a senior director