A Policies Document for NXT that is less "How to" and more "How we do"

Victoria Mueller

Hi All,

I am new as a Data Analyst to my Healthcare Foundation, and my first task is creating a Policies and Procedures document. Realistically, I know that most fundraisers and employees will not read through a 100-page document. The classes that BB University offers in NXT are great for teaching the "how to" for different areas of the database.

I would like to create a smaller document that includes fewer general instructions like "how to add a constituent" and is more "these are our mandatory fields…this is when you add a constituent…this is our policy on updating constituents…" assuming team members have already taken their assigned BBU training courses. This is just an example, I would also include everything else like gift entry, access, etc.…

I really want this to cover all bases and include our best practices to keep data integrity and keep our database clean without being unnecessarily long. I am new to this position and new to Raisor's edge, I would love to hear from some of you folks with experience!

Is this a good idea, is this something you have done before? If so, please share and attach any examples or outlines I can learn from! I have been searching but can't seem to find anything that aligns with what's in my head or what is new in NXT lol.

Dariel Dixon

Welcome to the community @Victoria Mueller. I always suggest taking a look at @Spring Velazquez's post.

https://community.blackbaud.com/discussion/60177/policies-procedures-manuals-oh-my

It's a great starting point. I think that creating SOPs and other documentation varies wildly. I would not worry about the length of the document, as long as it does what you need it to do. You'll never be able to mandate people to read it, but you can always refer to it if you have rule breakers.