Field Monitoring
1.0.1
Changes to VisitInitial Release1.0.0Technical Documentation1.0.1
1.0.1
Changes to VisitInitial Release1.0.0Technical Documentation1.0.1
  • Field Monitoring Module Documentation
  • INTRODUCTION
    • Project Background
    • Opportunities
    • Objectives
    • Scope of the Field Monitoring Module
    • Glossary / Terminology
    • FAQ
    • Report an Issue / Contact us
  • PRODUCT / END-USER DOCUMENTATION
    • Overview
    • User Groups
    • User roles and permissions
    • Field Monitoring Module Navigation
    • Overall User Interface
    • Settings
      • Adding and Editing Questions
      • Sites Management
    • Plan
      • Building the Rationale For the Monitoring Activity
      • Logging Known Issues
      • Templating Checklists for Field Monitoring Activities
    • Collect
      • Activities Overview
      • Drafting a Monitoring Activity
      • Checklist / Questionnaire Setup
      • Checklist Review
      • Assigning / Accepting / Rejecting a Visit
      • Data Collection
      • Report Finalization
      • Submission / Completing a Monitoring Activity
    • Analyze section
      • Monitoring Activity
      • Country Overview
  • TECHNICAL DOCUMENTATION
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Data Model
    • Fixtures and Management Commands
    • Integration with permissions framework
    • API Documentation
      • Error Handling
    • Frontend
      • Module Structure
      • Build Process
    • Offline Collection module
Powered by GitBook
On this page
  1. PRODUCT / END-USER DOCUMENTATION

Plan

PreviousSites ManagementNextBuilding the Rationale For the Monitoring Activity

Last updated 5 years ago

The Plan section enables creating the overall Field Monitoring annual plan, strategy, and approach. Also, in this section, users can associate questions to entities. Individual Monitoring Activities are planned in detail in the .

The overall UI of the Plan section is presented below:

This section consists of the following parts:

The allows building the rationale for the strategy and approach for the year’s Field Monitoring activity;

The allows logging known issues related to a Partner, CP Output, or Site/Location;

The allows for prestructuring field monitoring activities. These templates can be used and customized during the .

Rationale area
Issue Tracker area
Templates area
Collect phase
Collect section
The overall UI for the Plan section