Decision Memo — DM-004 — Early Logistics Decisions
Session: 4 Date: 2026-04-20 Topic: What the group needs to decide now vs. later; outstanding logistical questions
Purpose
This memo organizes the group's outstanding decisions by urgency: what must be decided now, what should be decided closer to the event, and what can be decided on arrival.
Decide now (before summer 2026)
1. Get tickets
Status: Unknown — depends on whether Lakes of Fire 2026 is on sale. Action: The developer should check Lakes of Fire 2026 registration status. Regional burns often sell out early (some with ticket lotteries or registration windows). Missing the window is a real failure mode. Owner: Developer (event-culture knowledge; likely knows how ticketing works)
2. Confirm the trip duration and travel dates
Status: Unknown. Action: Confirm when Lakes of Fire 2026 begins and ends. Plan arrival for setup day (typically one day before gates officially open). Plan departure for the day after strike. Build travel days into the timeline. Owner: Group decision; developer initiates
3. Vehicle plan
Status: Unknown. Questions to answer: - How many vehicles are making the trip? - Can all gear (shade structure, water containers, generator or battery system, coolers, tents, packing) fit in one vehicle? - If not, what requires a second vehicle? - Who is driving which vehicle, and is anyone carpooling from different locations? Owner: Matt (logistics lead); developer provides event packing context
4. Generator or solar + battery?
Status: Unknown — depends on site rules. Action: Verify Lakes of Fire 2026 generator rules and amplified sound rules before Matt commits to a power setup. Owner: Developer researches rules; Matt decides based on findings
5. Pre-event group conversation
Status: Not yet scheduled. Action: Schedule a specific conversation — in person or video — where the developer walks Amber and Matt through the event model, what to expect, what surprised them, and the pre-event checklist review. This is a required deliverable, not an optional nice-to-have. Owner: Developer sets time; all three attend Timing: At least 4–6 weeks before the event
Decide closer to event (1–3 months before)
6. Group food plan
What to decide: - How many shared meals per day (current target: 1) - Who is responsible for which meals - Perishable shopping timing (when to buy, where to pick up ice) - Any dietary restrictions or preferences that affect group cooking
7. Campsite size and layout plan
What to decide: - What is the campsite footprint at Lakes of Fire? Are sites pre-assigned or first-come? - Matt designs camp layout once dimensions are known: shade area, sleep tents, kitchen, gray water location, landmark position
8. Sound equipment scope
What to decide: - Does Matt want to bring sound equipment for camp use? - What amplified sound rules apply? - Is the group interested in any informal "music at camp" offering?
9. Group gifting item
What to decide: - Does the group want to bring something giftable? - If yes: what, how many, who makes/procures/carries it? - Keep decision simple: yes/no, then one item, low-burden, 30–50 units
10. Volunteer plan
What to decide: - Does anyone in the group want to volunteer for event functions (setup crew, gate crew, Rangers)? - Volunteering at most regionals earns perks (early access, ticket discounts, deeper community connection) - Developer should research Lakes of Fire 2026 volunteer opportunities and bring options to the group
Decide on arrival
- Tent positioning (relative to sun angle, drainage, neighbor camps, sound sources)
- Exact camp layout within the site
- Which art installations and sound camps are worth prioritizing once the site map is in hand
Open research questions that block decisions above
| Question | Blocks | Action |
|---|---|---|
| Lakes of Fire 2026 ticket sale dates and process | Decision 1 (tickets) | Developer checks LoF website / email list |
| Event dates and duration | Decisions 2, 6, water math | Developer checks LoF website |
| Campsite assignment process | Decision 7 | Developer checks LoF website |
| Generator rules | Decision 4 | Developer checks LoF event guide when available |
| Amplified sound rules | Decision 8 | Developer checks LoF event guide |
| On-site water availability | Water planning | Developer checks LoF resources |
Summary of what's unblocked today
The following can be acted on without additional research:
- The developer can check LoF 2026 registration status right now. If tickets are available, buy them.
- The developer can schedule the pre-event group conversation. This does not require any event-specific details.
- Matt can begin assembling the shade structure, cooking kit, and water containers from the INFRA checklist memo — these don't depend on site-specific rules.
- Each group member can review their personal packing checklist (see PACKING-framework.md) and identify what they're missing.
Decision memo
- Keep: This framework as the logistics tracking document — update when decisions are made
- Assign: Developer owns all "research LoF 2026 details" actions; brings findings to the group
- Assign: Matt initiates vehicle plan conversation with the group
- Assign: Developer schedules pre-event group conversation
- Reject: Waiting on event details before starting gear procurement — most gear decisions don't depend on site-specific rules
- Revisit: This memo at the pre-event group conversation to confirm all decisions are made