Establish the foundation
Align on priority questions, data permissions, governance, and the people needed to deliver.
03 / Delivery & governance
A focused question. A defined output. A clear record of how the work was done.
Explore this chapterThe work cycle
An initial piece of work could produce a landscape brief, evidence summary, or opportunity brief. Scope and review criteria would be agreed before work begins.
Agree the question, intended users, expected output, and what would make the work useful.
Set responsibilities, dependencies, review points, and a realistic sequence of work.
Confirm source permissions, access, handling requirements, and the expertise needed.
Develop and review the output. Make sources, assumptions, and unresolved questions visible.
Review the work against the agreed scope and decide what is worth doing next.
Accountability
The records connect the question, the sources, the judgment, and the next step.
A work plan would identify the expected outputs, accountable owners, dependencies, review points, and acceptance criteria. Each item should connect to the question the work is intended to answer.
A source record would preserve origins, dates, permitted uses, and quality limitations. Access would be assigned for agreed purposes and removed when no longer needed.
A review record would show who checked the output, how the evidence was interpreted, and which questions remain. Reported activity would be distinguished from demonstrated effectiveness.
Material changes, their rationale, and approval would be recorded. The work plan would identify who resolves issues, escalates risks, and responds to incidents.
Reporting would distinguish completed work, next steps, and blockers. Administrative arrangements would cover appropriate approvals, financial oversight, records, and conflicts of interest for the work undertaken.
Development phases
Each phase should establish a reason to proceed. Evidence, delivery capacity, and agreed safeguards guide the next step.
Align on priority questions, data permissions, governance, and the people needed to deliver.
Develop focused use cases, test analytical workflows, and refine outputs with participating institutions.
Expand participation and use cases where evidence, capacity, and agreed safeguards support it.
Clear responsibilities
100Fold’s role in this model is to support information, introductions, and coordination.
Sharing one contribution would not open the rest of an institution’s records. Permitted uses, access, and information release would be agreed for the relevant work.
The model does not include a pooled fund or payment intermediary. Donors would use their chosen giving arrangements; participating institutions would retain their own funding, approval, and due-diligence responsibilities.
Scoping framework
A defined scope connects the question, context, available information, and intended output.
The issue to understand and the decision the work would inform.
The relevant geography, time frame, and implementation context, including the people closest to the work.
Relevant information already available, its sources, and what could be shared with permission.
The intended landscape brief, evidence summary, or potential introductions, with criteria for review and use.
Scope, timing, responsibilities, and participation would be agreed before work begins. The available information and required expertise would determine what a useful first piece of work could deliver.