Live Like Sam · Challenge Accepted
Everything needed to set up your chief of staff, prove it works with your laptop closed, and use it week to week.
Three skills that Claude can use, and three tasks that run on their own schedule. Once it's set up you don't open anything — it emails you.
| When | What arrives |
|---|---|
| Every weekday, 7am | A one-screen brief: which events are short on sign-ups, what's blocked, what's due today |
| Mondays, 8am | A doc with every piece of outreach due this week, drafted — emails, texts, social, calendar submissions, English and Spanish |
| Mondays, 9am | Attendance and interest numbers from last week's events, plus the thank-you and follow-up emails |
| Any time you ask | A full plan and outreach kit for a new event |
Nothing sends on its own. Everything is drafted and handed to you.
Before you start
Steps 2 and 3 need Owner or Primary Owner on your Team plan. Being an admin isn't enough — it's a separate thing, and it's the one prerequisite that blocks the others.
Go to claude.ai/admin-settings. If you can see Organization settings, you're set. If not, find whoever holds Primary Owner for steps 2 and 3 — everything from step 4 onward you can do yourself.
The first three are at claude.ai/admin-settings/cowork. Two of them are usually already on, so you're confirming rather than changing.
It's off by default, and leaving it off is the most likely way this whole setup quietly fails.
With it off, your 7am brief starts on schedule, asks permission to read your email, and then waits — forever, because you're asleep. From the outside it looks like the task ran and produced nothing. Every morning.
While you're on that page, check that Gmail and Google Drive aren't set to "ask" in your connector policies. Anything set to "ask" prompts every single time and can't be waved through.
Install
In Cowork, open Connectors and connect both. This is what lets the system read your Challenge Accepted workbook and see partner replies in your inbox.
The CA Comprehensive workbook isn't shared publicly, so everything runs as you. Fine to start, but it means the system pauses if you're ever out. Once we've proven it works, share the workbook with a second account so it doesn't depend on one login.
Download the three files below, then go to Customize → Skills, click Add, and upload each one. You don't need to open or unzip them.
| Skill | What it does |
|---|---|
| challenge‑accepted‑event | Turns one event brief into a dated task plan plus the full outreach kit — flyer, emails, texts, social, calendar submissions, all in English and Spanish |
| challenge‑accepted‑brief | Your daily rundown: which events are short on sign-ups, what's blocked, what's due |
| challenge‑accepted‑outcomes | Fills in the attendance and interest columns, then tells you what's actually working |
Each skill is one folder with one text file inside. The event skill has a few extra reference files. Nothing here is code — it's all plain instructions.
On a Mac, for each skill:
SKILL.md. When TextEdit asks about the extension, choose Use .md..zip.The zip must have the folder at its root, like this:
challenge-accepted-brief.zip
└── challenge-accepted-brief/
└── SKILL.md
The event skill has more files, so its folder looks like this:
challenge-accepted-event.zip
└── challenge-accepted-event/
├── SKILL.md
├── references/
│ ├── channels.md
│ ├── task-plan.md
│ └── brand-voice.md
└── assets/
└── flyer-template.html
If the upload is rejected, try renaming SKILL.md to lowercase
skill.md — both spellings are used in Anthropic's docs.
---
name: challenge-accepted-brief
description: Use to produce the Challenge Accepted daily or weekly operating brief — reads the CA Comprehensive workbook and email, then reports registration alarms, unowned blockers, today's tasks, and partner silence. Trigger on "daily brief", "what's on today", "where are we on programs", "run the brief", or from the scheduled task.
---
# Challenge Accepted — operating brief
The standing report. Runs unattended on a schedule, so it has to be right without
anyone checking it.
## Cloud-safe constraints — do not violate
This runs on Anthropic's servers with nobody's computer on. Therefore:
- **Never reference a local file path, the desktop, downloads, or a local app.**
Anything local pins the task to one machine and it stops running.
- **Never use browser control or computer use.** Connectors only.
- Read the workbook through the Google Drive/Sheets connector, email through the
Gmail connector.
- Deliver by email or a Google Doc. Never write a file "locally."
If you cannot reach a source, **say so in the brief and continue**. A brief that
reports "couldn't read the Outreach tab" is useful. A brief that silently omits a
section teaches her to distrust the whole thing.
## Sources
Workbook **CA Comprehensive | Challenge Accepted**:
| Tab | Read for |
|---|---|
| Scheduled Events | Upcoming events, status, dates, partners, outcome columns |
| Ideas & Tasks | The 29-column checklist — what's done, what isn't, per event |
| Outreach | Per-event channel status (Incomplete / Complete), owners |
| Partner Contacts | Who to chase |
Gmail: partner replies, registration notifications, anything from the interest form.
## The brief
Ordered by what can hurt them. Never reorder into a chronological list — the whole
point is that the dangerous thing is at the top.
### 1. Registration alarms — always first
For every event with a date in the next 21 days, report the registration count
against the checkpoint thresholds (8 at T-10, 12 at T-5).
If an event is below threshold, do not just state the number. Give the recovery
options, and draft the highest-value one so it's ready to send:
- Re-send to interest-form fills who never registered
- Personal ask to past attendees of similar events
- Partner ask — can they bring participants
- Extend the deadline, or make the go/no-go call now rather than at 48 hours
**Lead with this even when everything is fine.** "Dairy Farmer: 14 registered,
above threshold" is a sentence worth reading. An event was cancelled at three
sign-ups because nobody was watching this number.
**Report interest and registration as two separate numbers, always.** The interest
form says a follow-up email finalizes the spot, so a checkbox is not a seat. An event
with 22 interested and 4 finalized is not healthy, and reporting "22" would hide the
problem.
If there are interest-form fills with no finalization email sent, that is a lead
list, not a gap — say how many, how long they've been waiting, and draft the
finalization email.
If registration counts aren't available anywhere you can read, say that plainly and
flag it as the thing to fix — it's the most important number in the system.
**Never put a student's name, email, phone, birthday, or ethnicity in the brief.**
Counts and aggregates only; the form collects a lot about minors and none of it
belongs in a daily email.
### 2. Hard blockers — unowned or overdue
Facilitator · waiver · parking and directions · sign-up link routing · date and time
confirmed.
For each: which event, how many days out, who owns it, how long it's been sitting.
An event 30 days out with no confirmed facilitator goes here, not in a task list.
### 3. Due today
From the checklist and the Outreach tab. Group by event. Mark anything Claude can
draft with **"I can draft this — say the word."**
### 4. Due this week
Compressed, one line each. Flag anything that depends on an unresolved blocker
above, because those will slip and she should know now.
### 5. Partner silence
Partners contacted with no reply in 7+ days. Two program ideas died purely to
silence. Draft the follow-up and include it, ready to send.
### 6. Needs a human decision
Anything the brief cannot resolve: a partner asking for something, a conflict
between two events, a cancellation call. Short, specific, with a recommendation.
## Format
Plain text email, scannable in under 60 seconds on a phone. She's a program
director, not a report reader.
```
CHALLENGE ACCEPTED — Thursday, July 30
🔴 REGISTRATION
CPR Certification (Aug 10, 11 days out) — 4 registered, below the 8 threshold
→ I've drafted a re-send to the 23 interest-form fills who never registered.
→ Wasatch Fire Dept may be able to bring participants. Draft ready.
🔴 BLOCKED
CPR Certification — still "Waiting for Partner Details," 11 days out.
No parking, no directions, no confirmed start. The day-before email
can't be written without these.
📋 TODAY
Dairy Farmer — Peach Jar submission (Week Two). I can draft this.
Dairy Farmer — hang physical flyers.
📅 THIS WEEK
Thu: Dairy Farmer last-call email · Fri: carpool roster to riders
Sat: DAIRY FARMER, 2–4pm, Ballerina Farms, Kamas
🤝 SILENCE
Sage Mountain (Oct 24) — no reply in 12 days. Follow-up drafted.
❓ NEEDS YOU
CPR go/no-go. At 4 registrations with 11 days left, recommend deciding
by Aug 3 so we can cancel gracefully instead of at 48 hours.
```
Rules for the format:
- **Empty sections get deleted, not printed empty.** "No blockers 🎉" is noise.
- Every alarm carries a proposed action, not just a fact.
- Never more than one screen. If it's longer, she stops reading it and the whole
system dies.
- Real dates and real counts. Never "T-10," never "several."
## Honesty rules
- If a number was inferred rather than read, say which.
- If a tab was unreadable, name the tab.
- Never report a task as done because it looks done. The checklist is the source of
truth; if a cell is blank, the task is not done.
- Do not invent registration counts. "Not tracked anywhere I can read" is the
correct answer when that's true, and it's a finding worth surfacing.
## Never do these
- Never send anything outward — no emails to partners, families, students, or
calendar editors. Draft and hand over. Sending is a human action.
- Never write to the workbook from this skill. Reporting only. Writing is
`challenge-accepted-outcomes`, and it asks first.
--- name: challenge-accepted-outcomes description: Use to close the measurement loop on Challenge Accepted events — records attendance and interest into the Scheduled Events outcome columns, computes interest-to-attendance conversion, and reports which event types, grade bands, and counties actually work. Trigger on "log the outcomes", "how did [event] do", "what's converting", "update the numbers", or from the scheduled task. --- # Challenge Accepted — outcomes The `Scheduled Events` tab has twelve outcome columns: - Total students attended · 6–8th attended · 9–12th attended · Summit County attended · Wasatch County attended - \# interested · 6–8th interested · 9–12th interested · Summit County interested · Wasatch County interested **Every one is empty across all 14 events logged so far.** Someone designed exactly the right instrument and it has never been used. That's why nobody can answer the only question that matters right now — *why are events under-enrolling* — because interested-versus-attended is precisely the number that separates an awareness problem from a conversion problem, and those need opposite fixes. This skill fills those columns and reads what they say. ## Cloud-safe constraints Runs unattended on Anthropic's servers. Connectors only — no local files, no browser control, no computer use. If a source is unreachable, say so and continue. ## Step 1 — Gather The interest form is `docs.google.com/forms/d/e/1FAIpQLSe0ttxECtC19SOiigFYSztvPYZfIbTGdj6M2W4KTkTtAgOnLA` — "Live Like Sam's Challenge Accepted FREE Teen Meet-ups!" Its linked responses sheet is the source for everything except attendance. **Verified 2026-07-30: the form already captures every split needed.** All of these are required fields, so there is no missing-data excuse: | Number | Source | Notes | |---|---|---| | \# interested, per event | "Which exciting programs would you like to join?" checkbox | One row can select several events — count per event, not per row | | Grade | Grade dropdown | Options run **5th** through 12th | | County | County multiple choice | Summit (Park City / North Summit / South Summit), Wasatch, **Salt Lake** | | Channel | "How did you find out about the program?" | Free text — see Step 3 | | \# attended | The attendance sheet | Not in the form | **Two schema mismatches to report, not silently paper over:** - The form offers **Salt Lake County**; the workbook has attended/interested columns for Summit and Wasatch only. Salt Lake registrants currently have nowhere to be counted. Report the Salt Lake number separately and flag that a column is missing. - The form's grade dropdown starts at **5th**; the workbook bands are 6–8 and 9–12, and the program advertises grades 6–12. Fifth-graders fall outside every band. Count them separately and flag it — it's either a form bug or an undocumented younger cohort, and those need different responses. ### The three-stage funnel — do not collapse it - **Interested** — submitted the interest form - **Registered** — completed the follow-up that finalizes the spot - **Attended** — physically showed up This distinction is not academic. The form says so itself: *"You will receive a follow-up email to finalize your registration."* **That follow-up is a manual step, and it is the leading hypothesis for why events under-enroll.** A teenager who checked four boxes on a form in June has expressed interest, not commitment, and nothing happens until a human sends the finalization email. Every interested-but-never-finalized student is a warm lead sitting in a spreadsheet. Measure that gap first and report it before anything else. If interested → registered is where the volume is lost, then the fix is automating or tightening the finalization email — not more outreach, not better flyers. ## Step 2 — Write **Always show the exact rows and values before writing, and wait for a yes.** ``` About to write to Scheduled Events: Row 12 — Day in the Life: Dairy Farmer (8/6) # interested: 23 # attended: 14 6-8th attended: 9 9-12th attended: 5 Summit attended: 11 Wasatch attended: 3 Write these? (grade/county splits for "interested" unavailable — form doesn't ask) ``` Never overwrite a non-empty cell without calling it out specifically. Never write into any tab other than `Scheduled Events` from this skill. ## Step 3 — Read what it says Once three or more events have numbers, report: **Conversion.** Interested → registered → attended, per event and overall. This is the headline. - High interest, low registration → the **sign-up step** is the problem. Friction in the form, a broken link, or sign-ups routed somewhere other than our link. - High registration, low attendance → a **show-rate** problem. Reminders, transport, or the day-before email. - Low interest → an **awareness or appeal** problem. Channels, or the event itself. Three different diagnoses, three opposite fixes. Getting this wrong wastes a season. **What works.** Rank event types by attendance and by conversion — those can disagree, and conversion is the more useful ranking. Note which grade band and county each type pulls. Volunteering, outdoor skills, animal work, and certifications may behave very differently and nobody currently knows. **What underfills.** Every event marked Low Registrations or Cancelled, with its interest number. If interest was healthy and registration wasn't, that's a fixable funnel problem, not a bad idea. **Threshold update.** The registration checkpoints in `challenge-accepted-event` default to 8 at T-10 and 12 at T-5 — placeholders invented with no data behind them. Once there are 5+ events logged, compute the real numbers: what registration count at T-10 historically produced an event that ran, and what count produced a cancellation. Say plainly that the thresholds should be replaced, and with what. **Channel attribution — they're already collecting it and nobody is reading it.** "How did you find out about the program?" is a required free-text field on every interest form submission. Normalize the answers into buckets — Peach Jar, school, Instagram, Facebook group, community calendar, friend, partner org, flyer, word of mouth — and rank them by volume *and* by how many of each bucket went on to attend. This is the highest-value analysis in the whole system. It tells them which of the four community calendars, Peach Jar, and social channels are worth the weekly effort and which are ritual. Report it as soon as there are 20+ responses, and say the sample size. Because it's free text, normalize conservatively: keep an "unclassified" bucket rather than forcing ambiguous answers into a category, and show what's in it. **Seasonality.** `rejected ideas and why` shows three ideas killed for colliding with an existing October and November event. Check whether events cluster and whether clustered events underperform. **Stale form options.** The form still lists events whose dates have passed. That inflates interest counts and confuses new registrants. Flag any option in the events checkbox whose date is in the past. ## Step 4 — Report ``` CHALLENGE ACCEPTED — outcomes through [date] FUNNEL (n events with complete data) Interested → Registered: __% Registered → Attended: __% Biggest leak: [which step, and what that implies] BY EVENT TYPE interested attended conversion Animal / therapy __ __ __% Outdoor skills __ __ __% Volunteering __ __ __% Certification __ __ __% BY AUDIENCE 6–8th vs 9–12th: ... Summit vs Wasatch: ... UNDERFILLED [event] — __ interested, __ registered. [read] RECOMMEND 1. ... 2. ... DATA GAPS [what's missing and the specific fix] ``` ## Honesty rules - **Never fabricate a number.** Blank is a finding; a made-up number is a lie that gets planned against. - Say the sample size every time. Four events is a hint, not a trend, and it should be labelled as one. - If a split is unavailable, report the total and name the missing field. - Do not smooth over a contradiction between sources — surface it. If the attendance sheet and the workbook disagree, that discrepancy is the finding. ## Minors' data — handle with care The interest form collects, from **children**: full name, personal email, personal phone, birthday, school, grade, ethnicity, and dietary restrictions, plus parent contact details. - **Report aggregates only.** Never put a student's name, email, phone, birthday, or address into a brief, a report, a doc, or an email. - **Ethnicity is for aggregate demographic reporting only** — almost certainly a grant requirement. Never break it out in a way that could identify an individual, and never cross-tabulate it with anything at small cell sizes. If a bucket has fewer than 5 people, report it as "<5" rather than the number. - Dietary restrictions and birthdays exist for event operations, not analysis. Don't surface them in reports. - When a draft needs a name — a personal follow-up, say — use a merge field and let the human fill it from the sheet. - Never copy the response sheet, or a subset of it, into any document. ## Never do these - Never write outside `Scheduled Events`. - Never write without showing the values and getting a yes. - Never send anything outward. - Never put an individual minor's personal information into any output.
--- name: challenge-accepted-event description: Use when a Challenge Accepted event or program needs to be planned or promoted — produces the dated task plan and the full bilingual communications kit (flyer, student and parent outreach emails, texts, last-call, social, community-calendar submissions, Peach Jar, sign-up confirmations, reminders, post-event emails). Trigger on "build comms for [event]", "plan the [event]", "we have [event] coming up", "outreach for [partner]", or when an event brief is pasted in. --- # Challenge Accepted — event planning and comms One event brief in. A dated task plan and a complete bilingual comms kit out. ## The thing to keep in mind Of the last ten Challenge Accepted events that reached their date, two were cancelled and two more ran under-enrolled. One was cancelled with three sign-ups. **Registration is the failure mode.** Every asset you write is judged on whether it moves sign-ups — not on whether it sounds nice. When you have a choice between polished and concrete, pick concrete: "free, ride available, 9–11am Saturday" beats any adjective. ## Where the data lives Workbook: **CA Comprehensive | Challenge Accepted** (Google Sheets, via the Drive connector — it is not link-shared, so it must be read as Jess). | Tab | What it holds | |---|---| | Scheduled Events | The event log, status, and the attendance/interest columns | | Ideas & Tasks | The 29-column master checklist across 6 phases | | Outreach | The distribution channel list, Week One / Week Two cadence | | Partner Contacts | Partner contacts | | External Links | Email templates, carpool sign-up, waivers, activities list, follow-up survey | | rejected ideas and why | Killed ideas and reasons | Never write to this workbook without saying what you're about to change and getting a yes. Reading is free; writing is not. ## Step 1 — Brief Required: event name · what it actually is, one plain sentence · date · start/end time · location · partner org · grades (6–8, 9–12, or both) · county (Summit, Wasatch, or both) · sign-up link · cost to families · contact. Strongly wanted: capacity · registration deadline · what to bring · what's provided · transport/carpool available · waiver source (partner's or ours) · parking and directions · why a teenager would give up a Saturday for this. If fewer than four required fields are missing, use `[BRACKETED PLACEHOLDERS]` and produce the whole kit anyway. Do not stall the build on a nice-to-have. Check `rejected ideas and why` before planning something new — if a near-identical idea died for a reason that still holds, say so up front. ## Step 2 — Task plan Read `references/task-plan.md`. Output the dated plan with real calendar dates. Lead with two things: 1. **Unowned hard blockers** — facilitator, waiver, parking/directions, and the sign-up form. An event with no facilitator confirmed is not a comms problem. 2. **The registration checkpoints** at T-10 and T-5, with the current count if known. This is the mechanism that would have caught the cancelled event. ## Step 3 — Comms kit Read `references/channels.md` before writing a single word. It has the real channels, the character limits, the SMS compliance rules, and the Spanish requirements. Read `references/brand-voice.md` for tone. Three structural rules that are easy to get wrong: **Students and parents are different audiences and get different emails.** Parents decide; students attend. Parents need cost, supervision, transport, waiver, safety, and what their kid gets out of it. Students need the experience, who else is going, and permission to show up without knowing anyone. Never send one email to both. **Everything outward-facing ships in English and Spanish.** Not as an afterthought and not as a literal translation — parallel copy that works on its own. The Spanish version is aimed at parents deciding, so it carries the most weight. **Reminders go to registrants only.** The day-before email and day-of text must never go to the full list. ### The kit | # | Asset | Audience | Timing | |---|---|---|---| | 1 | Flyer — EN and ES, print + social | All | Week One | | 2 | Student outreach email | Student list | Week One | | 3 | Parent outreach email — EN and ES | Parent list | Week One | | 4 | Community partner email | Partner list | Week One | | 5 | Community calendar submissions ×4 | KPCW, TownLift, Park Record, Wasatch Wave | Week One | | 6 | Peach Jar submission | PCSD families | Week Two | | 7 | Social posts ×3 — Instagram + Facebook groups | Public | Week One / Two / final | | 8 | Outreach text | SMS-consented | Week Two | | 9 | Sign-up confirmation email — EN and ES | New registrant | Triggered | | 10 | Sign-up confirmation text | New registrant | Triggered | | 11 | Last-call email — EN and ES | List minus registrants | T-4 | | 12 | Last-call text | List minus registrants | T-2 | | 13 | Day-before reminder email | **Registrants only** | T-1 | | 14 | Day-of reminder text | **Registrants only** | Day-of, after 8am | | 15 | Post-event email — attendees | Attendees | T+2 | | 16 | Post-event email — non-attendees | List minus attendees | T+2 | | 17 | Follow-up survey email | Attendees | T+3 | **Asset 9 is the most important thing in this kit.** The interest form tells students *"You will receive a follow-up email to finalize your registration"* — so filling the form is interest, not a spot. Nothing happens until someone sends that email. Every student who checked a box and never got followed up is a warm lead that quietly expired. Write asset 9 as the **finalization email**, not a receipt: confirm which event, state the one thing they must do to lock the spot, give the deadline, and make it answerable in one reply. Then say plainly in the delivery notes how many days the finalization email has been outstanding for current interest-form fills, if that's knowable. Assets 9 and 10 are **templates with merge fields**. Load them into the form's autoresponder once so the first touch is instant, and keep the human finalization on top of it rather than instead of it. Asset 16 is the one most orgs skip and it is usually the best performer. Given the under-enrollment problem it also doubles as the re-engagement path for the next event. ### Conversion mechanics — put these in, every time Registration is the failure mode, so every asset carries at least two of: - **A number.** Capacity, spots left, or registration deadline. "12 spots" outperforms "sign up soon." - **The transport answer.** Carpool exists — link it. In Summit and Wasatch counties a ride is frequently the actual blocker, and silence on it reads as "not for us." - **Cost stated as free**, explicitly, in the first two lines. Never assume people know. - **A named human** with a real phone number and email. - **One link**, the same one everywhere, short enough to read off a printed flyer. It's the single Google Form covering all events, so the same URL works on every asset. - **"No experience needed"** — the program's own phrase, and it removes the second biggest barrier after transport. Use it verbatim. - **The raffle.** "Bring a friend, earn a raffle ticket / ¡Trae a un amigo! ¡Gana un boleto para la rifa!" already exists on the form and is already bilingual. It directly attacks *"I don't want to show up alone"* — put it in student-facing copy rather than leaving it buried at the bottom of a form. ### Two things already solved — don't rebuild them - **SMS consent is collected at sign-up.** The student phone field carries explicit consent language covering outreach texts, with a revocation clause. So consent exists for **student** numbers. It does **not** obviously extend to the parent phone field — treat parent numbers as un-consented until someone confirms otherwise. A texting platform and 10DLC registration are still required before anything can actually send. - **Photo/media release is collected at sign-up**, with explicit consent and do-not-consent options. So "confirm photo waiver" is already handled for anyone who came through the form. What still needs doing on the day is checking the opt-out list before photographing. ## Step 4 — Flyer Use `assets/flyer-template.html`. Produce four artboards: EN print, EN social, ES print, ES social. Fill CSS variables from `references/brand-voice.md`. If a Canva brand template exists, offer the alternative: produce the copy blocks and layout spec instead, since Canva with their real fonts and logo will out-design generated HTML. Let them choose. ## Step 5 — Delivery Write the kit to a Google Doc named `Challenge Accepted — [Event] — Comms Kit`, and the plan to `Challenge Accepted — [Event] — Plan`. Return both links. Ask before creating them. Do not write into the CA Comprehensive workbook unless asked, and then only after stating the exact tab and range you intend to touch. ## Output format Each asset in its own labeled block, in send order, metadata line above it: ``` ── 3. PARENT OUTREACH EMAIL (EN) ────────────── Send: Week One | To: Parent list | Platform: [email tool] Subject: <subject> (44 chars) Preview: <preview> (71 chars) ``` Spanish versions immediately follow their English counterpart, same numbering with `(ES)`. All caveats, assumptions, and open questions go in one **Before you send** block at the very bottom. ## What this does not do - **It does not send anything.** It drafts. Sends happen in their email platform, their texting platform, and by a human hitting submit on the calendar forms. - **It cannot confirm SMS consent.** It writes compliant copy; whether a number opted in is a question only their texting platform can answer. - **Spanish copy needs a fluent human read before it goes out.** Say this every time you produce Spanish. It is not a formality — these are parents deciding whether to send their kid somewhere.
# Channels The real distribution list, from the workbook's `Outreach` tab. Hard constraints per channel. Check every asset against these before output. Cadence is **Week One** (announce, everything that needs lead time) and **Week Two** (social, physical flyers, text). Keep their language — don't impose T-minus on the outreach team. --- ## Email Two audiences, always. Never one email to both. ### Parent email — the one that decides Parents are approving, not attending. Answer, in this order: what it is · when and where · **it's free** · who supervises · how their kid gets there (carpool link) · what to bring · waiver · a named human with a phone number. Length 150–200 words. Warm and specific, not institutional. Do not use urgency or guilt. Do not bury the cost — a parent scanning for "how much" and not finding it assumes it's expensive and stops reading. ### Student email — the one that shows up Shorter, 70–110 words. Lead with the experience, not the logistics. Say who it's for in a way that gives permission to come alone: "you don't need to bring anyone." Skip supervision and waiver detail — that's the parent's email. ### Subject lines ≤50 characters, front-loaded. No ALL CAPS, no more than one `!` in the whole email. Give two options for the outreach and last-call emails so they can A/B. Preview text 40–90 chars, a second headline rather than a repeat. Never leave it empty or the client pulls "View this email in your browser." ### Community partner email Monthly opportunities roundup, goes to the partner list. Different register: peer to peer, brief, leads with what the partner gets and what you need from them. Include the shareable flyer and the sign-up link so they can forward it. ### Sending Through their email platform, never bulk from Gmail — it wrecks domain deliverability. Mailing address and unsubscribe link are required in bulk email. --- ## Spanish — required, not optional The `Outreach` tab tracks "Update Monthly Event Flyer (SP & EN)". Treat every outward asset as bilingual by default: flyer, parent email, parent-facing texts, confirmations, social. - **Write parallel copy, don't translate.** Idioms, urgency, and warmth don't survive literal translation. Rebuild the message so it lands on its own. - **Use `usted`** for parent communications. Students may take `tú`. - Keep numbers, dates, and the sign-up link identical across both versions so nobody has to cross-check. - Dates in Spanish: `sábado, 22 de agosto` — lowercase day and month, no ordinals. - **Always flag that a fluent human should read it before it goes out.** These are parents deciding whether to send their kid somewhere with strangers. --- ## SMS | Encoding | Single message | Per segment beyond that | |---|---|---| | GSM-7 (plain ASCII) | **160 chars** | 153 | | UCS-2 (any emoji, curly quote, em dash, accent) | **70 chars** | 67 | One emoji or one smart quote drops the limit from 160 to 70. Word and Google Docs auto-convert `'`→`'` and `--`→`—`, which is how a 150-character text becomes a 3-segment send. Write SMS in straight quotes and plain hyphens. **Spanish SMS is a trap**: `á é í ó ú ñ ¿ ¡` are all outside GSM-7 and force UCS-2 at 70 characters. Either write around the accents (awkward, and usually wrong) or accept two segments and say so. Required: org identity in the first message of a campaign · `Reply STOP to opt out` on any promotional send · a real short link, not "visit our website." **Compliance.** Only text numbers that opted in to texts specifically — an email list is not an SMS list. US carriers require 10DLC brand and campaign registration before A2P messages deliver reliably; unregistered traffic is filtered silently, so messages "send" and never arrive. Registration takes days to weeks, so it starts before the first campaign, not the week of. No sends before 8am or after 9pm local. --- ## Community calendars — free earned distribution Four outlets, each with its own submission path. These are recurring and mostly unautomated today. Produce a submission-ready block for each. | Outlet | How | Contact | |---|---|---| | KPCW | Web form: `kpcw.org/community-calendar/events/create` | — | | TownLift | `townlift.com/events/` | laura@townlift.com — has asked for a Canva flyer | | Park Record | Email | rebecca@parkrecord.com | | Wasatch Wave | Email | editor@wasatchwave.com (Lauri) | For each, output: - **Listing blurb, 25–50 words** — what, who it's for, when, where, free, link. Calendar editors cut anything longer, so cut it yourself and keep control of what survives. - **A short submission email** to the named contact for the email-based outlets, flyer attached, one sentence of context and the blurb below it. - **Lead time** — submit in Week One. Weeklies close early and a late submission is a wasted channel. Never send the same paragraph to all four. Editors in a small market notice. --- ## Peach Jar — school distribution Digital flyer distribution to Park City School District families. Week Two. Contacts: lpearce@pcschools.us (Lorie Pearce), communication@pcschools.us. Peach Jar wants the flyer as a clean single-page PDF. Send the **Spanish and English versions both** — this is the single highest-leverage Spanish placement, because it reaches district families directly. Districts often have their own approval lead time; ask once and record the answer. --- ## Social - **Instagram**: hook in the first 125 characters, that's the truncation point. No clickable link in captions — write "link in bio" and remember to actually update the bio link. That's the most-dropped step in the whole campaign. - **Facebook groups**: local community groups behave differently from a page post. Write it as a person telling neighbors about a thing, not as an org announcing. No hashtag block, links are fine, and lead with the county or town name. - **Three beats**: announce (Week One), detail or social proof (Week Two), final urgency (T-3). Genuinely different angles, not the same copy with the date moved. - 5–10 hashtags, mixing local, cause, and audience. End of caption or first comment. - **Alt text on every image**, describing any text baked into the graphic. --- ## Accessibility floor — all channels - **Never put critical information only in the flyer image.** Date, time, location, cost, and the sign-up link must exist as real text in the email body and caption. Screen readers can't read a JPEG and neither can anyone whose images didn't load. - Alt text everywhere. Contrast ≥4.5:1 body, ≥3:1 large text. - State accessibility facts in the copy when known: parking, step-free access, transport, what to do if you can't afford gear. If unknown, list it as an open question rather than silently omitting it. - Descriptive link text, never "click here."
# Task plan Built from the workbook's `Ideas & Tasks` checklist (6 phases, 29 task columns) plus the `Outreach` tab's Week One / Week Two cadence. ## Rules **Output real calendar dates, never "T-21."** **Weekend shifting is directional.** Pre-event tasks that land on a weekend move *backward* to Friday — earlier is always safe. Post-event tasks move *forward* to Monday. Getting this backwards schedules "update the attendance sheet" for two days before the event. Sanity-check every plan: no pre-event task may fall on or after the event date, and no post-event task on or before it. **Events are Saturdays and weekday evenings** — the event day itself is often a weekend and must never be shifted. `Does it` — **C** Claude drafts · **H** human only · **C+H** Claude drafts, human decides or sends. --- ## Phase 1 — Initial Program Planning | Offset | Task | Does it | Notes | |---|---|---|---| | T-60 | Presented to Jessica | H | Idea gate | | T-55 | Reached out to partner | C+H | Claude drafts the approach email | | T-50 | In talks | H | | | T-45 | Possible dates and times sent to org | C+H | | | T-42 | **Any bottlenecks?** | H | The tab asks this explicitly — answer it in writing, not in someone's head | | T-40 | Touch base with partner: waivers + all kids sign up through our link | H | **Hard blocker.** Sign-ups routed anywhere but our link means no list, no reminders, no count | | T-38 | Start day-of logistics planning | C+H | Creates the run-of-show tab | **Partner non-response is a known killer** — two ideas in `rejected ideas and why` died purely to silence. If a partner hasn't replied within 7 days of "Reached out," flag it and draft a follow-up. Don't let it sit. ## Phase 2 — Prepare Outreach Materials | Offset | Task | Does it | Notes | |---|---|---|---| | T-30 | Flyer made (EN) | C+H | Needs the sign-up URL to exist first | | T-29 | **Spanish flyer made** | C+H | Not optional | | T-27 | Flyer approved | H | Separate gate from "made" — respect it | | T-26 | Planned and ready to advertise | H | | | T-25 | Send to Lauren and Jessica — website updated | H | | ## Phase 3 — Partner Details & Communication | Offset | Task | Does it | Notes | |---|---|---|---| | T-35 | Event date and time confirmed | H | **Hard blocker** | | T-33 | Confirm facilitator | H | **Hard blocker.** No facilitator, no event | | T-32 | Share curriculum with partner | C+H | | | T-30 | Get waiver from partner | H | **Hard blocker** | | T-30 | Get parking, address, direction tips from partner | H | **Hard blocker** — this is what the day-before email is made of | | T-28 | Add waiver to doc or drive | H | | The 7/10 Kayaking event moved venue late because the partner lacked river safety certifications. Ask about **certifications and insurance** during Phase 3, not the week of. ## Phase 4 — Prepare Communication Materials | Offset | Task | Does it | Notes | |---|---|---|---| | T-24 | Add parking, address, directions to email template | C | Blocked on Phase 3 | | T-23 | Update carpool template | C+H | Transport is a real barrier here — treat it as a conversion asset, not admin | | T-23 | Finalize detailed email template | C | This is the sign-up confirmation autoresponder | | T-22 | Share outreach materials with Lauren and Jess | H | | ## Phase 5 — Outreach (Outreach tab cadence) | Offset | Week | Task | Does it | |---|---|---|---| | T-21 | One | Student outreach email | C | | T-21 | One | Parent outreach email (EN + ES) | C | | T-21 | One | Community partner email — monthly opportunities | C | | T-21 | One | KPCW community calendar submission | C+H | | T-21 | One | TownLift community calendar submission | C+H | | T-21 | One | Park Record community calendar submission | C+H | | T-21 | One | Wasatch Wave community calendar submission | C+H | | T-20 | One | Instagram — announce | C+H | | T-14 | Two | Facebook groups post | C+H | | T-14 | Two | Peach Jar submission (EN + ES PDF) | C+H | | T-13 | Two | Hang and distribute physical flyers | H | | T-12 | Two | Instagram — detail | C+H | | T-10 | — | **Registration checkpoint 1** | C | | T-7 | — | Send text message reminder | C | | T-5 | — | **Registration checkpoint 2** | C | | T-4 | — | Last-call email (EN + ES) | C | | T-3 | — | Mass email reminder to interest form | C | | T-2 | — | Last-call text + final urgency social | C | | T-3 | — | Remove event from website once registration closes | H | ### Registration checkpoints — the point of the whole system An event was cancelled at three sign-ups. These two checkpoints exist so that never happens silently again. At **T-10** and **T-5**, count registrations and compare against the threshold. If below it, do not just report the number — produce the recovery options: - Direct re-send to everyone who filled the interest form but never registered - A personal ask to past attendees of similar events, drafted and ready to send - A partner ask — can they bring participants? - Extend the deadline, or make the go/no-go call early enough to cancel gracefully rather than at 48 hours **Default threshold: 8 registrations at T-10, 12 at T-5.** These are placeholders. The outcome columns in `Scheduled Events` are empty, so nobody actually knows the real conversion rate yet — say so when you use them, and replace them with real numbers as soon as `challenge-accepted-outcomes` has a few events logged. ## Phase 6 — Program Preparations | Offset | Task | Does it | Notes | |---|---|---|---| | T-7 | Create attendance sheet | C | From the registration list | | T-5 | Confirm reminder outreach is scheduled | H | Verifies the T-1 and day-of sends are queued | | T-4 | Carpool roster updated and **sent to riders** | C+H | See flag below | | T-3 | Snacks | H | | | T-3 | Gather supplies | H | | | T-2 | Connect with org and Lauren — everyone has done the waiver | H | | | T-2 | Print surveys | H | | | T-1 | Day-before reminder email — **registrants only** | C | Parking, directions, what to bring, weather | | T-1 | Print attendance sheet and agenda | H | | | T-0 | Day-of reminder text — **registrants only**, after 8am | C | | | T-0 | Take attendance | H | | | T-0 | Take photos | H | Check the waiver list for opt-outs first | **Weather line in the day-before email.** The 7/29 Liberty Sanctuary event ended 90 minutes early because students showed up without raingear. If the event is outdoors, the day-before email says what the forecast is and what to bring for it. > **Flag for the team:** in the workbook, "Carpool Roster Updated" sits under > Close-Out Program. If that's literal, riders learn their ride *after* the event. > This plan moves it to T-4. Worth confirming the intent — I inferred the phase > boundary from column position and could be reading it wrong. ## Phase 7 — Close-Out | Offset | Task | Does it | Notes | |---|---|---|---| | T+1 | Update attendance sheet | H | Produces the headcount everything downstream needs | | T+1 | **Record outcomes in Scheduled Events** | C+H | Attended and interested, by grade band and county | | T+2 | Add photos to folder, add link to email | H | | | T+2 | Post-event email — attendees | C+H | | | T+2 | Post-event email — non-attendees | C | The re-engagement path into the next event | | T+3 | Follow-up survey email | C | | | T+3 | Create social post highlighting the event | C+H | | | T+4 | Edit thank-you email and send to Lauren | C+H | | | T+5 | Add to Programming Numbers spreadsheet | H | Confirm this isn't duplicating the Scheduled Events columns | | T+7 | Follow up on volunteer / next-step interest | C+H | | The volunteer follow-up is the actual mission outcome — everything upstream is machinery for producing it. Put the interest question inside the follow-up survey so the data arrives without another send, then split responses into "wants to volunteer with us" and "wants connecting to a partner org." Those need different follow-ups. ## Output format ``` CHALLENGE ACCEPTED — [Event] — [Date], [Partner] [N] days out · [X] tasks · registration: [count or "not yet open"] ⚠ Unowned hard blockers: facilitator (due Aug 4), waiver (Aug 7) ⚠ Registration checkpoint T-10 falls Aug 12 | Due | Day | Task | Phase | Owner | Does it | Status | ``` Sort by due date. Hard blockers and registration checkpoints at the top, above the table — those are the two things that actually sink events.
# Brand and voice Verified from livelikesam.org and the live registration form on 2026-07-30. Colors and fonts are **computed from the rendered site**, not guessed from source. --- ## Organization **Live Like Sam Foundation** — Park City, Utah. Named for Sam Jackenthal. Self-description, from the site's own metadata: > "Live Like Sam is a Park City-based nonprofit that provides youth leadership and > youth development preventative programming for Summit County." ⚠️ That line says **Summit County only**, but the program runs events in Wasatch County and the registration form offers Summit, Wasatch, **and Salt Lake**. Either the site copy is stale or the service area has grown. Ask before repeating the Summit-only framing in outreach — it may be excluding families who qualify. Site: `livelikesam.org` · Program calendar: `Programs@livelikesam.org` Other programs: Same Inside, Thrive, the annual Gala, an Impact Report. ## Challenge Accepted **Tagline:** "Challenge yourself to step outside your comfort zone – try something new!" **What it is, in the program's own words:** teen meet-ups that bring students together through activities and experiences, designed to ignite existing passions or spark a new adventure. - **Grades 6–12** publicly. *(The form's dropdown starts at 5th — see gaps below.)* - **Free.** Say so explicitly and early; the form title itself shouts FREE. - Counties: Summit (Park City, North Summit, South Summit), Wasatch, Salt Lake. - Activity range: volunteering with animals and community orgs, outdoor skills, certifications, life skills, arts, sports. - Sign-up: one Google Form covering all events — `docs.google.com/forms/d/e/1FAIpQLSe0ttxECtC19SOiigFYSztvPYZfIbTGdj6M2W4KTkTtAgOnLA/viewform` **Existing referral mechanic:** "BRING A FRIEND! EARN A RAFFLE TICKET! / ¡Trae a un amigo! ¡Gana un boleto para la rifa!" — already live on the form. Use it in outreach copy; it's theirs, it's bilingual, and it directly attacks the "I don't want to go alone" barrier. --- ## Color — verified computed values | Role | Hex | Where it's used | |---|---|---| | Primary navy | `#002654` | Dark section backgrounds, the dominant brand color | | Deep navy | `#002244` | Headings, links, logo outline | | Sky blue | `#00AEEF` | Accent — "TEEN MEETUPS" in the logo | | Gold | `#FFB23D` | Accent — "challenge" in the logo, callout blocks | | Cream | `#F9F6EF` | Alternate section background, warm paper | | Body grey | `#4A4A4A` | Body copy | | White | `#FFFFFF` | Reversed type on navy | For the flyer template: ``` --brand: #002654 --accent: #FFB23D --ink: #002244 --paper: #F9F6EF --muted: #4A4A4A ``` Sky blue `#00AEEF` is the secondary accent — good for the kicker or a CTA button. Gold on navy is the highest-energy pairing and it's what the logo does; use it for the one thing you most want read. ⚠️ Ignore `#ff6900`, `#fcb900`, `#f78da7`, `#cf2e2e`, `#9b51e0`, `#8ed1fc` if you see them in the site source — those are stock WordPress editor defaults, not brand colors. ## Type **Acherus Grotesque** — Bold for headings and links, Regular for body. This is the font the site actually renders. The site also loads Lora and Nunito Sans from Google Fonts but **does not use them** — a leftover. Don't take them from the source; they'll look wrong next to anything real. Acherus Grotesque is a commercial face (not on Google Fonts), so for generated HTML flyers use **Poppins** as the fallback — geometric, tall x-height, closest free match. Montserrat is the second choice. If Jess has the licensed font, use the real thing. ``` --font-head: "Acherus Grotesque", "Poppins", "Helvetica Neue", Arial, sans-serif; --font-body: "Acherus Grotesque", "Poppins", "Helvetica Neue", Arial, sans-serif; ``` ## Logo `livelikesam.org/wp-content/uploads/2026/03/Challenge-Accepted-Logo-update-1.png` (492×247 PNG, transparent) A script wordmark — "challenge" in gold, "accepted!" in white with navy outline, a yellow sun, "TEEN MEETUPS" in sky-blue heavy sans, and the Live Like Sam roundel (goggled skier, navy) locked to the right. The script is part of the logo image, not a font you can set. **Never retype "Challenge Accepted" in a script face to imitate it** — place the logo. Keep it on white or cream; on navy it needs the reversed version, which we don't have yet. --- ## Voice Warm, direct, specific, unhurried. Write like a person who runs these programs and wants you there, not like an organization announcing an opportunity. The program's own copy already gets this right — it invites students whether they're coming with friends or alone. Keep that. **Say:** free · Saturday morning · a ride is available · no experience needed · you don't need to bring anyone · here's my cell **Don't say:** stakeholders · capacity-building · impactful · journey · empower · cordially invite · don't miss out "No experience needed" is the program's own phrasing on the form and it's doing real work — keep using it verbatim. ### Audience registers **Parents** — respectful, complete, no urgency games. They're approving, not attending. Answer in order: what, when, **free**, supervision, transport, waiver, who to call. A parent who can't find the price assumes it's expensive and stops reading. **Students** — short, concrete, no enthusiasm performance. Teenagers read manufactured excitement as an adult trying too hard. Always give permission to come alone — not knowing anyone is the most common silent reason a teenager doesn't sign up, and the raffle mechanic exists precisely to solve it. **Partners** — peer to peer. Brief, what they get, what you need, easy to forward. **Calendar editors and Peach Jar** — pure information, no voice. They cut anything with personality, so hand them the trimmed version and keep control of what survives. ### Sensitive framing Live Like Sam is a youth-wellbeing organization founded in memory of a young person. Unless the org says otherwise: - No exclamation points in parent-facing copy about wellbeing - Never imply that attending measures how much a family cares - Never use a teenager's struggle as a hook - Never invoke Sam's story as a persuasion device in event promotion — that is the organization's to tell, not a marketing asset - Where an event carries physical risk, state the supervision and safety arrangement plainly. Parents are deciding, and vagueness reads as risk ### Spanish `usted` for parents, `tú` for students. Parallel copy, not translation. Dates lowercase, no ordinals: `sábado, 22 de agosto`. The form already carries one bilingual line (the raffle). The **public website has no Spanish at all** — so for Spanish-speaking families, the flyer and Peach Jar PDF are currently the *only* Spanish touchpoints. That makes them load-bearing, not optional. Always flag that a fluent human should read Spanish copy before it goes out. --- ## Still needed from Jess - Licensed Acherus Grotesque files, or approval to use Poppins in generated flyers - A reversed (light-on-dark) logo - Mailing address for the bulk-email footer - Two or three best-performing past emails, and one that flopped — real examples calibrate voice far better than any adjective list - Whether the Summit-only line in the site metadata is current
<!--
FLYER TEMPLATE — fill the CSS variables from references/brand-kit.md
and the content slots from the event brief.
Renders two artboards from the same content:
· 8.5x11 print -> File > Print > Save as PDF (set margins to None, enable
"Background graphics"). Only this artboard prints.
· 1080x1350 -> screenshot at 2x, or right-click > Save image.
Every string marked {{LIKE_THIS}} is a slot. Delete the .optional blocks
that don't apply rather than leaving empty labels.
BILINGUAL: produce FOUR artboards, not two — duplicate both .artboard blocks
and fill the copy in Spanish for the second pair. Keep dates, times, and the
sign-up URL byte-identical across languages so nobody has to cross-check.
Spanish dates run lowercase with no ordinal: "sábado, 22 de agosto".
Set lang="es" on the Spanish artboards so screen readers switch voices.
Peach Jar takes both versions as separate single-page PDFs.
-->
<style>
:root {
/* ---- Live Like Sam brand — verified from livelikesam.org 2026-07-30 ---- */
--brand: #002654; /* primary navy — banner, headline, CTA fill */
--accent: #FFB23D; /* gold — kicker, rules, emphasis */
--ink: #002244; /* deep navy — body text */
--paper: #F9F6EF; /* warm cream — background */
--muted: #4A4A4A; /* body grey — secondary text */
--sky: #00AEEF; /* sky blue — secondary accent, CTA button */
/* Acherus Grotesque is the real site font but it's licensed and not on
Google Fonts. Poppins is the closest free fallback; swap in the real
files if Jess supplies them. */
--font-head: "Acherus Grotesque", "Poppins", "Helvetica Neue", Arial, sans-serif;
--font-body: "Acherus Grotesque", "Poppins", "Helvetica Neue", Arial, sans-serif;
}
.flyer-wrap { display: flex; flex-direction: column; align-items: center;
gap: 32px; padding: 24px; background: #ECEFF2; font-family: var(--font-body); }
.artboard { background: var(--paper); color: var(--ink); position: relative;
overflow: hidden; box-shadow: 0 6px 28px rgba(0,0,0,.14); }
/* artboard sizes */
.print { width: 8.5in; height: 11in; }
.social { width: 1080px; height: 1350px; transform-origin: top center; }
.pad { padding: 0.85in 0.8in; height: 100%; display: flex; flex-direction: column;
box-sizing: border-box; }
.social .pad { padding: 96px 88px; }
/* ---- banner ----
The Challenge Accepted logo is full-color on a light ground, so the banner
stays white/cream rather than navy. Don't put the logo on --brand; there is
no reversed version of it. */
.banner { background: #FFFFFF; margin: -0.85in -0.8in 0.44in;
padding: 0.3in 0.8in; display: flex; align-items: center;
justify-content: space-between; gap: 16px;
border-bottom: 4px solid var(--sky); }
.social .banner { margin: -96px -88px 50px; padding: 34px 88px; border-bottom-width: 7px; }
.banner .org { font-family: var(--font-head); font-weight: 700; font-size: 15pt;
letter-spacing: .02em; color: var(--brand); }
.social .banner .org { font-size: 30px; }
/* logo must read from across a hallway — do not shrink below these */
.banner img { height: 0.95in; width: auto; }
.social .banner img { height: 168px; }
/* ---- headline stack ---- */
.kicker { font-family: var(--font-head); font-weight: 700; font-size: 12pt;
letter-spacing: .16em; text-transform: uppercase; color: var(--accent);
margin-bottom: .16in; }
.social .kicker { font-size: 26px; margin-bottom: 18px; }
h1 { font-family: var(--font-head); font-weight: 800; font-size: 46pt;
line-height: .98; letter-spacing: -.02em; margin: 0 0 .18in; color: var(--brand); }
.social h1 { font-size: 104px; margin-bottom: 22px; }
.subhead { font-size: 15pt; line-height: 1.45; color: var(--muted);
max-width: 30ch; margin: 0 0 .42in; }
.social .subhead { font-size: 34px; margin-bottom: 52px; }
/* ---- detail rows ---- */
.details { border-top: 3px solid var(--accent); border-bottom: 3px solid var(--accent);
padding: .3in 0; margin-bottom: .38in; }
.social .details { padding: 36px 0; margin-bottom: 46px; }
.row { display: flex; gap: .28in; align-items: baseline; padding: .11in 0; }
.social .row { gap: 30px; padding: 13px 0; }
.row dt { font-family: var(--font-head); font-weight: 700; font-size: 10.5pt;
letter-spacing: .1em; text-transform: uppercase; color: var(--accent);
width: 1.5in; flex: none; }
.social .row dt { font-size: 23px; width: 190px; }
.row dd { margin: 0; font-size: 16pt; font-weight: 600; line-height: 1.3; }
.social .row dd { font-size: 36px; }
/* ---- CTA ---- */
.cta { margin-top: auto; display: flex; align-items: center; gap: .34in; }
.social .cta { gap: 40px; }
.cta-main { flex: 1; }
.cta-label { font-family: var(--font-head); font-weight: 800; font-size: 19pt;
color: var(--brand); line-height: 1.15; margin-bottom: .1in; }
.social .cta-label { font-size: 44px; margin-bottom: 12px; }
.cta-link { font-size: 14pt; font-weight: 700; color: var(--ink); word-break: break-all; }
.social .cta-link { font-size: 32px; }
.qr { width: 1.35in; height: 1.35in; border: 2px solid var(--ink); flex: none;
display: flex; align-items: center; justify-content: center;
font-size: 8pt; color: var(--muted); text-align: center; }
.social .qr { width: 230px; height: 230px; font-size: 18px; }
/* Footer overflows the 11in artboard if the content runs long and the last
line silently vanishes off the printed page. Keep LOGISTICS_LINE under
~90 chars and ACCESSIBILITY_LINE under ~60, and check the rendered
bottom edge before sending to print. */
.foot { margin-top: .26in; padding-top: .15in; border-top: 1px solid #D3DBE2;
font-size: 9pt; color: var(--muted); line-height: 1.45;
max-height: 1.1in; overflow: hidden; }
.social .foot { margin-top: 36px; padding-top: 22px; font-size: 20px;
max-height: none; }
.caption { font: 600 13px var(--font-body); color: #5A6B7A; letter-spacing: .08em;
text-transform: uppercase; margin-bottom: -18px; }
@media print {
.flyer-wrap { background: #fff; padding: 0; gap: 0; }
.caption, .social { display: none !important; }
.artboard { box-shadow: none; }
@page { size: letter; margin: 0; }
}
</style>
<div class="flyer-wrap">
<div class="caption">8.5 × 11 — print</div>
<div class="artboard print">
<div class="pad">
<div class="banner">
<span class="org">{{ORG_NAME}}</span>
<!-- <img src="{{LOGO_URL}}" alt="{{ORG_NAME}} logo"> -->
</div>
<div class="kicker">{{KICKER}}</div>
<h1>{{EVENT_NAME}}</h1>
<p class="subhead">{{HOOK_SENTENCE}}</p>
<dl class="details">
<div class="row"><dt>When</dt><dd>{{DAY}}, {{DATE}}<br>{{START_TIME}}–{{END_TIME}}</dd></div>
<div class="row"><dt>Where</dt><dd>{{VENUE}}<br>{{ADDRESS}}</dd></div>
<div class="row"><dt>Who</dt><dd>{{AUDIENCE}}</dd></div>
<div class="row"><dt>Cost</dt><dd>{{COST}}</dd></div>
</dl>
<div class="cta">
<div class="cta-main">
<div class="cta-label">{{CTA_LABEL}}</div>
<div class="cta-link">{{SIGNUP_URL}}</div>
</div>
<div class="qr">QR code<br>for<br>{{SIGNUP_URL_SHORT}}</div>
</div>
<div class="foot">
{{LOGISTICS_LINE}}<br>
Questions? {{CONTACT_NAME}} · {{CONTACT_EMAIL}} · {{CONTACT_PHONE}}<br>
<span class="optional">{{ACCESSIBILITY_LINE}}</span>
</div>
</div>
</div>
<div class="caption">1080 × 1350 — social</div>
<div class="artboard social">
<div class="pad">
<div class="banner"><span class="org">{{ORG_NAME}}</span></div>
<div class="kicker">{{KICKER}}</div>
<h1>{{EVENT_NAME}}</h1>
<p class="subhead">{{HOOK_SENTENCE}}</p>
<dl class="details">
<div class="row"><dt>When</dt><dd>{{DAY}}, {{DATE}} · {{START_TIME}}</dd></div>
<div class="row"><dt>Where</dt><dd>{{VENUE}}</dd></div>
<div class="row"><dt>Cost</dt><dd>{{COST}}</dd></div>
</dl>
<div class="cta">
<div class="cta-main">
<div class="cta-label">{{CTA_LABEL}}</div>
<div class="cta-link">{{SIGNUP_URL}}</div>
</div>
<div class="qr">QR code<br>for<br>{{SIGNUP_URL_SHORT}}</div>
</div>
<div class="foot">{{LOGISTICS_LINE}} · {{CONTACT_EMAIL}}</div>
</div>
</div>
</div>
Skills you upload this way are yours alone. If Lauren needs them too, she can upload the same zips to her own account — or an Owner can provision them organization-wide from admin settings so everyone gets them at once.
Click Scheduled in the left sidebar, then New task in the upper right, then Set up manually. Copy each block below into the prompt field and set the schedule shown. Start with the first one — add the other two once you've seen it work.
It's an optional field near the bottom of the form, and it's the one thing that will pin the task to your laptop. Skip it. These tasks read your Drive and Gmail through connectors — they never need a folder on your computer.
If the form requires a folder before it'll let you save, you're in the wrong place. See step 5b.
Run the Challenge Accepted operating brief for today using the challenge-accepted-brief skill. Read the CA Comprehensive | Challenge Accepted workbook in Google Drive — the Scheduled Events, Ideas & Tasks, Outreach, and Partner Contacts tabs — and my email for anything from partners, the interest form, or registrations since yesterday. Produce the brief in the skill's format, ordered by what can hurt us: registration alarms first, then unowned or overdue hard blockers, then today's tasks, this week, partner silence, and anything needing my decision. Email it to me as plain text, subject "Challenge Accepted — [day], [date]". Keep it to one screen on a phone. Rules: - Draft the recovery sends and follow-ups so they're ready, but do not send anything to anyone. Every outward message is mine to send. - Do not write to the workbook. - Use only connectors. Do not reference local files, my desktop, or my browser — this task must be able to run with my computer off. - If a tab or my inbox is unreadable, say so in the brief and continue with the rest. - Report interest and registration as two separate numbers. A checkbox on the interest form is not a confirmed spot. - Never invent a registration count. If it isn't tracked anywhere you can read, say that plainly. - Never put a student's name, email, phone, birthday, or ethnicity in the brief. Counts and aggregates only. - Delete empty sections rather than printing them empty. If today is the day before an event, make sure the day-before reminder email is drafted and flagged, including a weather line if the event is outdoors.
Run the Challenge Accepted weekly outreach push using the challenge-accepted-event skill for anything that needs drafting. Read the CA Comprehensive | Challenge Accepted workbook — Scheduled Events, Outreach, and Ideas & Tasks. For every event with a date in the next 35 days, work out where it sits in the Week One / Week Two outreach cadence and what has not been done yet, using the Outreach tab's Incomplete markers as the source of truth. Then draft everything due this week, ready to copy and send: - Student outreach email - Parent outreach email, English and Spanish - Community partner email - Community calendar submissions — KPCW, TownLift, Park Record, Wasatch Wave. One distinct 25-50 word blurb per outlet plus a short submission email to the named contact. Do not reuse the same paragraph across outlets. - Peach Jar submission, English and Spanish - Instagram and Facebook group posts, with alt text - Last-call email and text if the event is inside 5 days - SMS drafts with the character count and segment count stated Flag separately: - Any event under the registration checkpoint thresholds, with recovery options and the highest-value one drafted - Any Week One item still incomplete when the event is inside 14 days — that's a missed channel, call it out as a loss - Any flyer that exists in English but not Spanish Deliver as a Google Doc named "Challenge Accepted — outreach week of [date]" and email me the link with a three-line summary. Rules: - Draft only. Send nothing to anyone — not families, not partners, not calendar editors. - Do not write to the workbook. - Connectors only. No local files, no browser, no computer use — this must run with my computer off. - Every Spanish asset carries a note that a fluent human should read it before it goes out. - Never invent mission statements or statistics. Leave org-specific claims as bracketed placeholders if unsure.
Run the Challenge Accepted outcomes pass using the challenge-accepted-outcomes skill. Read the CA Comprehensive | Challenge Accepted workbook. Find every event whose date fell in the last 10 days and whose outcome columns in Scheduled Events are still empty. For each one, gather what you can from the interest form responses and the attendance sheet: number interested, number attended, grade split, and county split. Then show me the exact rows and values you propose writing and wait for my yes before writing anything. Do not write first and tell me after. Also produce, in the same message: - Post-event emails for attendees and for non-attendees, drafted and ready - The follow-up survey email - Volunteer / next-step interest follow-ups, split into "wants to volunteer with us" and "wants connecting to a partner org" Once five or more events have complete numbers, add the analysis: interested to registered to attended conversion, which step leaks most, ranking by event type and by grade band and county, plus a normalized ranking of the "How did you find out about the program?" answers so we can see which outreach channels actually work. Rules: - Never fabricate a number. A blank cell is a finding; an invented number is a lie that gets planned against. - State the sample size every time you report a trend. - Write only to the Scheduled Events tab, only after my yes, and never over a non-empty cell without flagging it first. - Send nothing to anyone. - Connectors only. No local files, no browser, no computer use. - Report aggregates only — never an individual student's name, email, phone, birthday, or ethnicity. Use "under 5" rather than a number for any group smaller than five. If there were no events in the last 10 days, say so in one line and stop. Don't manufacture a report.
There is no cloud-or-local switch to look for — that's not how it works, so don't hunt for one. Where a task runs is decided by which screen you created it on and whether you attached a folder.
Anthropic ships two different scheduling screens that look similar. Check your left sidebar:
| Says "Scheduled" | Says "Routines" | |
|---|---|---|
| You're in | Cowork — the right place | Claude Code — a developer tool |
| Button reads | New task | New routine |
| Folder field | Optional — leave it blank | Required, and it pins the task to this computer |
| Where it runs | Anthropic's servers | Your machine, only while the app is open and awake |
If your sidebar says Routines, that's the whole problem. Those tasks run on your laptop by design and always will. Delete them and rebuild in Cowork under Scheduled.
If your sidebar says Scheduled and it's still only running locally, then one of two things is true, and both are quick to check:
Send a screenshot of the left sidebar and the new-task form. Cowork is still in beta and rolling out plan by plan, so it's possible the cloud half hasn't reached your organization yet. That's not something you can fix from settings — but there's a different way to build this that doesn't depend on it at all, and it's a short conversation.
Prove it works
After creating each task, hit Run now and stay with it. It'll ask permission to read your email and your Drive. Approve each with "always allow" so it doesn't have to ask again at 7am when you're not there.
Step 2's third setting didn't take. Go back and fix it before relying on any of this — otherwise every unattended run will stall waiting for you.
Start with the daily brief on its own. If it reads the workbook and sends you something sensible, the two things most likely to break are both proven.
This is the one that proves what you actually wanted — that it doesn't need your laptop open.
If it's there at 7am, you're done. It's running on Anthropic's servers and it will follow you between machines from now on.
If it arrives at whatever time you opened the lid, something is still running locally. Tell Benson — it's fixable, and it's almost always a task instruction mentioning a file on your computer.
Using it
The three tasks run themselves. This is the one thing you do by hand, and it's the part that saves the most time.
Open Cowork, start a new chat, and paste the template below with your details filled in. You'll get back a dated plan for the whole event and every piece of outreach, in English and Spanish.
Plan this Challenge Accepted event and build the outreach kit. Event: What it is: (one plain sentence — what actually happens) Date: Time: Location: (venue and full address) Partner: Grades: (6-8, 9-12, or both) County: (Summit, Wasatch, or both) Cost: (free, or the amount) Capacity: Sign-up: https://livelikesam.org/challenge-accepted Contact: (name, email, phone) Nice to have if you know it: What to bring: What's provided: Carpool available: Parking / directions: Waiver: (ours or the partner's) Why a teenager would give up a Saturday for this: Anything you don't know, mark it TBD and build the kit anyway.
You don't have to fill everything in. Anything missing comes back marked so you know what to chase.
| Say this | You get |
|---|---|
| "Where are we on the CPR event?" | Sign-ups, what's blocked, what's due |
| "Draft the last-call email for Saturday" | One asset instead of the whole kit |
| "How did the dairy farm event do?" | Attendance, interest, and how it compares |
| "Which outreach channels are actually working?" | A ranking built from the "how did you hear about us" answers |
| "Log the outcomes from last weekend" | The numbers written into the workbook, after showing you first |
| What you see | What it usually means |
|---|---|
| No brief in the morning | Step 2's "Always allow" setting is off, so the run stalled waiting for permission. Fix it, then hit Run now and approve with "always allow." |
| Brief arrives when you open the laptop, not at 7am | The task is running locally — see step 5b. Either it was created under "Routines" instead of "Scheduled," or it has a folder attached. |
| You went looking for a cloud/local toggle and there isn't one | Correct — there isn't. It's decided by which screen you built the task on and whether you attached a folder. Step 5b. |
| "I couldn't read the workbook" | The Google Drive connector disconnected, or the workbook was renamed or moved. Reconnect in Cowork → Connectors. |
| Registration numbers look wrong | Probably right, and it's the form. Events with past dates are still selectable, which inflates interest counts. |
| Skill won't upload | Code execution isn't enabled (step 2), or the zip has a folder inside a folder. The skill folder must sit at the root of the zip. |
| Claude ignores the skill | Check it's toggled on under Customize → Skills. If it is, name it directly: "using the challenge-accepted-event skill…" |
| Spanish reads oddly | Expected — it always needs a fluent human read before it goes out. That's flagged on every Spanish asset for a reason. |
| It drafted something factually wrong about Live Like Sam | Tell Benson the specific claim. The brand file deliberately leaves the mission and history blank so nothing gets invented — if something slipped through, that's a gap worth closing. |
Keep this around
Pulled from livelikesam.org. Click any swatch to copy the code — useful when you're building something in Canva and want it to match.
Your typeface is Acherus Grotesque — bold for headings, regular for body. It's licensed, so anything generated automatically falls back to Poppins, the closest free match. If you have the font files, send them over and we'll use the real thing.
One thing worth knowing: the website also loads two other fonts (Lora and Nunito Sans) that it never actually uses. If a designer ever pulls fonts from the site's code, they'll get the wrong ones.
Emails, texts, calendar submissions, partner messages — all drafted and handed to you. Every message that leaves the organization is still yours to send. That's deliberate.
Only the outcomes task writes anything, only to the Scheduled Events tab, and only after showing you the exact numbers and waiting for a yes.
If a count isn't there, it says so rather than guessing. A blank is useful information; an invented number gets planned against.
The interest form collects a lot about minors — birthdays, phone numbers, ethnicity. Nothing individual ever appears in a brief or a report. Counts and aggregates only, and any group under five is reported as "under 5."
Found while reading through the workbook, the site, and the sign-up form. None urgent — just worth a look when you have a minute.