Setting Up a Three-Person Wake-Up Pod Without It Falling Apart

Three people is the smallest group that can survive one person having a bad week. A pair collapses the moment either half goes easy on the other; a pod of six diffuses responsibility until nobody actually checks. Three keeps enough social weight to matter and few enough people that nobody can hide in the crowd. It only works, though, if you agree on the mechanics before anyone misses a wake-up — arguing about the rules after the first slip is how pods die in week two.

Do these five things at setup, in order:

1. Pick a single proof format, in writing, before day one. “A photo” is not a rule. “A photo of the kitchen clock plus your face, sent by 7:15 AM” is a rule. Vague proof standards are where every pod’s first real fight starts, because two people will remember the agreement differently.
2. Name the exact response window. Decide how long a member has to post proof after their target time — five minutes, fifteen, thirty — and write the number down. An undefined window means someone posts at 7:52 for a 7:00 alarm and nobody knows if that counts.
3. Assign who calls a miss, not just what happens after one. Pods often agree on a consequence but never agree on who’s responsible for actually flagging that the window passed. Without an assigned caller, everyone assumes someone else is watching, and misses go unrecorded.
4. Decide the miss consequence before anyone needs it. A small, immediate cost — sending the other two $5, doing ten burpees on video, buying the next coffee round — works better than a vague “we’ll talk about it,” because a vague consequence gets negotiated down in the moment.
5. Set one no-questions-asked pass per person per month. Real life produces genuine exceptions — a flight, a stomach bug, a 3 AM hospital run. A pod with zero flexibility breaks on the first legitimate emergency; a pod with unlimited flexibility never enforces anything. One pass, no discussion required, splits the difference.

The rule that saves the most pods isn’t rule three or four — it’s rule one. Most pod arguments aren’t about whether someone missed. They’re about whether what they sent counted.

None of this requires trust in each other’s character. It requires agreement on five specific numbers and one job assignment, settled once, before the group needs any of them. DontSnooze automates rules two, three, and four for a pod once you’ve agreed on them — the app tracks the window, flags the miss, and logs it for all three of you — but the five decisions above still have to happen between the three humans first. No app can settle rule one for you.