It's Sunday morning. You're supposed to be leading worship. Or preaching. Or running the service. Instead, you're behind the soundboard helping a volunteer find a monitor channel.. for the third Sunday in a row.

Create a Church Media System That Puts Sunday in Your Team's Hands

Build one Notion hub that puts every role, every step, and every piece of context in front of your volunteers, so you're not the one jumping in every five minutes.

Yes, I want my Sundays back ($197)

Money-back Try-It-On-Sunday guaranteeWorks with free NotionLifetime access

“This was the step I didn't know I needed to get effective SOPs and training in the hands of my team.”

Bobby — Souls Church

The Cornerstone Worship and Media hub in Notion, linking to every Sunday tech-team role

Self-paced video course12 sessions across 3 modulesBuild your first SOP in week one

You're Supposed to Be Overseeing. Instead, You're the Help Desk.

You have a bigger job on Sundays.

Maybe you're the worship leader, on stage with a guitar. Maybe you're the production director, supposed to have eyes on the whole service.

Maybe you're the pastor, about to preach.

Maybe you're a part-time volunteer with a day job, doing this on top of everything else.

Whoever you are, you're not supposed to be running every station yourself.

But here's what your Sunday actually looks like.

You jump into ProPresenter for two minutes to fix the song order.
Then over to sound to help with a monitor mix.
Then back to cameras to remind the new operator which angle is which.
Five minutes here. Three minutes there. Ten interruptions before service even starts.

By the time the service is running, you've done five people's jobs in five-minute chunks. None of them well. And you never got to focus on your actual role.

It's not because your volunteers are bad. It's because they don't have what they need to do their job without you.

The information lives in your head.

So the only path to the answer runs through you.

One leader put it this way:

“I had basically become the walking Wikipedia page for our entire tech setup. Calling me was faster than digging through a 21-page document. Which kind of defeats the whole point.”

Sunday running through you

You're behind the soundboard, not on stage.
Every volunteer defaults to you for every question.
Five-minute interruptions across every station.
Service starts and you've already done five jobs.

Sunday running on the system

Volunteers pull up their role on a phone and find the answer.
Every step they need is documented where they look first.
You spend Sunday on your actual role.
The team can run a service when you're not there.

The Church Notion System gets you there.

Why Your Last Attempt Didn't Stick

You tried writing it down.

Maybe a Google Doc. Maybe a binder at the soundboard. Maybe a Notion page you started and abandoned.

The system was built for you, not for the volunteer who'd never used it before. Too long for the experienced person. Not detailed enough for the new one. So everyone went back to asking you.

CNS uses dual-level SOPs to fix this. Two reading depths on the same page, so the experienced volunteer and the brand-new one can both use it without coming to you. Tutorial videos live where they're needed, not buried in a playlist.

A real CNS SOP page in Notion — a numbered checklist with an embedded tutorial video below it

One SOP, two reading depths. The seasoned volunteer scans the checklist; the first-timer expands the same steps for the full walkthrough and the tutorial video.

That's the structural fix that makes documentation actually stick.

Three Steps to a Sunday Your Team Can Run

CNS walks you through the whole build, in order, so the answers move out of your head and into your team's hands.

Build the system

Set up your Notion hub and write your first dual-level SOPs using the voice-to-SOP method. Test one with a real volunteer by the end of Module 1.

Record the training

Record short, task-level tutorial videos and embed them right inside the SOPs, plus a knowledge base your volunteers can grow into.

Roll it out

Use the rollout tactics that get your team consulting the system on a real Sunday, instead of defaulting to you.

What You Get on the Other Side

A system that puts every role, every step, and every piece of context in your team's hands, so you're not the one jumping in every five minutes.

A working Notion hub for your media team. Every role, every step, every piece of context in one place.
Volunteers who pull up their phone and find the answer before pulling you into their station.
Your time on Sunday spent on your actual role.
A team that can grow without you being the bottleneck on every new volunteer's training.
Rollout tactics that get your team using the system on a real Sunday, not “someday.”
And eventually, when you need to step away for a week off, a family emergency, paternity leave, vacation, or just a Sunday off, your team already has what they need to run Sunday.

This is for you if:

You lead your church's media or production team in any capacity. Staff, volunteer, paid, part-time, full-time.
You have a primary Sunday role you can't actually focus on because you're constantly pulled into other stations.
You have between 2 and 8 volunteers, and you're tired of being the person every one of them defaults to.
You want your team to handle the small stuff on their own.
You've tried writing things down before and it never stuck.

This is not for you if:

You already have proper role documentation that works.
You want me to build it for you (this is self-paced, you do the work).
You want a quick-fix template (this is a system you build, not a template you stare at).

How Church Media Leaders Are Getting Their Sundays Back

Real words from people who have built CNS at their own churches.

“The biggest impact has been realizing I'm not alone. We all feel a sense of importance to our roles as Production Directors or Creative Leaders on a Sunday, and we have an overwhelming mental checklist during the week to ensure our Sundays run smoothly. CNS helped streamline our SOPs, troubleshooting docs, and volunteer trainings.”

Nicole — Local Church

“I have gotten ideas from everybody in this course. There's been some great ideas, and I think this has been an excellent resource for us.”

Bobby — Souls Church

“I'm learning something new every week, no matter if it's a big thing or a small thing.”

Cohort member

“The power of a video, I found to be super, super helpful. I'm on paternity leave now and it was like, 'Guys, here's how you unlock the building.' You can read all the text if you want to, but here's how you do that.”

Cohort member

“CNS gave me a place to brain-dump everything required to run a smooth Sunday, in one spot my team can access without coming to find me.”

Nicole — Local Church

I want this too ($197)

Money-back Try-It-On-Sunday guaranteeWorks with free NotionLifetime access

What's Inside: 12 Sessions, 3 Modules

A slide from a CNS course session explaining where tutorial videos live — A look inside the course sessions.

Build the System

What you walk away with: A working Notion hub with your first SOPs built using the dual-level structure that gets volunteers to actually read them. Tested with a real volunteer on a real Sunday by the end of Module 1.

The Sound / Audio SOP checklist in the CNS Notion system

Vision & Setup
Why most documentation efforts fail, and the foundational shift that fixes it. The setup decisions that determine whether the whole system gets used or ignored.
Mapping Roles & Dual-Level SOPs
The dual-level SOP framework that fixes the documentation length problem. The voice-to-SOP pipeline that gets you building faster by talking instead of typing. How to map every role on your team without missing the invisible ones.
SOP Skeletons & Notion Formatting
The three phases every Sunday SOP needs to be structured around. Notion formatting principles that keep SOPs scannable on a phone. The volunteer test that tells you whether an SOP actually works.
SOP Tutorial Videos: Why and Where
Why short task-level videos beat long polished ones every time. The placement principle that determines whether videos get watched or ignored. The length guideline that keeps you from over-producing.

Record and Organize Training

What you walk away with: A training layer your volunteers will actually use. Short SOP tutorial videos embedded right inside the SOPs, plus a knowledge base that helps volunteers grow beyond the basics.

A CNS SOP step with a tutorial video embedded right inside it

Recording Tools & Workflow
The recording stack that works for church media without overspending. The workflow that prevents you from re-recording the same thing twice. What to lock in before you ever hit record.
Editing & File Organization
The minimum editing workflow that ships videos fast, without becoming a full YouTube production. The folder structure that keeps your training library findable months later. How to organize so adding new videos stays cheap forever.
Knowledge Base Tutorials
The difference between do-this-now tutorials and deeper learning content, and why your team needs both. How topic-based training develops volunteers beyond just executing their role. The kinds of knowledge base content that pay off long-term.

Troubleshoot, Roll Out, and Make It Yours

What you walk away with: A system that doesn't just exist, but actually gets used. Troubleshooting pages so volunteers solve problems themselves. Rollout tactics that put the system in your team's hands on a real Sunday. Plus walkthroughs of real church builds so you can steal the best ideas.

The ProPresenter role page in the CNS Notion system, with tutorials and a workflow change log

Troubleshooting Workflows
The troubleshooting structure that lets volunteers solve problems without calling you. Which Sunday-morning problems are worth documenting and which aren't. The format that turns a problem into a self-serve fix.
Change Log & Update System
The single habit that keeps the system from drifting the second you get busy. Why most documentation rots, and the maintenance rhythm that prevents it. The reason I had to rebuild CNS once, and how to never repeat that.
Rollout Mechanics
The seven tactics that get your team using CNS on a real Sunday. How to put the system in front of volunteers everywhere they already look on Sunday morning. The single conversational habit that determines whether volunteers default to the system or to you.
Making It Your Own
How to make CNS reflect your specific church, not a generic media team. The categories of church-specific content most teams overlook. The simple rule for spotting what belongs in CNS and what doesn't.
Real Church Walkthroughs
Real walkthroughs of CNS pages built at other churches. The structural moves you can steal from people who've already done the work.

The Try-It-On-Sunday Guarantee

Watch Sessions 1 through 3. Build one SOP. Test it with a volunteer on Sunday.

If Sunday isn't simpler, email me. I'll refund your $197 in full and you keep the templates, the AI prompts, and the Build Guide.

I'm that confident the method works.

The Honest Part

I built CNS at my own church because I needed it.

I'm not at my church full-time. Most Sundays I'm on stage playing guitar with the worship team. I can't be everywhere at once. So I built a place that holds everything the team needs.

Then I got busy, the system drifted, volunteers started defaulting back to me, and I had to rebuild it.

You're not learning this from someone who teaches it in theory. You're learning it from someone who lives the exact problem you live, and who has built (and rebuilt) the answer.

What Other Churches Have Built

Souls Church Hub in Notion — Production Booth section with Sound, Media, Camera, and Worship team sub-pages

One built it role by role and uses the voice memo to SOP pipeline to keep adding new processes as they come up.

Local Church Workspace in Notion — Teams Portal and Staff Dashboard with training guides and role checklists

Another rolled it out to streamline volunteer trainings and troubleshooting.

Community Christian Fellowship workspace in Notion — Sunday Service Tech, Band, Other Roles, and Post Sunday Service Roles

Another church has to load-in and load-out every Sunday, so they built their pages around that reality.

A few of them have already tested the system the hard way. Stretches of paternity leave, family emergencies, weeks they couldn't be there.

One member texted his team before paternity leave and basically said,

“You guys have everything you need. I'm off this week to be with my wife and the new baby. The link to the Notion pages is below. You've got this.”

He turned his phone off. The service ran. Nothing burned down.

Their teams ran the service because everyone had what they needed.

Sunday no longer runs through one person.

Stop running between stations. Put the answers in your team's hands.

Get me out of the weeds ($197)

Money-back Try-It-On-Sunday guaranteeWorks with free NotionLifetime access

Why CNS Sticks Where Other Documentation Doesn't

Most “systems” for church media are PDFs nobody reads, or one giant Google Doc that gets outdated the day after you write it.

There's plenty of training on the tools. There's almost nothing on the system that runs the tools. CNS is built around three things you won't find anywhere else.

A dual-level SOP in Notion — a quick checklist that expands into detailed numbered steps

Documentation volunteers actually read.

Dual-level SOPs: a quick checklist for the seasoned vet and an expanded walkthrough for the first-timer, on the same page. The “too long for me, not enough for them” problem, solved.

A tutorial video embedded inside a CNS SOP, on the page where it is needed

Help shows up at the exact step they need it.

Tutorial videos live inside the SOPs, on the page where they're needed. Not buried in a YouTube playlist.

The Mobile Cam role page in the CNS Notion system

Your team has what they need without you being the help desk.

The hardest part isn't building it. It's getting your team to consult the system first, before asking you. The training teaches the habits that shift your team from “ask you first” to “check the system first,” so they have what they need without you being the help desk.

What's Included

You Get

All 12 video sessions, organized in 3 modules$497
The CNS v3 Notion template$67
CNS Build Guide PDF. Step-by-step walkthrough to follow alongside the videos$27
AI Prompts. SOP Builder (voice memo method), Troubleshooting Guide Builder, Change Log Entry Builder$37
Access to the CNS private community$47/mo

Total value$628 + $47/mo

Your price$197

One time. Yours for life. Community access included.

“This was the step I didn't know I needed to get effective SOPs and training in the hands of my team.”

Bobby — Souls Church

Build the system. Get my Sunday back ($197)

Money-back Try-It-On-Sunday guaranteeWorks with free NotionLifetime access

FAQ

I've tried documenting things before and my volunteers didn't read it. Why will this be different?

The honest answer: most documentation gets ignored because it's too long for the experienced volunteer and too thin for the new one. CNS's dual-level SOP structure fixes that. The course also covers the rollout mechanics that get volunteers to actually consult the system instead of defaulting to you.

Will this work if my volunteers don't want to use Notion?

They don't need a Notion account. You publish each role's page to the web, send them a link, they bookmark it on their phone. From their side it's a webpage. No login. No app.

How is this different from Planning Center or RealmConnect?

Those tools handle scheduling and communication. CNS is the operational manual behind the scheduling. What each role actually does on Sunday morning, step by step.

I am bivocational. I have 2 or 3 hours a week max. Is this realistic?

Yes. Most of the early sessions are 20 to 40 minutes of work that pay off immediately. You can build your first usable SOP in week one. You can build the full system over a few months in small increments.

I've never used Notion. Will I be lost?

Session 1 walks you through setting up Notion from scratch and duplicating the template. I assume zero prior experience.

Will this work for my small church?

Yes. CNS works the same way at any size. The roles you build SOPs for might be fewer, but the structure is identical. A 2-person team gets just as much value as a 10-person team.

Why is it $197?

Here's the math. The 12 video sessions across 3 modules? Cohort-style programs like this go for $497+. The CNS v3 Notion template — already structured, already formatted, ready to duplicate today? $67. The CNS Build Guide PDF that walks you through every step alongside the videos? $27. The AI prompts — SOP Builder (the voice memo method), Troubleshooting Guide Builder, Change Log Builder. The voice-memo method alone saves you weeks. $37. Plus the CNS private community where other media leads are building right now. $47/mo. That's $628 in one-time value, plus the community, for $197 one time. Yours for life.

I'm not church staff. I'm just a volunteer trying to help. Is this still for me?

Yes. A lot of the people who get the most out of CNS are part-time or volunteer leads who don't have unlimited time. The whole point of the system is to give the most-stretched-thin person their Sunday back.

Build the system. Get my Sunday back ($197)

Money-back Try-It-On-Sunday guaranteeWorks with free NotionLifetime access