DevResults Information Requirements

System Setup:

To create a new DevResults site, we provide a setup template (or a series of templates) that captures 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:

  • Activities
  • 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 activities report on which indicators
  • Which disaggregations go with which indicators
  • Which activities report during which reporting periods
  • Which organizations manage which activities
  • Which activities report at which locations, per reporting period, for each part of the results framework that relates to their indicators
  • Which activities report at which administrative divisions, per reporting period, for each part of the results framework that relates to their indicators
  • Which users are associated with which activities

This is the minimum amount of information required for DevResults to be functional per activity.

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.

Budget ToolsFor each activity, list all budget line items, their amount, currency, source, date, typeDifferentiate between accrued, disbursed, etc.
FilteringFor each activity, indicator, location, or organization: list a set of tags by which you'd like to filter informationTags may go beyond or cut across the results frameworks, e.g. "climate", "gender", "faith-based", etc.
ChecklistsFor each activity, create checklists for non-quantitative goalsEnumerate their steps, give deadlines, assign persons responsible for completion and managers who can give approval
Logic ChecksIndicator results can be flagged if they fail to pass a common-sense logic test that compares the result to a set value or another indicatore.g. # individuals served" should be less than "Total population"
Other reportingIf you want to generate reports automatically from DevResults, Microsoft Word templates must be provided that note what information should be inserted where

Data tablesIf you intend to collect individual-level data or update DevResults data using arbitrary data setse.g. Hospital registers or student attendance lists
System syncsIf you want to regularly automatically import information to DevResults from other systems (like accounting), provide access to that systemCustom syncs will be developed in close collaboration with the engineering team
CalendarYou can add calendar events at the activity or program level once the site is live

Document storageYou can store any kind of document or file per activity or at the program level once the site is live

PhotosYou can upload photos per activity once the site is live

Didn't answer your question? Please email us at