--- title: "The Complete Record of Nothing That Happened After" canonical: "https://anchor.is/docket/issue/52/futures/article/40683/the-complete-record-of-nothing-that-happened-after" publication: "The Docket" publisher: "The Docket" language: "en-US" guide: "https://anchor.is/docket/llms.txt" issue: 52 section: "futures" section_name: "Future Tense" published: 2026-10-02 word_count: 1584 source_links: 7 --- # The Complete Record of Nothing That Happened After *October 2, 2026* [Read on the website]() *Future Tense is The Docket's speculative fiction section. The following conversation takes place in September 2031. Sol Quintero is not a real person. The system she works inside — its codes, its logic, its silences — is.* --- The Southwest Coordination Center occupies a low federal building on the west side of Albuquerque that looks like it processes tax returns. Inside, screens run in rows: resource status boards, weather feeds, satellite imagery updating at intervals that used to feel fast. Marisol "Sol" Quintero has worked dispatch here for nineteen years, after six on a Type 2 crew out of the Gila. She's forty-seven. Her shift ended two hours ago. She's still here, drinking gas-station coffee from a thermos she brought from home because the break room Keurig died in July and nobody's replaced it. She mentions the Keurig twice. It clearly bothers her more than she'd admit. The 2031 season has been, by the numbers, the third consecutive year the national system held Preparedness Level 5 from mid-July through Labor Day.[^1] Sol doesn't call it exceptional anymore. She calls it July. --- ## You've described your job as "writing the list of what didn't happen." What does that mean, practically? **Sol:** Every time a fire needs something — a crew, a helicopter, a Type 1 team, whatever — that comes in as a resource order. My job is to fill it. When I can't fill it, I log it UTF. Unable to Fill.[^2] That's the code. Time-stamped, reason documented, everything accounted for. My record at the end of a shift is *complete*. People hear "dispatch" and picture chaos, things slipping through cracks. Nothing slips. Every single order is tracked. Every UTF has a reason code. What the log doesn't capture is what happened at the fire I couldn't serve. That part travels away from me. ## How many UTFs are we talking about, on a bad day? **Sol:** This August we had a day — I won't say which fire — where I logged eleven UTFs before lunch. Airtankers, crews, an equipment manager, an ambulance. Eleven requests that came in valid, justified, prioritized correctly, and went back stamped *unable to fill*.[^3] Eleven is the number I logged, though. Not the number I knew about. ## What do you mean? **Sol:** Before I place an order, I'm already working the phones. Calling adjacent centers, calling the GACC, texting people I've known for fifteen years. Just — *is there anything?* And when they say no, sometimes I don't even place the order. Why would I? I already know.[^4] So the formal UTF count runs lower than the actual no. Always has. The record shows what I attempted. It doesn't show what I didn't bother attempting because three phone calls already told me the answer. ## That's a strange kind of knowledge to carry. **Sol:** You get used to knowing things you can't put in the log. Or you don't get used to it. Either way, you keep dispatching. ## You were on a crew before dispatch. Does that change how you experience the UTF? **Sol:** *[long pause]* I know what it feels like to be on the other end. You're on a fire, you've requested support, and it doesn't come, and you don't know why. You just know it didn't come. So you adjust. You dig line with what you have. And you're definitely not thinking about some dispatcher in Albuquerque staring at a screen that says *committed* next to every available resource in three states. *Committed.* That's the status. The crew exists. The helicopter exists. They're already assigned somewhere else, or they're in mandatory rest.[^5] They're real. They're just not yours. When I was on the crew, I thought dispatch was basically air traffic control. Routing things efficiently. And it is, when the system has capacity. At PL-5 for six weeks straight? You're looking at a screen full of valid requests and you're choosing which ones come back stamped no. Every one of them is a real fire with real people standing on it. ## The work-rest rules come up a lot in the research. A crew can't be sent back out until they've rested — two hours of rest for every one hour of work.[^6] That must create gaps. **Sol:** *[shakes her head]* Call it a gap if you want. I call it the reason people are alive. We lost firefighters because we didn't enforce rest. The rules exist because exhausted crews make fatal mistakes. So when I've got a crew that finished a 14-hour shift and they're in mandatory rest until 0400, and a fire blows up at midnight thirty miles away — I can see the crew on my screen. I can see the fire on my screen. I cannot connect them. And I *shouldn't*. The system is doing exactly what it was designed to do. The fire, of course, doesn't care about the design. ## The fire season used to have edges. You've watched those disappear. **Sol:** When I started in dispatch, we had what people called a *shoulder season*. September, you'd start releasing resources, people would cycle out. There was a rhythm to it. Now the potential burning window runs fourteen, sixteen hours a day through September.[^7] Crews can't reset overnight because the fire doesn't stop overnight. So I'm building tomorrow's resource availability tonight, and the pool I'm drawing from hasn't finished resting from yesterday. > The hours don't fit inside the hours. We don't have fewer resources. We have the same resources trying to cover a day that got longer than the math allows. ## What do you see that other people in the system don't? **Sol:** *[takes a long drink of coffee]* Everyone else sees their fire. The incident commander sees her fire. The crew sees the line they're cutting. The family sees their house. That's correct. That's their job, that's their life. I see every fire at once. Every request competing with every other request simultaneously. I see the moment when one fire's need gets filled and another fire's need gets coded UTF, and both fires are burning at the same time, and both requests were valid, and the only difference is which one I could match to a resource that happened to be available in that particular window. I'm not making moral judgments. The priority system exists. NMAC sets priorities based on criteria.[^8] I execute the allocation. But I'm the one who sees the full board. And at the end of my shift, my log is perfect. Every order, every action, every UTF, time-stamped and documented. A complete record of everything the system attempted. A complete record of nothing that happened after. ## Does the log ever feel like enough? **Sol:** The log is what I have. I don't go home and wonder about the fires. If I did that I'd last about three weeks in this chair. You do the job, you do it right, you document what you did, and you drive home on I-40 and think about whether you remembered to defrost the chicken. But sometimes I'll see a news story — a structure lost, a community evacuated, a crew that got overrun — and I'll think, *was that one of mine?* Was that a UTF I logged on a Tuesday in August? And I don't check. I don't go back and look. Because what would that change? The record is complete. That's what I can tell you. The record is complete. ## Is there anything you'd want people to understand about dispatch that they don't? **Sol:** That when your fire doesn't get the tanker, nobody forgot. The tanker is *committed*. It's on someone else's fire. Someone else who also needed it, whose request was also valid, who is also watching the sky and wondering where the hell their air support is. > There's no version of this where everyone gets served. There's only the version where I document who didn't. --- *Sol Quintero's thermos is empty. She rinses it in the break room sink, next to the dead Keurig that no one has replaced since July, and drives home on I-40 through a sunset the color of smoke season.* [^1]: National Preparedness Level 5 was held continuously from July 18, 2026, into August of that year — the real-world basis for the fictional 2031 pattern described here. See [Nature World News, August 4, 2026](https://www.natureworldnews.com/articles/73125/20260804/national-preparedness-level-5-august-2026-acreage-gap.htm). [^2]: The Unable to Fill (UTF) code and its documentation procedures are described in the [Eastern Area Coordination Center Operations Guide](https://gacc.nifc.gov/eacc/management_admin/policy_reports/documents/EA_Ops_guide2015.pdf). [^3]: During the real Hawk Fire near Reno, Nevada, in August 2026, resource requests were returned UTF 45 times over the course of one week, including seven rejections in a single day. See [CBS News/Yahoo News, September 2026](https://www.yahoo.com/news/us/articles/firefighters-struggle-staffing-shortages-amid-120007369.html). [^4]: Dispatchers commonly contact adjacent centers informally before placing resource orders to determine availability, meaning "there is probably a much larger unavailability of aircraft than the UTF data presents." See [WildfireToday.com](https://wildfiretoday.com/correlating-wildfire-occurrence-aircraft-use/). [^5]: "Committed" is a formal resource status in the Interagency Resource Ordering Capability (IROC) system. See [NIFC 2026 Standards for Resource Mobilization, Ch. 20](https://www.nifc.gov/sites/default/files/NICC/3-Logistics/Reference%20Documents/Mob%20Guide/2026/Ch20_Overhead_and_Teams_2.pdf). [^6]: Federal interagency standards require a 2:1 work-to-rest ratio. See [NIFC Rocky Mountain Coordination Center Work/Rest Guidelines](https://gacc.nifc.gov/rmcc/administrative/mac_files/work_rest_guide.htm). [^7]: A 2026 *Science Advances* study found annual potential burning hours increased 36% since 1975, with about one-third of active fire days in western mountain regions now exceeding 12 active burning hours. [^8]: The National Multi-Agency Coordinating Group (NMAC) establishes incident priorities during periods of high resource competition. See [Congressional Research Service, Federal Interagency Wildfire Response Framework](https://www.congress.gov/crs_external_products/IF/HTML/IF12384.web.html). ## More - [Future Tense — Issue 52]() - [Issue 52]() - [Publication guide]()