Dear all,

I have been asked to produce a audit report on the data quality of Raisers Edge. I have begun to create queries for the most obvious things like title missing, postcode blank, addressee/Salutation blank etc... Is there anything else outside of the norm I could include in my report to determine whether we need to pay for the clean up to be done externally.

All advice will be appreciated.

Many Thanks

Ryan Abbott

Really depends on what you define as an Organisation as 'missing' or 'unclean' data.   Seems you've cover the basic stuff, which I would hope you didn't have many that hit those criteria :)  If you are getting a lot of hits on the queries you've mention and still getting new ones, I'd look to implement some serious data entry procedures.  In the database I would mark those key areas as essential, so you can't even create/save a new record without them being present.
 

Now for Database cleaning, I would look at cleaning out dead wood.  As I'm sure you're a fund raising Organisation I'd look to clean out those that haven't giving in a finite period, say in the last 3+ years, marking them as archived. 

Andrew, I am going to have to disagree with you on some of your points.  I think it is essential to have a complete list of queries to run regularly to find errors in the system.  And there is very often no way to stop RE from accepting incorrect data and human error becomes a factor.  Yes, where you can you should make data required but even though it is required does not mean it was entered correctly!  RE is also missing a huge checks and balances with its business rule where it runs only on opening a record not on closing - so conditionally required fields (based on internal policies i.e. records with a foundation constituent code must have a foundation type attribute.) do not get caught until either a) you open the record again or b) you run an audit query.

I completely disagree about cleaning out dead wood.  I believe there is absolutely no value in marking records as inactive simply due to inactivity.  It does not make searching quicker or have any other value.  Every time I run a query for a mailing, prospect meeting, phone-a-thon I am using giving dates as criteria - sometimes 3 years or sometimes 5 or more when we are focusing on reactivation.  I keep them as active records to be included in these pulls whenever needed.  I only inactivate records where a constituent has asked to be "removed" fromt he database or receive "no contact".

Ryan, I have about 10 queries that I check on a daily bases to do cleanup for our data base, but two of them really help:   

One query is filtered on the field "Constituent" and I pull in "last changed by" - exclude yourself

then the other queries is filtered on the field "Constituent" and I pull in "Added by" - exclude yourself

With these two queries I can see who in the office has set up a brand new constituent and also see who makes

changes on a constitutents record.  These are the ones I check top to bottom.  I'm the only one in the office who can enter gifts though, so any errors there, then I know it's me who made the error.  Hope this helps a little bit

Lynn Taniguchi

Have you considered the integrity of the tables being used. ie constituent, attributes, funds, etc. Our are all being used incorrectly so need to be revamped and cleaned up.