Higher Ed Users - Employee Status Tracking

Lisa Geiersbach

For Higher Ed Raiser’s Edge users, I have a very puzzling question-

We currently track current employees and previous employees as constituent codes.  Currently, to report on employee donor participation rates for, say, 2018, I need only query by code of Current Employee or Previous Employee with start/end dates to indicate they were employed during 2018.  Easy and simple.

However, we are now wanting to start tracking these employees by their status (such as part time, full time and adjunct) to compare employee donor participation rates by subgroup.   This makes things very tricky….  I could add the subgroup as a relationship to our Organization with start/end dates each time their status changes, but what if their status changes mid-year, or they are a previous employee with multiple status’ in 2018?  Also, relationship status’ are not able to be filtered in reports.  Not so simple and very complicated.

Alternatively, I could add the status as an attribute.  However, attributes cannot have two dates (date from and date to), which would make it impossible to decipher which year to place them in for that particular status.

I am stumped on this one…..has anyone on here dealt with a similar situation and have a possible solution?   

Lisa

Lisa S. Geiersbach
Director of Advancement Services

Northwood University

 

Larry Wheeler

Maybe you can use two attributes for Begin and End?  If the End attribute has a null date, then = current employee?

I know having a bunch of attributes isn't fun, but that was my first thought.

Dariel Dixon 2

That sounds like that could be a problem.  I was thinking maybe you could add a gift attribute and query off that, however that would require knowing every employee's status at the time of the gift.  That might be a lot of work.  However, I think a gift attribute may be easier than a constituent attribute as it should not change.  The constituent status would change too often for it to be much help.  You could still include/exclude the attributes on the reports, so that is an option as well.  It may slow down your gift entry, so it would be a bit of a trade-off.

Christine Cooke 2

Dariel Dixon:

That sounds like that could be a problem.  I was thinking maybe you could add a gift attribute and query off that, however that would require knowing every employee's status at the time of the gift.  That might be a lot of work.  However, I think a gift attribute may be easier than a constituent attribute as it should not change.  The constituent status would change too often for it to be much help.  You could still include/exclude the attributes on the reports, so that is an option as well.  It may slow down your gift entry, so it would be a bit of a trade-off.

I like the idea of the gift attribute also -- I kind of use it that way but I put the graduation year of the student(s) on the parents gift records to help with participation reporting.