How Auburn and UAB Modernized University Housing Operations

A summer turn is not a single job. It is a sequence of decisions: what condition a room is in, what needs attention, who will do the work, whether the work meets the standard, and when the room can be released for move-in. Every step may involve a different person. Every incomplete handoff can leave the next team working with only part of the picture.

For a university housing department, the academic calendar makes those handoffs especially consequential. Inspections, custodial work, maintenance, and contractors must converge on a date that is already set. A completed inspection does not mean a repair is finished. A finished repair does not mean someone has verified it. A room can appear complete on one team's list while still blocking another team's work.

Auburn and UAB describe moving toward a shared operational record with EZOS. Their accounts are different in emphasis: Auburn's highlights daily visibility and damage-charge documentation; UAB's highlights the path from inspection findings to work orders and early move-in service requests. Together, they offer a practical account of coordinating people and records—not a claim that a platform removes the need for institutional judgment.

Two campuses, a shared coordination problem

Auburn's reported operating context includes 1,400 suites, 3,498 bed spaces, and approximately 250 service areas. Its inspections cover much more than move-out: move-in, health and safety, mechanical rooms, buildings, generators, furniture, and final punch work all appear in the supplied materials. A useful operational view must accommodate those different settings without treating every checklist as the same task.

Auburn's earlier coordination included Smartsheet. The institution described teams overlapping in the same spaces and returning to rooms without one coordinated view of progress. The issue was not simply whether a team could record its own work. It was whether leadership could see the dependencies across teams and identify what needed attention next.

UAB reports approximately 3,400 beds across six residence halls and approximately 1,700 residential units, with EZOS in use since 2021. Its account describes replacing paper-based work-order handling and email coordination with connected records. At both institutions, the operational question is the same: can the person responsible for the next step trust the information left by the person before them?

Auburn: visibility that supports a daily decision

Auburn describes leadership reviewing room progress and outstanding work daily. A shared view gives supervisors a way to identify gaps and adjust resources before those gaps affect move-in. That is a more useful management signal than a collection of completed-task totals: it helps distinguish work already done from work still preventing readiness.

The distinction matters when several teams need access to the same room. Repeated visits and overlapping work are coordination problems as well as scheduling problems. Knowing the current state of a room gives leaders a better basis for deciding which team should enter next and which unresolved items deserve escalation.

The supplied account describes the value of that visibility, but it does not quantify hours saved or room visits eliminated. The defensible takeaway is narrower: Auburn reports using timely progress information to supervise turn. It is not evidence of a measured productivity gain or a universal staffing model.

A charge is only as reviewable as its record

Damage assessment adds another handoff: the one between the person inspecting a room and the person reviewing a resident's question about a charge. A photograph in a disconnected folder is not the same as a photograph connected to the correct room and resident record. The context captured during inspection is what makes the record useful later.

Auburn's account links stronger documentation to easier review. Timestamped photographs can be retrieved when a charge is questioned, reducing the need to reconstruct events from separate files or recollections. The purpose of that record is not to make every charge stand. It is to support a decision grounded in the available evidence, including a refund when appropriate.

In May 2026, Auburn reported approximately 4,000 damage charges. Of those, 60 were disputed—approximately 1.5% of all charges. Following review, 15 disputed charges were refunded and 45 were upheld. The upheld charges represented 75% of the 60 disputes.

Those denominators must stay attached to the numbers. Approximately 98.5% of charges were not disputed; that is an undisputed-charge share, not a dispute-resolution rate. The 75% uphold rate describes only the disputed charges. Neither figure establishes that every undisputed charge was correct, that disputes should be rejected, or that documentation alone produced the result.

Auburn also reported increased capture of damage over time. The supplied materials do not quantify a revenue increase, so this account does not infer one. The operational lesson is about evidence standards: capture useful photographs, connect them to the right record, and ensure the person handling an appeal can retrieve the information needed for a fair review.

UAB: make an inspection finding lead somewhere

An inspection can identify every issue in a room and still fail to prevent a move-in problem if its findings do not reach the people responsible for the work. A handwritten note, an email, and a separately entered work order create multiple points where information can wait, be reinterpreted, or be missed.

UAB describes using inspection findings to generate work orders automatically, alongside coordinated access for staff and vendors. Connecting a room's condition to its work history gives teams a way to trace what was found and what was done, rather than rebuilding that history from separate conversations.

The workflow has five distinct stages: inspect the room, document the finding, assign the work, verify completion, and report readiness. Keeping those stages distinct matters. An assigned work order is not completed work; completed work is not necessarily verified work. Supervisors still need a way to see the exceptions before signing off.

What UAB's 17.6% figure does—and does not—measure

UAB reported 17.6% fewer resident service requests during the first two weeks after move-in, measured over two academic years. That is a specific early-occupancy measure. It speaks to the period when residents first experience their rooms, not to all maintenance activity throughout the year.

The supplied materials do not include raw request counts, a control group, or an independent causal analysis. They also do not adjust the comparison for occupancy changes. The result should therefore be read as UAB's reported experience, not proof that software alone caused the change.

It is not a measured cost reduction, a staffing-savings claim, or a promise that another university will see the same percentage. For a team applying the lesson, the useful starting point is measurement discipline: define the post-move-in window, count requests consistently, and understand how occupancy and portfolio changes affect a year-to-year comparison.

Access is part of the operating model

UAB reports 50 internal staff users and 15 external vendor users. Some staff operate in both inspection and work-completion roles. That makes role design more than a permission-setting exercise: the system needs to reflect who can identify an issue, who can act on it, and who is accountable for verifying the result.

Clear access lets staff and vendors update their own work while maintaining a shared record for supervisors. It also makes exceptions easier to route. Giving someone responsibility to complete a task should not leave ambiguity about who can approve the room or when an issue must be escalated.

These are principles to apply deliberately, not a prescription to give every participant the same access. External vendors need access appropriate to their assignments. Dual-role staff need clear expectations about when they are recording a condition and when they are closing work. Institutional oversight remains part of the process.

Training for the job, not just the interface

Both institutions emphasize expectations and training. The useful unit of training is a real responsibility: perform an inspection, attach the right evidence, complete an assignment, verify a repair, or escalate an exception. Learning where to click is only part of knowing what a completed record should mean.

Auburn reports a few days of administrative training, a few hours for inspection technicians, and a one-hour group refresher. UAB reports training in hours rather than weeks. Those are institution-reported training experiences. They are not the same as total implementation time, and they should not be treated as a promised rollout schedule.

The shared lesson is to explain the operating change before expecting consistent use of the tool. Teams need to understand why evidence is required, what another group depends on, and who makes the final decision. That context gives a checklist meaning beyond its completion status.

What another campus can put to work

Start by following one room from move-out to move-in approval. List each inspection, handoff, work assignment, and verification. Look for duplicate entry, missing evidence, and moments when two teams use the same status word to mean different things. This mapping is a recommended starting point, not an additional measured outcome from either institution.

Next, choose a baseline your team can actually maintain. Repeat visits, unresolved inspection findings, damage disputes, and service requests in the first two weeks after move-in are different measures of different problems. Pick a consistent definition rather than combining them into a single success percentage.

Agree on evidence and ownership before expanding access. Define required photos, inspection criteria, resident attribution, who assigns and closes work, who verifies it, and which exceptions require leadership review. A bounded building or workflow can provide a practical setting for training and feedback before a wider rollout.

Finally, compare like with like. Use the same reporting periods and definitions, account for occupancy and portfolio changes, and treat exceptions as material for process improvement. The goal is a better basis for making the next decision—not a headline metric detached from the work behind it.

The honest ledger: evidence, limits, and plans

The source white paper describes structured interviews with housing operations leaders about prior processes, adoption, turn workflows, damage documentation, and facilities outcomes. This story is an editorial synthesis of those supplied materials and the corrected public edition. It does not introduce new interviews, new quotations, or independent verification.

Auburn's original materials also describe a custodial program planned for January 2027 and a goal of a roughly one-week turn using Housing Ambassadors. These are forward-looking plans, not completed outcomes. They are not presented here as achieved time savings or promises for other institutions.

Neither institution's experience should be described as a measured result of adopting the new EZOS Core PMS. The evidence concerns inspection, turn, and facilities workflows. It supports a grounded discussion of visibility, documentation, automation, and responsibility within those workflows—not a causal guarantee or a broader system-adoption claim.

The common thread is practical: a room's condition, the work it needs, and the person responsible for the next step should not live in separate accounts of reality. Auburn and UAB describe making those connections more visible. Their reported experiences give other housing teams questions to ask, measures to define, and handoffs to examine before the next move-in date arrives.