# Brigade Reporting

**URL:** <https://discourse.codeforamerica.org/t/brigade-reporting/1520>\
**Category:** Participatory Governance\
**Tags:** network-change\
**Created:** [September 30, 2022, 11:16pm UTC](https://discourse.codeforamerica.org/t/brigade-reporting/1520 "2022-09-30T23:16:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mari](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mari/32/992_2.png) [@Mari](https://discourse.codeforamerica.org/u/Mari)\
**Post date:** [September 30, 2022, 11:16pm UTC](https://discourse.codeforamerica.org/t/brigade-reporting/1520/1 "2022-09-30T23:16:50Z")

</div>

This past year, the Network team has been experimenting with new Brigade reporting processes to replace the big End of Year reporting process from previous years.

To recap, here are the current major changes in the new reporting process:

- Reporting is separated into two categories: **Brigade general activity reporting vs Project reporting**

- **Brigade general activity reporting** is centered around the Brigade’s overall engagement. This should be completed by Brigade leader(s).

- **Project reporting** is centered around a specific project’s engagement and outcomes. This can be completed by project leads, project members, and/or Brigade leader(s). **Brigade leaders should be empowered to divvy up project reporting responsibilities to others.** Project reporting is on a per-project basis (one project per form submission).

After piloting reporting on a quarterly cadence, we’ve learned that it is best to set-up a reporting process that is flexible for Brigades.

# **Proposal**

Brigade Reporting will be open and available to complete on a quarterly basis but Brigades have the option to backfill previous quarters anytime during the year.

We encourage Brigades, especially Brigades fiscally sponsored by Code for America to complete reporting quarterly, if possible. In addition, we will be working to support Brigades and projects with tracking their engagement and defining and communicating outputs/outcomes/impact.

**Why reporting is important** : Brigade reporting is an essential activity for the CfA Network program to understand what support needs and gaps there are to address in our Brigade community, to equip Brigades with information to help communicate their Brigade’s impact and engagement when building partnerships or growing their volunteer base, and to provide information about the activities and impact of the entire Brigade Program to secure funding to sustain the CfA volunteer Network program at-large.

> **Network Team Brigade Reporting Steward: Marianne Miranda, Brigade Community Research Specialist**  
> If you have any questions, need for support, and recommendations related to Brigade reporting, please contact Mari at [mmiranda@codeforamerica.org](mailto:mmiranda@codeforamerica.org).

# Ways to Participate

### 1. **Prompts for Discussion**

💭 Share your thoughts in the comments section below.

- What are your initial thoughts about the proposal?

- What reporting cadence would feel doable for your Brigade?

- What types of support would your Brigade need / what would your Brigade leaders, project leads, and relevant Brigade members need to feel equipped to report on your Brigade’s activities and projects?

### 2. **Brigade Reporting Questions Feedback Document**

**Want to suggest a change or addition in the content for both reporting forms?** [Add a comment/suggestion in this Google Doc](https://docs.google.com/document/d/1LotBoqQmJJmvFuAr5vwHqJCFuXM11CIV3a4kPKiWwwo/edit#heading=h.tneev5jrd4aw). You can also directly email Mari at [mmiranda@codeforamerica.org](mailto:mmiranda@codeforamerica.org). Our goal is to get to the point where the questions remain relatively the same so that the Network can focus on sharing guidance and best practices around reporting and Brigades can adopt processes to capture information that is expected from the start in a way that makes sense for each Brigade.

#### Relevant Discourse Posts

- [The Current State & Future of Brigade Reporting (Q1-Q3 Reporting Open)](https://discourse.codeforamerica.org/t/the-current-state-future-of-brigade-reporting-q1-q3-reporting-open/1508)

---

<div class="post-metadata">

**Author:** ![Mari](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mari/32/992_2.png) [@Mari](https://discourse.codeforamerica.org/u/Mari)\
**Post date:** [October 20, 2022, 1:07am UTC](https://discourse.codeforamerica.org/t/brigade-reporting/1520/2 "2022-10-20T01:07:26Z")

</div>

Here’s what folks shared in the Participatory Governance area at Brigade Congress:

- Provide scripts and/or easy ways to push out this reporting from brigade organizers to project organizers over Slack (but make sure brigade organizer get outputs)
- Keep it short and easy – we have day jobs
- The reporting requirements this year were absolutely ridiculous (sorry!) Make the forms short, simple + optional. We’re volunteers!
  - +1

- Being able to report **AFTER** a heavy phase of work was **CRITICAL**. Volunteers don’t have time to volunteer and report; they only have time for either/or.
- Backfill is exciting because project timing or personal obligations can mess with the ability to do quality reporting “immediately” (so to speak)

 ![IMG_8104](https://us1.discourse-cdn.com/flex020/uploads/codeforamerica/original/1X/514e275aa3ed0a3d6ad78f341425359cf6d1dd40.jpeg)

---

<div class="post-metadata">

**Author:** ![Mari](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mari/32/992_2.png) [@Mari](https://discourse.codeforamerica.org/u/Mari)\
**Post date:** [July 1, 2023, 6:42am UTC](https://discourse.codeforamerica.org/t/brigade-reporting/1520/3 "2023-07-01T06:42:52Z")

</div>