Record the meeting
Enter the meeting date and region once. Attach the meeting minutes and monthly report in the meeting section.

PERFORMANCE FOLLOW-UP
Follow these steps after each monthly performance meeting.
Enter the meeting date and region once. Attach the meeting minutes and monthly report in the meeting section.
Add one card per issue. Choose its health-system block and focus area, describe the agreed action, and assign it to MoH, region, district, or facility.
Enter the responsible person's name, cadre, phone, email, start date, due date, and whether evidence is available. Add another action before saving if needed.
Open an action in the tracker to add a comment, update status or due date, and attach progress evidence. Use Overview to review trends and download summaries.
Each workspace section supports a different part of the action cycle.
Status helps teams understand what needs attention.
Default for a new action; also used when an ongoing action passes its due date.
Work has started and the responsible person is progressing the action.
The agreed action has been completed.
Enter the meeting details once, then add each issue and agreed action below.
Search, filter, open an action, and record follow-up.
Actions grouped by meeting month; rate reflects current status.
Current status distribution
Compare done, ongoing, and not done actions
Issue distribution across the six blocks
MoH, region, district, and facility
Submission volume by date entered in the tracker
Open actions grouped by days past due
Actions with evidence recorded
A meeting, follow-up, or recorded update counts as an action. Each issue is counted once.
No MoH Central escalations match the current filters and access scope.
Most recently entered or updated within the selected filters
Review and track requests to remove erroneous records.
Create users and assign their role and geographic scope.
Manage organisational units and inspect the system audit trail.
Import a legacy action CSV after loading the Ministry organisation hierarchy. Preview checks all action, reporting-region, and assigned-unit mappings first. Rows with unresolved mappings stop the import so they can be corrected before any records are written.
Upload the DHIS2 organisationUnits JSON response. Include paging=false in the API URL. The level JSON is optional; if provided, it supplies the official names for each numeric level.
The import refreshes previous DHIS2 units while preserving action records. Check the hierarchy after import before creating users.
Visible to system administrators only.
Capture one issue and the action agreed by the meeting.