Monitoring and Evaluation with ActivityInfo
Monitoring and Evaluation is becoming more and more important in the lifecycle of a programme. We want to simplify the work of Monitoring and Evaluation officers, so we created Database templates that can be adapted to your needs quickly and easily. You can work with the Blank Database template if you plan to monitor programmes within your organization or with the Multi-partner reporting Database template, if you plan to cooperate with other partner organizations.
In the past, we discussed how you can move from a Framework, such as a Logical Framework or a Results-based framework, to an online system. In this blog post we will take a look at some Database templates that can be used for Monitoring and Evaluation and we will ask key questions to help you design Forms that will reflect your activities.
Why Monitoring and Evaluation?
If you want to track the progress of your efforts as a person, as a team and as a whole organization you must capture the correct information and monitor the progress towards specific goals.
When you monitor how your activities progress in relation to the overall programme development, you can quickly respond to emerging needs or shortages. Also, when you start evaluating the progress of these activities at designated times, you can measure their success and understand the reasons behind this success. Finally, a Monitoring and Evaluation system makes sure you are accountable to internal and external stakeholders.
Before you start working with a Database in ActivityInfo, think of your implementation plan. Gather the team members who will participate in the system, assign Roles to them and draft the data flow processes between them. Also, think of the indicators you will track and define what the baseline data is and what kind of information you need to monitor and evaluate, in order to have a complete overview of the progress towards your objectives.
Monitoring and Evaluation in ActivityInfo
There is no need for technical knowledge to start using ActivityInfo; the platform offers Database templates with predefined Roles which you can assign to your team when you invite them to work with you using the platform. This allows you to get started quickly and to focus on designing your Forms in the best way possible to reflect your M&E objectives.
Using the Database templates
In ActivityInfo, the Blank Database template is ideal when you don’t need to work with multiple organizations and advanced team structures for Monitoring and Evaluation reporting. It comes with three different Roles; Administrator, Data Entry and Read only. These Roles define the kind of permissions your team members have in the resource where you invite them.
You can watch the following tutorial to quickly get started with this template and invite some users.
You can also follow the step-by-step guidelines for setting up this Database.
There is another template Database which is more suitable for collaborative M&E systems, that is if you have many partner organizations cooperating and reporting for a programme and you need to restrict the access of some users to data related only to their organization. You can watch the following tutorial to quickly get started with this template and read more about the multi-partner reporting Database in our User Manual
Designing Forms: decide on the structure
After you have selected the Database template that best suits your needs, you are ready to create a structure to reflect the information flow of your programmes and activities. You might need just one Form or you might need a more complex structure using multiple Forms linking to each other. Forms with Subforms are useful when you want to collect data on a repetitive basis or if you want to collect more details in some specific cases.
Some questions you can ask yourself before you start designing your Forms are the following:
- Will you be collecting numbers or narratives, or both?
Then, add Quantity and Text fields.
- Should users choose one or more than one options from a list of available options?
Then, use Selection fields.
- Will you need to Lock reporting for specific periods of time or need to know when something happened?
Then, add a Date, Month, Fortnight or Week field.
- Is the information related to geographic locations?
Consider using the Geodatabase or adding a Reference Form with customized locations.
- Do you need to link to another Form and bring in more options?
Add Reference fields and read about Key fields.
- Do you need to repeat the data collection process on a frequent basis?
Consider designing a Form with a Subform.
- Are there questions that must be answered?
You should make the fields for these questions Required.
- Are there questions that can and should be omitted depending on the type of information added?
You can set Relevance rules to define when a question should appear.
- Do you need to automate calculations?
Then, read about Calculated fields and writing expressions.
- Should users be notified when a similar record exists?
You should use Key fields.
- Are there rules that must be met for a Record to be valid?
Consider setting validation rules.
Finally, keep in mind that users can import their data in your Forms which can be very useful if they have big amounts of data outside ActivityInfo. Also they can make a Database available offline and work when Internet connectivity is limited.
Designing Forms: Reference Forms
In ActivityInfo you can link Forms to each other and bring in information added to one Form, as options to select from, in another Form. This gives you countless possibilities.
You can create some Reference Forms if you plan to use and reuse some information and you want to easily refer to them in other Forms. Reference data could be a list of your programmes and projects, a list of cities where your organization is active, a list of donors or even a list of entities which benefit from your work. Then, you can start designing a Form to collect the data needed for each of the Records of this list.
An example would be to design a Reference Form to list all your programmes and their activities along with the starting and ending date and the available budget, as shown in the sample image below.
Then you could design a Form to collect indicators related to each activity. Instead of designing a different Form for every activity of your programmes, you can reference the first Form so when you add data you can just select the activity for which you are adding the data. Then, with relevance rules you can define which indicators will appear as questions depending on the activity that was selected.
To get more ideas on how to use Reference Forms take a look at this example where we design Forms for measuring the costs of the activities of various programmes.
Assigning Roles and permissions
By assigning Roles you define the exact permissions your team or partners will have to the Database and the Forms you designed. Each template has a different set of Roles which you can use as they are, edit or duplicate to create new ones.
Let’s take a look at some interesting roles.
The Role of Administrator can be found in every Database template; it includes all the permissions available in ActivityInfo apart from adding a Database. Users can add a Database if they are on a Free Trial account or if they are the Technical Contacts of a paid subscription. Users with this Role should know how your programmes work and what exactly you want to monitor. You can assign this Role to more than one person. Administrators can coordinate the data collection as well, as they are the ones who can add users to a Database and define their permissions.
In the Blank Database template, the Data Entry Role is the most common Role which can be used for all the team members that will work in data collection. The Read Only Role is useful for people who need to have an overview of the reporting process and the results, such as a Donor for example.
In the Multi-partner reporting Database template, the Sector Lead Role includes a variety of permissions which allow users to create their own teams of users via the ‘Manage users’ permission, among other actions. The Reporting Partner Role is equivalent to the Data Entry Role of the Blank Database template with the difference that here you can restrict the actions based on the organization in which the user belongs. You can define that when you invite a user using this template.
You can also edit the permissions that an individual user has been given via the Role assigned to them, by overriding the Role’s permissions only for that user. Finally, you can add an existing user to additional Forms and Folders.
What do you think of the Roles and the Database templates? Have you created your own Database for Monitoring and Evaluation?