A place for Capacity Estimates in Tess

Hi everyone,

How does your organization record Capacity Estimates in Tess? I'm having problems figuring out where to store the Capacity Estimates that I do for our $50K+ level suspects/prospects. In an ideal world, I would like to be able to attach the Estimates to accounts and then use it for list pulls.

Note: We have done WealthEngine screenings in the past, and I read through the Forum posts and replies on inputting WE info into Tess, and that isn't what we're looking to do here.

Any ideas?

Genna Davidson, Arena Stage Research Associate (202-600-4028)

Parents
  • Genna,

    We did a wealth screening back in 2005 and put that data (a capacity number and a ranking of sorts) into attributes.  In 2007 we did another wealth screening as part of a special campaign.  At that time we set up a special moves management systems to track everything so I created a custom tab to enter things like "estimated capacity", "affinity" , High/medium/low gift estimates" etc.  - basically things that were solicitation related but didn't fit in solicitations.

    That campaign is now over so I have modified our custom tab and moved the data from the 2005 wealth screening into it.  So now our custom tab contains the special campaign solicitation information plus info from both weath screenings.

    The nice thing about the custom tab is that I was able to put in short descriptions about the weath screenings and the dates of the screenings (I also have a help document with more detail).  I like to imagine that its 5 years in the future and there is an entirely different staff looking in our database.

    Dale

  • I would like to "second" the idea of using a custom tab. The descriptions that Dale describes have been so helpful to us over the years to help new staff understand at a glance what they are looking at. Also, we have secured the tab so that Dev staff can see it, but no one else in the organization. We didn't really like the idea of capacity indicators being too visable to folks (and therefore have the potential to be completely misinterpreted without context).

    Good luck -
    Erin

Reply
  • I would like to "second" the idea of using a custom tab. The descriptions that Dale describes have been so helpful to us over the years to help new staff understand at a glance what they are looking at. Also, we have secured the tab so that Dev staff can see it, but no one else in the organization. We didn't really like the idea of capacity indicators being too visable to folks (and therefore have the potential to be completely misinterpreted without context).

    Good luck -
    Erin

Children