Programme Management: A plan built from your logframe, with the reason any activity is late.

An activity slips because a purchase is stuck, a hire hasn’t signed or a permit is missing, and the reason sits in another department.

With one Excel workbook per project and decisions buried in meeting minutes, it is hard to say what is ready to start.

Relief One, Programmes & impact

How it works

Which activities can start, and what blocks them.

Start from your approved documents. The AI turns logframe, workplan and budget files into a draft plan, each line citing where it came from; a person accepts them line by line.
Plan. Work breakdown, Gantt with dependencies and country working calendars, critical path.
Check readiness. An activity shows whether it can start, and if not, why, its earliest possible start and what would unblock it.
Govern. Actions, risks, issues, decisions, meetings and change requests in one place, each linked to the work it affects.

What it does.

Plan from your documents: The AI turns logframe, workplan and budget files into a draft plan a person accepts.
Gantt and critical path: Dependencies, country working calendars, drag to re-plan, revisions logged.
Readiness: Whether an activity can start, and if not, what is blocking it and what would unblock it.
Your rulebook as data: Your policy rules evaluated per project, with phase gates and a what-if simulator.
Next actions: Ranked by what they unblock, each with one verb: Approve, Upload, Sign.
Risks, issues and decisions: Linked to the work they affect, and change requests with their impact spelled out.
Project rooms: Your existing workbook, tab by tab, but live, and exported back.
Field capture offline: Synced when the connection returns.

The full list

Project rooms: The project page reproduces your existing workbook tab by tab, but live, and exports back to it.
Your rulebook as data: Your organisation’s policy rules loaded as data, evaluated per project with phase gates and a what-if simulator (“extend by 9 months → a mid-term evaluation switches on”).
Gantt and critical path: Drag to re-plan, successors move, revisions logged; alternative sequences simulated before you adopt one.
Operational conditions: Procurement delivered, budget available, staff in post, document approved, partner agreement signed, security clearance…
Next actions ranked by what each unblocks: with one verb (Approve, Upload, Sign, Deliver).
Risks: (probability × impact), issues with escalation, decisions with rationale, change requests with an impact read in plain words (“does the donor need to agree?”).
Responsibility matrix: (accountable, responsible, consulted, informed).
Project reviews: That freeze the board of their day; a one-page brief and a handover pack.
Field capture offline: synced when back online.
Cross-project views: Map, country pages, portfolio health.

What makes the difference

Planned 15 April. Earliest now 16 November. Waiting on a purchase. 7 months late. Said in words, on the activity.
Click any figure to see how it was calculated.
A short menu for each role, so everyone starts on their own work.

With your AI agent

One question can cross several modules.

The programme manager accepts the draft plan line by line.

A question: “Build the plan for Inclusive Schools Mopti from the approved documents.”
Reads: Programme Management, Workspace: Home, Drive, Calendar & Office, Grant Management & Donor Reporting, Finance & Fund Accounting
Comes back: A draft plan, citing the page each line came from (To validate)
On this module’s pages: A plan drafted from the approved documents

More use cases

Connected to

It shares its records with these modules.

MEAL: Show what changed, and how you know.
Grant Management & Donor Reporting: What each grant still needs from you.
Procurement & Supply Chain: Purchase orders that match their invoices.
HR & Payroll: Staff and consultants, managed together.
Finance & Fund Accounting: Does each project cover its costs?
Workspace: Home, Drive, Calendar & Office: Where the team works, wherever it sits.

In numbers

Built in 6 weeks on the base, 241 screens, 293 requirements traced, accessibility (WCAG 2.1 AA) checked automatically on ~70 screens at every build, English and French including user content.

Before you book a demo.

If we extend a project, which of our rules come into play?

The what-if simulator shows you before you decide. Your policy rules are loaded as data: extend a project by 9 months, and a mid-term evaluation switches on. Alternative sequences of work can be simulated before you adopt one.

What happens to a project’s history when its manager leaves?

It stays with the project. Project reviews freeze the board as it stood that day, decisions are kept with their rationale, and a one-page brief and a handover pack go to whoever takes over.

Can we start with Programme Management alone?

Yes. Each organisation starts with the base, then picks its modules. You can start with one and add others later.

Can we switch a module off later?

You can, and its data is kept. A module switched off disappears from menus and search, and switching it back on restores it.

Can you import from our spreadsheets and current tools?

Yes: people, projects, budgets, policies, files (including a one-time import or a live two-way sync with Google Drive), and the content of your existing workbooks. Connectors to your other systems are built as part of the project.

Next module

MEAL: Show what changed, and how you know.

Programmes & impact

MEAL: Show what changed, and how you know.
Field Data Collection: Offline mobile forms that feed your indicators.
Case Management: Confidential files for each person you support.
Cash & Voucher Assistance: Pay each household once, and reconcile the round.
Information Management & Maps: Who does what, where.

Add to your Relief One
The base: The part every organisation gets.
Relief One

Book a demo of Relief One.

Tell us how your organisation works and which modules you are looking at. We show you Relief One on the parts that matter to you.