The Room Check Routine: Catching the Dead Battery on Thursday

Thursday, 16:10, at Northgate Retail's head office. Jas, the junior technician, is walking the twelve meeting rooms with a clipboard and a laptop, in the same order as last week. In room four the remote's battery is dead and the display will not wake from the panel either, because the panel's button has been stuck since someone spilt coffee on it. In room seven the card has gone from the table. The sharing cable has been unplugged at the display end, where nobody can see it, because the cleaners moved the table on Tuesday. In room nine the room system shows a message asking to be signed in again. Three rooms, three faults, twenty-five minutes, no audience. On Monday morning those would have been three calls at 09:01, two of them from regional managers, and Jas would have been the person running up the stairs.

The room check routine is a short, fixed, logged inspection of every meeting room on a schedule. There is a weekly walk for all of them and a morning check for the rooms with something important in them that day. There is also a test call that proves a room works end to end. The routine exists because most room faults appear between meetings, not during them. A fault that appears on Tuesday evening will be found by whoever walks in first. That is the organiser at 09:01 unless it is the desk on Thursday. This article is part of our Meeting Room & AV Support series. It is about what the walk checks, when, who does it, and how the log turns a routine nobody notices into a number somebody can see.

It covers what a check catches that a ticket cannot, then the weekly walk and what is checked in each room. Next come the morning check for the rooms that matter, the test call, and consumables, which are batteries, cables and markers. Then it covers the check log and why it records passes as well as faults, followed by what the walk finds and what it costs, at a fictional desk, in ranges. Who walks, a short war story and the room check log to copy finish the article.

What a Check Catches That a Ticket Cannot

A ticket arrives when someone has found the fault, and in a meeting room the someone is the organiser, at the start of a meeting, with an audience. That is the worst possible moment to discover anything, and it is the moment at which every fault that developed since the last meeting is discovered. Nobody else has been in the room. Batteries do not die during meetings; they die on the shelf and are found at 09:01. Cables do not unplug themselves while a slide is up; they are pulled when the table is moved on Tuesday and found on Monday. The room system does not lose its sign-in mid-call; it loses it overnight and announces it to the next person who tries to join. A check finds all of these on Thursday, which is the same fault at a different price.

This is the idea of Fixing Before the Ticket applied to the one place where "before" is worth most. The gap between a fault being found by the desk and being found by a meeting is the gap between a two-minute fix and a reputational event. Rooms also have a property most equipment lacks: they are used by a different person every hour. None of those people owns them. None will report a dead battery after their meeting because they got the meeting done without it. A laptop's owner raises a ticket when it misbehaves. A room has no owner. The walk is the owner.

The check also catches the faults that are never reported at all. A room whose camera has drifted to show the ceiling generates no ticket, because the people in the room cannot see what the remote half sees. The remote half assumes it is their own connection. A room whose microphone battery is low works for the first ten minutes and fails at the thirtieth, long after anyone would connect it to the room. These are the faults a desk only learns about months later, from a manager who mentions that "that room has always been a bit rubbish". By then the room has a reputation and a booking pattern to match. A check turns a reputation into a line in a log.

The Weekly Walk

The walk is every room, once a week, in the same order, by one person with the room bag and a laptop that is known to share. It takes two to three minutes a room once the routine is known. In each room the technician does what the organiser will do on Monday, in the order the card lists it. Wake the display and confirm it shows the idle screen with the room's name. Choose the input the cable is labelled for and confirm the label and the display agree. Plug the walk laptop into the cable, or share to the room wirelessly if that is the room's method, and confirm a picture. Press the mute button and confirm the light. Turn the room volume up and play a sound. Check the remote is present, in its holder, and wakes the display. Check the room system is signed in and shows its calendar. Look at the card, which must be present, legible and the current version. Look at the room, for a cable on the floor, a camera pointing somewhere odd, a chair against the display.

Fix what can be fixed on the spot and open a ticket for what cannot. A dead remote battery is replaced from the bag and logged as fixed on the walk. A stuck panel button is a ticket, with the room, the symptom and the date. The display stays usable from the remote until the ticket is worked. The distinction matters for the log. A walk that fixes six things and opens no tickets looks, in the ticket data, like a walk that found nothing. The log is what carries the six. Faults found on the walk get a source of their own, "found on check". That way, the measuring article can count them separately from the faults found by organisers, which is the whole point of the exercise.

Walk on Thursday afternoon, or whatever day leaves one working day before the week's heaviest meeting day. A fault found on Thursday is fixed on Friday and the room is right for Monday. A fault found on Monday is a fault found during a meeting. A fault found on Friday afternoon is fixed on Monday morning, in a hurry, while the room is booked. The day is less important than the regularity. A walk that moves around the week is a walk that is skipped the week it is needed, and the war story in this article is about exactly that.

The Morning Check for the Rooms That Matter

Some rooms get a second check on the morning they matter. Those are the boardroom on board day, the large room before the all-hands, the training room on the morning a course starts, any room with an external audience in it. The morning check is the weekly walk's routine done in three minutes for one room, finishing with a test call. It is done before the organiser arrives, which means knowing the calendar. The desk's room cover for the day reads the rooms' calendars first thing, or the day before, and picks out the meetings whose failure would be noticed above the desk's head. Most days there are none. Some days there is one, and the three minutes are the cheapest insurance the desk buys all week.

Board days and large events need more than three minutes and are the subject of Board Days and Big Events, which adds the rehearsal, the person who stays, and the fallback room. For the ordinary important meeting, the morning check is enough. It ends with the technician leaving the room exactly as the organiser will find it. The display is on and showing the idle screen, with the input selected. The cable is coiled at the right seat, the remote in its holder, the card on the table. The room system is signed in and showing the meeting. The organiser walks in, plugs in, and starts. They will never know the room was checked. That is the measure of a good one.

The Test Call

The test call is the only check that proves a room end to end. The display, the sharing, the camera, the microphone and the sign-in can each pass on their own. The room can still fail to hold a meeting. The technician joins a test meeting from the room system, or from the walk laptop in rooms without one. They also join from a second device somewhere else, usually their phone in the corridor. From the room they confirm the camera shows the table, not the ceiling. From the phone they confirm they can hear the room and the room can hear the phone. From the walk laptop they share a picture into the call and confirm it arrives on both the room's display and the phone. Then they leave the call, which is itself a check. A room system that cannot leave a call cleanly is a room whose next meeting starts inside the previous one.

Keep a standing test meeting for the purpose, owned by the desk, with a name that says what it is. That way, nobody on the walk has to create one and nobody wandering into the room's calendar wonders what it is. Rooms with a room system can have the test meeting in their calendar on walk day at the walk's time, which also proves the calendar is being read. The test call takes about a minute and is the part of the walk most often skipped when the walker is in a hurry. The display is on and the picture is up and the room looks fine. The room looked fine at Meridian Parts too.

The remote half's experience is what the test call measures and nothing else does, and its failures are the subject of Hybrid Meetings and the Remote Half. The walk cannot fix a room that was never designed for hybrid meetings, but it can find the camera that drifted and the microphone that died. Between them, those account for most "nobody could hear us" complaints that reach the desk a week late, if at all.

Consumables: Batteries, Cables, Markers

Replace batteries on a schedule, not on failure. A remote or a wireless microphone whose battery is replaced every so many weeks on the walk, whether or not it is dead, never dies in a meeting. The cost is a handful of batteries a month against a walk the desk is making anyway. Write the replacement date on a small label on the battery cover, so that the walker can see at a glance whether this is the week. Keep the two sizes the rooms use in the room bag in quantity. Rechargeable microphones go back on their charger at the end of the walk and the walker checks that the charger's light is on. A charger with its cable kicked out is a microphone that is dead by Wednesday.

Cables are checked at both ends and at the tether. The end at the display is the one nobody sees and the one the cleaners pull; the end at the table is the one that gets bent by being pushed in at an angle. A cable with a damaged end is replaced from the bag on the spot and the old one goes back to the desk, not into the bin. That way, the measuring article can count how many cables a room gets through, which is a number facilities will eventually want. The tether is checked because an untethered cable is a cable in someone's laptop bag by the end of the month. The adapter ring is counted, because adapters are the single most-walked item in most buildings.

Markers are nobody's job, which is why every whiteboard in the building has four markers and none that write. The walk tests each marker with a stroke on the board and bins the dry ones, and the bag carries replacements. Whether this is the desk's job or facilities' is a question that has consumed more meeting time than the markers ever would. The practical answer is that it belongs to whoever is already in the room with a clipboard. The desk gets the credit, which is worth having, and the room gets markers, which is the point. Spares on the shelf are counted at the end of the walk against the standard's list, and a short shelf is a ticket to reorder, raised the same day.

The Check Log

The check log is one line per room per walk. It gives the date, the walker, a pass or fail for each check, what was fixed on the spot and the number of any ticket opened. It records passes as faithfully as faults. The passes are not padding. A room's log is its history. The history tells the desk that room four's remote has needed a battery every three weeks for a quarter. It says that room nine has lost its sign-in twice in a month, and that room seven's card has gone missing three times. That last one is a different problem from a card that was never there. A log that only records faults cannot show a pattern, because a pattern is faults against a background of passes.

Where the log lives matters less than that it is one place and that the walk cannot finish without filling it in. A spreadsheet with a row per room per week does the job. A knowledge base page does it with better visibility. A ticket per walk, with the per-room findings as internal notes and a linked ticket for each fault that needs work, does it with the best audit trail. If you run QuerySolv, a ticket the walk opens for a stuck panel button is an ordinary ticket. It is in the same queue as the one an organiser raises by e-mail about the same room. That is what lets the two be counted side by side later. The walk's tickets carry their own source so the count can tell them apart. In any tool, the test of the log is whether a technician who has never walked the rooms could read the last two months and tell you which room to worry about.

The log also closes a gap that prevention always has, which is that nobody sees the tickets that did not happen. A walk that finds three faults a week and fixes them on the spot has prevented three calls. The ticket data shows only that room calls went down, which could be anything. The log is the evidence that it was the walk. Converting "found on check" counts into an honest estimate of calls prevented, without claiming every find would have been a call, is the method in Measuring the Tickets That Never Arrived. The log is the raw material it needs. A dead battery found on Thursday is not a prevented ticket until the log says the room had a meeting on Monday.

What the Walk Finds and What It Costs

Take the fictional desk at Northgate Retail to put a shape on it. Twelve rooms, one walker, thirty to forty minutes a week including the log, which is about two and a half to three hours a month of a junior technician's time. The walk finds between three and six things a week in a building that has not been walked before. It settles to one or two a week once batteries are on a schedule, cables are tethered and the cards have stopped walking. Before the routine, Northgate took twenty to thirty room calls a month. After a quarter of walking, with nothing else changed, the count was between ten and fifteen. The ones that came were more often a presenter's laptop than the room.

Those are one desk's figures in ranges, and your own depend on how many rooms you have and how long they went unwalked. The arithmetic that matters is the exchange rate: two and a half hours a month of walking, with no audience, against ten to fifteen walks a month at 09:01, with one. The hours are roughly even. The walks are not the same kind of hour, and a desk that counts them as the same has not been in the boardroom when the screen went blue. The counting method for room tickets per room and per cause, and the quarterly conversation with facilities that the log makes possible, are in Measuring and Reducing Room Tickets.

Who Walks

The walk rotates, and the junior technician walks first. It is the best induction to the rooms a new technician can have, because by the third week they know every room's layout, every card and every quirk on the exceptions list. The room calls they take afterwards are calls to rooms they have stood in. It rotates because a walk that belongs to one person is skipped when that person is away, and because the person who walks every week stops seeing the room and starts seeing the clipboard. A desk of one walks alone and gets facilities to share it, which also solves the question of who owns the markers.

Facilities walk the rooms too, for their own reasons, and a shared walk with a shared log is better than two walks with none. The division that works is that either team can do the routine and fix the consumables. The desk owns the tickets, the log's review and the test call, because the test call needs the walk laptop and an account the desk controls. A check that is done by whoever is passing is a check that is done by nobody on the week it matters. Put the walker's name on the rota, put the rota where the desk can see it, and treat a missed walk as a missed ticket, which is what it will turn into.

A Short War Story: The Skipped Thursday at Meridian Parts

Meridian Parts had a weekly walk on the rota and a desk lead, Lukas, who allowed it to be skipped when the queue was heavy. It was heavy for three Thursdays in a row during a stock system upgrade. On the fourth Monday the finance director held the quarterly results call with the company's bank from the large meeting room. The room system, which had lost its sign-in the previous week and told nobody, asked her for an account. When the desk had signed it back in, the table microphones, whose batteries were two walks overdue, worked for nine minutes and died. The bank's relationship managers heard the second half of the results from a phone in the middle of the table. The call was finished on the phone. The finance director's note to the managing director was two sentences long, one of which asked what the walk was for. The cost was eleven minutes of a results call and a morning of Lukas explaining the three skipped Thursdays. There was a rule afterwards that the walk is never skipped and the queue waits forty minutes for it. The lesson Lukas wrote on the rota was that a check that is skipped when the desk is busy is skipped in exactly the week it would have caught something.

The Room Check Log

The log below is one sheet per walk, one line per room, and it is filled in standing up, so it is boxes and short blanks. Section A is the walk's header. B is the per-room line with its checks in the order the walk does them. C is the consumables and the spares count at the end. D is the summary that goes to the monthly review. Keep the completed sheets, or the spreadsheet rows they become, for at least a year, because the pattern in a room's history is the thing the log exists to show.

ROOM CHECK LOG — ONE SHEET PER WALK
Date: ____________   Walker: ______________   Walk started: ______   Finished: ______
Walk laptop shares: [ ]   Room bag restocked before walk: [ ]   Test meeting ready: [ ]

A. PER ROOM (one line each; P = pass, F = fail, X = fixed on the spot, T = ticket opened)
Room ______   Display wakes, idle screen shows room name ......... [ ]
              Input matches cable label ............................ [ ]
              Share from walk laptop (room's one method) ........... [ ]
              Mute light works; room volume plays sound ............ [ ]
              Remote present, in holder, wakes display ............. [ ]
              Room system signed in, shows calendar ................ [ ]
              Test call: camera shows table / phone hears room /
                 room hears phone / share arrives / leaves cleanly . [ ]
              Card present, legible, version ____ .................. [ ]
              Cable both ends seated, tethered; nothing on floor ... [ ]
              Batteries: remote (date ____) mic (date ____) ........ [ ]
              Fixed on the spot: ______________________________
              Ticket opened: ________  for: ______________________

(repeat the block for each room, in walk order)

B. CONSUMABLES AND SPARES (end of walk)
   Batteries used: size ____ x __   size ____ x __      Markers replaced: __
   Cables replaced: __ (old ones returned to desk)      Adapters missing: __
   Spares shelf vs standard:  displays __/__  remotes __/__  controls __/__  mics __/__  cables __/__
   Reorder ticket raised: [ ] number ________

C. SUMMARY FOR THE MONTH
   Rooms walked: __/__   Faults found: __   Fixed on the spot: __   Tickets opened: __
   Rooms with a fault two walks running: ______________________________
   Morning checks done this week (room, date, meeting): ______________________________

Jas's three Thursday faults took twenty-five minutes and two batteries, and the stuck panel button became a ticket that facilities worked on Friday. On Monday the regional managers' meeting in room four started on time, which nobody noticed, because nothing happened. The log noticed. It was the third week running that room nine had needed signing back in, and that line, not any 09:01, was what got the room system's account looked at properly. Prevention does not announce itself. It has to be written down to exist at all.

Frequently Asked Questions