Monthly Reporting

Hey everyone,

We’re introducing a simple monthly update template for all SPEs and funded projects that makes it easy for people to see the value you’re creating. These reports will help get fast feedback on what you’ve shipped, create visibility around new features and put all the relevant evidence needed for future proposals in one place.

What we’re asking you to do

  • At the end of each month or at the end of a milestone (whichever comes first), post an update as a reply in your original proposal thread on the forum.
  • Use the following minimal template. You can adapt the wording, but please keep all the sections so we have consistent information across projects:

It should take ~5 minutes to produce. The key is that the update is:

  • Short and easy to scan
  • Linked to concrete artefacts (PRs, repos, docs, deployments, etc.)
  • Clearly tied back to the proposal’s milestones and goals

As a reference, you can look at the ongoing Explorer RFP updates, which follow a similar pattern.


Here’s the template:

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

Period: [Start date – End date]

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

:light_bulb: 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.

If anything about this format doesn’t work for your project, reach out so we can adjust while still keeping reports comparable across the ecosystem.

5 Likes