Reports

The Reports module — internally Reports v2 — handles the recurring administrative reports your church already runs on paper. Weekly attendance count from each cell. Monthly giving summary from each branch. Quarterly discipleship update from each ministry leader.

You define a report template, assign it to specific roles or users with a cadence, and then collect submissions on the schedule. The data lives in one place, with reminders, overdue tracking, and rollup views.

Templates vs submissions

Two concepts:

• A template is the structure of a report — its fields, its assignees, its cadence. You define this once and it stays. See Report templates.
• A submission is one filled-in instance of the template for a specific period. Pastor Mary, week of June 2nd, Sunday Worship attendance count = 47. You complete these on the schedule. See Submitting a report.

A single template can produce hundreds of submissions over time — one per assignee per period.

What kinds of reports work well here

• Weekly attendance counts per cell or branch.
• Monthly giving / collection summaries.
• Cell leader updates ("How are your members doing? Any prayer requests?").
• Ministry head reports.
• Pastor-to-bishop monthly reports in denominational structures.

Anything that's currently a recurring email or paper form sent up the org chart is a candidate.

What doesn't work here

• Ad-hoc one-time data collection — use a form instead.
• Real-time dashboards — those are in the dashboard and giving / attendance reports, not here.

Cadence options

Templates can be scheduled:

• Weekly — due each week on a chosen day.
• Fortnightly — every two weeks.
• Monthly — due on a chosen day of the month.
• Quarterly — every 3 months.
• Annually — once a year.

Each period generates one expected submission per assignee. If they don't submit by the due date, the system flags it overdue and (optionally) fires a reminder.

Drill-downs and rollups

Reports v2 ships with a global missed drill-down: see every overdue submission across every template in one place. From any report you can also drill into individual periods to see which assignees submitted on time, which were late, and which never submitted.

Per-period view toggles let you flip between "by assignee" (who submitted what) and "by field" (aggregate across submissions in a period).

Demographics

Separate from the manual reporting workflow, GCM also auto-generates a Demographics report from your member data — age distribution, gender split, member-type breakdown, geographic distribution. No setup required.

Hero links and deep-linking

Recent updates added hero links from outside /reports-v2/* so navigation from email reminders, dashboard widgets, and Slack-pasted URLs all land correctly. Members deep-linking from the dashboard land on a pre-filtered list of their assigned reports.

Permissions

Action	Admin	Shepherd	Member
Create / edit template	yes	no	no
Submit a report	yes if assigned	yes if assigned	yes if assigned
View submissions	yes	scoped to their submissions and assignees they manage	own only
View rollup analytics	yes	scoped	no

Assignment is at the template level — any role (admin, shepherd, member) can be required to submit a report, depending on what the template asks for.

Next steps

1. Report templates — define the structure.
2. Submitting a report — the assignee's side.
3. Demographics — auto-generated, no template required.