Prospect/Portfolio prioritization

Jessica Thrift 2

Hey there-- I work with a handful of gift officers who have a portfolio assigned to them. They want to start prioritizing their portfolios, entering their "top 25" and "next 25" prospects so that they can, for example, make a list in NXT webview with the top 25 and next 25 prospects, and make sure they have a future action scheduled for all 25 of them. I am tasked with determining the best way for them to indicate each donors relative "ranking" within the portfolio. We do have the prospect module. One idea I have is to use a rating for prioritization. For example, if I create a rating with a source of "Major Gift Office" and the category is "rank" or "priority" then they could enter the 1-25 and 26-50 values in the description, and they can build lists based on that priority value. 


I was also considering a constituent attribute (I am resistant to this for a few reasons, but I'm not unreasonable). 


Do you do this? Do you have any tips, experience, or advice to share? Thanks!!! 

Ryan Hyde

We do something a little similar, and we do track it through a constituent attribute. Each solicitor divides their list up into three groups:


1.) Super hands on, active high value donor

2.) Donors who engage, but who do not increase their giving

3.) Major gift donors who engage but do not respond to most cultivation/soliciation efforts (self paced/guided donors)


I think categorizing rather than ranking works better for these types of things. Each group needs to be treated differently, and the first group requires more attention than either the 2nd or 3rd, and with this system, you don't need to fret over the distinction between the 25th and the 26th donor in your hierarchy.


 

Jessica Thrift 2

Ryan Hyde:

We do something a little similar, and we do track it through a constituent attribute. Each solicitor divides their list up into three groups:

Thanks so much for that info, Ryan. Do you have the prospect module as well? I am wondering now, after having a little time to mull this over, if I should use the Prospect Classification field because

1. it's exclusive (I have a fear of someone inadvertently creating multiple entries of "top active prospects" as well as "hands off prospects" on the same record)

2. it keeps the grouping/ranking close to prospect management and out of the general "pool" of data, which is everything in Attributes

3. it is physically close to Prospect Status on the screen, and since they are closely related concepts, they will often be used and updated together. 


Of course, I still have not taken any action on this, so if anyone else wants to chime in, holler at me! 


Thanks again!  

Jen Claudy

Just FYI, in Config you can set an Attribute to "Allow Only One" and RE will not allow duplicate Attributes when saving a record.

Jessica Thrift 2

That's true! Good reminder, Jen. Thank you.