Delivery
The work sits next to the people it serves.
Programmes, enrolment, activities, milestones and evidence live in the same workspace as the people and the consent. Delivery is no longer a folder on someone’s desktop, or a WhatsApp thread that dies when the phone is replaced.
How it is built
Programmes are the container
The work has a name, a period and a location. Activities do not float free of the programme they belong to.
Evidence attaches to the work
Files and links sit on the activity, person or programme they support. Not a parallel archive.
Coverage is a live question
Who was reached, under which activity, with what evidence — answerable during the period, not only at close-out.
Your close-out should not be a project
The old way versus IMP
The usual log
- Activity logs in WhatsApp, Excel and a shared drive that only one person understands.
- Photos of the session live on a phone. When the phone is lost, so is the evidence.
- Nobody can say, at close-out, who was reached under which activity.
- Programme status is a weekly email, rewritten every Monday.
The IMP log
- Programmes are first-class: name, period, status, locations.
- Enrolment is explicit — people join the programme they are actually served by.
- Activities and milestones sit on the people and the plan they belong to.
- Evidence — files and links — attaches to the record, and exports with it.
What is actually in the product
Live workspace capability — not a roadmap dressed as a feature list. The ceiling is published on the same page as the capability.
In the workspace today
- Programmes with status, period and location
- Enrol / unenrol / re-enrol
- Activities and milestones on the delivery log
- File and link evidence on the activity, person or programme
- Activity snapshots on the reports page (IMP MERL)
- CSV export of activities and programmes
- Import templates for programmes, activities and milestones
Honest ceiling
- Not a mobile offline field-capture app (not in product yet)
- Not an enumerator management system for national census
- Not a replacement for DHIS2 or a health MIS
Built to handle the messy reality
Define the programme
The container the work lives in — so activities, people, results and claims have somewhere true to land.
Enrol
Coverage is enrolment, not a headcount in a workshop report. Re-enrolment is a first-class action.
Log the work
Activities and milestones against the people and the plan. Status is on the record, not in the weekly email.
Attach evidence
A photo, a register, a link. It sits with what it supports. Close-out does not mean hunting a drive.
What delivery looks like in practice
From programme setup to evidence on the record — one path, not five folders.
- 01
Define
Name, period, locations — the container the work lives in.
- 02
Enrol
People join the programme they are actually served by.
- 03
Log
Activities and milestones against the people and the plan.
- 04
Attach
Evidence sits with the record it supports.
From fire drills to a live record
Programme manager
From
Weekly status by email
To
Live coverage of who was reached
Field staff
From
A form that never quite matches the logframe
To
Activities on the same record
Leadership
From
Asking three people for the same number
To
One delivery picture
Questions buyers actually ask
- Is this a mobile offline field app?
- Not yet. IMP is the organisational system of record. Field capture can feed it (CSV today; Kobo connect, list and preview live, with map/sync on the roadmap). The workspace holds what remains.
- Can we attach photos and files?
- Yes. Evidence sits on the activity, person or programme it belongs to — files and links.
- Can we import a legacy activity log?
- Yes. Templates for programmes, activities and milestones with column mapping. Designed for spreadsheet-first teams.
Explore more of IMP
The work stays when people leave
Don’t wait for the laptop to be on a plane. Brief the cycle the way you would brief a successor.
Already have the note? Tell us about this cycle — we price from that.