CV Campus OS · Ministry Hub demo
Three things you'll actually do — fill out a Connect Card, register for an event, open a report — with enough teaching in between that the screens make sense when you get there.
Everyone in this account is invented. The sample campus is Northfield State — a ministry that does not exist, with students who do not exist. Every name is generated from word lists and every address ends in @example.com. No student from a real campus is in here, and no record belongs to a living person. The sandbox is wiped and rebuilt on a schedule, so whatever you add is temporary — and so is anything you break.
First, two words that get used wrong
A form is the thing that catches an answer. That's all it is. Name, phone, class year, “yes, text me about the retreat” — a form holds the questions and files the answers.
A page is where you put a form. And the same form can sit in four places at once: on a web page, inside an email, behind a QR code on a table tent, at the end of a text message. Four doors, one form, one list of answers.
That's the part worth slowing down on. The Connect Card a freshman scans at your table and the Connect Card on your website are not two lists to merge later — they're the same form, and the answers land in the same place, tagged with where they came from. Seventeen forms ship in this hub. None of them owns a page.
This is the one most campus ministers have backwards, and it costs them sign-ups every fall.
Where somebody goes to look around. Many doors, no hurry.
A short path built for one decision. Nothing else on it to click.
Both are real and both matter. You need the website. But when you put a retreat sign-up on your website — next to the staff page, the giving link, the podcast and the fall calendar — you've handed a distracted 19-year-old nine ways to leave. That's the leak. A funnel closes the other eight doors.
The page you're reading is a funnel page. There's nothing in the corner to click.
The spine of the whole hub
A pipeline is a line, and a stage is a place in it. The discipleship pipeline uses the C's — seven stages, and every report in this hub is a slice of them.
| Stage | What it actually means | |
|---|---|---|
| 0 | Community | A Connect Card came in. She's on the radar, and that's all you know. |
| 1 | Crowd | She showed up to something. At least one event. |
| 2 | Prospect | A real two-way spiritual conversation happened. Not a hello. |
| 3 | Congregation | She's a regular at the weekly gathering. |
| 4 | Committed | She's in a small group. |
| 5 | Core | She's leading or serving — on the leader track. |
| 6 | Commissioned | Sent. Leading, going, multiplying. |
A stage is not a label on a person. It's a description of where the relationship actually is, today, and the only person it describes is you — how far you've gotten with her. Nobody is a “Crowd student.” Somebody is a person you've met once.
Inactive is a tag, never a stage. There's no stage for drifting off, and there's no moving backwards. If a senior stops coming, she keeps the stage she earned and picks up a tag that puts her on the lapsed report. Demoting people is how a CRM starts lying to you — the day you move somebody back to Crowd, you've erased the conversation you had in March.
Do this one
Use a name you'll recognize in a list of a hundred — Test Student is fine — and any email address. Answer it the way a freshman would: fast, half the optional fields blank.
Then go looking. The contact is there inside a few seconds, and three things are true about it that nobody typed: it's carrying the tags for the form and the source it came from, it has a Campus Minister Assigned, and it is standing at Community in the discipleship pipeline. That last one is the whole point — she entered the line by answering a question, not because a staff member remembered to add her.
Sign-in details come to you by email, one seat at a time. They are never posted on a page like this one.
One event — the fall retreat — is one opportunity on a staff-side pipeline. It moves through your planning line: booked, promoted, open, closed, ran it, debriefed. That opportunity is the retreat itself, and the people who work on it are staff.
Each student who signs up gets her own record, on the registration pipeline. Ten stages, from filled out the form all the way through checked in at the door.
Because everything messy about a retreat belongs to the registration, not to the student and not to the event:
None of that is a fact about the student. It's a fact about her and this trip. Put it on her contact record and it's wrong by the next retreat. Put it on the event and you've built a spreadsheet with 60 columns.
Put it on the registration and you can run a trip with deposits, balances, waivers and medical forms and answer “who still owes me money” without opening a spreadsheet at all. Next year she registers again, and that's a new record — the old one stays exactly as it was.
Do this one
Sign up as the same test student. Use the registration page the way she would, from a phone.
Then open Opportunities and switch to the registration pipeline. Your registration is sitting in the first stage with her name on it, its own payment status, and its own set of blank paperwork fields waiting to be filled. Open the planning pipeline beside it and the event itself is one card, in one stage, where it belongs.
Two objects, two lines, one retreat.
The part most demos skip
You'd stop trusting the rest of this page if we let you find this on your own, so here it is.
Small groups aren't real objects yet. Today the hub knows that a student is in a group, because somebody typed a group name into a text field on her record. It can't hold eight groups with their own leaders, rooms and rosters — which means two spellings of “Tuesday Guys” read as two different groups. Every group report says so on the page it prints, so you always know which numbers are counted and which are inferred.
Check-in isn’t built yet. There’s no attendance spine in the product yet, so the reports that need one — lapsed students, attendance over time, one student's history — tell you attendance isn't switched on in this account instead of showing you an empty table dressed up as zero.
The sample campus models both of them the finished way: eight groups with real leaders and rosters, and a full term of attendance. So you can see the shape of the reports before the plumbing is done, and you can tell which is which, because the demo says which is which.
A director staring at fifteen identical buttons picks none of them. So each one says what question it settles and whose job it is.
Fourteen of them answer a question. The fifteenth is the one you'd print before a board meeting, and the one your supporting church would understand without you in the room.
Do this one
Start with 01 · Roster and search the test student you created ten minutes ago. She's in the master list with her stage, her days in stage, the minister assigned to her, and the tags that say where she came from.
Then open 15 · Director Summary and watch her move the count by one.
There's a switch at the top for the sample campus — Northfield State, with a full term of students, groups and attendance behind it. Flip it to see what a report looks like when a ministry has been running it since August. The sample side is marked on every page and every download, so a printed sheet can't be mistaken for a real one.