• Replies 11 replies
  • Subscribers 413 subscribers
  • Views 375 views
  • Users 0 members are here
Related

Suppressing Deceased Constituents

Colleen Miller
$organization
Hello, we're having some troubles in suppressing deceased constituents and I'm hoping someone will be able to offer some assistance. We've been trying for quite some time now to figure out a way to suppress individuals who are deceased and households where BOTH members are deceased from lists and extractions. The way we've gone about it is to suppress any record where A1 is marked as deceased (as any household with a living member should have that member in the A1 position). Unfortunately, this suppresses any record in which one person is marked as deceased, even if the A1 constituent is not marked as such. We currently are not marking deceased individuals as inactive, but I know that's any option. Does anyone know of any pros or cons that go along with marking deceased constituents as inactive, especially within a household that has a living member? I assume it would not disrupt pulling the living member of that household, correct? And does anyone know why pulling on A1 Status = Deceased pulls in households with a living member? Thanks, Colleen
  • $organization
    Tessitura lets you mark the household itself as deceased! So in our consortium we make sure that all three records (HH/A1/A2) have a status of deceased when both members have passed. We also encourage all consortium members to inactivate deceased records, though in the months after there are sometimes lingering pledges paid by trusts, subscriptions used by unknown relatives, etc. -- Mike
  • $organization
    We've made it a practice to dissolve the household when one primary affiliate becomes deceased. We then ensure that there is still a connection between the two individual files and that the deceased file is inactivated.
  • $organization
    Colleen, I also struggled for months with this. No matter what I tried I was constantly finding my list manager query was not catching everyone. So what I found I had to do was create two different list manager queries. One for finding households with A1 deceased and one for finding (true) Individual accounts with A1 deceased. I then use both of these lists in my suppression for extractions and/or run my list manager lists against these to be sure I am not mailing to deceased. I have attached the queries to because they will not post correctly here.
    A1 Deceased List Manager Queries.docx
  • $organization
    We have had issues with this before, but have found a system that seems to work well. When an Individual is deceased, we inactivate their account. We ensure that all of our list pulls and extractions suppress any Inactive accounts. When the person who is deceased and is part of a Household, we do three things: first, we remove their A1 or A2 indicator (but keep them attached to the Household), then we inactivate their individual account, then we make sure the Address/Salutation fields in the Household reflect this change. I haven't had any problem with this method. Inactivating these accounts has produced no unwanted results as far as I am aware, and suppressing inactive accounts is very easy to do. Pulling Household accounts with 1 deceased member works fine.
  • $organization in reply to Terry Stevens
    Thank you, I'll take a look at this!
  • $organization in reply to Leslie McKinley
    Leslie, we are already swapping A1 and A2 when A1 is deceased. The problem is that when we then try to pull a list that only suppresses households where both members are deceased, it suppresses households where A1 is not marked as deceased. I'll look into the attribute idea, thanks!
  • $organization in reply to Summer Hirtzel (Past Member)
    Summer, thank you! I'm looking at all suggestions that have been made, but I'm glad to know inactivating an individual account won't affect pulling the household itself.
  • $organization

    What I’ve always done is  if A1 is deceased is swap it with the living A2.   Would that work for you?

     

    If you don’t want to inactivate if both are deceased – why not create an Attribute for the HH to code as Deceased HH. 

     

    From: Terry Stevens [mailto:bounce-terrystevens8563@tessituranetwork.com]
    Sent: Monday, February 06, 2017 4:01 PM
    To: McKinley, Leslie <LMcKinley@nycitycenter.org>
    Subject: Re: [Tessitura Development Forum] Suppressing Deceased Constituents

     

    Colleen, I also struggled for months with this. No matter what I tried I was constantly finding my list manager query was not catching everyone. So what I found I had to do was create two different list manager queries. One for finding households with A1 deceased and one for finding (true) Individual accounts with A1 deceased. I then use both of these lists in my suppression for extractions and/or run my list manager lists against these to be sure I am not mailing to deceased. I have attached the queries to because they will not post correctly here.

    From: Colleen Robinson <bounce-colleenrobinson8213@tessituranetwork.com>
    Sent: 2/6/2017 12:18:21 PM

    Hello, we're having some troubles in suppressing deceased constituents and I'm hoping someone will be able to offer some assistance. We've been trying for quite some time now to figure out a way to suppress individuals who are deceased and households where BOTH members are deceased from lists and extractions. The way we've gone about it is to suppress any record where A1 is marked as deceased (as any household with a living member should have that member in the A1 position). Unfortunately, this suppresses any record in which one person is marked as deceased, even if the A1 constituent is not marked as such. We currently are not marking deceased individuals as inactive, but I know that's any option. Does anyone know of any pros or cons that go along with marking deceased constituents as inactive, especially within a household that has a living member? I assume it would not disrupt pulling the living member of that household, correct? And does anyone know why pulling on A1 Status = Deceased pulls in households with a living member? Thanks, Colleen




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • $organization in reply to Summer Hirtzel (Past Member)

    Yes, thanks for the suggestion, Summer! This is the most related thread I could find, but I am trying to completely remove a  deceased A2 and create a new A2 constituent in the same household. I have already marked the A2 as deceased in the name field and inactivated the record, but I am unable to remove the tag. Any thoughts or ideas? Thanks so much!

  • $organization in reply to Danielle Schussel (Past Member)

    I believe that to remove the A2 tag, you have to reactivate the record briefly. It should be the first option in the Constituent menu when you're looking at the individual record. Then you can remove the A2 tag and deactivate again.

  • $organization in reply to Maery Simmons (Past Member)

    Hello Maery, thank you for the reminder. In addition to reactivating the record,. I needed to copy household contact information onto the individual, uncheck primary affiliation under relationships, decease and inactivate the record again, reassign the A2 to the other person (also under relationships), and regenerate the salutation. It turned out to be a quick fix but required a few more steps.