Address Finder Update

Chris Pearce

I am running Address Finder update for the first time and am confused about the best "Head of Household" processing selections. Most, but not all, spouses have a separate constituent record so I believe that selecting "export both constituents separately" is my best bet.  Yet the documentation I've read (and customer support folks I've spoken to) seem to discourage that choice.  Oh, and  I understand the differences between the options, just not understanding how it might impact my data when i run Address Finder. Thanks for any insight.

Rachel Slager 2

Can you clarify: if you are exporting both constituents, shouldn't they have the same address?



Generally, address finding services charge per person returned, so if you give them both, you pay for both even if they have the same address.  That's one reason not to do it, but I'm not sure how AlumniFinder structures charges.  Second reason, an outside resource is providing you with addresses which you'll most likely want to clean and structure in accordance with the way you record data - like spelling out streets, or often times, correcting the returned data for spelling errors.  If you export both people, seems like you'll be double cleaning.

Christine Cooke 2

I understand Rachel's point about some services charge per record and doing each separately and having them have the same address would be a waste.  On the other hand, I look at each constit separately as an opportunity to find out if maybe the household has split and therefore you could end up with separate addresses for each "spouse" indicating they are no longer a spouse.  This would help down the line, because you would not be sending mail to Mr. and Mrs. when they are no longer.  And many times -- in my experience, they do not bother to tell you (unless it is very fresh and a hostile situation).



I think it can also depend on how consistent and confident you are about your HoH protocols/procedures.



You just have to weight the pros and cons for your org and what you want to get out of it in the end -- and what our budget allows if it a per record project.



my two cents.

Chris Pearce

Christine Cooke:

I understand Rachel's point about some services charge per record and doing each separately and having them have the same address would be a waste.  On the other hand, I look at each constit separately as an opportunity to find out if maybe the household has split and therefore you could end up with separate addresses for each "spouse" indicating they are no longer a spouse.  This would help down the line, because you would not be sending mail to Mr. and Mrs. when they are no longer.  And many times -- in my experience, they do not bother to tell you (unless it is very fresh and a hostile situation).



I think it can also depend on how consistent and confident you are about your HoH protocols/procedures.



You just have to weight the pros and cons for your org and what you want to get out of it in the end -- and what our budget allows if it a per record project.



my two cents.

Those are great points and I think you articulated my primary concern much better than I did myself: I am not confident about HoH protocols/procedures.  This helped immensely. Thank you.

Chris Pearce

Rachel Slager:

Can you clarify: if you are exporting both constituents, shouldn't they have the same address?



Generally, address finding services charge per person returned, so if you give them both, you pay for both even if they have the same address.  That's one reason not to do it, but I'm not sure how AlumniFinder structures charges.  Second reason, an outside resource is providing you with addresses which you'll most likely want to clean and structure in accordance with the way you record data - like spelling out streets, or often times, correcting the returned data for spelling errors.  If you export both people, seems like you'll be double cleaning.

Thanks for your insight.  We have a flat rate for this particular update, so the cost is not an issue.  I had not considered doubling the work on the back end, but I think it would be worth it in this case.  As far as your clarifying question: yes, they "should" have the same address. Thanks again for your response.