Jeremy Bowersox, Director of Housing Operations and Off- Campus Life for Embry-Riddle Aeronautical University’s Daytona Beach campus, oversees the business-operations side of housing: assignments, billing, facilities coordination, customer service, and the workflows that connect them.

Over time, many of those workflows had grown beyond the limits of the team’s existing setup. Exemption requests, room conditions, document management, and follow-up processes lived across Microsoft Forms, Excel spreadsheets, email chains, and other tools.

For Jeremy, the decision to evaluate new housing technology was not about chasing something new for its own sake. It was about timing, operational fit, and reducing the amount of critical work happening outside the core system.

“It was just time.”

—

Jeremy Bowersox

Director of Housing Operations for Embry-Riddle’s Florida Campus

That timing mattered because Embry-Riddle was not looking for a simple point solution. They needed software that could support the day-to-day reality of running housing operations at a complex institution, across two campuses with different processes and operating contexts.

I Think My Mind Is Changing a Little Bit

Jeremy is well-versed in the conference circuit and spends serious time in the exhibit hall. Embry-Riddle ran a formal RFP, casting a wide net and evaluating the major options in the housing management space.

Going into the Housing.Cloud demo, Jeremy had his top in mind — and Housing.Cloud wasn’t one of them. Then something shifted.

“Before the demo, I was pretty much sold on who my top two were going to be, and Housing.Cloud wasn’t one of them. As we went deeper into the demo — I realized, I think my mind is changing a little bit.”

—

Jeremy Bowersox

Director of Housing Operations for Embry-Riddle’s Florida Campus

What stood out was not a single flashy feature. It was the overall feel of the product: modern, mobile-friendly, and built with an appropriate level of flexibility. Jeremy had seen systems that felt too rigid, and others where configuration itself became the work. Housing.Cloud landed in the middle.

“It’s customizable in the sense of there’s enough options for it to do what you want to do, but it’s not so customizable that it’s just too many options.”

—

Jeremy Bowersox

Director of Housing Operations for Embry-Riddle’s Florida Campus

That balance mattered. Students are not always sitting at computers when they interact with a housing portal. Housing teams need room to adapt software around real processes, but not so much flexibility that every workflow has to be built from scratch. In the demo, Jeremy saw a product that felt modern enough for students and practical enough for staff.

Two Campuses, Two Time Zones, One Implementation

Embry-Riddle’s implementation was uniquely complex because it involved both the Florida and Arizona campuses, each with its own business processes, stakeholders, and implementation needs. Jeremy led the Florida-side housing operations work while aligning with Arizona’s parallel implementation process, which had its own operating context and constraints. The teams went live over the summer, in the middle of fall-assignment season. With the benefit of hindsight, Jeremy says timing mattered as much as technology.

“If I had to go back, I would change our implementation cycle to go live in October versus the summer.”

—

Jeremy Bowersox

Director of Housing Operations for Embry-Riddle’s Florida Campus

The teams adapted along the way, splitting implementation sessions so housing teams and IT/financial stakeholders could focus separately. That helped, because different groups needed different things from the system. Housing cared about the day-to-day operational workflow. IT and financial systems had their own priorities. The implementation had to make room for all of it.

The implementation also required the teams to make sense of Housing.Cloud through the lens of their own operational calendar — not just where to click, but how the pieces fit into the natural cycle of housing work.

The Product Is the Product

At just 20 days live on production, Jeremy sees the direction clearly. The furniture creation feature — which let him build out all inventory in two days instead of sending a spreadsheet to engineering — was an early win.

“That saves the engineering team their time. It saves me my time.”

Room condition reports and key tracking are moving out of facilities spreadsheets and into the system. The goal is simple:

“The less I can have to do outside of a system, the better.”

—

Jeremy Bowersox

Director of Housing Operations for Embry-Riddle’s Florida Campus

That goal shows up in everyday workflows. Exemption requests, for example, currently live across email chains, document attachments, spreadsheets, comments, and follow-up emails. Jeremy wants those requests to become an in-system form-and-task workflow: a student submits the request, uploads documents in one place, and the request becomes a task for the right person to review.

For Jeremy, the value comes down to three things: a complete product model, responsive partnership, and the right amount of flexibility.

That matters in housing operations, where teams are often trying to reduce the number of side systems, spreadsheets, and workarounds required to support students and staff.

The Proof Is in the Workflow

Jeremy knows his peers are paying attention. Embry-Riddle’s coordinated two-campus rollout reflects the kind of operational complexity many housing teams are trying to solve.

“I’ve talked to some of my colleagues and I think they’re interested to see how we end up on the other side.”

His instinct isn’t to explain Housing.Cloud to peers — it’s to show them.

“I would show them what I’m doing. Because it’s hard to explain — they’re so used to what they have.”

—

Jeremy Bowersox

Director of Housing Operations for Embry-Riddle’s Florida Campus

For a seasoned housing operations leader at a complex, two-campus institution, the proof is not in a pitch deck. It is in the actual working instance: the application process, the operational workflows, the configuration choices, and the day-to-day experience of the team using it.

Embry-Riddle is still early in its Housing.Cloud journey, but Jeremy can already see the direction: less work outside the system, a more modern student and staff experience, and a housing platform built to evolve with the way institutions actually operate.