Case study 12 · Community

Daily community operations in one app.

A management application for membership, study groups, attendance, donations, events and operational reporting.

Rows of seating in a community church prepared for group activitiesCITY HARVEST / Project overview
What changed

Community teams can maintain member and group information in one place and prepare recurring reports from the same set of records.

1,000+

member records

Maintained by local teams in one application.

60+

cell and study groups

Attendance, transfers, donations and events tracked per group.

0

recurring reports compiled by hand

Weekly and management reports are prepared from current records.

01Delivery scope

What the work covered.

An internal application for membership, zones, study and cell groups, attendance, transfers, donations, events and recurring reports.

02Engineering context

The parts that had to work together.

Many local groups contributed updates to the same organisation-wide picture. The application needed practical entry screens, clear access rules and reports that could be prepared from current records.

How the parts connect3 parts · one system
  1. 01

    Local teams

    Members, groups and weekly activity

  2. 02

    Shared application

    Attendance, events and contributions

  3. 03

    Operations

    Configuration, access and reporting

Functional overview of community records and operational reporting. This diagram summarises the project scope; it is not a production architecture diagram.
03 · The challenge

Membership records, group activity and weekly reporting covered many local teams. Manual updates made it difficult to keep information current and prepare a reliable organisation-wide view.

04 · What we built

The build.

  1. 01An internal application for member registration and profiles.
  2. 02Zone, study and cell group management.
  3. 03Attendance, transfers, donations and events.
  4. 04Configurable reports for weekly activities and management review.
05 · Included in the project

The features.

  • Membership registration
  • Zone and group management
  • Attendance, donations and events
  • Operational reports and access controls
Next case studyInsurance
One system for policyholders and partners.

A customer app, public website and internal platform sharing the same policy information, with APIs for distribution partners.

  • Web platform
  • Mobile app
  • Signature service
~1 hourto configure a new insurance product
.NETAngularSQL ServerRedis
Read the GIC case study
Have a similar challenge?

Let’s look at your workflow.

If your team is working through a similar community problem, tell us about your users, existing systems and what needs to change.