Teams Page Redesign
+ Team Orientation Interest

Why change

How people flow

The General Interest in Team workflow

One new workflow per location: General Interest in Team, owned by the respective location's Inroads Lead. Anyone signing up for (or attending) Team Orientation who isn't placed into a specific team workflow lands here — the undecided, and walk-ins who never signed up online.

This workflow's success is not staying in it. It exists to bridge people into an actual team workflow — the win is their name appearing in one. Two automations run it:

Trigger	Automation
Lands in General Interest	Inroads Lead gets an intro step — reach out before the 3rd Sunday, be a face to find at Orientation
No Orientation Completed tag after the orientation date	Auto-creates a call task for the Inroads Lead — "we missed you, the next one is [date]"
After a Sunday's attendance is complete: Orientation Completed but not in any team workflow	Auto-added to General Interest — the Inroads Lead follows up to land them on a team
Their name appears in any team workflow	Card auto-completes — graduated. That's the metric: General Interest → team workflow

People already on a team are already in their team's workflow — an Orientation RSVP just tags them; General Interest never touches them.

Reporting on this workflow is simple and honest: cards completed = people who found a team; cards aging = people the Inroads Lead is still fighting for.

From notes to data — on the profile

Today, orientation attendance lands as a note on the person's Planning Center profile. The proposal moves it to a "Team Orientation" custom tab — sitting in the profile sidebar exactly like Vulnerable Sector Check and CPR Certification do now.

What we get

Headcounts before Sunday — filter people by Orientation RSVP – [date] per location for setup, hospitality and breakout planning. No leaks — every form submission has a workflow home; nobody ends in a mailto link. Honest reporting — RSVP vs attended vs no-show per location, per month, straight from tags. One form to maintain instead of 21 copies. People actually show up — on submit they add the date straight to their calendar, and an automated reminder email lands 3 days before each orientation with the time, location, what to expect, and kids info.

Already shipped — the Sunday side

The back half of this funnel is live: the Breakout Lead attendance experience has been rebuilt to be far more user-friendly on the day. Leads pick their location and the attendance form opens inside a guided page — a coach bar follows along step by step as they submit (name & team → tick everyone → done), sized so nothing hides below the fold on a phone. A built-in roll call handles walk-ins who aren't on the list: jot their first and last name (email optional), work a per-person checklist to get them signed up to the right team, reload, and tick them — so attendance is confirmed for everyone before the breakout closes.

This proposal completes the picture: the website captures interest and RSVPs at the front, the attendance guide confirms who actually came at the back, and the tags meet in the middle for reporting and follow-up.

What it takes

• Webflow (web team): one new form page; team dropdown wired to the existing hidden-field lookup (team_name, people_flow_[location]); cards repointed; two new hidden fields (orientation_rsvp_date, signup_type). The date logic is ~10 lines of JS (already written and verified in the prototype).
• Planning Center (admin): create General Interest in Team workflow per location, assigned to the Inroads Lead; create a "Team Orientation" custom field section (RSVP date, Completed date) — this replaces writing notes on profiles, so RSVP and attendance become filterable in Lists instead of buried text. The existing attendance automation switches from creating a note to writing this field.
• n8n (existing): extend the current form automations to route signup_type = undecided / rsvp_only into General Interest in Team, plus three scheduled jobs — every Thursday, send the reminder email to everyone tagged for that Sunday's orientation (3 days out); after each orientation, create a call task for anyone in General Interest without Orientation Completed and sweep attendees who aren't in any team workflow into General Interest; and daily, auto-complete any General Interest card whose person now appears in a team workflow.
• No change to the Sunday attendance process — it already applies Orientation Completed.
• Branding: everything is built to the C3 Assembly Brand Guidelines (palette, typography, tone — as shown in this prototype) on the current site, and adapted to the new site when it launches. The form logic, workflows and tags carry over unchanged — only the skin moves.