Development sector
For donors and development partnersMonitor the projects you finance from the records behind them
For donors, development partners and their task teams: progress against plan, spending totals, results and risks read project by project from the implementer's records, without keeping the implementer's books. Monitoring by sector is in development.
The development partner edition is in development. Today the product is used by the implementer, and a financier is given a login to the implementer's workspace. The first group of modules below is what that login reads today; the second stays with the implementer or is not built yet. Its menu shows the cost table, appraisals, projects, each project's lifecycle and Project Book, spending totals, the risk log, contracts and the financier summary. The engine also answers it for advance totals, activities, the annual work plan, results indicators and the executive overview, which its menu does not list. It does not show invoice lines, invoice aging, monthly expenditure, the interim financial report workbook or procurement. It cannot change records, except in the risk log, where it can record entries and ratings for the projects its grant reaches.
A task team leader prepares for a supervision mission
A fictional development partner finances a basic education project in Northland. Two weeks before the mission, its task team leader wants to see what has been spent, what is at risk and which results are behind, from the implementer's records rather than an emailed spreadsheet.
-
Partly built Financed projects
The task team leader signs in to the implementer's workspace with a financier's login and opens the financed project. The implementer creates projects today with a code and a title, and a financier's login reads them. Simple projects, with further modules added one project at a time, are in development.
-
In the product Spending totals
Spending totals: counts and sums of invoices and advances. The invoice lines behind them stay with the implementer.
-
In the product Risks
Open risks with their ratings. The task team records its own rating on a late textbook delivery.
-
Partly built Results and indicators
Results indicators against their targets. A missing reading shows as a dash, not as zero. Results indicators and achievement are in the product. Who recorded a reading is not stored yet, and a named state for a missing value is in development.
-
Built — next release Monitoring and alerts
Panels across every financed project, by sector. Today each project is read one at a time.
| Risk | Owner | Rating |
|---|---|---|
| Textbook delivery late | Procurement unit | High |
| Teacher vacancies in two districts | Human resources | Medium |
| School grants unspent at year end | Finance unit | Medium |
Fictional organisation, people and figures. Each step carries the label of the module it uses; a step labelled In development or Planned describes the design, not today's product. A step labelled Partly built uses a module only part of which runs today; the line under it says which part.
The people this edition is designed around
Task team leaders
Each financed project's spending and advance totals, cost table, contracts, risks and Project Book, read from the implementer's records. The invoice lines behind the spending totals stay with the implementer.
Portfolio and sector managers
Monitoring panels and a portfolio by project and sector are in development. Today a financier's login reads each project the grant reaches, down to its activities.
Fiduciary staff
Spending totals today. The interim financial report workbook is read by the implementer, not yet by a financier's login; closure and the clearance of open items are in development.
Managers
A login that reads and does not change records, except entries and ratings in the risk log. By default the edition leaves out voucher entry, procurement entry and field capture.
What this edition switches on, and what runs today
Of the 37 modules this edition switches on by default, 6 are in the product, 17 are partly built, 14 are built for the next release, 0 are in development and 0 are planned. Checked against the product on 10 October 2026; the next release checked on 14 October 2026.
What a financier's login reads today
Plan
Partly built
Financed projects
Each project you finance and its place in the implementer's organisation.
The implementer creates projects today with a code and a title, and a financier's login reads them. Simple projects, with further modules added one project at a time, are in development.
Partly built
Annual work plan
The implementer's annual work plan and budget.
Deriving, confirming and withdrawing a work plan run in the engine today; their screen is in development, and a financier's login reads a plan only through the engine, not from its menu. Designing a plan line by line, copying last year's, and Excel import and export are in development.
In the product
Cost table
Cost lines with their financing source, checked against the financing plan.
A financier's login reads the cost table. Uploading it from Excel stays with the implementer.
Partly built
Appraisal
Reads an appraisal document and reports which assumptions it can tie to a cited page.
Works where the separate checking engine is installed. It is not packaged with the product yet.
In the product
Activities
The activities of a plan and their steps.
Deliver
Partly built
Financed contracts
The contracts under each financed project and what they draw on.
A financier's login reads the contract screen: the award, the evaluation and what the contract draws on. Milestones and deliverables are in development.
Money
In the product
Spending totals
Counts and sums of the implementer's invoices and advances.
A financier's login reads totals only. Invoice lines, their aging and monthly expenditure stay with the implementer.
Results
In the product
Executive overview
An overview of activities, their steps and coverage.
Partly built
Project Book
One project's record, assembled only from records that exist, with a page for what it could not say.
The Project Book and a printable export are in the product. Charts, and PowerPoint, PDF and Excel files, are in development.
Partly built
Results and indicators
Indicators with baselines, targets and reported values.
Results indicators and achievement are in the product. Who recorded a reading is not stored yet, and a named state for a missing value is in development.
Partly built
Financier view
A read-only summary for financiers, and spending and plans read by financing source.
A read-only programme summary for financiers is in the product. Reading spending and plans by financing source is in development.
Govern
In the product
Risks
Risks, issues and decisions in one log, with proposals held apart until a person confirms them.
What stays with the implementer, or is not built yet
Plan
Partly built
Pipeline steps
The steps work moves through, and where each item stands.
The organisation's chain of approval steps, and each activity's place in it, are in the product. Steps that a project names for itself are in development.
Built — next release
Timeline
Dates from every record on one timeline, and a baseline a manager locks.
Deliver
Built — next release
Today and tasks
Daily tasks, a work log, carry-overs and this week's capacity.
Built — next release
My team
For a team leader: members, their open tasks, this week's load, late items, blockers and the next meeting.
Built — next release
Recurring operations
Weekly or monthly work, with missed runs recorded.
Built — next release
Requests and cases
Requests with response clocks, and a named reason for every decline.
Partly built
Training events
Training events and their participants.
Training records are kept by the engine. Their screen is in development.
Partly built
Assistant
Ask a question in words.
A text question box is in the product, but production is not connected to a language model, so it refuses each question by name instead of answering. Answers, assistants that work with the person's own access, and an inbox of what they propose are in development.
Money
Partly built
Interim financial reports
The implementer's interim financial report workbook and withdrawal applications.
The workbook is in the product for the implementer's administrators; a financier's login cannot open it. Withdrawal applications are not a record yet; they are in development.
Results
Built — next release
Monitoring and alerts
Each project's physical, financial and procurement progress, milestones, reports due, risks and alerts, panel by panel, with no single score.
Built — next release
Portfolio
Every project's status by name, with no single score.
Built — next release
Targets
Targets that split down and results that roll up, where the split must add up.
Built — next release
Reports
Progress reports in which every figure traces to the records.
Progress summaries exist in the product today. The report builder is built for the next release.
Partly built
Delay insights
Rule-based delay scores and a bottleneck view.
Rule-based delay scores and a bottleneck view are in the product. One factor of the score is switched off, and the page says so and shows the highest score still possible.
Built — next release
Closure
What stands between a project and closing, the sign-offs, the completion report and the archive.
Govern
Built — next release
Blockers
Blockers that move up until someone who can decide owns them.
Built — next release
Meetings and decisions
Agenda, attendance, minutes, decisions, and actions that become tasks.
Built — next release
Accountability
Everything open that nobody owns, counted and named.
Partly built
Audit log
Who changed what, and when.
The audit log lists changes for administrators. Refusals and agent actions are not logged yet, and some record types are not logged.
Partly built
Approvals and notifications
Approval requests, their reminders and escalation, and each person's notifications.
Each activity moves through the organisation's approval steps today. Approval requests with reminders, escalation and notifications are in development.
Settings
Partly built
Sign-in and organisation settings
Signing in, the organisation's settings, and switching modules on or off for the organisation.
Sign-in is in the product. Switching modules on or off, and each person arranging their own menu, are in development.
Partly built
Users and access
Accounts, roles and the grants that decide who sees which project.
Users and roles are in the product. A grant editor, and access to one project by default, are in development.
Built — next release
Organisation structure
The organisation names its own levels, such as divisions and departments, or ministries and agencies.
In the product
Plan and usage
What the organisation's plan includes and how much of it is used.
Partly built
Spreadsheet sync
Reads the activity plan from the organisation's spreadsheet and reports what it refused.
A sync from one fixed spreadsheet layout runs and reports today. Reading other layouts is in development.
A label is a claim about the product people can use today
A module counts as in the product only when it runs in the live product. Work that is built and tested but not released yet is labelled Built — next release; work still being built is labelled in development.
In the product
Runs in the product today.
Partly built
Some of it runs in the product today; the note under it says which part.
Built — next release
Built and tested on the release branch, not in the live product yet. It reaches the live product with the next release.
In development
Being built. Not in the product yet, and not offered to customers until it is.
Planned
Designed, not built yet.
Not switched on by default in this edition. Once module settings ship, an administrator will be able to switch on any of these that are built:
- Procurement Partly built
- Field capture on a phone Planned
- Expert inputs Planned
- Advances Partly built
- Accounts Built — next release
- Fixed assets Planned
- Time and invoicing Planned
Editions are designed to change the words and the menu, never what the product can do. The other editions: Projects, Companies, Consultants and team leaders.
See today's product with fictional data
The public demo runs in your browser on a fictional programme. Its labels are older than this page's; where they differ, the labels on this page are the ones checked against the product.