Your 35-Pound Bag Is a Theoretical Exercise (Not Gear)
**What actually matters here?** Whether you'll move when it counts. And I'm going to be direct: most people who build a 35-pound 72-hour bag have never carried it more than from the car to the bedroom.
**Why the weight matters.** A loaded pack at that threshold isn't worn—it's dragged. After mile two, your shoulders remember it. After mile five, you start making compromises: ditching water, dropping the medical kit, leaving behind the thing you packed specifically for day three. That's not a backup plan; that's a liability.
**The gap between 'what I built' and 'what I'll actually carry.'** I see this constantly. Someone specs out a bag with the right plates, the right meds, the redundant comms, and they test it once in their driveway. Then the scenario happens—an actual evacuation, not a drill—and suddenly weight distribution and carry time matter in ways the internet checklist didn't predict.
**Here's what I'd do instead.** Build to 20 pounds first. That's your baseline—water, food, shelter basics, a quality medical kit, a light source, nav tools. *That* weight you can move with. Then add to 28 pounds if your specific use case demands it (overland trip, actual wilderness buffer, known terrain with distance). Anything beyond that is optimization theater.
**The 72-hour conversation changes when you add terrain and fatigue.** A 35-pound bag works great on YouTube. It works great in your garage. On foot, in daylight, carrying it three miles while managing stress? Different animal. That's when you find out whether you actually trained with the load or just bought it.
**My recommendation:** Weigh what you have. Pick it up. Walk it a full mile at a normal pace. If you're thinking about setting it down before you hit the one-mile mark, you already know the answer. Strip it down, keep what matters, and make it something you'd actually move with under pressure. Training with the real weight beats owning the theoretical one.