You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present, the software does its best to match donors to the Voter Registration List (VRL). If there is no match, OAE staff look the donor up in the VRL manually. If a manual search doesn't work, we send postcards to donors for them to fill out and return to attest that they meet all matchability requirements. When we can confirm ourselves through any part of this manual process that a donor is matchable, we go to the contribution on OEP.org, click "Select Status" and click "Match Contribution" and then enter the match amount and then click "Submit." Handling these VRL no matches is 90% of our work.
We find that the same donors give frequently, often setting up recurring monthly contributions. When those recurring donors are no match on the VRL, we have to go through all steps of the above for them every time they give. This is in part due to the fact that the "Previous Donations" section at the bottom is not populated unless the software finds and someone selects a particular entry in the VRL as the correct one.
Example (if this donor had been a no match to the VRL, we'd have to go through the above steps in the manual process all 21 times!):
So, what we are hoping for is some way that OAE staff can identify these recurring donors that we have already confirmed are matchable manually when they first gave. Some thoughts:
(1) If we select "Match Contribution," can that donor then go into a new database and if a new donor entry matches either the VRL or the new database, then the software shows us somehow that they were identified as matchable?
(2) If there is no VRL match, can the software just populate the "Previous Donations" with that donor's entered address, and then if they give again, at least we can see that they have given multiple times and can see that we already matched them before?
I am open to other ideas. THose were just two random thoughts.
The text was updated successfully, but these errors were encountered:
At present, the software does its best to match donors to the Voter Registration List (VRL). If there is no match, OAE staff look the donor up in the VRL manually. If a manual search doesn't work, we send postcards to donors for them to fill out and return to attest that they meet all matchability requirements. When we can confirm ourselves through any part of this manual process that a donor is matchable, we go to the contribution on OEP.org, click "Select Status" and click "Match Contribution" and then enter the match amount and then click "Submit." Handling these VRL no matches is 90% of our work.
We find that the same donors give frequently, often setting up recurring monthly contributions. When those recurring donors are no match on the VRL, we have to go through all steps of the above for them every time they give. This is in part due to the fact that the "Previous Donations" section at the bottom is not populated unless the software finds and someone selects a particular entry in the VRL as the correct one.
Example (if this donor had been a no match to the VRL, we'd have to go through the above steps in the manual process all 21 times!):
So, what we are hoping for is some way that OAE staff can identify these recurring donors that we have already confirmed are matchable manually when they first gave. Some thoughts:
(1) If we select "Match Contribution," can that donor then go into a new database and if a new donor entry matches either the VRL or the new database, then the software shows us somehow that they were identified as matchable?
(2) If there is no VRL match, can the software just populate the "Previous Donations" with that donor's entered address, and then if they give again, at least we can see that they have given multiple times and can see that we already matched them before?
I am open to other ideas. THose were just two random thoughts.
The text was updated successfully, but these errors were encountered: