White Paper

White Paper / Building MapToc

Vision and roadmap

Build program memory first. Make evidence reusable across reporting, evaluation and future programs.

MapToc's vision is for every funded program to leave a source-linked record of what happened, what changed and what remains uncertain, while there is still time to act. That record should grow during implementation and help the next person understand the work after teams change or funding closes.

The vision

The long-term aim is for the living program record to become standard evidence infrastructure for funded work. Institutions set the record requirements at the start. Authorized users maintain it through ordinary program activity. Funders and managers gain a clearer view of resources, delivery and outcome evidence while decisions remain open.

Across an organization, these records could make it easier to find relevant experience from earlier programs. A useful network would preserve differences between contexts as carefully as it reveals similarities. A connection between two records is a starting point for investigation, not proof that an intervention will transfer successfully.

The roadmap

Stage What we are building towards What must be established
1. Capture and review Source-linked proposals, a review inbox and an approved program record. Reviewers can check useful evidence without losing context or adding excessive work.
2. Connected workflow Authorised shared-folder connections, file-change detection and review digests. Sources stay in scope, access is respected and duplicate or changed files are handled reliably.
3. Institutional oversight Funding context, review requirements, exceptions and source-linked outcome views. Organizations gain timely visibility while program teams reduce repeated reporting effort.
4. Reporting and evidence reuse Reusable reports, evidence packs, requirement checks and complete review history. Records are traceable and exportable without implying independent assurance.
5. Portfolio intelligence Search across permitted programs, relevant lessons and recurring evidence gaps. Definitions, context and permissions are strong enough for meaningful comparisons.

This is a proposed sequence, not a dated release commitment. MapToc remains in development. Pilot results will determine priorities and whether a capability is ready to expand.

What the first pilots should test

A pilot should begin with a defined program, a limited source collection and named reviewers. It should examine the whole workflow: connecting sources, handling proposals, checking citations, retrieving evidence and preparing a report. A faster export is not a net saving if review and maintenance take more time than they remove.

Alongside workload, pilots should test whether a reader can understand a significant implementation decision from the record, whether uncertainty survives extraction, and whether evidence remains accessible at handover. These are practical tests of program memory.

From one program to a network

Expansion should start only when individual records are useful. Future teams could search for a delivery constraint, an adaptation or a lesson and see the evidence behind it. Cross-program discovery must retain the location, population, timing, resources and limitations that affect relevance.

Sharing would be deliberate and permission-based. A lesson may be suitable for wider use even when its original source contains information that must stay restricted. The homepage network remains an illustration of this vision, not a live set of participating organizations.

The intended impact

The ambition is less repeated evidence assembly, clearer outcome explanations and learning that survives staff changes and funding cycles. Better records can support evaluation and decisions. They cannot supply missing evidence, guarantee completeness or establish causality on their own. Public claims about MapToc's impact should follow measured pilot results.

The direction: outcome evidence infrastructure

Build from a useful program record toward funding transparency, program integrity and explained outcomes. The intended sequence adds funding context and institutional requirements, milestone review, reusable reports and evidence packs, then permissioned portfolio intelligence.

The ambition is for institutions to make a continuous, source-linked outcome record a shared standard from award to closure. The mechanism must remain proportionate: use existing records, reduce repeated submissions and direct human attention to material gaps and decisions. The record can support audit preparation, but MapToc does not perform independent assurance or certify audit readiness.

Updated 24 September 2026 · Map the Outcome