# Monthly Reports

Monthly reports are leadership packs — a regular, structured way for authors to communicate status to the organization's leaders. There is one report per author per month, each carrying a simple health signal and precise controls over who can read it.

## One report per author per month

Reports are scoped to an **author and a month**: each author writes one report for a given month. This keeps the cadence predictable and makes it easy to line up reports across authors and across time. The content itself is **flexible** — there is no rigid template, so authors can shape each report to what matters that month.

## RAG status

Every report carries a **RAG status** that gives leaders an at-a-glance read on health before they open the detail:

| Status | Signal |
|--------|--------|
| Green | On track |
| Amber | Some concern or risk |
| Red | Serious concern, needs attention |

Because the status is a single, consistent field across all reports, leadership can scan a month's packs and immediately see where to focus.

## Visibility

Reports support three visibility options so authors can match the audience to the sensitivity of the content. Owners always retain access.

| Visibility | Who can read it |
|------------|-----------------|
| Private | The author and owners only |
| Group | Members of a named group, plus owners |
| Admins | Owners and admins only |

- Use **private** for a personal or sensitive report meant only for leadership.
- Use **group** to share with a specific team — for example, a department reading its own leadership pack. Groups are managed in [Members, roles & groups](/docs/admin/members-and-roles).
- Use **admins** for reports intended for the leadership tier as a whole.

Choose visibility deliberately: it is the mechanism that keeps a candid report in front of the right eyes and away from the wrong ones.

## Who can author reports

Creating a report requires the **`report:author`** permission, or an **admin** or **owner** role. This keeps authorship in the hands of the people responsible for reporting status while still allowing owners and admins to write reports directly. To let a non-admin write reports, grant the report author permission as described in [Members, roles & groups](/docs/admin/members-and-roles).

## A typical monthly rhythm

1. Grant **`report:author`** to the people who should write reports.
2. Each author writes their **one report for the month**, filling in the flexible content.
3. The author sets a **RAG status** — green, amber, or red — to summarize health.
4. The author chooses a **visibility**: private, a specific group, or admins.
5. Leaders scan the month's reports by RAG status and read into the ones that need attention.

## Related

- [Portfolio](/docs/admin/portfolio)
- [Projects & roadmaps](/docs/admin/projects-and-roadmaps)
- [Members, roles & groups](/docs/admin/members-and-roles)
- [Resource planner](/docs/admin/planner)