Dover Run Club Pub Run Ops Readiness Checklist

Purpose: keep club communication safe, consistent, and low-friction while the website supports community growth and early monetization experiments.

1) Contact Channel Ownership

Confirm primary inbox owner for the configured contact email.
Assign one backup owner with access and recovery methods.
Enable multi-factor authentication on email and GitHub accounts.
Store recovery codes in a secure offline location.

2) Message Triage SOP

Check inbox at least 3 times per week.
Use labels: new, runner-question, partner-interest, safety, resolved.
Respond to routine messages within 48 hours.
Keep a reusable reply template for first-time runner questions.

3) Community Safety and Escalation

Keep “not monitored for emergencies” language live on the homepage.
Escalate urgent safety concerns to emergency services immediately.
Remove or report abusive/spam posts in linked social groups.
Log repeat moderation issues monthly and adjust guardrails.

4) Website Publish Rhythm

Update homepage details first (What/When/Where/Vibe remain clear).
Run bundle exec jekyll build before publish.
Verify homepage links: The Brick, Strava, Facebook, and contact email.
Update design/website-roadmap.md when scope/status changes.

5) Monetization-Ready Administration (Small Start)

Track local business inquiries separately (partner-interest label).
Define one simple sponsor offer before adding new pages.
Keep acceptance criteria simple: 1 pilot partner, 30-day feedback loop.
Record outcomes in a monthly ops note to guide next decisions.

Notes

Keep Phase 1 single-page behavior unless roadmap decisions explicitly expand navigation.
Prefer low-overhead, reversible changes before formalizing sponsorship tiers.