Listen to your buildings.
Every day is different.

What if your buildings could tell you what they need?

Not a work order. Not a complaint from a student's parent on move-in day. The building itself — telling you which restroom is about to run out of towels, which lecture hall sat empty all afternoon, and which hallway actually needs attention tonight.

That's not a concept video. That technology exists right now, it's affordable, and it's changing how the best campuses in the country run their facilities. I'm Keith Mowen, the CEO of Contract Service Solutions, a leading facilities and custodial services provider. And for the next few minutes I want to show you what we call a living campus — no sales pitch, just the idea. Because once you see it, you can't unsee it.

Here's how most campuses clean today: somebody — years ago — wrote a schedule. Building A on Mondays and Thursdays. Restrooms twice a day. Lecture halls every night. It's what we call a static schedule — and it runs the same way whether it's finals week or spring break.

Think about what that means. The conference room nobody used on Tuesday gets the same attention as the lecture hall that ran full all day. The quiet third floor gets vacuumed while the student union — the building your prospective families walk through — waits its turn.

So ask yourself one question: are you cleaning where the building actually needs it — or just cleaning because it was on the old static schedule?

Every campus I've ever walked has the same problem, and it isn't the people. Your custodians work hard. The problem is that a static schedule pretends every day looks the same — and on a campus, no two days look the same. Class schedules shift. Events pop up. Enrollment moves around the buildings. The schedule stays static while the campus moves.

And with budgets under real pressure, that gap gets expensive. You're paying for effort in the wrong places — and the places that need it most are where the complaints come from.

So here's the shift. Stop treating a building like a fixed object on a maintenance calendar — and start treating it like something alive.

A living facility breathes: people flow in and out all day, and that flow is measurable. It speaks: modern fixtures and small sensors can report what's actually happening — in real time. And if you're listening, the service can respond: effort goes where the building says it's needed, the day it's needed.

That's the whole idea. The campus tells you what it needs. You listen. You act. Everything I'm about to show you is just that loop, three different ways.

Start with how a building speaks. The technology here is smaller than most people expect — sensors about the size of a quarter. They sit in a door jamb and count how many people walked into a space. They sit inside a paper towel or toilet paper dispenser and report how full it is. Battery powered, wireless, installed in minutes.

Here's what that does for a restroom. The one that runs low on paper towels at ten in the morning? Today, nobody hears about that until someone complains at two. With sensors, the dispenser itself sends the alert — towels are low, this restroom's had heavy traffic — and the nearest team member gets it on their phone before anyone ever notices a problem. The restroom asks for its own service.

Now zoom out from one restroom to a whole building. Door counters on every wing tell you which floors actually got used today — not which floors the schedule assumed would be used. That's the difference between guessing and knowing.

And two things worth saying clearly, because facilities leaders always ask. First: these are counters, not cameras. They count events — a door swing, a fill level. No images, no identities, no personal data. Second: this runs on its own cellular connection. It never touches your campus network, so there's nothing for your IT department to lose sleep over.

Next, the muscle. Autonomous floor scrubbers — we run machines that clean corridors and large open floors on their own, safely, around people. Set the route, and the machine handles the long, repetitive grind that used to eat hours of a person's shift.

Two things matter here. First, every run is documented — the machine records where it cleaned, when, and for how long. Coverage you can prove, not assume. Second — and this is the part people get wrong — the machine doesn't replace your people. It takes the most repetitive hours of the night and hands them back, so your team's skill goes where machines are useless: detail work, disinfection, the restrooms, the touchpoints. Same team, aimed at what people are actually good at.

So the building is speaking, and the machines are working. Where does it all go?

One screen. We built a platform that pulls every signal together — occupancy by area, dispenser levels, alerts, machine runs, inspection scores — a live map of the campus where you can see, building by building, area by area, what's happening and what's been done. Green where things are covered. Red where something needs attention. Not a monthly report. Live.

And here's where it pays off: the schedule. Remember the static schedule — written years ago, running on assumptions? This is its replacement: the dynamic schedule. A living campus builds tonight's plan from what the buildings reported today. The lecture halls that ran full get the full treatment. The wing that sat empty gets a lighter pass — and those hours flow to where the day actually happened. Tomorrow the data's different, so tomorrow's schedule is different. That's the whole difference in one line: a static schedule cleans by habit — a dynamic schedule cleans by need.

Listen to your buildings — every day is different.

One honest note on what this means for cost, because every CFO watching is doing math right now. This isn't about fewer people. It's about the same budget producing more — because none of it is spent on empty rooms. When effort follows real usage, service quality goes up in the places people actually experience, and the published staffing standards most campuses budget against start to look conservative — because those standards assume you're guessing. When you're not guessing, you get more out of every hour than the tables say you should.

So put it together. What changes on a living campus?

Complaints start disappearing — because problems get caught by a sensor before a person ever experiences them. Service levels stop being opinions — every area's level of service is set by measured use, and verified by inspections you can see. Budget conversations change — you walk into them with data: here's how every building was used, here's where every hour went, here's the quality score to show for it. And your facilities program stops being a black box — for you, or for your board.

That's not a future promise. Every piece of this — the sensors, the machines, the platform, the daily plan — is running in real buildings today.

If you found value here, I share one short video like this every week — one idea from where campus facilities are heading, no pitch, just the thinking. Subscribe to the newsletter, or follow the channel — whichever you prefer. The link's right below.

And if you'd like to know what your own buildings would say if they could talk, that's exactly what a Campus Opportunity Assessment is for. The first conversation costs nothing — and here's our promise on the on-site assessment itself: if we don't find you real opportunities, it's free. Just reply to the email that brought you here.

I'm Keith Mowen. Thanks for the time — and take a fresh look at your buildings on the way home. They've been trying to tell you things for years.

Somewhere on your campus right now, a restroom just ran out of paper towels. Here's the problem: you won't find out for hours — not until someone complains, or a prospective family notices it on a tour. By then the damage is done.

What if that restroom could raise its hand the moment it happened — and the right person was already on the way to fix it, before anyone else even noticed?

That's not the future. That's a sensor the size of a quarter, and it's running on campuses today. I'm Keith Mowen, the CEO of Contract Service Solutions, a leading facilities and custodial services provider. Let me show you how a restroom learns to ask for its own service.

Think about how a restroom problem reaches you today. Something runs out, or breaks. Minutes go by — sometimes hours. Eventually somebody's annoyed enough to say something: a student, a professor, a facilities email, a comment card. That complaint is the first time you learn there was a problem.

Here's what every facilities leader knows in their gut: a complaint is a lagging indicator. By the time you hear it, the bad experience already happened — usually to a lot of people, and sometimes to exactly the person you least wanted to have it, on the worst possible day.

And here's the part that should really bother you. For someone to actually file a complaint, they have to be pretty upset. Most people who walk into a restroom with no paper towels don't say a word — they notice, they shrug, they move on. It's not worth their time to complain. But they noticed. Every one of them. So the handful of complaints you hear are the tip of an iceberg — for every person who spoke up, there are dozens who had the exact same experience and stayed silent. That silent majority is quietly forming an opinion about how this campus is run. When you fix the problem before it happens, you're not just avoiding the one complaint — you're serving all the people who never would have told you, and those are the ones who quietly get happier.

Running a building on complaints means you're always a step behind. Always reacting. Always apologizing. The best facilities teams in the country are flipping that — catching the problem before it becomes an experience. And it starts with letting the building do the reporting.

So how does a building report on itself? With sensors a lot smaller and simpler than people expect — many about the size of a quarter.

A few examples of where they go in a restroom. On the entry door: a small counter that logs every door swing — every person who comes and goes, all day long. Inside the paper towel dispensers and on the toilet paper holders: sensors that report how full they are, in real time. They're battery powered — batteries that last years — and wireless, so installation takes minutes. No wiring, no construction.

Now, two questions every facilities leader and every IT director asks — and the answers matter.

First: are these cameras? No. They're counters and level sensors. They count a door swing or measure a fill level. No images, no video, no identities — nothing personal, ever.

Second: do they run on our network? No. They use their own cellular connection. Nothing touches your campus IT — nothing for your security team to review, and nothing new for them to defend.

Now put it together — and here's where it gets smart.

We start by benchmarking the restroom. Those door-swing counters tell us how much traffic a restroom typically takes before it needs service — before the towels run low, before the first request ever comes in. Say we learn a particular restroom needs service about every 280 door swings. Once we know that number, we set the alert to fire below it — at 250.

So it's a busy morning near the science building, and that restroom is stacking up traffic. The moment it hits 250 swings — just short of where it usually starts to have a problem — the nearest team member gets an alert on their phone: this restroom, service it now. They're there and it's handled before the towels ever run out.

We're not reacting to an empty dispenser. We're servicing the restroom on its way to empty, based on its own real traffic — proactively, every time. Nobody ever experiences the problem, because it's solved before it becomes one.

And here's the part that matters for you: every bit of it is logged. The benchmark, the alert, the response, the time it took. So you don't just get a cleaner restroom — you get proof. You can show, with data, how fast your team responds and how few problems ever reach a person. The restroom stopped being something you react to, and started asking for its own service.

And once a building can report on itself, it doesn't stop at restrooms. Those same door counters tell you which spaces actually got used today. The conference room that sat empty all afternoon? You know. The lecture hall that ran back-to-back? You know that too.

That's not just interesting — it's the fuel for something bigger. Remember the difference between a static schedule and a dynamic one: a static schedule cleans by habit; a dynamic schedule cleans by need. This is where the need comes from. The building's own usage data tells tonight's schedule where the day actually happened — so your team's hours follow the real activity, instead of a guess written years ago.

The restroom sensor that saved you a complaint this morning is the same sensor helping you build a smarter plan tonight. It's all one system: the building senses, and the service responds.

So what actually changes when your buildings can ask for service?

Complaints drop — because problems get solved before people experience them. Your team looks great — showing up at the right place at the right time instead of scrambling after the fact. Your buildings feel consistently cared for — the restrooms on tour day are as good as any other day, because nothing's waiting on someone to notice. And your budget works harder — effort follows real use, so you're not spending on empty rooms while busy ones wait.

None of that requires more people or a bigger budget. It requires the building telling you what it needs — and a team set up to listen.

If you found value in that, I put out one short video like this every week — one idea from where campus facilities are heading, no pitch. Subscribe to the newsletter or follow the channel, whichever you prefer — the link's right below.

And if you're curious what your own restrooms and buildings would tell you if they could, that's exactly what a Campus Opportunity Assessment uncovers. The first conversation is free — and our promise on the on-site assessment: if we don't find you real opportunities, it's free. Just reply to the email that brought you here.

I'm Keith Mowen. Thanks for the time — and next time you walk past a quiet restroom on campus, ask yourself how you'd even know if something was wrong. Soon, the restroom will tell you.

Here's a question most campus budgets can't answer: what level of clean are you actually paying for?

There's an industry standard for this — five defined levels, from spotless down to neglected. Most campuses will tell you they're funded for Level 2. But here's the truth on almost every campus I've walked: they're funded for one level, and they're delivering a patchwork of all five — without knowing which space is getting which. They're guessing. And guessing is expensive.

I'm Keith Mowen, the CEO of Contract Service Solutions, a leading facilities and custodial services provider. Let me show you how to stop guessing your APPA level — and why the campuses that measure it get more clean for the same dollar.

Quick primer, because this is the vocabulary every facilities budget should be built on. The industry — APPA — defines five appearance levels.

Level 1 is orderly spotlessness — a showcase. Level 2 is ordinary tidiness — clean, professional, what most people expect of a good building. Level 3 is casual inattention — you start to notice. Levels 4 and 5 are dinginess and neglect — the ones that end up in a complaint, or a photo a parent takes on a tour.

Here's the key that trips people up: the higher the number, the less frequent the service, and the lower the appearance. So Level 1 costs the most to maintain, Level 4 the least. And here's the thing — not every space should be Level 1. Your main entrance on admissions day? Level 1 or 2, absolutely. A mechanical room nobody sees? Paying Level 1 money for that is a waste. The right answer is different for every space.

So here's how it usually goes wrong. A campus sets a target — we're a Level 2 campus — and then cleans on a static schedule built years ago to hit that number everywhere. Same frequency, building to building, whether or not the usage justifies it.

Two expensive things happen at once. You over-serve the spaces nobody's using — you're paying Level 2 effort on a building that sat nearly empty all semester. And you under-serve the spaces that are slammed — the student union during peak weeks quietly slides to a Level 3 or worse, because the static schedule never accounted for how busy it actually got.

So ask the question from the last video a different way: are you cleaning each space to the level its real use demands — or just to the level the old static schedule assumed? Most campuses genuinely can't answer that. They can't tell you, building by building, what level they're funded for, what level they're actually delivering, and whether the two match. That gap — between assumed and actual — is where the budget leaks and the complaints come from.

Here's the fix, and it's the whole idea in one sentence: let real usage set the level.

Remember the sensors — the door counters, the occupancy data. Now point them at this problem. Instead of guessing, you measure how much each building and each area actually gets used. Then you assign the appropriate APPA level to match. The busy union, the packed lecture halls, the main entrances — they earn Level 1 or 2, and they get it consistently, because the data proves they need it. The archive wing that sees a handful of people a week? It can safely sit at a Level 3 or 4 — cleaned less often, because honestly, that's all its use requires.

Watch what that does to the budget. The hours you were quietly wasting over-serving empty space get redirected to the high-traffic space that was silently slipping. Nothing gets neglected that people actually experience — and nothing gets gold-plated that nobody sees. Same total effort. Aimed by data instead of habit. Every space at the level it has actually earned.

Now here's the part that gets a CFO's attention. The industry doesn't just publish appearance levels — it publishes production rates: how many square feet one person can clean, per level, in a shift. Those rates are the benchmark almost every custodial budget in the country is built on.

But look closely at what those standard rates assume. They assume a fixed schedule. They assume you're cleaning by habit. They assume you don't know, day to day, where the work actually is — so they build in the slack of a team working a little blind.

We're not working blind. When your service is driven by live usage data and a dynamic schedule — when every hour is aimed at exactly the space that needs it, and none is spent on the space that doesn't — you get more out of each labor hour than those standard rates assume you can. The benchmark was written for guessing. Measuring beats it.

For you, that shows up one of two ways, your choice: the same budget buys a higher, more consistent appearance level than the tables say it should — or you hold your current level and it costs less to deliver. Either way, you've beaten the standard, because you stopped guessing.

So what changes when usage sets the level?

You can finally answer the question we started with. Walk into a budget meeting and show it: here's how every building was actually used, here's the level each one is set to and why, here's your cost per cleanable square foot, and here's the quality score proving you're delivering it. That's not an opinion anymore — it's data your board can trust.

You stop overpaying for empty space. You stop under-serving the spaces that shape how your campus is judged. And you beat the published production standard, because your program measures what everyone else assumes. Same mission, a sharper dollar — and a facilities line you can finally defend with numbers.

If you found value in that, I put out one short video like this every week — one idea from where campus facilities are heading, no pitch. Subscribe to the newsletter or follow the channel, whichever you prefer — the link's below.

And if you'd like to know what level each of your spaces is actually funded for versus what it needs — that's exactly what a Campus Opportunity Assessment measures. The first conversation is free — and our promise on the on-site assessment: if we don't find you real opportunities, it's free. Just reply to the email that brought you here.

I'm Keith Mowen. Thanks for the time — and the next time someone tells you what level your campus is cleaned to, ask them how they know.

Every facilities operation is really a dozen moving parts at once — inspections, complaints, work orders, staff schedules, callouts, training, service requests. And on almost every campus, each one of those lives somewhere different. A clipboard here. A spreadsheet there. A text message. Somebody's memory.

What if all of it lived in one place — and better yet, what if all those parts actually talked to each other? So a complaint became a work order, a callout instantly reshuffled tonight's schedule, and a low inspection score automatically sent more help to that building?

That's the tool facilities has been missing. We built it. It's called Facility Hub Live — and I want to show you why it's less of a dashboard and more of a brain.

Here's the reality of running a facilities program. You're juggling quality inspections, tenant feedback, work orders and service requests, staff schedules, sick calls and time off, training and certifications, standard operating procedures. That's a serious operation.

And on most campuses, every one of those things lives on its own little island. The inspection scores are in one system — if they're in a system at all. The complaints are in an inbox. The work orders are on a different platform. The schedule is a spreadsheet. When someone calls out sick, covering the shift is a scramble of phone calls, because the schedule has no idea that person is out and no idea which areas matter most tonight.

Nothing shares. Nothing connects. And that disconnection is exactly where quality slips through the cracks — the complaint that never became a work order, the struggling building whose low scores never changed the schedule, the callout that left the busiest wing short-handed. It's not anyone's fault. It's the tooling. Facilities has never had one system that holds it all.

So we put it all under one roof. Facility Hub Live is a single platform, one login, and inside it every part of the operation is a module.

There's inspections, with live quality dashboards and trend analysis, plus a dedicated night-operations inspection system. There's a feedback tracker — every compliment, complaint, and work order in one log. There's a service and PTO tracker, so every time-off request and callout is visible. There's a training academy — assigned courses, certifications, and every employee's history. There are work schedules. There's a library of standard operating procedures and documents. And it's all permission-controlled, so the right people see the right things.

That alone — one place instead of ten — is worth a lot. But that's not the real magic. One place is just a filing cabinet with a login. The magic is what happens when those modules start talking to each other.

This is the part that makes it a brain instead of a binder. Every module feeds the others. One metric drives another. All of it funnels into a central intelligence that can actually act.

Let me make that concrete. A complaint comes into the feedback tracker — it automatically becomes a tracked work order, tied to that building's inspection history, and flagged for the next visit. Nothing gets lost. A building's inspection scores start slipping — the system raises that building's priority in the schedule, and can trigger targeted training for the crew that covers it. Usage data shows one wing is slammed and another is empty — the dynamic schedule sends the hours where the people actually were. And when someone calls out, the hub knows — it rebalances tonight's coverage automatically, protecting the highest-need areas first, instead of leaving a supervisor making frantic phone calls.

No spreadsheet can do that. A spreadsheet just holds a number. A brain takes a signal from one corner of the operation and turns it into the right action in another — on its own. Inspections inform the schedule. The schedule absorbs the callouts. Complaints become tracked work. Usage drives the whole thing. Every service and every request, tracked end to end, feeding the next decision.

So what does a connected brain like that actually give you?

A dynamic schedule that reflects real need instead of an old habit. Absence coverage that reprioritizes itself the moment someone's out. Work that always flows to the areas being used the hardest. Complete tracking of every service performed and every request made — nothing dropped. Quality trends you can watch over time. Training and certifications that stay current. Satisfaction you can actually measure.

And because every bit of it lives in one hub, you — the client — get to see it too. The same brain, the same screen we use to run your program. You're not waiting on a monthly report to find out how things are going. You're looking at the operation thinking in real time.

Here's the honest history. Facilities did get software — the CMMS, the computerized maintenance management system. For decades that's been the tool of the trade, and it did a job: it logged work orders and tracked assets. But most CMMS platforms are exactly that — a work-order tracker sitting off to the side. They record what happened. They don't connect your inspections to your schedule, your callouts to your coverage, your complaints to your crews. They store data. They don't think.

Facility Hub Live is the next step: an intelligent CMMS. It ties every system together into one connected brain — where every element of performance is coordinated, and the whole operation gets smarter because the parts talk to each other. That's the difference between software that records and a system that thinks. It's the intelligent CMMS you never thought was available — and it's the tool you've been missing.

If you found value in that, I put out one short video like this every week — one idea from where campus facilities are heading, no pitch. Subscribe to the newsletter or follow the channel, whichever you prefer — the link's below.

And if you'd like to see what running your own campus on one connected brain would look like, that's part of what a Campus Opportunity Assessment shows you. The first conversation is free, and our promise on the on-site assessment: if we don't find you real opportunities, it's free. Just reply to the email that brought you here.

I'm Keith Mowen, the CEO of Contract Service Solutions, a leading facilities and custodial services provider. Thanks for the time — and ask yourself how many of your facilities pieces are still living on separate islands. Imagine them finally talking to each other.

Here's something odd about how most campuses clean. The schedule was written for a building that doesn't exist — an average building, on an average day.

But your buildings aren't average, and no two days are the same. Monday's packed; Friday's a ghost town. The science wing ran three back-to-back labs while the humanities building sat empty. And yet tonight, every one of them will get cleaned exactly the way it did last night — because the schedule says so.

What if tonight's cleaning plan was built from what actually happened in your buildings today? That's dynamic scheduling. I'm Keith Mowen, the CEO of Contract Service Solutions, a leading facilities and custodial services provider. The whole idea is one line: listen to your buildings, because every day is different.

Most campuses run a static schedule. It was written once — maybe years ago — and it runs the same way every night, no matter what happened during the day. Building A, Mondays and Thursdays. Every restroom, twice. Every hallway, nightly. Set it and forget it.

Here's the problem, and it's baked right into the timing. On a campus, the activity happens during the day — classes, events, foot traffic, exam weeks. But the cleaning happens at night, after everyone's gone. So your night crew shows up and cleans based on an assumption somebody made months ago — with zero knowledge of what actually happened in those buildings that day.

That's cleaning by habit. And cleaning by habit means the same thing every single night: you over-clean the spaces nobody touched, and you under-clean the spaces that got hammered. The empty wing gets its full nightly service; the packed student union gets the same routine pass it always gets, whether 500 people came through or 50. Effort in the wrong places, every night, on repeat.

So flip it. Instead of guessing, let the day tell the night what to do.

All day long, while classes are running and students are moving through your buildings, the sensors are quietly logging reality — which areas got used, how heavily, where the traffic actually was, which restrooms crossed their thresholds. By the time the day winds down, you don't have a guess about where the work is. You have a map of it.

And that map builds tonight's schedule — around one principle: clean where the cleaning actually needs to be done, and move the labor to match.

Think it through. Why would you clean a conference room that nobody set foot in today? You wouldn't — so you take those minutes and reallocate them to a functional area that saw heavier use than normal. Now flip it: why would you clean a space that just hosted a 300-person event with the exact same effort you'd give it on a quiet Tuesday night? You shouldn't — that space needs more tonight, so the schedule sends more people to it. The lecture halls that ran full get the full treatment. The wing that sat empty gets a light pass, or safely gets skipped. Every hour of labor follows the real need — pulled off the spaces that didn't earn it, and pushed onto the ones that did. Tomorrow the data's different, so tomorrow night's plan is different.

That's the core of it. Students are in the buildings by day; the cleaning happens at night; and now the night crew arrives with a plan built from the day that just happened — not from a schedule written last year. The building tells you where it needs you. You listen.

Here's what that looks like at shift change. The supervisor pulls up the dashboard — the green, amber, and red map of how the campus was actually used today. And the system turns that map into tonight's assignments.

Every team member gets a plan specific to tonight — this hallway is priority, these rooms saw heavy use, give that wing a light pass, skip the floor nobody touched. Not the same laminated card they've carried every night for three years. Today's plan, for today's building, in their hand when they walk in.

That's the difference a dynamic schedule makes on the floor. Your people stop running a generic routine and start running the right routine — and they can see exactly why, because it came straight from the building's own day.

Now, dynamic means it bends around reality — including the surprises. Someone calls out sick. On a static schedule, that's a scramble, and usually the busiest wing is the one that goes short because the person assigned to it is the one who's out. A dynamic schedule knows about the callout the moment it happens and rebalances the whole night automatically — protecting the highest-need areas first. The gap gets covered where it matters most, not left to chance.

And it decides the best who for each job, too. The autonomous scrubbers take the big repetitive floors — the long corridors, the open lobbies — on their own, documenting every run. That frees your people to go where humans actually make the difference: the detail work, the restrooms, the high-touch surfaces, the judgment calls a machine can't make. Machines on the grind, people on the craft — and the schedule puts each exactly where they're worth the most.

So what do you get from all this? Better service exactly where it's needed, and a lot less effort wasted where it isn't. And on a tight budget, that matters more than ever — because when none of your hours are spent on empty rooms, the same budget simply produces more. Cleaner buildings where people actually are. Service levels you can prove. A night crew that's never guessing, and never scrambling.

It comes back to one line: a static schedule cleans by habit; a dynamic schedule cleans by need. That single shift — from habit to need — is the difference between a program that's always reacting and one that's always a step ahead, because it's listening to the building instead of a piece of paper.

If you found value in that, I put out one short video like this every week — one idea from where campus facilities are heading, no pitch. Subscribe to the newsletter or follow the channel, whichever you prefer — the link's below.

And if you'd like to know what your own buildings' days would tell your nights, that's exactly the kind of thing a Campus Opportunity Assessment uncovers. The first conversation is free, and our promise on the on-site assessment: if we don't find you real opportunities, it's free. Just reply to the email that brought you here.

I'm Keith Mowen. Thanks for the time — and tonight, somewhere on your campus, a crew is cleaning an empty room on schedule while a busy one waits. It doesn't have to be that way anymore.