Difference between revisions of "Template:Rac7templates"
(Created page with "While we've been looking at the project selection page, you may have noticed some red links below the names of the projects. So far we haven't talked about these red links but...") |
m |
||
| Line 1: | Line 1: | ||
| + | ==Templates== | ||
| + | |||
While we've been looking at the project selection page, you may have noticed some red links below the names of the projects. So far we haven't talked about these red links but now we will! - these are ''Referral Templates''. | While we've been looking at the project selection page, you may have noticed some red links below the names of the projects. So far we haven't talked about these red links but now we will! - these are ''Referral Templates''. | ||
| Line 39: | Line 41: | ||
...we get the following: | ...we get the following: | ||
| + | |||
[[File:rac_templates_3.png|border]] | [[File:rac_templates_3.png|border]] | ||
| + | |||
The fields ringed in red are those that the system has filled in automatically. So as you can see, this template has filled in plenty of the information we're going to need. | The fields ringed in red are those that the system has filled in automatically. So as you can see, this template has filled in plenty of the information we're going to need. | ||
| Line 49: | Line 53: | ||
* Therefore, always double check that the right information is there. A template will often be the most common information, but will require a bit of tweaking before you click "Continue". | * Therefore, always double check that the right information is there. A template will often be the most common information, but will require a bit of tweaking before you click "Continue". | ||
| + | ==Progress Statuses== | ||
| + | |||
| + | The above example shows a template which helps us with one particular scenario, but what we need are really a series of templates for the following scenarios: | ||
| + | |||
| + | * A client phones in to ask questions about benefits. We think they need a chat with the advisor [Matt] and so we schedule an appointment, within a week. | ||
| + | * The client visits our office, has a chat with the advisor, and it seems like their chances of getting some money are good. Within two days we will call the council on their behalf and ask for the relevant forms to be posted out. | ||
| + | * The client brings in the completed forms, we check them and send them off. If we don't hear anything within two weeks, we will call and ask for an update. | ||
| + | |||
| + | (The three stages of the diagram above.) | ||
| + | |||
| + | This can be done with a series of ''Progress Statuses'' within a template. If we use a template which has several statuses, we will see an extra box on the Record a Contact screen... | ||
| + | |||
| + | |||
| + | [[File:rac_templates_4.png|border]] | ||
| + | |||
| + | |||
| + | ...and if we change this drop-down box to a Status/Progress stage, the other boxes on the Record a Contact screen will fill themselves in automatically, as shown. | ||
| + | |||
| + | |||
| + | [[File:rac_templates_5.png|border]] | ||
| + | |||
| + | |||
| + | So a template may just be one scenario, but it can also be a series of linked scenarios. This kind of approach works very well for: | ||
| + | * Pieces of work that happen regularly, and are all similar, with the same rough timescales | ||
| + | * Processes that you aim for, to make sure your quality of service remains good | ||
| + | * Timescales imposed upon you by funders - for example, a commitment to respond to phone enquiries about winter fuel allowance within two days. | ||
| − | + | It's also really useful for in-office work such as CRB applications. You probably already have a desired timescale for CRB applications, for example: | |
| + | * ''When someone expresses an interest in volunteering, we aim to get them in for a chat within two weeks.'' | ||
| + | * ''If they want to become a volunteer, we give them the forms at this meeting, and we want them back within a week.'' | ||
| + | * ''When we receive them back, we send the forms on within 24 hours.'' | ||
| + | * ''If the volunteer doesn't receive their CRB back within three weeks, we will start hassling on their behalf.'' | ||
| − | + | ==Workflows== | |
Revision as of 22:16, 3 January 2013
Templates
While we've been looking at the project selection page, you may have noticed some red links below the names of the projects. So far we haven't talked about these red links but now we will! - these are Referral Templates.
Referral templates are a simple part of the Charitylog system that can be very powerful and useful. They provide a way to speed up data entry, particularly for a chain of actions that happens often with many different clients. Consider this chain of actions - the first half of one of the earlier examples.
If you were an organisation regularly advising people about benefits, you might well find that this chain of actions was happening again and again, with roughly the same thing happening every time. Here's the diagram again, updated with the timescales, and what we might be putting in the "Record a Contact" screen each time.
So we might reasonably think, "It's tedious having to fill out the same thing every day. People come in for benefits advice, need an interview with an advisor, and then we help them apply. Can't we make the system fill in these common scenarios automatically?"
Indeed we can, and this is where Referral Templates come in. Using Referral Templates, administrators can set up common chains of actions as a series of pre-filled-out Record a Contact screens. These screens can have the majority of the data entry done already - each screen can have:
- The Referrer already entered
- The contact method filled in
- The text in the "Details of Contact" already filled in
- The Project Subcategory already set
And if required in the bottom half:
- Whether or not further actions are needed
- Who needs to do the further actions
- What the response method should be
- What the further actions should be (the text in the "Further Action Needed" box) already filled in
- When the further action needs to be done by
So let's take the first bit of the diagram above. If we just tick the box next to the "Benefits Advice" project...
...we get a normal "Record a Contact" screen. But if we use the red line instead, "Benefits - Standard Enquiry"...
...we get the following:
The fields ringed in red are those that the system has filled in automatically. So as you can see, this template has filled in plenty of the information we're going to need.
Remember:
- The information that's there can be altered or added to as required. The template just fills in the fields for you, but it doesn't save the information. You can change it to suit your needs.
- Therefore, always double check that the right information is there. A template will often be the most common information, but will require a bit of tweaking before you click "Continue".
Progress Statuses
The above example shows a template which helps us with one particular scenario, but what we need are really a series of templates for the following scenarios:
- A client phones in to ask questions about benefits. We think they need a chat with the advisor [Matt] and so we schedule an appointment, within a week.
- The client visits our office, has a chat with the advisor, and it seems like their chances of getting some money are good. Within two days we will call the council on their behalf and ask for the relevant forms to be posted out.
- The client brings in the completed forms, we check them and send them off. If we don't hear anything within two weeks, we will call and ask for an update.
(The three stages of the diagram above.)
This can be done with a series of Progress Statuses within a template. If we use a template which has several statuses, we will see an extra box on the Record a Contact screen...
...and if we change this drop-down box to a Status/Progress stage, the other boxes on the Record a Contact screen will fill themselves in automatically, as shown.
So a template may just be one scenario, but it can also be a series of linked scenarios. This kind of approach works very well for:
- Pieces of work that happen regularly, and are all similar, with the same rough timescales
- Processes that you aim for, to make sure your quality of service remains good
- Timescales imposed upon you by funders - for example, a commitment to respond to phone enquiries about winter fuel allowance within two days.
It's also really useful for in-office work such as CRB applications. You probably already have a desired timescale for CRB applications, for example:
- When someone expresses an interest in volunteering, we aim to get them in for a chat within two weeks.
- If they want to become a volunteer, we give them the forms at this meeting, and we want them back within a week.
- When we receive them back, we send the forms on within 24 hours.
- If the volunteer doesn't receive their CRB back within three weeks, we will start hassling on their behalf.
