Difference between revisions of "Using the system to manage basic fundraising"
(→Template to manage Collection Tins left with organisations.) |
(→Using Just an Extension Database to manage Collection Tins) |
||
| (15 intermediate revisions by the same user not shown) | |||
| Line 88: | Line 88: | ||
…and the stages on the template as follows: | …and the stages on the template as follows: | ||
| − | [[File: | + | [[File:fun_raise11.JPG|700px|alt="a screenshot of the referral stage list. The stages are labelled: new request for collection tin, collection tin delivered, collect and replace, and ceased - no longer required."]] |
The diagram below displays the workflow of the stages: | The diagram below displays the workflow of the stages: | ||
| Line 103: | Line 103: | ||
The [[Referral_Templates|template has be set up]] as follows: | The [[Referral_Templates|template has be set up]] as follows: | ||
| − | [[File: | + | [[File:fun_raise12.jpg|700px|alt="a screenshot of the template set up page. The template is labelled 'collection tin for staff / volunteer'."]] |
…and the stages on the template as follows: | …and the stages on the template as follows: | ||
| − | [[File: | + | [[File:fun_raise13.jpg|700px|alt="a screenshot of the stage set up page. The stages are labelled 'collection tin issued' and 'collection tin returned'."]] |
The diagram below displays the workflow of the stages: | The diagram below displays the workflow of the stages: | ||
| Line 118: | Line 118: | ||
Below is the main setting of the extension database: | Below is the main setting of the extension database: | ||
| − | [[File: | + | [[File:fun_raise14.jpg|700px|alt="a screenshot of a collection tin extension database set up. The extension database is set up to appear against referrals."]] |
Below you will find an example of the fields: | Below you will find an example of the fields: | ||
| − | [[File: | + | [[File:fun_raise15.jpg|700px|alt="a screenshot of the collection tin extension database field set up. The extension database is set up to appear against referrals."]] |
Once complete return to the [[Project_Set_Up|set up of the Collection Tins project]] and got to the [[Project_Set_Up#Additional_Data_Collection_tab|Additional Data Collection]] tab to setup up the Extension Database on the project. | Once complete return to the [[Project_Set_Up|set up of the Collection Tins project]] and got to the [[Project_Set_Up#Additional_Data_Collection_tab|Additional Data Collection]] tab to setup up the Extension Database on the project. | ||
| − | [[File: | + | [[File:fun_raise16.jpg|700px|alt="a screenshot of the setting in additional data collection in the project set up. This is set to be shown after every referral and action."]] |
The user will be displayed the following screen to enter information about each collection tin: | The user will be displayed the following screen to enter information about each collection tin: | ||
| − | [[File: | + | [[File:fun_raise17.jpg|700px|alt="a screenshot of the extension database fields for the collection tin information, including the amount, the date issued, the serial number and return date."]] |
| − | |||
===Report Options=== | ===Report Options=== | ||
| Line 150: | Line 149: | ||
Below is the main setting of the extension database: | Below is the main setting of the extension database: | ||
| − | [[File: | + | [[File:fun_raise18.jpg|700px|alt="a screenshot of the collection tin extension database set up, which is set to be recorded on the organisation person records as opposed to the referrals."]] |
Below you will find an example of the fields: | Below you will find an example of the fields: | ||
| − | [[File: | + | [[File:fun_raise15.jpg|700px|alt="a screenshot of the collection tin extension database field set up. The extension database is set up to appear against org person records."]] |
The user will be displayed the following screen to enter information about each collection tin: | The user will be displayed the following screen to enter information about each collection tin: | ||
| − | [[File: | + | [[File:fun_raise17.jpg|700px|alt="a screenshot of the extension database fields for the collection tin information, including the amount, the date issued, the serial number and return date."]] |
===Report Options=== | ===Report Options=== | ||
Latest revision as of 09:03, 1 May 2024
The system does not have specific features designed solely for fundraising, however there are certain features that can be used to help manage fundraising. This guide will look at the areas of the system that can be setup in relation to fundraising activities.
Contents
Managing Donations and Legacies
Donations and Legacies can be managed on the system using a project and extension database or with just an extension database. This section will look at both methods.
Using a project to manage Donations and Legacies
In this example we will look at receiving a donation and sending a thank you letter. The diagram below is the process that is to be setup;
Project Set Up
The first step is to set up a project, the images below display the recommended settings:
General Settings
Record A Contact Settings
On the Types of Orgs and People tab select the people and organisations that you would receive donations from.
Using Templates
Templates can be used to manage the workflow when receiving donations and legacies. In this example there will be two templates, one to manage donations and one to manage legacies. See Referral Templates for full details on setting up template)
The first template will be for donations, this will assign the project subcategory 'Donations', see Project Subcategories (Users will need to have access to enter subcategories).
The following stages have been setup;
Extension Database
An Extension Database is going to be used to report on the monies received.
The fields will be as follows;
- Type: Donation or Legacy
- Gift Aid Cert Received: Yes or No
Managing Collection Tins
If you use volunteers,staff and shops to collect donations on behalf of the organisation you can look at the following options.
Using a project to manage the issue of the collection tin
Project Setup
Below is a basic process chart on issuing Collection Tins.
The first step would be creating a project. and making this available to staff, volunteers and organisation. Below is some example screen shots of the suggested project settings;
Give the project an appropriate name.
As above you may wish to allow recording of time and travel to monitor resources.
Select the record types for those who may take a Collection Tin.
Using Templates
Using templates will manage the process of issuing, returning and replacing tins. There are two templates that this example will use, one for organisations and one for staff/volunteers.
Template to manage Collection Tins left with organisations.
The template has be set up as follows:
…and the stages on the template as follows:
The diagram below displays the workflow of the stages:
When a request to site a new collection tin is received a new referral will be created on the Organisations record and initially this will be set to the default stage for 'New Request'. An outstanding action will appear on the staff member or volunteers action list that is to deliver the tin. From here the template will auto populate as each step is updated. If the tin is permanently returned the 'Ceased' stage will be selected closing the referral/process. In addition to the template an extension database can be used to record the values etc (explained in a later section)
Further option: you could create a new org/person record type called Collection Tins. Each tin with serial number would be added as a record. The project could then be set on the 'Types of orgs/people' tab to use an additional organisation (bottom section) with the record type 'Collection Tins' ticked. The alternate name would be set as Collection Tin and you would want to tick the option 'Tick the box if you want the extra organisation/person to only be associated with 1 open referral at a time.' In Operational Rules you could set history to be on the receiver and extra org and you will see the details on the Collection Tins history tab.
Template to manage Collection Tins issued to staff and volunteers
The template has be set up as follows:
…and the stages on the template as follows:
The diagram below displays the workflow of the stages:
Setting up an extension database
In order to report and manage the tins you may wish to set up an extension database for the project.
Below is the main setting of the extension database:
Below you will find an example of the fields:
Once complete return to the set up of the Collection Tins project and got to the Additional Data Collection tab to setup up the Extension Database on the project.
The user will be displayed the following screen to enter information about each collection tin:
Report Options
You will be able to use a series of reports to mange the project, the two most useful being:
KPI Report Designer This will report on the overall statistics of the number of referral and demographic data.
Progress Interval Report This will report on each stage of the process.
Extension Database Reports This will report on the outcome of the donation.
Using Just an Extension Database to manage Collection Tins
You can have just an extension database to record the details of collection tins, this will not produce reminders on the action list.
Below is the main setting of the extension database:
Below you will find an example of the fields:
The user will be displayed the following screen to enter information about each collection tin:
Report Options
You will be able to use the following report:
Extension Database Reports This will report on the outcome of the donation.
