**TL;DR.** Two emails went live today. If you're a coach, you'll get a notification the moment a new member lands on your roster — name + one click into their profile. If you're a member, starting next Friday at 4pm in your local time zone, you'll get a one-week recap: applications submitted, interview invites, offers, and what's still in the queue. Quiet weeks get nothing.
Both emails use the same HiringFunnel design as the daily digest. We don't send anything you didn't earn — empty weeks are silent.
Why these two
Coaches told us the slow part of onboarding a new member wasn't the routing logic — it was learning *that* a member had landed. Until now, you found out by refreshing the dashboard. Now you find out by checking your inbox.
Members told us the daily digest was great for hot signal (interview invite came in this morning) but didn't replace the conversation about progress over a week (am I applying enough? are interviews picking up? what should I focus on next week?). The Friday recap is the answer.
Neither of these add a setting. There's nothing to configure. They just start working.
What the Friday recap actually contains
Four counters over the last seven days, only the non-zero ones render:
Applications submitted: — every job your worker (or your VA) successfully applied to.
Interview invites: — emails our classifier flagged as a real invite (not a recruiter mass-blast).
Offers: — actual offer letters, also classified from your inbox.
Outstanding queue: — jobs already scored, waiting in your queue to be applied to.
If a week was genuinely empty — no apps, no invites, no offers, nothing queued — you get no email. We want this to be useful, not noisy.
The subject line is **"{First}, your week in review."** The CTA goes straight to your dashboard.
What the coach ping contains
Subject is **"{Member name} is on your roster."** Body says who landed and links straight to their profile page. That's it. Sent the moment routing assigns them, not on a delay.
What's next
We're already triaging a small data-quality finding from today's prod smoke (six members had non-standard time-zone strings stored from an older intake flow — they'd been silently skipped from the daily digest too, and the fix lands separately). After that, the next move is whatever you tell us: reply to the recap and let us know if the cadence, the counters, or the framing should shift.
This is the first "what we shipped" post. The plan is to keep these tight: what changed, why it changed, and what you should expect to see in your inbox or your dashboard. No marketing.