Delivery plan

A milestone-gated roadmapfor grant accountability.

The roadmap aligns product work, compliance controls, partner pilots, reporting, and independent evaluation. Each phase produces evidence outputs suitable for grant monitoring.

§24-month roadmap

Milestone-gated delivery

Six phases.Every gate earns the next.

The pilot runs over 24 months. Each phase produces evidence and clears a funder gate before the next begins — no phase advances on optimism.

  1. Months 1-2

    Mobilization and governance

    Finalize award controls, delivery ownership, procurement plan, reporting cadence, risk register, and grant compliance calendar.

    Kickoff pack, governance charter, risk register, procurement file

    Gate · Funder accepts mobilization evidence

  2. Months 1-3

    Discovery and technical architecture

    Validate user requirements, map data sources, confirm MVP boundaries, and complete security and privacy design.

    Product requirements, architecture diagrams, data map, DPIA scope

    Gate · MVP scope locked with compliance signoff

  3. Months 3-8

    MVP build and data model

    Build project profiles, diligence scoring, reporting workflows, partner intake, analytics foundations, and public website.

    Working MVP, test results, accessibility review, demo script

    Gate · MVP passes security and acceptance criteria

  4. Months 7-14

    Pilot onboarding and verification workflow

    Onboard pilot buyers and project developers, test evidence workflows, and generate initial buyer reports.

    LOIs, onboarding records, report samples, issue log

    Gate · Pilot participants validate workflow usefulness

  5. Months 12-20

    Reporting, training, and public outputs

    Deliver workshops, stakeholder learning sessions, report templates, and compliance-ready documentation.

    Training records, webinar materials, report exports, feedback analysis

    Gate · Funder accepts public-benefit outputs

  6. Months 20-24

    Independent evaluation and scale plan

    Commission evaluation, reconcile outcomes against KPIs, and decide whether to scale, pivot, or stop.

    Final evaluation, impact statement, scale-readiness plan, financial update

    Gate · Board/funder go/no-go decision

02Reviewer-readable record

Milestone evidence

Every phase needs areviewer-readable record.

This prevents the platform from appearing as an open-ended software build and gives funders concrete proof of delivery.

MilestonePeriodEvidence fileApproval gate
Mobilization and governanceMonths 1-2Kickoff pack, governance charter, risk register, procurement fileFunder accepts mobilization evidence
Discovery and technical architectureMonths 1-3Product requirements, architecture diagrams, data map, DPIA scopeMVP scope locked with compliance signoff
MVP build and data modelMonths 3-8Working MVP, test results, accessibility review, demo scriptMVP passes security and acceptance criteria
Pilot onboarding and verification workflowMonths 7-14LOIs, onboarding records, report samples, issue logPilot participants validate workflow usefulness
Reporting, training, and public outputsMonths 12-20Training records, webinar materials, report exports, feedback analysisFunder accepts public-benefit outputs
Independent evaluation and scale planMonths 20-24Final evaluation, impact statement, scale-readiness plan, financial updateBoard/funder go/no-go decision