A community care team handling benevolence requests from a church-management form
The church
About 5,500 people, with Planning Center connected. Ten months on CareNote.
What they set out to do
Run benevolence as a desk: a request the community can actually reach, and a written record of what was decided and given.
How it works now
Someone in the community asks for help through a Planning Center form, and an automation turns the submission into a care request. Twelve categories sort it precisely: housing, auto, food, transportation, moving and handy help, mental health and counseling, multiple needs at once, and a general check-in for everything else.
Requests are routed to a group rather than to one named person, which is why nobody becomes the bottleneck. The need goes out to the group and whoever can take it does. The staff member who owns it files a report saying what was decided and what was given, and that closes the request. Nearly every request this church has opened is now closed, with the written decision attached to it.
What it takes
Fifteen paid seats, two forms, two automations, and group routing so no one person is the bottleneck.
By the numbers
- 20
- care requests last month, every one from a form
- 415 of 425
- care requests closed
- 267
- written care reports filed
- 76
- requests routed to a group rather than a person
Is this your church?
A benevolence ministry lives or dies on two things: a request form the community can reach, and a written record of what was decided. Group routing means no single person becomes the bottleneck.
See it set up the way you would run it
Start a free trial and build this yourself, or book a demo and we will walk through the write-up closest to how your care ministry already works.
More churches like this
Other write-ups in shape 4, Form-driven intake.