Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
AVE-38 Business consultation to understand the current Bequest process
Business Process
start from when the team is notified of a bequest all the way to the point where they complete work and pass the money to the relevant stakeholders
Two types of bequest:
Normal standard Bequest
Through a Trust
Hapreet Barsan does this job mainly and is Managed by Demelza Birtchnell
Obtain the copy of will and assess. Check if the person is in Jarvis. If existing record, decease the person. Check if opportunity exist and mark it as Closed Won
Alexander Miller’s team manage the Planned Giving, they go out and acquire Bequest opportunities
There are cases where the Bequest have some conditions which needs to be consulted with office of general counsel. (if we can receive the donation or not)
Create a Estate account. Primary contact is usually the solicitor or the executor. Secondary contact is the deceased contact. 90% of the time contacts are brand new
create org account for the law firm and link the solicitor to that account.
For existing contacts, the change the account now to the new Estate Account.
Draft email to the delegate and request approval from office of general counsel
Prepare spend plan
Try to store all documents in Jarvis, but there are some documents that are stored in university drive specially if there are sensitive information
if contact type has alumni, it is considered as Alumni .the same thing applies for Gift Recognition credit. For estate, we check the Signator contact for alumni contact type.
Reports used are in USYD Planned Giving Dashboard. Reports on Gift Record Type is “Planned Gift”.
The diagram below is focused on the creation of contacts and accounts.
Record Structure
Illustrated below is the structure of record for Bequest process. It needs to be fleshed out and communicated to the team with proper documentation. Based on initial assessment, inconsistencies in data arise when certain connections are missed because linkage of objects are loose which then may lead to inconsistent interpretation of data.
Referring to a comment made in AQ community, having the Account to Account relation as in our example below makes a lot of sense. What could be looked into then is do we have to connect the deceased contact to its former account?
Challenges:
Alain: Big part of the planned giving is not solicited. which is not TAP driven.
Harpeet: Alot of the time they don’t know if the donor is an Alumni or not. The matching process is manual process
Harpeet: main is is on Reporting. Currently it takes a lot of manually going through lists. For example he needs to report on all the estates received last month. He has to manually prepare them. The reporting process is challenging.
Alain: Challenge is mapping the estate and the deceased person.
Allain: wants to generally have a wholistic view of a contact how much hard and soft credit given. As well as if a person left us a bequest.
Alain: its not easy to understand different activities of a contact based on their estates. (engagement history) before the bequest.
BI DRS Taskforce Wishlist from Alain
# | Description |
A001 | Address/Email/Telephone validation/clean-up |
A002 | Align the Account Address to the Primary Contact Address |
A003 | Account and Contact Roles Clean-up (standardized values/remove duplicates) |
A004 | Add missing Account/Contact roles in relationship |
A005 | Alumni with no Education data (review, attach education) |
A006 | Contacts with Education data but not typed as Alumni/Graduand |
A007 | Education record with blank school data |
A008 | Add default value to contacts without address preference (impacts account/contact address updates) |
A009 | Gifts/pledges from Household accounts without Gift recognition credits |
A010 | Soft Credits not migrated from Advance |
A011 | Implement Giving Consortium for some migrated gifts (to correctly record the total gift amount) |
A012 | Check for invalid dates |
A013 | Review Giving Summary section in Accounts – remove/replace fields which do not align with our calculation |
A014 | Active Household Account without Contacts |
A015 | Review Accounts special handling (e.g. Do No Contact, Do Not Mail etc. against its contact special handling |
A016 | Standardise Data Sources data |
A017 | Duplicate Account/Contact cleansing/Establish process |
A018 | Opportunities without prospect pool |
A019 | Influential Alumni tag |
A020 | High Potential Tag |
A021 | Academic / School mapping |
A022 | Scholarship History mapping |
A023 | Non ASR volunteering data monitoring |
A024 | Campaign Partners Pipeline monitoring attached to Jarvis pipeline |
A025 | RP Pipeline monitoring attached to Jarvis pipeline |
A026 | Designation Classifiation cleaning |
A027 | Estate / deceased contact relationship |
A028 | Additional Opportunity type (mid tier?, HL adocacy?) |
A029 | STudent / prospective student mapping with contacts / account |
Meeting recording
https://uni-sydney.zoom.us/rec/share/ga0cVqIEbyNPLSOSRqKmT9P7FD4qAIsxLepM3mG0teCAiRPKFqG1zE-vR-EmG9Di.9xqBzeadM2KnjSrp
Passcode: 1%@Qgq+0