Project manager or team leader in any sector? Start with projects or see the team view.
Work plans, approvals, advances, procurement, M&E and interim financial reports in one system. Every figure is traced to its source, and anything never recorded is designed to show as missing, not as zero.
Partly built Annual work plan
| Activity | Unit | Budget | Status |
|---|---|---|---|
| 2.1.3 Teacher training, grades 1–3 | PESS-N | $184,000 | Approved |
| 2.2.1 Textbook printing | Curriculum | $412,500 | Step 4 of 9 |
| 3.1.2 School grants, round 2 | Finance | $960,000 | Waiting 12 days |
| 1.4.1 EMIS data audit | Planning | Not recorded | Draft |
No budget was entered for 1.4.1, so it is designed to show as missing and not to be counted as $0 in any total. A named "not recorded" state is in development.
Partly built Approvals and notifications
2.2.1 Textbook printing: approval steps from your financing agreement
Partly built Advances
| Advance | Holder | Amount | Age |
|---|---|---|---|
| ADV-0142 | Southmere district office | $18,400 | 74 days |
| ADV-0151 | Teacher Training College | $9,250 | 41 days |
| ADV-0158 | Curriculum Unit | $4,100 | 12 days |
Liquidation policy: 60 days. ADV-0142 is overdue and will be flagged in this quarter's IFR.
Partly built Interim financial reports
| IFR line, Q3 | Amount | Source |
|---|---|---|
| Opening designated account balance | $642,180 | Q2 IFR · line 9 |
| Expenditure, Component 2 | $1,204,350 | 38 payments |
| Advances outstanding | $31,750 | 3 advances |
| Exchange difference | Not recorded | rate not entered |
Each amount is designed to open the records behind it, and a missing exchange rate to be reported as missing, not left out. The workbook of approved and paid invoices by category is in the product.
Partly built Assistant
How answers are designed to look. Production is not connected to a language model yet, so today the assistant refuses each question by name instead of answering.
One number, and what it is made of
Component 2 of a fictional programme's quarterly report. The total sits on top of the payments behind it, not beside them. Partly built Interim financial reports
A school grant of $24,000 to Southmere is entered against activity 3.1.2 in Component 2, with its invoice.
In the product Invoices and expenditure
The budget check, then the director. The activity moves through the steps your organisation set.
Partly built Approvals and notifications
Each activity moves through the organisation's approval steps today. Approval requests with reminders, escalation and notifications are in development.
Component 2's total in the report workbook is the sum of 38 payments, and the workbook lists every one of them.
Partly built Interim financial reports
The interim financial report workbook is in the product. Withdrawal applications are not a record yet; they are in development.
No exchange rate was entered for September. The line says so, and the total says it leaves that line out.
In development A named state for a missing value
| Uses of funds | Amount | Behind it |
|---|---|---|
| Component 1 · Teachers | $386,400 | 14 payments |
| Component 2 · School grants | $1,204,350 | 38 payments |
| ↳ 3.1.2 Southmere grant | $24,000 | Approved, 5 of 5 steps |
| Component 3 · Systems | $217,900 | 9 payments |
| Exchange difference, Sept | Not recorded | rate not entered |
| Total uses, Q3 | $1,808,650leaves out 1 line with no rate |
Work-management software is built for company teams shipping projects. A project management unit has to account for every dollar of public money to a ministry and a donor, so it needs records that hold up in an audit.
Every supervision mission starts with days of collecting files from implementing units and reconciling versions by hand.
A total in a report can't be traced to the activity, payment or advance behind it. Auditors notice, and so do task teams.
A missing value is counted as nothing, so a dashboard looks healthy because nobody entered the bad news.
Drawn with a fictional programme's data. Partly built Annual work plan Partly built Approvals and notifications Partly built Interim financial reports
Partly built Annual work plan
Deriving, confirming and withdrawing a work plan run in the engine today; their screen is in development. Designing a plan line by line, copying last year's, and Excel import and export are in development.
See it in the tourPartly built Approvals and notifications
Each activity moves through the organisation's approval steps today. Approval requests with reminders, escalation and notifications are in development.
See the worked examplePartly built Advances
Advances and a reconciliation total are in the product. Showing an unrecorded return on every row is in development.
See it in the tourPartly built Interim financial reports
The interim financial report workbook is in the product. Withdrawal applications are not a record yet; they are in development.
See the worked examplePartly built Audit log
The audit log lists changes for administrators. Refusals and agent actions are not logged yet, and some record types are not logged.
See it in the tourPartly built Assistant
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. People decide: approvals and changes are always made by a named person, programme data sent to the AI model is not used to train it, and AI can be switched off for a deployment.
See it in the tourCost tables (COSTAB) and next-project planning are in the product today. Procurement bids and awards, withdrawal-application tracking and the annual work plan screen are partly built, and field monitoring on a phone is designed but not built. The product tour labels every screen, and the solutions page labels every module.
| Spreadsheets & email | General work-management tools | Projects Manager | |
|---|---|---|---|
| Pricing | Free, but staff time is not | Per user per month, often with minimum seat counts | Per programme; implementing-unit and viewer seats priced separately |
| Approval steps from your financing agreement | By email | Build it yourself with automations | Configured for you at onboarding |
| Advances and liquidation | A separate register | Not built in | Advances register in the product; the withdrawal-application tracker is partly built |
| Interim financial reports | Compiled by hand | Not built in | A workbook of approved and paid invoices by category; line-level sources and uses is being built |
| Results framework and indicators | A separate file | Custom fields | In the product; readings with their source are being built |
| Missing data | Blank cells summed as zero | Blank fields | A missing indicator reading shows as a dash, not zero; a named "not recorded" state is in development |
| AI | None | Often a paid add-on or credit-metered | Monthly allowance included in every plan (the assistant is not connected to a language model in production yet); answers cited or withheld |
| Where data is hosted | Wherever the file goes | Fixed regions; residency often enterprise-only | Region agreed with you before go-live; hosting is not yet live |
| How you buy | Not applicable | Credit card or enterprise contract | Quotation, then invoice against a purchase order |
"General work-management tools" summarises the published pricing and feature pages of leading products, as reviewed in October 2026. Individual products differ, and many can be extended with integrations.
Templates and checklists for the documents your financing agreement requires. Free, no sign-up.
A neutral specification and justification templates for buying a project MIS.
TemplateSources and uses, reconciliation, and the review problems to avoid.
TemplateQuantity × unit cost, quarterly phasing, the links reviewers check.
ChecklistFour weeks of preparation, so the mission finds no surprises.
We load your current annual work plan and implementing units from the files you already use.
Approval steps, roles and reporting views are set to match your financing agreement.
Hands-on sessions for coordinators, finance, M&E staff and implementing units.
A separate installation for your programme. Production hosting is being arranged; pilots are agreed individually.
Every plan costs the same for everyone, everywhere. Pay monthly, or pay ahead: 10% off for 6 months, 20% off for 12 months. Every workspace starts with a 14-day trial of everything (on request until self sign-up opens), and viewers are free up to each plan’s limit.
Yes. It is licensed per programme per year and invoiced, so it can be entered in your procurement plan and bought through the method that fits its value. We prepare a quotation on request, and the free procurement pack helps you draft your own specification.
We host each programme's installation; the region is agreed with you before go-live. Production hosting is being arranged. Where law or ministry policy requires data to stay in the country, in-country or client-hosted installation can be discussed; none has been done yet.
By role. Everyone who adds or changes records is a person who can edit, and an implementing unit's staff can be limited to their own unit; donors, ministries and auditors are free viewers up to your plan's limit.
Yes. Onboarding starts by loading your current annual work plan and unit list from the spreadsheets you already use.
Your workspace becomes read-only and nothing is deleted: nothing is deleted and your records stay readable. The retention period, the export route and a written deletion receipt are what we intend to commit to in the terms and the data-processing agreement — those are still in draft and not in force, so ask us for the current position before you rely on it
Yes. It can be switched off for a deployment. When it is on, answers are designed to cite the records they came from.
A 30-minute walkthrough: a work plan, an approval, an advance, and the IFR a task team would see. We reply as soon as we can.