A bad night at a fraternity can end a chapter, and sometimes it ends a life. I built the system that keeps the record.

Situation

The guest list is the only line between a closed community and a stranger.

Greek events aren't open parties. They're closed communities with hundreds of guests, alcohol, and real liability. When the list fails, a chapter is on the hook for whoever walked through the door.

In reality, it was a spreadsheet.

When it fails, people get hurt.

Three people pay for it: a guest who needs safety, a bouncer who can't afford to be wrong, and a host responsible for everyone inside.

And IFC decides what they pay.

IFC is the Interfraternity Council. They sanction, suspend, and close chapters, and every host's worst night is the one they have to explain to IFC the next morning.

Complication

DoorList shipped as a safety platform. A QR scan didn't make it one.

By the time I joined, the scanner was already shipping. It was the visible piece of the product, but scanning a QR code isn't the same as knowing who's at the door, and it isn't the same as making someone accountable for letting them in.

And even the scan was optional.

Some were paid, some weren't. Some nights the phone couldn't connect in a crowded house. And once a bouncer recognized a name on the list, the phone went in the pocket and the guest got waved through. So I spent three weekends at the door and two more in interviews to find out why.

The scan wasn't safety. A record was, and the accountability it enforced.

Speed had never been the bottleneck. Trust had. A safety system that depends on a tired person choosing to use it isn't a system. It's a policy with a login screen.

Resolution

Leading design across nineteen months with two engineers and the IFC compliance team, I prototyped two directions: one that made scanning faster, one that made the bouncer visible on the record. The second tested better, because speed had never been the problem.

I redesigned the scan around one principle: a bouncer can't let anyone in without seeing their own name on the record, and no guest gets a faster path just because they're recognized.

Every guest tied to a verified identity. Every scan stamped with the bouncer's name and a time no one could edit after the fact. Every guest flow identical, so familiarity couldn't unlock a shortcut. The log also captured who each guest arrived with, and a network of known relationships built up across events.

And IFC, who used to find out about incidents after the fact, now watches every scan across every event as it happens.

Hosts confirm risk management before doors open. Bouncers check in with their name attached. The council that decides whether a chapter survives sees the night unfolding in real time, not after the call comes.

Safety platforms don't scale on safety alone. They scale when they protect the institution.

Guests told us they felt safer, which is what I'd designed for. What I hadn't predicted was what the log did for the fraternities themselves. When something went wrong, the evidence protected them from blame they'd otherwise carry, and that turned a safety feature into a liability shield. The product became indispensable to the people running the events, not just the people attending them. The hosts started saying it out loud.

One million entries across two hundred chapters, and no more stories that can't be verified.

Guest lists that can't be faked. Entry logs that can't be disputed. A safety system that doesn't depend on a person deciding to enforce it.