System Setup:
To create a new DevResults site, we provide a few templates that capture the program information needed to create a fully functional platform for monitoring and evaluation. These templates are designed specifically for each client based on your geographic areas of focus. Once we begin the setup process, DevResults staff will be available to walk you through each step. We can help organize and structure this program information.
Required lists of program information:
- Projects (aka awards, grants, activities, initiatives, etc.)
- Organizations
- Results Framework(s)
- Indicators
- Disaggregations
- Locations
- Administrative Divisions
- Users
- Reporting Periods
Required linkages between these lists of program information:
- Which indicators fall under which part(s) of the results framework(s)
- Which projects report on which indicators
- Which disaggregations go with which indicators
- Which projects report during which reporting periods
- Which organizations manage which projects
- Which projects report at which geographic places
- Which users are associated with which projects
This is the minimum amount of information required for DevResults to be functional per project.
Previous Data:
Previous indicator results can be added only after setup of the site is complete. If your previously recorded indicator results do not conform to the indicator definition you have specified in DevResults, there are five options for how to proceed:
- Track down the disaggregated data from its original source
- Estimate the disaggregations for previous data (inaccurate estimates could be misleading)
- Define previous data and future data with separate indicators (which makes it difficult to examine changes over time)
- Re-define the indicator to fit previous data (the data is less useful when less specific)
- Do not include any data that does not fit the indicator definition (loss of previous information and record of work)
Information required to enable additional features:
Only after system setup is complete can other features be enabled.
| Feature: | Task: | Detail: |
|---|---|---|
| Budget Tools | For each project, list all budget line items, their amount, currency, source, date, type | Differentiate between accrued, disbursed, etc. |
| Filtering | For each project, indicator, location, or organization: list a set of tags by which you'd like to filter information | Tags may go beyond or cut across the results frameworks, e.g. "climate", "gender", "faith-based", etc. |
| Checklists | For each project, create checklists for non-quantitative goals | Enumerate their steps, give deadlines, assign persons responsible for completion and managers who can give approval |
| Logic Checks | Indicator results can be flagged if they fail to pass a common-sense logic test that compares the result to a set value or another indicator | e.g. # individuals served" should be less than "Total population" |
| Other reporting | If you want to generate reports automatically from DevResults, Microsoft Word templates must be provided that note what information should be inserted where | |
| Data tables | If you intend to collect individual-level data or update DevResults data using arbitrary data sets | e.g. Hospital registers or student attendance lists |
| System syncs | If you want to regularly automatically import information to DevResults from other systems (like accounting), provide access to that system | Custom syncs will be developed in close collaboration with the engineering team |
| Calendar | You can add calendar events at the project or program level once the site is live | |
| Document storage | You can store any kind of document or file per project or at the program level once the site is live | |
| Photos | You can upload photos per project once the site is live |
Didn't answer your question? Please email us at help@devresults.com.