Managing the shift
I managed 4 to 6 inspectors and 2 to 4 keyroom helpers on a shift, which meant figuring out who was going where, checking that inspections had actually been finished, and following up when the reports didn't match what we needed.
Georgetown Residential Living · Summer 2025
A shift at
Georgetown.
In the summer, Georgetown fills up with people who are only staying for a little while, and the rooms still have to be ready when they get there.
I worked in the Harbin Keyroom, assigning inspections, helping run the office, and building tools for the things we kept having to chase down.
Read the case study A small version of the jobInteractive reconstruction · Synthetic data
Residence hall / schematic
Select a room to see who is assigned and when its group arrives.
Ready To inspect Needs attentionSchematic · Not to scale
My work
The arrival schedule told us when a room needed to be ready, I used that to assign inspections, and then checked whether the work had been finished and reported properly.
I lost access to most of the original system when I left, so I rebuilt this demonstration using the project components I still had. The rooms, people, schedules, and layout are fictional. There are no student records here, and nothing connects to Georgetown's systems.
Behind the model
Someone has to
keep track.
Operations Specialist, Georgetown Residential Living
May to September 2025
Building the dashboards
There were about 24 of us using the tools. I built the dashboards in Next.js, with Supabase underneath, so we could look at arrival times, failed inspections, work orders, and keyroom visits without having to piece the whole picture together ourselves.
The inspection responses started in Google Forms, landed in Sheets, and came into Supabase through CSV connectors I wrote. The biggest table had more than 20,000 inspection records, and the housing data covered more than 3,000 living spaces. Those are records and rooms, not thousands of people using my app.
Tracking keys
I also built a key tracker, with Google sign-in and access controlled through Supabase. When a key went missing, I pulled the logs for the inspector who last had it, and found that another team had told the inspectors to use a faulty handoff procedure. We never found the key, we changed the lock, and we changed the instructions for exchanging keys between shifts.
How I built the software
I used AI to help write the code, and I don't want to be weird about that. I knew the work we were trying to get done, decided what the tools needed to show, and connected the data so we could use it.
A little more about me
How I Think
I read a lot about why people do things and then catch myself doing whatever the book said people do. Usually after deciding that part doesn't apply to me. I like having an explanation for things, which gets me into trouble when I find one I like and stop looking.
That's part of why I like The Lean Startup. You can spend an afternoon reading about a problem and feel like you've done something about it. Eventually you have to try something. Preferably something small enough that being wrong won't ruin your week. I find that harder once I've explained an idea to a few people and started feeling like I owe it a defense.
Working with people adds another problem. You explain something, they nod, and later you find out you had two different conversations. I've seen people get conflicting instructions from different teams and then have to answer for the result. Before I tell somebody they did something wrong, I want to understand what they thought they were supposed to do.
I want people to be able to ask me a question without feeling stupid for asking. I still expect the work to get done, but I care about whether we're getting better at doing it together. And when I'm the one who's missed something, I hope they'll tell me.
Brodie
Open to opportunities
Contact me
I'm looking for work, and I'm willing to move for it. Frequent travel is fine too.