Thursday, 23:50. The progress bar on the screen hasn’t moved for ninety-two seconds. Tom taps the side of the laptop, a gesture of purely superstitious engineering, and the software finally collapses into a ‘Not Responding’ white-out. It is the eighth time since dinner. In a portacabin tucked behind the production compound of a city-park festival in Manchester, the air smells of wet polyester and the kind of cheap energy drink that makes your teeth feel fuzzy. The rain is a steady, rhythmic drumming on the corrugated metal roof, a metronome for a task that has no end in sight.

Priya, the event coordinator, doesn’t look up from her clipboard. She is staring at a stack of cardboard boxes that contain 10,000 blank RFID wristbands. To anyone else, they are just colorful loops of fabric and plastic. To Priya, they are 10,000 individual failures of procurement. Beside her, an intern named Bea is methodically tapping a wristband against a small desktop reader. *Beep.* A green light. She sets it in the ‘done’ pile. *Beep.* Green light.

The Discovery at 03:10

At 03:10, the silence is broken by a soft gasp. Bea has been staring at row 4,812 of the master spreadsheet. She realizes that the UID-the unique identifier for the chip-has been written twice. Somewhere in the mountain of three thousand ‘completed’ bands, there is a duplicate. If two people show up at the gate tomorrow with the same encoded ID, the system will flag the second one as a fraudulent clone. The gate will lock. The queue will swell. The radio will crackle with the stressed voices of security guards who don’t care about software glitches.

“We don’t know which one it is.”

– Bea, intern

Tom looks at the three boxes of finished bands. He looks at the clock. He looks at the door, which I earlier tried to push open despite the very clear ‘PULL’ sign bolted at eye level. We are all prone to missing the obvious when the pressure is high enough. Tom doesn’t suggest re-scanning the three thousand bands. He just clears the error and tells Bea to keep going. He is gambling on a statistical probability that the two people holding those specific bands won’t arrive at the same entrance at the same time. This is how festivals are built: on a foundation of exhausted gambles.

The Poison of Heroics

The problem isn’t the software crash, or the duplicate entry, or the rain. The problem is that this night is currently being classified as a “great team effort.” In the debrief meeting on Monday, someone will mention how Priya, Tom, and Bea stayed up until 4:00 AM to “get the job done.” They will be praised for their dedication. There might even be a round of drinks. And because the rescue succeeded-because the gates opened and the bands mostly worked-the cost of the failure will remain invisible.

The heroics are the poison. When an organization rewards the midnight scramble, it silently decides that prevention is a waste of money.

If the bands had arrived from the factory already encoded, UID-printed, and verified, the portacabin would have been dark. The team would have been sleeping. But that would have required a line item on a purchase order months ago. It would have required a decision made in the light of day, rather than a frantic correction made in the dark.

The Architecture of the Grid

As a crossword constructor, I spend my life obsessing over the grid-the underlying structure that makes the surface possible. If I screw up the numbering of 14-Across, the entire Southeast corner of the puzzle becomes an unsolvable mess of nonsense. You can’t ‘hero’ your way out of a bad grid once the ink is dry. You have to get the architecture right before the first clue is written.

In the world of event tech, the ‘grid’ is the data. If you are encoding bands on a trestle table hours before doors open, you aren’t building a festival; you are trying to fix a broken grid while the players are already waiting with their pens out.

The 13.56 MHz Handshake

Every phone ping or microwave burrito in the portacabin shifts this fragile electromagnetic environment, causing the handshake to fail.

To understand why this happens, you have to look at how the handshake actually works. When Bea taps a wristband on that desktop writer, a very specific sequence of events occurs in a fraction of a second. The writer emits an electromagnetic field at 13.56 MHz. The copper antenna inside the wristband-whether it’s encased in silicone, wood, or fabric-picks up that energy through induction. This powers the tiny silicon chip. The chip wakes up and says, “I am here.” The writer then sends a command to write a specific string of data to a specific memory block.

The writer has to wait for a confirmation from the chip that the data was received and stored. This is the ‘handshake.’ In a factory environment, this happens on a calibrated assembly line with high-powered industrial encoders and shielding that prevents interference. In a portacabin in Manchester, you have three laptops, two mobile phones, a microwave in the corner, and a desktop writer that was likely bought because it was the cheapest one on a certain e-commerce site. Every time someone’s phone pings or the microwave finishes a burrito, the electromagnetic environment shifts. The handshake fails. The software freezes. The human cost begins to climb.

The Subsidy of Nerves

We treat labor as a variable expense and hardware as a fixed one. This is a mistake. The labor of Tom, Priya, and Bea is treated as “free” because they are salaried or on a flat event fee. Therefore, the decision to buy blank bands and encode them manually appears to save the budget money. But it’s a subsidy. The event is being subsidized by the nervous systems of its staff.

When you look at a manufacturer like WXR, the value proposition isn’t just the physical object. It’s the removal of the 3:00 AM portacabin scenario. They offer data encoding and UID printing at the factory level. This means the bands arrive with the data already burned into the silicon, verified by industrial-grade testers, and physically printed on the strap so that row 4,812 on the spreadsheet matches the physical number on the wrist. There is no duplicate. There is no software crash.

But for a procurement officer sitting in an office in October, the “blank” bands are $0.05 cheaper per unit. They see a $500 saving on a 10,000-band order. They don’t see the $2,000 worth of pizza, energy drinks, transport, and subsequent burnout-induced productivity loss that will happen in a portacabin six months later. They don’t see the “rescue tax.”

The Adrenaline Paradox

This is the central paradox of modern operations: we are addicted to the adrenaline of the save. We have created a culture where the person who prevents the fire is ignored, but the person who crawls through the smoke to put it out is promoted. If Priya had insisted on factory-encoded bands, she would have had to justify the extra cost to a director who would have asked, “Why can’t we just do it ourselves?” If she fails to justify it, she ends up in the portacabin. If she succeeds in the portacabin, she proves the director right: they *could* just do it themselves.

It is a closed loop of dysfunction.

I think about this every time I see a “Great Team Effort” post on LinkedIn. I see the photos of tired people smiling through their exhaustion, surrounded by empty coffee cups. I see the comments praising their “hustle.” What I don’t see is anyone asking why the process required them to be there in the first place. We have mistaken stamina for strategy.

At 04:45, the last band is tapped. The box is taped shut. Tom shuts down the laptop with a definitive click. They walk out into the gray Manchester morning, their eyes stinging from the screen glare. They have “won.” Tomorrow-or rather, in three hours-the gates will open, and the bands will work. The “heroic rescue” will be logged as a success.

But next year, the budget will be exactly the same. The procurement officer will see the “saving” from the blank bands and sign the same contract. The software will be the same version. And Priya, Tom, and Bea-or perhaps a new intern, because Bea will have quit by then-will find themselves back in that portacabin, listening to the rain, waiting for a progress bar that refuses to move.

We keep buying back our mistakes at a premium because we refuse to pay the market rate for a solution. We prefer the drama of the 4:00 AM scramble to the boredom of a plan that actually works. We are so busy being legends that we’ve forgotten how to be efficient.

The portacabin is a vault where we store the 10,000 mistakes we were too busy to prevent.

The true cost of a “great team effort” is often just the interest we pay on a debt of poor planning. Until we stop rewarding the rescue, we will never invest in the lighthouse. We will keep pushing the door that clearly says pull, wondering why our shoulders hurt, while the rain continues to drum on the roof of a cabin that should have been empty hours ago.