We're currently embarking on a documentation project: Procedures and Policies. I'd like to know those who have carried out something similiar, how do you find the right balance of what to write? I ask this because Raisers Edge has its own help files (Tools Help) as well the PDF guides. Working under the assumption that everyone is trained on RE before they start using it, the guide we write IMO should be more procedural based? I don't want to completely re-write Blackbauds Documentation, and so would welcome the thoughts of others who have also pondered this. Many thanks Reza Islam | Data Control Manager The Children's Society | Edward Rudolf House | Margery Street | London | WC1X 0JL *: reza.islam@childrenssociety.org.uk (: 020 7841 4536 | Fax: 020 7841 4500

We are dealing with the same issue.  There is a fine line between polices, how we want it done and procedures, how to do it.  What started out as a standards guide morphed into so much more. I will keep the forum posted on how this projcect progresses.