As part of our last capital campaign, donors could have spaces named depending on their giving level. There wasn't any particular appeal for this. Some chose specifically to give a set amount in order to name a space, and other top donors were presented with various special naming opportunities befitting their level. As such, there isn't a specific source code tied to an appeal. However, we want to record both the ask and those who chose to name spaces in Tessitura. Luckily, the gift officer has a very thorough manual spreadsheet with the details.
My question would be, where should we actually record this info? My gut reaction is to record named spaces as an attribute where the attribute type is Named Space, and then the details are the name of the space itself. Does this make sense, or is there a better way to accomplish this?
Hi Kevin Hower and fellow Named Space folks. Curious how you chose to move ahead with this in your instance. I am looking into a similar situation, however I would like the named spaces to be limited and attached as one per person, thereby avoiding any duplication in gift officer asks. Has anyone worked with a limiter like this? Named Spaces as seats in a performance, maybe?
We ended up going with research notes with a specific note type. It's fine. The info is all there, but it's not super easy to access via reporting. You still kind of have to know who all of your named donors are before you pull the list.
I think for specific naming campaigns like selling bricks, benches, etc. I would do an elevated event. The spaces or items to be named would be event levels. The hiccough with this plan is that it doesn't work super well for extended capital campaigns that cross fiscal years.
The only other thing that I can think of would be a custom attribute with attribute types that match the named spaces. A lot of manual work to maintain, but it would be the easiest way to get quick access to the whole list.