I implemented a workaround for moves management within RE7. We used Action Type and Action Status to record pipeline moves. Having action dates on these meant we could report on: number of moves per month, how many prospects in a fundraiser's portfolio were at each status, (average) time elapsed between moves, history of pipeline activity and analysis of bottlenecks etc.
I was excited to see NXT had a Prospect Status Date field and a Prospect Status History pane. However, these fields were not replicated within RE7 and we can't export this data from NXT to do custom reporting.
Please add the metrics above to the Fundraiser's Workcentre so we can continue to monitor these and improve our Moves Management.
I think this is rediculous, that they gave an option, but then don't actually allow us to do anything with it. Its been requested 7years ago, and nothing. Its like standing infront of a carmel popcorn store, smelling them make, it, but you cant eat it. Its a waste of time to even use the propsect management tool if you cant report on it.
I note that this idea was posted in 2016. It seems to me that this is some of the most important functionality a fundraising database could have - the ability to track moves.
It is incredibly frustrating not to be able to track development teams progress with donors through the pipeline. This is a basis measurable for development officers and we are unable to report on it either in RE7 or NXT.
Please make this happen! It's such a good idea to have status history and comments, but the information is completely unusable on a constituent record in webview. It needs to be visible in lists, Analyze, and to be exportable.
We definitely need it! i need to be able to report out how many prospects moved into/out of a status each month! this is beyoond frustrating!
Need to be able to report out how many prospects moved into/out of a status each month. The data is clearly in NXT, but cannot currently get it out, even through Insight Designer. Using custom fields is certainly a workaround, but if the data is there, why not just open the 'prospect status' and 'prospect status date' fields as 'measures' in Insight Designer so we can filter based on the status and date. Certainly would resolve a lot of headaches and make things more efficient.
Absolutely needed. Our fundraisers will be entering a separate action just for the "move" so we can report on them.
Ditto!!!
You're almost there! You know it's an important metric to track, now please let us filter and report on it!
Agree with Craig, I would love to avoid creating a workaround if the data is on the webview. It would be great if these data could be exported to the database view or just having a nice reports on: 1) how long prospects stay on a particular status; 2) How many prospects have been moved from status A to status B.
I'd rather not create a workaround when clearly the data is there, we just cannot access it. I'm waiting patiently until the day I can give an accurate moves management pipeline report to our team, whether out of NXT or RE...preferably both.
We are also working to create work-around reporting in order to capture duration of prospect status via Actions. It would be a lot easier to just have a date field with prospect status so we didn't have to worry about custom reporting and excel spreadsheets to do the job of the database.
Ability to report on how long prospects are in different 'statuses' or 'stages' is critical to our fundraisers' work and performance evaluations. Our chief philanthropy officer the senior management team are in need of this reporting capability and they continue to ask for this feature to be developed - either as exportable fields in database view, or as a reporting feature/analyze function in the NXT view.
Sure would be nice to be able to use the Prospect Status Start and End dates in Lists, or as a Filter field anywhere. Right now you can only see Overdue ones (time set on the back end to display a pop-up) when you open the individual record. Thanks
We also rely on the Action Status table and have it set a mandatory field in database view.