Donors Data Management- Draft Proposal.

Rationale: Never to allow a single person, trustee* or otherwise, to hold Donors’ nominal and contact details together. (* ) Charitable number: Pending.

Practical dispositions:

I. For donors contacting a trustee personally known to them, this trustee shall:

a. Communicate the amount said to have been donated, date of payment, donor’s chosen narrative option, and donor’s first name to the treasurer;

b. This trustee shall communicate first name and surname of the donor to coordinator or whoever allocates username and password for access to the state of the account blog;

c. The same trustee shall finally thank donor and communicate to them the allocated username and password.

d. This donor’s contacts details (emails address or phone numbers etc…) shall only remain with same trustee until a final Donor Data Management Strategy is passed by the Board*.

e. Until a Donor Information Strategy is passed by the Board, the same trustee shall be responsible for keeping the donor informed of RSVP developments at least once a month or at mutually convenient frequency.

II. For donors advising RSVP of a donation using hartdns@yahoo.co.uk or u44sm5@abdn.ac.uk picked from the blog:

II.1. If the treasurer is contacted only:

f. The treasurer shall allocate codes or take the donor’s chosen narrative option;

g. The treasurer shall then communicate the first name and surname of the donor and allocated or chosen code to coordinator or whoever allocates username and password for access to the state of the account blog;

h. The treasurer shall thank donor and communicate to them the allocated username and password;

i. The treasurer shall retain the contact details of the donor until a final Donor Data Management Strategy is passed by the Board (exception to rationale stated at the beginning);

j. Until a final Donor Information Strategy is passed by the Board, the treasurer shall be responsible for keeping the donor informed of RSVP development at least once a month or at mutually convenient frequency.

II.2. If the coordinator is contacted only:

k. He shall allocate codes or take the donor’s chosen narrative option or seek code allocation from treasury (which ever is agreed);

l. The coordinator- or whoever does so- shall allocates username and password for access to the state of the account blog to the donor;

m. He shall then communicate donor’s first name and Surname as well as chosen or allocated code to the treasurer;

n. The coordinator shall thank donor and communicate to them the allocated username and password;

o. The coordinator shall retain the contact details of the donor until a final Donor Data Management Strategy is passed by the Board (exception to rationale stated at the beginning);

p. Until a final Donor Information Strategy is passed by the Board, the coordinator shall be responsible for keeping the donor informed of RSVP development at least once a month, or at mutually convenient frequency.

Finally, NO donors personal data shall be passed onto any third parties, except legally competent agencies of Her Majesty's government such as the UK police.

Top.          Home