Monthly Reports

This document outlines the monthly update requirements for all SPEs and funded projects. The objective is to provide clear, consistent visibility into progress, shipped work, and impact relative to approved proposals.

Written By Mehrdad Sadeghi

Last updated 16 days ago

Context

Monthly updates are used to surface delivered value and progress, enable fast, asynchronous feedback, and centralize evidence for future proposals and renewals. By posting these updates, you provide a clear signal of accountability to the community and make your progress visible, which can meaningfully improve your chances of receiving future funding from the treasury. These updates also allow the work to be highlighted through other channels, helping increase visibility and recognition across the ecosystem.

Update Requirement

An update must be posted at the end of each month or upon completion of a milestone, whichever occurs first.

  • Updates must be posted as a reply in the original proposal thread on the forum

  • The following standard update template must be used

  • All template sections are required to ensure consistency across projects

Quality Expectations

Updates must be:

  • Concise and easy to scan

  • Linked to concrete artefacts, such as:

    • Pull requests

    • Repositories

    • Documentation

    • Deployments

    • Demos or dashboards

  • Explicitly mapped to proposal milestones and goals

The focus is on verifiable progress rather than narrative reporting.

Reference Example

For an example of a compliant update, see the ongoing Explorer RFP updates, proposal thread, which follows this structure.

Standard Update Template

[Project / Team Name] — Update #[N]

Period: [Start date – End date]

Status: [On track/At Risk/Missed*]

Status guidance:
On track - Everything is fine, progressing as expected
At risk - Needs attention, elements are blocked or there is a risk a deadline is missed.
Missed - Deadline has been missed

Summary (1 to 2 sentences):

One-line description of what was completed during this period and why it matters. Focus on outcomes, not process.

Completed Deliverables:

List concrete outputs with links. Group by milestone if applicable.

  • [Deliverable name or milestone]

    • Short description of what shipped or was completed

    • Link(s): PRs, issues, docs, releases, dashboards

ETA for Next Update: [Date]

Planned by Next Update:

  • Brief bullet list of what is expected to be completed by the next report.