CPCana Workflow Strategy Guide

A Gentle, Step-by-Step Field Guide for Staff, Ministry Leaders, and Volunteers Chesterfield Ministry Operations Edition

Every week in a vibrant church, hundreds of moving parts must coordinate harmoniously: worship orders, pastoral visits, room reservations, curriculum printing, sacramental supplies, audio/video slides, and outreach initiatives.

When ministries rely on scattered emails, text messages, and memory:

• The "I Assumed You Had It" Void: Two people assume the other ordered the communion juice; nobody did.
• The Hallway Commitment Black Hole: A volunteer tells a pastor after Sunday service, "I can coordinate the nursery snacks," but by Tuesday morning that conversation has evaporated into the ether.
• The Thursday Afternoon Fire Drill: Staff scramble under intense stress to finish a task that could have been peacefully completed on Tuesday had they known it was waiting on them.
• Notification Paralysis: Inboxes fill with 50-reply "reply-all" chains, leaving staff overwhelmed, anxious, and checking their email during family dinner.

A well-architected workflow is not bureaucracy or corporate red tape. It is an act of pastoral stewardship. It creates a calm, transparent workroom where expectations are crystal clear, mental clutter is cleared away, and staff and volunteers can focus on loving people and making disciples.

If software terms feel clinical, remember: our platform is simply a digital model of a well-organized church workroom:

Before creating a single card, understand the architecture of how work nests inside the system:

[ ORGANIZATION / CHURCH ]
       │
       ▼
   [ PROJECTS ]       (e.g., "Sunday Bulletin Production", "Easter 2027")
          │
          ▼
      [ SECTIONS ]    (e.g., Content Intake, Layout, Proofing, Print)
             │
             ▼
         [ TASKS ]    (e.g., "Submit Order of Worship", "Proofread Hymns")
                │
                ▼
            [ SUBTASKS ] (e.g., "Call to Worship", "Confession", "Pardon")

Two things sit alongside this ladder rather than inside it:

• Teams (e.g., Worship Arts, Children's Ministry, Facilities) group people, not projects.
• Folders (e.g., "Weekly Worship", "Annual Events") are your personal way to group projects in your own sidebar. Everyone arranges their own.

The number one reason workflows become messy is that people start creating tasks before deciding what kind of container they need.

Use this simple diagnostic decision tree before creating anything:

                          ┌───────────────────────────┐
                          │ What kind of work is it?  │
                          └─────────────┬─────────────┘
                                        │
        Does it take weeks/months, involve multiple people, and have stages?
                                        │
                    ┌───────────────────┴───────────────────┐
                   YES                                     NO
                    │                                       │
                    ▼                                       ▼
             It is a PROJECT!             Does it take several steps or days
          (e.g., VBS 2027,                 to complete by one or two people?
       Weekly Bulletin, Fall Retreat)                       │
                                            ┌───────────────┴───────────────┐
                                           YES                             NO
                                            │                               │
                                            ▼                               ▼
                                     It is a TASK!                   It is a SUBTASK
                                  (e.g., "Order VBS                (e.g., "Compare 3
                                    Snack Supplies")                 grocery prices")

• Rule of Thumb:
  • If it has a deadline of 30 minutes to 2 days for one person → Task.
  • If it groups several tasks that share the same phase → Section.
  • If it has its own budget, timeline, team, or recurring cycle → Project.

Every church project falls into one of two fundamental categories. Mixing them up causes confusion:

┌──────────────────────────────────────────────┬──────────────────────────────────────────────┐
│ TYPE A: ONGOING CYCLES (Operations)          │ TYPE B: TARGET MISSIONS (Milestone Events)   │
├──────────────────────────────────────────────┼──────────────────────────────────────────────┤
│ • Repeats continuously (Weekly or Monthly)   │ • Has a clear beginning and fixed end date   │
│ • Tasks reset, recur, or move across stages  │ • Once the event is over, the work is done   │
│                                              │   (CPCana has no project archive yet, so leave  │
│                                              │   it as a reference or ask an admin to       │
│                                              │   delete it)                                 │
│ • Examples:                                  │ • Examples:                                  │
│   - Weekly Bulletin Production               │   - Vacation Bible School 2027               │
│   - Sanctuary Facilities Upkeep              │   - Christmas Eve Candlelight Concert        │
│   - Monthly Communion Preparation            │   - Church Sanctuary AV Upgrade              │
└──────────────────────────────────────────────┴──────────────────────────────────────────────┘

In a church office, work is often interconnected. A single task often matters to two different ministry teams:

• Example: "Clean and Prepare Fellowship Hall for 60 People on Friday Night".
  • The Youth Ministry needs to know it's happening for their game night.
  • The Facilities Team needs it on their cleaning work order list.

The Old Way: Emailing both teams, or typing the task twice into two different spreadsheets (which quickly get out of sync).

The Architectural Way (Multi-Homing): In our platform, you can attach one single task card to two projects simultaneously.

• When the custodian checks it off in the Facilities Work Orders project, it instantly updates to complete inside the Youth Ministry project!
• There is only one source of truth. No duplicated work, no conflicting notes.

Not every piece of church information belongs on a shared project task board:

• Child Protection & Background Checks: Never put criminal background check results, abuse awareness certificates, or notes about sensitive volunteer vetting inside a public task card or comment thread. These belong exclusively in the dedicated Child Protection Module (/admin/child-protection), where records are protected by strict administrative role permissions and confidential Compliance Shares.
• Onboarding Budgets & Equipment Costs: Equipment procurement costs (Capex) and recurring software seats (Opex) belong in the dedicated Onboarding Module (/admin/onboarding), preserving financial confidentiality for staff and intern hires while keeping project boards focused on execution.

Every new project starts with three columns: To Do, In Progress, and Done.

While that works for a solo programmer, it almost always fails in a collaborative church team. Why? Because "In Progress" becomes a graveyard. Ten people dump cards into "In Progress," and nobody knows who is waiting on whom, where the bottleneck is, or who has the ball.

Choose the stage archetype that matches how work naturally flows through your ministry:

1. The Assembly Line Pipeline (Best for Creative & Media Work)

Tasks move sequentially from left to right through specialized stations.

• Example (The Weekly Bulletin): Content Intake → Admin Layout → Editorial Review → Print & Folding → Digital Publish
• Why it works: You immediately see bottlenecks. If eight cards are piling up in "Editorial Review," the team knows exactly where to help.

2. The Functional Category Board (Best for Facilities & Operations)

Tasks are grouped by room, team, or department rather than time. Nothing travels across a board like this: each lane is a standing area of responsibility. Because the lanes aren't named To Do, In Progress, or Done, moving a card between them doesn't change its status.

• Example (Church Campus Maintenance): Sanctuary | Classrooms & Nursery | Fellowship Hall | Grounds & Parking | HVAC / Plumbing

3. The Weekly Calendar Rhythm (Best for Worship Planning)

Tasks are organized by weekly service timing or recurring production cadences.

• Example (Worship Order Planning): Monday: Scripture & Themes | Wednesday: Music & Slides | Friday: Final Proof & Print | Sunday Morning Live

4. The Milestone Roadmap (Best for Major Events)

Tasks are grouped by chronological countdown intervals.

• Example (Fall Festival or VBS): 3 Months Out | 1 Month Out | 2 Weeks Out | Event Week | Post-Event Teardown & Thank-Yous

The secret to smooth transitions between stages is establishing gatekeeper rules. CPCana doesn't check these for you, so put them on the card as a subtask checklist where everyone can see them:

┌──────────────────────────────────────────────────────────────────────────────┐
│ STAGE GATEKEEPER SPECIFICATION                                               │
├──────────────────────────────────────────────────────────────────────────────┤
│ STAGE: "EDITORIAL REVIEW"                                                    │
│                                                                              │
│ ENTRY CRITERIA: When can a card enter this stage?                            │
│ [✔] Master layout document is completely populated.                          │
│ [✔] Draft PDF is generated and attached to the card.                         │
│ [✔] Upstream data entry coordinator has checked off their layout subtasks.   │
│                                                                              │
│ EXIT CRITERIA: When can a card leave this stage?                             │
│ [✔] Proofreader has reviewed for typos, proper names, and scripture citations│
│ [✔] Worship Director has confirmed song keys and hymn numbers.               │
│ [✔] Card is moved to the "Ready to Print" column.                            │
└──────────────────────────────────────────────────────────────────────────────┘

When designing ministry workflows involving minors (Nursery, Sunday School, VBS, Youth Group, or Children's Choir), safety cannot be left to informal assumptions:

In your stage architecture:

1. Intake / Application Stage: Gather volunteer interest, contact details, and ministry preferences.
2. Safety Vetting Gatekeeper: Before moving a candidate onto a classroom roster, check that their DocuSign agreement, MinistrySafe training, and background check show as current in /admin/child-protection. CPCana doesn't block the move for you, so make this check part of the stage.
3. Active Serving Stage: Only volunteers with active compliance are slotted into schedules, rosters, and tasks. If a worker's status turns 🔴 EXPIRED, CPCana doesn't pull them off anything automatically. The weekly renewal check files a review task, and the ministry lead should keep them off the schedule until they renew.

A great workflow is only as good as the cards within it. When a task is vague, volunteers hesitate, staff get confused, and deadlines slip.

Every task card created in the system must answer five questions:

┌─────────────────────────────────────────────────────────────────────────────┐
│ 1. TITLE:        What physical action must be taken? (Action-Verb Rule)     │
│ 2. ASSIGNEE:     Who holds the baton right now? (The Single Baton Rule)     │
│ 3. DUE DATE:     What day is this needed? (If the time matters, put it in   │
│                  the title or description; the due date is a day only.)     │
│ 4. DESCRIPTION:  What are the instructions, inputs, and links?              │
│ 5. DELIVERABLE:  What attached file or proof shows this is finished?        │
└─────────────────────────────────────────────────────────────────────────────┘

Compare these real-world church task cards:

• ❌ Mystery Card: "Baptisms"

  • The problem: What does this mean? Are we scheduling a baptism? Ordering towels? Printing a certificate? Counseling parents? Filling the font?

• ✅ Ironclad Card: "Submit Approved Baptism Names & Family Details to Admin for Bulletin"

  • Why it works: The action, the deliverable, and the recipient are clear in five words.

• ❌ Mystery Card: "Sound Board"

  • The problem: Who is doing what, and when?

• ✅ Ironclad Card: "Clean & Label Wireless Microphone Packs in Sound Booth for Sunday"

A task should never be assigned to multiple people.

When a card is assigned to two or three people:

• Person A thinks Person B is handling it.
• Person B thinks Person A has it covered.
• Person C assumes they were only looped in as a courtesy.
• The work never gets done.

In churches, responsibilities frequently rotate from week to week (preaching pastors, liturgists, elder prayer leaders, communion preparers).

To handle this cleanly in reusable project templates:

1. In the template, set the task description to note the qualified pool:
   • Task: "Prepare and Deliver Sunday Sermon"
   • Description: Role Pool: Hugh, Owen, Tony, Adam D, Justin H, CJ, Mitch, Guest.
2. During the weekly kickoff or scheduling pass, the project manager connects the specific person serving that week.

The number one reason staff and volunteers abandon church software is Notification Fatigue.

If a volunteer proofreader receives ten automated system notifications on Monday morning for work that cannot possibly be proofed until Thursday afternoon, they will quickly stop reading emails from the platform. When notifications are ignored, the system fails.

Think of an Olympic relay race. The runner on leg two does not start sprinting while the first runner is still in the starting blocks. They wait quietly in their zone until the first runner approaches.

1. The "Locked Until Ready" Pattern

Instead of handing everyone every task on Monday morning:

• Give each downstream task a blocked by dependency on the task that has to finish first.
• CPCana keeps the downstream task locked until its blockers are marked Done, and holds back its assignment notification while it's locked.
• The moment the last blocker is Done, the task unlocks and its assignee gets one timely notification right when their work can actually start. No automation rule needed.

2. Just-in-Time Task Creation

Why populate a board with 30 tasks at the start of the week?

• Keep the board clean.
• When the layout draft is marked Done, a Create task automation adds the proofreading task to the Review section.
• Reviewers only see work when work actually exists.

3. Personal Notification Hygiene

Every user should configure their personal profile (/settings → Notifications):

• Instant email notifications: Turn off the ones you don't need (such as Task assigned to you and Added to a project). Leave Task unlocked on so you hear when it's your turn.
• Direct @Mentions: Keep ON. (Ordinary comments never send instant email; they wait for the digest by design.)
• Email Digest: Set to Daily (the default).
  • Result: Instead of 18 individual emails throughout the day, the user receives one morning email, around 8–9 AM Central, showing everything due today.

The 1-Click Email Unsubscribe Relief Valve

What if a volunteer or busy staff member feels their inbox is getting cluttered, but lacks the technical confidence to navigate settings menus?

• Every notification email from CPCana has an "Unsubscribe from all emails" link at the bottom, and Gmail and Apple Mail show their own Unsubscribe button at the top.
• Either one turns off all of that person's CPCana emails, including the digest, without requiring them to log in, remember a password, or contact an administrator. In-app notifications keep working, and they can turn individual emails back on any time under Settings → Notifications.
• As a workflow architect, teach this to your ministry leads as a vital pastoral safety valve: volunteers never need to feel trapped by system notices.

The greatest threat to peaceful church workflows is false urgency.

If an Administrative Coordinator receives a notification on Tuesday morning saying "Due Today: Typeset Sunday Bulletin" when the preaching pastor has not yet submitted the sermon title or scripture texts, two damaging things happen:

1. Spike Anxiety: The administrator experiences unnecessary stress for work they are physically blocked from starting.
2. Alert Blindness: Over time, staff become numb to system notifications, eventually ignoring real, critical deadlines.

To uphold the Relay Baton Principle, the platform enforces Locked-Task Notification Suppression:

┌─────────────────────────────────────────────────────────────────────────────────────────────┐
│ THE 4 LAWS OF LOCKED-TASK NOTIFICATION SUPPRESSION                                          │
├─────────────────────────────────────────────────────────────────────────────────────────────┤
│ 1. NO BATON UNTIL IT'S YOURS:                                                               │
│    Assigning someone to a locked task sends NO "task assigned" notice. Their name stays on  │
│    the card, but their inbox stays quiet. Deadline reminders that do arrive say so plainly: │
│    "Due today: 'Typeset Bulletin' (currently waiting on 'Submit Sermon Info')."             │
│                                                                                             │
│ 2. URGENCY ESCALATES ON THE BLOCKER, NOT THE BLOCKED:                                       │
│    When a blocking task is due tomorrow, due today, or overdue, its own reminder also names │
│    who is waiting on it (the blocker needs a due date for this):                            │
│    "⚠️ Heads up: Lynn, Heather is waiting on this completion."                               │
│                                                                                             │
│ 3. THE BLOCKER DELAY WARNING & ON-DEMAND NUDGE:                                             │
│    Each morning a prerequisite is overdue, downstream assignees get a Dependency Alert:     │
│    "Dependency Alert: Prerequisite 'Submit Sermon Info' is overdue, blocking your task      │
│    'Typeset Bulletin'."                                                                     │
│    Any time a task is locked, a [Nudge assignee] button lets you send the blocker's owner   │
│    a polite reminder (once a day).                                                          │
│                                                                                             │
│ 4. THE BATON HANDOFF (TASK UNLOCKED):                                                       │
│    The second the final prerequisite is checked off, the system automatically fires:        │
│    "Task unlocked: 'Admin Layout & Typesetting' has been unlocked in Weekly Bulletin."      │
└─────────────────────────────────────────────────────────────────────────────────────────────┘

What the Team Sees: Blocker vs. Downstream Assignee

(Reminders go out once each morning, and a due date is a whole day, so a task counts as overdue starting the morning after its due date.)

1. The One-Click Dependency Nudge
   When a prerequisite is overdue, click Nudge assignee on the blocked task detail modal. The system sends a polite, pre-written alert directly to the blocker's assignee: "Heather is waiting on "Submit Sermon Title & Scripture" to start "Typeset Sunday Bulletin"." It arrives with the due-date and dependency reminders, by email under the subject Dependency nudge: … unless they've turned those emails off. No separate text message or awkward email required. (You can nudge each person once a day.)

2. Reassigning from the Role Pool
   If an assigned leader or volunteer falls ill or is traveling, open the task detail panel, check the designated alternates listed in the description's Role Pool, and reassign the task directly to the alternate. Deadlines, checklist progress, and downstream links all stay intact.

3. Clearing or Waiving a Blocker
   If a planned element is canceled or not needed this week, a ministry lead can simply remove the dependency link in the task detail panel (or mark the blocker Done with a comment noting it was skipped). Marking the blocker Done unlocks every task that was only waiting on it; removing one link unlocks just that task (if nothing else is blocking it).

Automations are digital servants that handle repetitive administrative housekeeping. When properly configured, they save dozens of hours every month. When poorly configured, they cause digital chaos.

Every automation follows one simple rule:

WHEN [something happens to one task] → THEN [do one thing to a task]

┌──────────────────────────────────────────────┬────────────────────────────────────────────────────────┐
│ TRIGGER ("When this happens to the task...") │ ACTION ("Then do this automatically...")               │
├──────────────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ Its status becomes To Do / In Progress / Done│ Set a task's status                                    │
│ Its assignee changes                         │ Assign a task (a chosen person, or the same people)    │
│ Its due date is N days away (checked daily)  │ Move a task to another section                         │
│                                              │ Create a new task in a section                         │
└──────────────────────────────────────────────┴────────────────────────────────────────────────────────┘

Every rule watches one specific task. There are no extra conditions ("only if...") and no "when all tasks in a stage are done" trigger, so design around single, clear handoffs.

Sin 1: Rules That Undo Each Other

• The Error: Rule A says "When 'Proof' is Done, set 'Layout' to In Progress"; Rule B says "When 'Layout' is In Progress, set 'Proof' to To Do."
• The Disaster: Finishing the proof reopens it, and the team can never close the loop.
• The Remedy: CPCana refuses a rule that changes what it watches on the same task, and it stops any chain of rules after 5 steps, but it can't see two separate rules working against each other. Before adding a rule, read the project's other rules (the Print runbook sheet lists them all on one page).

Sin 2: The "Premature Evacuation" Trap

• The Error: Triggering a big next step from the first task in a stage to finish.
• The Disaster: The bulletin moves to the print shop while the sermon title and children's announcements are still blank!
• The Remedy: CPCana rules can't wait for "every task in the stage." Trigger on the last task in the stage instead (for bulletins, the final proofread), or use blocked by dependencies so the next task stays locked until everything it needs is Done.

Sin 3: Hard-Coded Calendar Dates in Blueprints

• The Error: Putting "Due October 18, 2026" in a task's title or description inside a reusable blueprint.
• The Disaster: In 2027, every project created from that blueprint carries last year's date.
• The Remedy: Keep dates out of blueprints. Apply the blueprint, then set due dates on the project's tasks.

Sin 4: Due-Date Rules on Work That Gets Reopened

• The Reality: CPCana skips a due-date rule while its task is Done, but the rule wakes up again if the task is reopened or repeats.
• The Trap: A watchdog you meant for one season quietly fires again next time the task comes around.
• The Remedy: Pause or delete one-time due-date rules once the work is finished. Check rule shows when a rule is being skipped because its task is Done.

Sin 5: Daily Scheduler Time Lag

• The Reality: Due-date rules are checked once a day, in the morning, not continuously.
• The Trap: Expecting a "due today" rule to fire at the exact moment something becomes due.
• The Remedy: Use status changes ("When marked Done ➔ assign the next task") for real-time handoffs; save due-date triggers for multi-day warnings.

Build rules from the project's Workflows & Automations ➔ Automation rules page (/projects/[id]/automations). Keep each rule simple, single-purpose, and tied to a clear human handoff. These four recipes are built into the new-rule window under Quick Recipes; each one fills in the form, and you pick the tasks.

Recipe 1: The Relay Baton (Done ➔ Hand Off the Next Task)

• Trigger: When a task is marked Done
• Action: Assign the next task to a person you choose (CPCana notifies them)
• Why it works: Eliminates hallway texts like "Hey, did you finish your part yet?" The next volunteer gets tapped on the shoulder exactly when the work is theirs.

Recipe 2: The Editorial Review Gate (Draft Done ➔ Review Starts)

• Trigger: When the draft task is marked Done
• Action: Mark its review task In Progress
• Why it works: Reviewers see the review go live the moment there is something to review, not before.

Recipe 3: The Due Date Watchdog (2 Days Out ➔ Urgent)

• Trigger: When a task is 2 days from its due date
• Action: Move that same task to your Urgent section
• Why it works: Work that's running close surfaces on the board by itself, without anyone combing through due dates.

Recipe 4: The Follow-Up Generator (Done ➔ Debrief Task)

• Trigger: When a task (often the event itself) is marked Done
• Action: Create a "Debrief & Review" task in your Review section
• Why it works: The lessons from Sunday's event get captured while they're fresh, instead of being forgotten by Tuesday.

Once your team is comfortable with basic cards and checklists, these advanced tools unlock massive time savings.

Standard task managers only give you a title and a description. But church work has specific details:

• Which room is needed?
• How many childcare workers are required?
• Is this funded by the general budget or a designated gift?
• Is communion gluten-free?

By clicking Manage Fields on any project, you can add custom columns:

• Text: Short free-form notes (e.g., Room Setup: Round tables, 8 per table).
• Dropdown: Select from a clean list (e.g., Ministry Area: Youth / Children / Adult / Worship).
• Checkbox: Boolean flags (e.g., Gluten-Free Communion Confirmed? [X]).
• Number: Quantities (e.g., Copies to Print: 450).
• Date: Specific event milestones (e.g., Rehearsal Date).

Every church office receives random requests from well-meaning members: "Can you put this in the bulletin?", "Can our committee reserve room 204 on Thursday?"

When these arrive via text, phone call, or email, they get lost.

The Solution: Project Intake Forms (/projects/[id]/forms):

1. Create a public form with required questions (Name, Event Date, Announcement Text, Room Needed).
2. CPCana gives the form a public link on its own site, named after the form (e.g., …/forms/bulletin-announcement).
3. Share the link with your congregation and committee chairs.
4. When someone submits the form:
   • A task card is automatically created in the column you picked when you set up the form (for example, "Intake").
   • The card is titled with the form's name and the sender's name (for example, Bulletin Announcement — Mary Jones), so it's easy to spot on the board.
   • All form answers are neatly listed in the description, along with who sent it.
   • If you chose a default assignee, it's assigned to them automatically, and they get a notification.
   • Zero re-typing or copy-pasting required!

Not every church contributor needs a staff username and password.

• Example: A guest preacher, an outside florist, a volunteer bringing potato salad, or a traveling missionary.

How to Use Guest Access (🔗 Share with guest):

1. Open the specific task card.
2. Click Share with guest, then + New guest link, then Copy.
3. Text or email the link to the guest.
4. When the guest clicks the link, their browser opens only that single task.
   • No login, no password, no account setup.
   • They can read the instructions, see the comments, and add their own. (Guests can't see attached files, so paste a share link to any file they need into the description.)
   • They cannot see the rest of your church database or other projects.
   • When they're finished, you can revoke the link with one click.

When setting a task to repeat (This task repeats), CPCana manages the lifecycle through an In-Place Reset Engine rather than creating duplicate task cards:

• Single Enduring Card: A repeating task stays as one card with one permanent ID and URL. When its cycle triggers, it resets directly in place. All comments, discussion threads, attached files (like bulletin proof PDFs), and activity history remain intact forever.
• Return to Base To Do: The card moves automatically back to the project's designated ★ Base To Do column (or default first To Do column), and its status resets to TODO.
• Subtask Checklist Reset: Any subtasks nested under the task are automatically unchecked and reset to TODO in the base column, ready for the upcoming week or cycle.
• Intelligent Due Date Clamping: Due dates roll forward by the repetition interval. If a task was overdue across cycles before completion, the date clamping engine advances the due date until it reaches or exceeds the target cycle date—so it never wakes up overdue!

Choose the right recurrence style for the job:

┌──────────────────────────────────────────────┬──────────────────────────────────────────────┐
│ STYLE A: "RESET ON A SCHEDULE"               │ STYLE B: "RESET AFTER IT'S DONE"             │
├──────────────────────────────────────────────┼──────────────────────────────────────────────┤
│ • Resets overnight on its repeat day         │ • Next reset timer begins ONLY after the     │
│   (around 1–2 AM Central),                   │   current task is marked Done                │
│   finished or not                            │                                              │
│ • Perfect for:                               │ • Perfect for:                               │
│   - Weekly Sunday Bulletin production steps  │   - Replacing HVAC filters every 90 days     │
│   - Weekly microphone battery rotation       │   - Deep-cleaning the nursery toy bins       │
│   - Monthly communion setup                  │   - Auditing keycard door access logs        │
└──────────────────────────────────────────────┴──────────────────────────────────────────────┘

Under /settings → Notifications → Email digest, staff and ministry leaders can choose Off, Daily, or Weekly, whichever rhythm fits their role:

┌──────────────────────────────────────────────┬──────────────────────────────────────────────┐
│ DAILY DIGEST (the default)                   │ WEEKLY DIGEST (every 7 days)                 │
├──────────────────────────────────────────────┼──────────────────────────────────────────────┤
│ • AUDIENCE: Active weekday staff, designers, │ • AUDIENCE: Preaching pastors, session       │
│   and administrative coordinators.           │   elders, and ministry committee chairs.     │
│ • CONTENT: Overdue, due today, due in the    │ • CONTENT: The same contents, once a week.   │
│   next 7 days, anything still unread in      │                                              │
│   your Inbox (mentions, unlocks, comments;   │                                              │
│   up to 20), and (for managers and admins)   │                                              │
│   a Project Summary.                         │                                              │
│ • RHYTHM: Every morning, around 8–9 AM       │ • RHYTHM: Seven days after the last digest,  │
│   Central.                                   │   not pinned to a particular weekday.        │
└──────────────────────────────────────────────┴──────────────────────────────────────────────┘

The bulletin is a textbook assembly line: each stage has one owner group, one cutoff, and one deliverable the next stage needs. A finished stage only unlocks the next one when the next stage's task is marked Blocked by it, and a cutoff time belongs in the task's title or description, since a due date is a whole day.

┌─────────────────────────────────────────────────────────────────────────────────────────────┐
│ MASTER BULLETIN TIMELINE (Chesterfield Presbyterian Church)                                  │
├─────────────────────────────────────────────────────────────────────────────────────────────┤
│ MON 12:00 PM │ Worship Planning & Preaching Theme Selected                                 │
│ TUE 12:00 PM │ Content Deadline: Sermon Scripture, Order of Worship, Hymn Numbers & Sacraments │
│ WED  5:00 PM │ Admin Layout & Data Entry Completed (Saturday & Sunday Versions)            │
│ THU 11:00 AM │ Draft PDF Proofs Uploaded to Stage 3                                         │
│ THU  2:00 PM │ Audit Pass 1 Completed: Musical & Service Flow (Heather)                     │
│ THU  4:00 PM │ Audit Pass 2 Completed: Full Editorial & Print Proof (Lynn)                 │
│ FRI  9:00 AM │ High-Speed Printing, Folding & Staging for Ushers (Admin/Facilities)         │
│ FRI  2:00 PM │ Digital Distribution: Church App & Website Publishing (Bliz/Web)            │
└─────────────────────────────────────────────────────────────────────────────────────────────┘

The Weekly Bulletin Section Blueprint:

1. Section 1: Communications & Announcements
   • Schedule Announcements (Tony, Lynn, Bliz)
   • Obtain / Create Graphic Slides (Tony, Lynn)
2. Section 2: Worship Order & Elements
   • Order of Worship Text (Call to Worship, Confession, Assurance, Songs)
3. Section 3: Preacher & Word
   • Sermon Title, Scripture, and Reflection Questions (Preacher Pool)
   • Designate Benediction Leader
4. Section 4: Sacraments (Monthly / As Needed)
   • Lord’s Supper: Session Approval & Elements Check
   • Baptisms: Candidate Legal Names & Prayer Leader
5. Section 5: Administrative Layout
   • Enter Data into Master InDesign / Publisher Template
   • Export PDF Proofs for Review
6. Section 6: Quality Audit & Reviews
   • Pass 1: Heather Worship Audit
   • Pass 2: Lynn Editorial Proof
7. Section 7: Production & Print
   • Print & Fold Sanctuary Bulletins
   • Print Children's Bulletins (CBC)

For major one-off events, design by Milestone Stages:

• Stage 1: 3 Months Prior (Strategy & Budget): Vision approval, budget approval, theme selection, lead volunteer recruitment.
• Stage 2: 6 Weeks Prior (Promotion & Registration): Intake form launched, banner graphics hung, promotional video played in service.
• Stage 3: 2 Weeks Prior (Logistics & Supply Audits): Supplies ordered to par levels, background checks completed, room reservations verified.
• Stage 4: Event Week (Execution): Room setup, sound checks, volunteer check-in rosters, emergency contact clipboards.
• Stage 5: Post-Event (Stewardship): Clean-up, thank-you notes mailed to volunteers, budget reconciliation, follow-up with visiting families.

Hospitality work is a category board crossed with a short pipeline: each new family enters at Intake and moves through a fixed sequence of welcomes, while standing lanes hold the recurring weekly duties.

[ Guest Card Received ] ──► [ 48-Hour Thank-You ] ──► [ Pastoral Call ] ──► [ Newcomers’ Lunch Invite ] ──► [ Connected to a Group ]

Churches run on weekly rhythms. Every single week, the same operational milestones recur: the Sunday bulletin must be assembled and printed, facilities staged, communion elements stocked, and audio/video gear checked.

Before the In-Place Reset Engine, recurring church projects faced two problems:

1. The Duplicate Explosion: Spawning new card copies every week littered the database with hundreds of abandoned duplicate cards, broke comment history threads, and buried attachments.
2. The Manual Scramble: Resetting checkmarks and dragging cards back to "To Do" by hand every Monday morning was tedious and error-prone.

CPCana solves this permanently with In-Place Resetting Tasks and Designated Base To Do Columns:

Step 1: Designate the "★ Base To Do" Column

In any recurring project (like the Weekly Bulletin Production board):

• Open the Kanban board or column settings.
• Click the star icon (☆) on the intake column (e.g. 1. To Do / Content Intake) to set it as the ★ Base To Do column.
• This tells CPCana: "Whenever any repeating task in this project resets, bring it back here."

Step 2: Configure Weekly Repeating Tasks

Set each milestone task (e.g., "Assemble Bulletin Proof", "Audio & Mic Setup", "Sanctuary Flowers") to repeat:

• Choose Reset on a schedule, repeat every 1 week, and set Next reset to the coming Monday. It will reset every Monday after that.
• Assign an owner and set the due date.
• Add subtasks for itemized checklists (e.g., under "Assemble Bulletin": Call to Worship text, Scripture reading, Hymn numbers, Session announcements).

Step 3: The Natural Weekly Flow

• Monday–Friday: Cards move across the board from ★ Base To Do through In Progress and Review/Proofing to Done. Subtasks are checked off. Proof PDFs and notes are posted directly in the task comments.
• The Weekend: Finished cards sit peacefully in Done.
• Overnight into Monday (around 1–2 AM Central): CPCana's recurrence engine evaluates active recurring tasks:
  1. The card's status automatically resets to TODO.
  2. The card moves back to the designated ★ Base To Do column.
  3. All nested subtasks are unchecked and restored to TODO in the base column.
  4. The due date advances to the next week (with intelligent clamping so overdue tasks never wake up overdue).
  5. The task ID, comments, attachments, and full audit history remain intact.

Staff arrive Monday morning to a clean, fresh board with zero duplicate cards and full historical context preserved!

Bringing on a new staff director, associate pastor, or key ministry volunteer requires coordinating across administration, facilities, technology, finance, and pastoral leadership. Trying to run this out of a casual task list leads to delayed keys, unconfigured email accounts, and unexpected hardware bills.

CPCana provides the dedicated Onboarding Module (/admin/onboarding) to solve this cleanly using Role Blueprints.

Step 1: Design Reusable Role Blueprints Once

Under /admin/onboarding/templates, administrators set up a blueprint for each role (Pastoral Staff, Admin & Office, Facilities, IT & Media, Worship & Music, Children & Youth, Key Volunteer, Other). Each blueprint sorts its checklist into four clear operational tracks:

┌──────────────────────────────────────┬──────────────────────────────────────┐
│ Track 1: Paperwork & Compliance      │ Track 2: Hardware & Equipment        │
│ • Direct deposit & tax forms         │ • Staff laptop / tablet              │
│ • Staff handbook sign-off            │ • Office desk & chair                │
│ • Child protection vetting           │                                      │
│ • 1-on-1 lunch with Sr. Pastor       │                                      │
│ • 30-day ministry check-in           │                                      │
├──────────────────────────────────────┼──────────────────────────────────────┤
│ Track 3: Software & Cloud Licenses   │ Track 4: Facility & Physical Access  │
│ • Church email (@church.org)         │ • Sanctuary & office brass keys      │
│ • CPCana task manager account           │ • Security RFID door fob             │
│ • Planning Center / ChMS login       │ • Campus facilities tour             │
└──────────────────────────────────────┴──────────────────────────────────────┘

(Shadowing and check-in steps like the lunch and the 30-day check-in go under Paperwork & Compliance; keys and door fobs go under Facility & Physical Access.)

Step 2: Launch the Case with Pre-Calculated Capex & Opex

When a hire is made, launch a new case (/admin/onboarding/new). Pick one or more role blueprints and CPCana copies in all their checklist items. On the same screen, choose who owns each track (for example, Facilities for keys, IT for software, the office for paperwork); those items then show up in each person's My Tasks. Items don't get due dates, so set expectations against the hire's start date yourself.

Crucially, the module calculates the true financial investment before Day 1:

• Capex Total: Upfront hardware purchases (e.g., $1,200 laptop + $25 key fob).
• Monthly Opex Total: Recurring monthly software seats (e.g., $15 email + $35 ChMS seat).

Admins can see the full cost before Day 1 without holding up the candidate's welcome. (The Onboarding Module is open to admins only.)

Step 3: Run the 30-Day Transition Roster

The supervising admin watches the candidate's progress bar on the onboarding roster (/admin/onboarding). As each department hands off their baton, the candidate moves smoothly from preparation to active, joyful ministry.

Like an automobile, every workflow system needs periodic maintenance to stay smooth and responsive.

Once a month, the church administrator or ministry lead should spend five minutes checking:

1. The Stale Task Sweep: Are there tasks marked "In Progress" with due dates in the past? Reassign, reschedule, or complete them.
2. The "Mystery Card" Check: Are any tasks titled with single words like "Flowers" or "Music"? Rename them with action verbs.
3. The Unassigned Card Sweep: Are there orphan tasks with no assignee? Give them an owner.
4. The Template Review: Have personnel changed? Update role pools in task descriptions, owners of repeating tasks, intake-form default assignees, and automation rules that assign people, so work doesn't get routed to former staff.
5. The Safety Net Cleanout: Admins, glance at All Trash (/admin/trash) to verify nothing was deleted by mistake. Everyone else, check your own Trash (/trash).

┌──────────────────────────────────────┬────────────────────────────────────────────────────────┐
│ WHAT HAPPENED?                       │ HOW TO FIX IT IN 30 SECONDS                            │
├──────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ "My task disappeared from the        │ 1. Check the Status filter at the top. My Tasks        │
│  screen!"                            │    hides Done tasks unless you add "Done".             │
│                                      │ 2. Check "Trash" in the sidebar (`/trash`). It         │
│                                      │    shows tasks you deleted; if someone else deleted    │
│                                      │    it, ask an admin to look in All Trash.              │
│                                      │ 3. Press Ctrl+K (Mac: ⌘+K) and type the card title.    │
├──────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ "I made a mess in Grid View /        │ Press Ctrl+Z (Mac: ⌘+Z) immediately. Just like Excel,  │
│  pasted across the wrong rows!"      │ this instantly undos your last bulk edit.              │
├──────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ "I'm overwhelmed by email            │ Go to Settings (bottom of the left sidebar) ->         │
│  notifications every day!"           │ Notifications. Turn off the instant emails you         │
│                                      │ don't need and set Email digest to Daily. It           │
│                                      │ arrives each morning around 8–9 AM Central.            │
├──────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ "The screen looks frozen or won't    │ Click browser Reload (F5 on Windows, ⌘+R on Mac)       │
│  show my colleague's new update."    │ to fetch a fresh sync from the database.               │
├──────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ "A task is assigned to the wrong     │ Open the task and change it under "Assignees",         │
│  person."                            │ or edit the Assignee cell in Grid View.                │
├──────────────────────────────────────┼────────────────────────────────────────────────────────┤
│ "I accidentally deleted a task!"     │ Don't panic! Go to sidebar -> "Trash", find it, and    │
│                                      │ click "Restore". (Deleting a project or column is      │
│                                      │ permanent, so CPCana asks first. If a column was          │
│                                      │ deleted, its tasks were moved to another column,       │
│                                      │ not lost.)                                             │
└──────────────────────────────────────┴────────────────────────────────────────────────────────┘

• Action-Verb Title: Naming a task by the actual physical action required (e.g., "Order 500 Communion Cups" instead of "Cups").
• Assignee: The single person holding the baton who is personally responsible for completing the task.
• Automation: A background rule that carries out actions automatically (e.g., changing a status, assigning someone, moving a card, or creating a follow-up task) when a trigger occurs.
• Board View: A visual board of columns (stages) where tasks appear as cards that move from left to right as work progresses.
• Capex Total: Capital Expenditures: one-time upfront hardware and equipment purchases (laptops, key fobs, brass keys) tracked in an onboarding case.
• Child Protection Module: The dedicated compliance registry (/admin/child-protection) tracking background checks, MinistrySafe certifications, and signed policies for youth and children workers.
• Compliance Gatekeeper: A stage rule your team follows: check that a volunteer's child protection status is current before assigning them work in a minor-serving ministry. CPCana doesn't check this automatically.
• Compliance Share: Access an admin grants to a person or team to view (or view and edit) all child protection records without full Admin privileges.
• Condition: A team agreement about when work can start (an entry condition) or be called finished (an exit condition). CPCana doesn't enforce these, so write them into the task as a subtask checklist. The one gate CPCana does enforce is Blocked by: a task can't leave To Do until its blockers are Done.
• Custom Field: A custom metadata column added to a project (e.g., Room Number, Dietary Restrictions, Printing Count).
• Digest Email: A consolidated morning summary email that bundles all of your day's tasks into one message, eliminating all-day inbox pinging.
• Grid View: A high-speed spreadsheet view within a project for editing titles, tags, assignees, priorities, statuses, and due dates across dozens of tasks at once.
• Intake Form: A public, no-login webpage that lets church members or committees submit requests directly into a project as structured tasks.
• Base To Do Column: The project column you mark with a ★, where repeating tasks return when they reset, and where a task goes when it's set back to To Do.
• In-Place Recurrence: The engine where repeating tasks and their subtasks reset status and advance due dates directly on the board without spawning duplicate cards.
• Locked-Task Suppression: Withholding the "task assigned" notice for a task whose upstream prerequisites are incomplete, so the assignee hears about it once, when it unlocks.
• MinistrySafe: Sexual abuse awareness and prevention training for church staff and volunteers, valid for 3 years.
• Monthly Opex Total: Operating Expenditures: recurring monthly operational costs (software licenses, email seats) tracked in an onboarding case.
• Multi-Homing: Making a single task live in two different projects at the same time without creating messy duplicates.
• Notification Fatigue: Mental burnout caused by receiving too many automated digital alerts, leading people to ignore all messages.
• Onboarding Blueprint: A pre-configured role template containing standardized paperwork, hardware provisioning, accounts, and shadowing steps for incoming staff or key leads.
• Process Blueprint (sometimes called a workflow template): A reusable set of stages, tasks, and subtasks an admin builds under Workflows (/admin/workflows) and anyone can apply to a new project. It doesn't carry dates or assignees, and each project can take one blueprint.
• Project: A master container holding all sections, tasks, files, and rules for an ongoing initiative or major event.
• Relay Baton Principle: The practice of assigning downstream tasks up front and marking them Blocked by the upstream task, so they stay locked and quiet until the upstream work is Done.
• Role Pool: A designated group of qualified team members who take turns rotating through a specific responsibility.
• Section / Stage: A distinct phase or category within a project (e.g., Intake, Drafting, Review, Completed).
• Subtask: A nested checklist step inside a parent task card.
• Task Unlocked Notification: An automated notification delivered to downstream assignees the moment all prerequisite blocker cards are completed.
• Trash Retention: The built-in safety net that keeps deleted tasks in Trash for 30 days before permanent purging.