Running Rapid Response in Victoria

At Youth Alive Victoria we say that every number is a name, and every name matters to God.

Rapid Response is how that conviction gets acted on after an event. I didn't design it. What I built is the system that runs it here in Victoria. It's the machinery underneath a process that already existed, so the process holds when the numbers get real.

It exists to close one gap: the distance between a young person responding at an event and a youth pastor from their own church actually making contact.

Where it was breaking

Follow-up ran on manual steps. Collect the responses. Match each person to a church. Prepare the communication, send it, then try to reconstruct afterwards whether anyone had been contacted at all. By the time a local ministry had the details in front of them, 24 to 48 hours had gone by.

That holds at small numbers. It stops holding when responses arrive faster than they can be sorted, when the ministry someone wrote down matches nothing on file, or when several people are each half-doing the same job. Matching a round of responses to churches by hand ran to five hours. And the cost of that isn't the five hours. A young person makes a decision, and nobody ever calls.

What I built

Two pieces: a portal for the churches, and a dashboard for our staff.

The portal is deliberately thin. A youth pastor opens their link, agrees to a short statement about how the information is handled, and sees the young people connected to their ministry, with enough detail to have a pastoral conversation and one control to record that it happened. There's nothing to learn and nothing to install, and it works on a phone, because that's where a youth pastor will read it.

The dashboard is where the operational work sits. Its job is to surface the records that need a person: a ministry name that matches nothing, a missing contact pathway, a likely duplicate, a young person with no youth ministry near them at all. Everything else moves without supervision. Around that it handles church assignment, notifications and reminders, SMS conversations, and an audit trail of what went out and when.

Handling the information

The system holds personal details about young people, so how that data is treated came before anything else. Before a single record appears, the portal says what the information is for. Pastoral follow-up, nothing else, and not to be passed on.

What changed

The old process ended with a list handed over and a hope. This one closes, and it closes sooner. Response data used to reach a local ministry 24 to 48 hours after an event. It now goes out before the event has finished. The gap this was built to close is no longer measured in days.

Across 120 ministries, 80% of responses come back with follow-up recorded, and the matching that took five hours takes two.

The 20% matters as much as the 80%. Staff can see which responses have stalled while there is still time to do something about it, rather than finding out months later that nobody called.

A decision at an event should be the start of something local. This is the part that makes sure it is.