Turn project documentsinto operational intelligence.

A development programme can be governed by multiple sources of information: research, proposal documents, donor agreements, objectives, workplans, indicators, reporting requirements, meeting notes, field engagements, participant records, activity evidence, follow-ups and periodic reports.

The problem is that these pieces of information can become operationally disconnected.

The proposal may define what the programme promised. The workplan may define what should happen. Field teams record what actually happened.

Reporting teams later need to reconstruct the relationship between all three.

Programme documents contain information that should influence day-to-day implementation.

Instead of leaving that information buried inside files, the platform creates structured knowledge categories that can support programme operations.

The objective is not merely to summarise documents. It is to make programme knowledge available to the operational system.

A workplan should not remain a static document once implementation begins.

The platform models workplan items so planned activities can become trackable operational commitments.

The workplan captured is the Annual Workplan 2026 at version v1, with two items visible and an average completion of 0% at the moment of capture.

Activities provide the connection between the programme plan and work carried out by the organisation.

The captured system currently shows two planned activities, including a Policy Dialogue and a Training Workshop.

The activity layer can connect programme work with the wider operating model.

Not every engagement takes place behind a desk.

The system includes a field workflow designed around officers conducting meetings, dialogues and other engagements, supporting structured capture of implementation evidence.

Typed notes are supported where a meeting is not recorded, and the workflow is intended to remain usable while an officer is conducting an onsite engagement.

The field layer converts a planned activity into a recorded engagement with participants, notes and evidence attached to it.

Because the engagement is modelled rather than filed, follow-ups and activity evidence remain connected to the reporting layer.

Traditional reporting workflows often require staff to reconstruct activity information after implementation has already happened.

This platform is designed so reporting draws from structured programme data captured throughout the operating cycle.

The intention is not to have AI invent reports from nothing. The system provides structured evidence and programme context from which reporting can be produced, reviewed and approved.

Producing a report internally is not necessarily the end of the reporting workflow.

Where donor submission is required, the system needs visibility into the submission requirement, the deadline, report readiness, submission status, donor response, required actions and follow-up.

The platform includes an “Ask Project Intelligence” capability. Its purpose is to allow users to interrogate processed programme documents without separating the AI experience from the project's source material.

The interface explicitly states that answers should be generated only from processed project documents, and should cite the relevant page, sheet or section.

This creates a fundamentally different experience from using a generic AI chatbot. The assistant operates inside the programme's knowledge boundary.

In organisational environments, a plausible answer is not enough. Users need to understand where important information came from.

The system is therefore designed around source-grounded project intelligence rather than unrestricted generation.

Once implementation data is structured, management can understand programme activity without manually rebuilding the picture from separate documents and spreadsheets.

The executive view should surface programme state and exceptions without requiring management to inspect every underlying record.