A group of University of Nebraska-Lincoln students built a rideshare-style app to coordinate sober rides through fraternities, and I want to talk about why that matters more than it probably got credit for.
The Daily Nebraskan covered this story, and honestly it's the kind of thing that usually gets a one-day news cycle and then disappears. Student builds thing, Greek life adjacent, moving on. But I've sat through enough Panhellenic council meetings where risk management was treated like a checkbox on a form to know that what these students did is actually harder than it sounds.
Risk Management Is Usually Theater
Here's the thing about Greek risk management policies: most of them exist on paper with very little infrastructure behind them. I've reviewed chapter standing reports where a house checked every compliance box but had no real system for how those policies actually worked on a Friday night. Sober monitor? Listed. Phone number posted? Technically yes. Actual functioning process? Ask me again in six months when something goes wrong.
What the UNL students built is different because it's operational, not just procedural. A rideshare-style app means there's a request, a record, a driver, a timestamp. That's accountability built into the structure rather than left to whoever happens to be sober and willing to give up their car keys that night. And that distinction matters enormously when you're on the governance side of Greek life and you're trying to figure out whether a chapter's safety program is real or just documentation for the university's benefit.
Panhellenic councils and IFC boards spend a lot of time crafting risk management standards. We pass them, we present them to university advisors, we put them in the chapter handbook. And then the execution falls entirely on individual chapter officers who rotate every year and may or may not actually care. It's a structural weakness that every council knows about and very few councils actually fix.
Student-Built Solutions Are Often Better Than Top-Down Mandates
The reason this app is worth taking seriously is that it came from inside the system. These are students who understood the actual problem - coordinating rides in a way that's reliable and doesn't depend on whoever answers a group chat - and built something to solve it. That's different from a national headquarters sending down a new risk management module that chapters are required to complete annually and promptly forget.
I've seen what mandated programs look like in practice. They're often generic, they don't account for how a specific campus or chapter actually operates, and the people rolling them out have never stood outside a chapter house at midnight trying to make a system work in real time. Student-designed solutions have a legitimacy that top-down programs often don't because they're built by people who actually understand the context.
That said - and I want to be clear about this - the app only works if chapters actually use it consistently. Building the tool is step one. Getting chapters to adopt it, maintain it, and treat it as a real operating procedure rather than a pilot program that fades out by spring semester is a completely different challenge. That's where governance has to show up.
What Greek Councils Should Actually Do With This
If I were still sitting on a Panhellenic executive board, I'd be thinking about how to formalize something like this across chapters rather than leaving it as a single-fraternity initiative. Not in a bureaucratic way where you slap a committee name on it and hold three meetings before it dies - but in a practical way where you identify what it takes to run this, figure out which chapters have the capacity to participate, and build it into chapter standards review.
Chapter standards review is where this kind of thing actually gains traction. When you're evaluating whether a chapter is in good standing, you look at GPA requirements, dues compliance, recruitment numbers, event programming. Risk management infrastructure should be part of that same conversation. And right now it usually isn't - at least not in a way that goes beyond checking whether the right forms are on file.
The UNL model, if it actually works at scale, gives councils something concrete to point to. Not just a policy but a system. That's a meaningful difference when you're trying to make the case to university administration that Greek life is capable of self-governance. Because that case gets harder to make every time a chapter fails at something that was supposedly covered by an existing rule.
Look, the Greek community is constantly trying to prove it deserves to exist on campus. I believe it does. But that argument gets made or broken in operational decisions - the ones that happen when nobody's watching and there's no advisor in the room. An app that creates a record and a process is exactly the kind of operational decision that actually moves the needle. It's not glamorous. It won't go viral on recruitment TikTok. But it's the kind of thing that keeps chapters functioning like organizations instead of just groups of people sharing a crest.
The students at UNL figured something out that a lot of Greek councils with full budgets and national support haven't managed to implement. That's worth more than a one-day news cycle.
