What MapToc does

MapToc is an AI program-intelligence product in development. It turns the reports, meeting notes and documents teams already produce into reviewable evidence signals, then connects approved material to decisions, risks, funding context and observed outcomes in a source-linked program record.

Organise what already exists

A team contributes a relevant update or document. The proposed system identifies candidate results, decisions, material changes, risks, lessons and unanswered questions. It should preserve the distinction between something a source reports and something the program has established.

For example, “attendance seems to have improved after outreach moved to Saturdays” is a reported signal. It is not yet proof that the schedule change caused the improvement. A reviewer should be able to preserve the signal and identify what further evidence is needed.

Keep the explanation with the result

Approved items are intended to connect to program objectives, dates, places and related records. A decision to change delivery can remain linked to the problem that prompted it and to later observations. Supporting and contradicting evidence should both remain visible.

Reuse the record

The planned record can support donor questions, report preparation, handover, evaluation and future program design. Reuse means finding and citing approved evidence; it does not mean submitting the same interpretation to every audience without review.

What often happens now	What MapToc is designed to make possible
Teams reconstruct answers from scattered documents	Evidence is organised as updates are contributed
Results lose the context behind them	Decisions, risks and changes remain connected
Lessons are hard to find after staff changes	A shared program history supports handover
Claims become detached from their sources	Approved items preserve source attribution

Keep the scope useful

MapToc should capture the road to the outcome, rather than every operational step. Task assignment, timesheets, scheduling and general file storage remain outside the core proposition. The test is whether an item helps someone understand what changed, why it changed, what result was reported or what evidence is still missing.

Connect funding without transaction overload

The proposed finance layer uses grant amounts, allocations, tranches and periodic expenditure summaries by category. Teams can attach receipts or contracts to a material decision when useful; maintaining every transaction in MapToc is not required.

Budget-to-actual comparison requires an actual expenditure summary for the same period, currency and scope. An allocation alone cannot establish spending or explain a variance. A route change, supply shortage or emergency response may provide a reported explanation; the record preserves the source and review status of that explanation.

Program management centres on objectives, milestones, consequential decisions, risks and outcome evidence. Accounting systems remain authoritative for financial transactions. A source-linked record can make evidence easier to retrieve and inspect, but it does not replace independent audit, certify compliance or make the record tamper-proof.