Board Days and Big Events: Prep That Prevents the Panic

Tuesday, 08:41, at Kestrel Aviation Services. The board meets at nine. The boardroom screen says "no signal" in large, calm letters. The finance director's laptop, from which the half-year figures are to be presented, is showing a progress bar and a message that it must not be turned off. Ola, on the desk for a year, has been summoned by the company secretary. He is standing at the back of a room containing two non-executive directors who arrived early, the chief executive, and a tray of pastries nobody is eating. The progress bar says eleven minutes. Ola has no second laptop, has never seen the deck, and does not know which of the three cables on the table is the one that works. The chief executive asks, pleasantly, whether it will be ready by nine. Ola says yes, which is the first thing to go wrong that is actually his fault.

A big event, for a help desk, is any meeting where the audience is large or senior, the start time cannot move, and a failure is public. A board day is its purest form. It has a dozen people whose time is the most expensive in the building, and a chair who cannot troubleshoot and should not have to. It has external attendees who will remember, and an agenda timed to the minute. Nothing in the technology is harder than an ordinary meeting. Everything about the consequences is. The desk's job on a board day is therefore not to fix things quickly. It is to have arranged, in the preceding week, that there is nothing to fix. This article is part of our VIP & Executive Support series. This article is about that week.

This article covers why board days are different, then the calendar and knowing the dates. Next comes the prep timeline, a week before, the day before and the morning, with the room check. We cover the spare laptop with the deck on it, then the rehearsal. Then come the standby technician and the quiet presence at the back, including what to do when it fails anyway. We finish with the debrief and the event ticket, a short war story, and the event prep checklist to copy.

Why Board Days Are Different

An ordinary meeting that fails loses ten minutes and someone goes to find a cable. A board meeting that fails loses ten minutes of twelve people, a chair's patience, the presenter's composure, and a piece of the organisation's reputation with every external person in the room. The technology is identical. The arithmetic is not, and the four things that make it different are the audience, the clock, the presenters and the single point of failure. The audience is senior and often external: non-executive directors, auditors, the bank, investors. The clock cannot slip, because the agenda has been circulated and the chair runs it to the minute. The presenters are people who cannot troubleshoot and must not be expected to. A finance director fumbling with a cable in front of the board is a finance director who looks unprepared, which is unfair and also what everyone will remember. And the single point of failure is usually one laptop, one cable, one deck, in a room used four times a year.

The same arithmetic applies, with smaller numbers, to the all-hands, the investor call, the client pitch, the regulator's visit and the annual general meeting. The desk should treat anything with an external audience or more than forty people in the room as an event. It should treat anything with the board or the executive team as a board day. There is no technique in this article that is not also good practice for an ordinary meeting. The difference is that for an event, every step is done, every time, in writing, by someone whose name is on it.

Board days are also, quietly, a test of the desk that the organisation is not aware it is setting. Take a board that has sat through two meetings where the screen worked, the deck was up, and a technician was somewhere nearby and invisible. That board will form a view of IT that no monthly report could give them. A board that has watched a progress bar forms the other view. The desk has roughly twelve chances a year to be judged by the people who approve its budget. The whole of the judgement is whether the screen came on.

The Calendar: Knowing the Dates

The first failure is not knowing the day is coming, and it is the commonest. That is because board dates are set a year in advance by the company secretary or the chief executive's assistant. They are circulated to the people who attend, which does not include the desk. The fix is to ask. Once a year, the desk lead asks the company secretary and each executive assistant for the dates of board meetings and committee meetings. They also ask for the dates of the all-hands, investor events and anything else with an external audience. The desk lead puts those dates in the desk's own calendar. The standing arrangement with each assistant, which is the subject of Working Through the Executive Assistant, includes a line asking to be told when the dates change, because they do.

The dates go in the desk's coverage calendar, the one that shows who is on the desk, who is on leave and what else is happening. That way, no technician books leave on a board day without noticing and no maintenance is scheduled for the night before. The coverage calendar itself, and why a small desk needs one, is in The Coverage Calendar. Mark the event with the name of the standby technician and the name of the deputy. That is because an event with one named technician is an event one cold away from having none.

Then open a ticket for the event, a week out, with the date in the title. The ticket is the record of the prep: the room check, the loaner, the deck collected, the rehearsal, the standby, each as a task with a name and a time. Where the tool can link tickets, as QuerySolv and many tools can, the event is one ticket with the tasks linked beneath it. In that setup, the desk can see at a glance which tasks are done. Where the tool cannot link tickets, a checklist in the ticket does the same work with a little more scrolling. The ticket has a second purpose, which is that it is where the debrief goes. That way, next quarter's prep starts from this quarter's lessons rather than from memory.

The Prep Timeline: A Week Before, the Day Before, the Morning

The prep runs on three dates, and the table below is the timeline. A week before, the desk confirms the facts: which room, who presents, from what device, and whether anyone joins remotely. It also confirms what the deck is and who owns it, and whether anything about the room has changed since the last event. The day before, the desk checks the room and builds the spare. The morning of, the standby arrives early, runs the final check, and withdraws to the back. Each date has an owner, and the owner is a name in the ticket, not "the desk".

The room check the day before is the step most desks skip because the room worked last time. It is the step that catches the most faults. That is because a room used four times a year is a room where the cable has walked and the clicker's battery is flat. Someone from marketing has re-paired the conferencing device to their own laptop. The check itself is a routine with its own card, The Room Check Routine, and this article does not repeat it. The board-day addition is that the check is done by the standby technician personally, the day before, on the actual screen with the actual deck. The result is written in the ticket. A room check is not "I looked in and it seemed fine". It is slide one on the screen, sound from the speakers, and a sentence in the ticket saying so.

The remote half deserves its own line in the check when anyone joins from outside. A non-executive director joining by video who cannot hear the finance director is a board meeting that has failed for one of its members. The board will stop to fix it. The conferencing service, the room microphone, the camera and the way the remote attendee sees the slides are tested the day before with a real call to a real colleague. The detail is in Hybrid Meetings and the Remote Half. The board-day addition is a second route: a dial-in number or a second device ready. That way, if the room system fails for the remote attendee, they are moved rather than waited for.

The Spare Laptop With the Deck on It

The spare is a laptop that is not the presenter's, signed in to an account that is nobody's. It is patched and restarted the day before so that no update is pending. The deck is loaded and already shown once on the room's screen. The spare sits on the table beside the correct adapter with the lid closed. It is the single most valuable thing the desk brings to a board day. Its value is entirely that it has been tested on that screen with that deck. A spare that has not been tested on the screen is a second thing that might not work.

The deck is the hard part, and the hard part is versions. Presenters change their decks until the moment they stand up, and the spare holding the version from Tuesday is a spare that will show the wrong numbers if it is ever used. The arrangement with the assistant is a cut-off: the deck is sent to the desk by, say, six the evening before. Any change after that is the presenter's to carry on their own device. The spare holds the cut-off version, and the presenter knows that if the swap happens they are presenting the six o'clock deck. In practice the cut-off version is nearly always the final one, because the late changes are to the speaking notes, not the slides. Where the organisation keeps its documents on a file service with version history, the spare can open the current version from there in the morning. That removes the versions problem entirely and adds the problem of whether the file service is reachable from the boardroom. The room check answers that.

The spare is signed in to a neutral account for two reasons. The first is discretion: a spare signed in as the finance director is a laptop that will show the finance director's mail notifications on a screen in front of the board. The second is that the spare must work for whoever picks it up, including the presenter who comes after the finance director and has never seen it. A neutral account with the presentation software, the conferencing client and the deck on it, and nothing else, is a machine that can be handed to anyone in the room. Lock it when it is not on the table. A laptop with the board pack on it is a document, and documents do not go to lunch.

The Rehearsal

The rehearsal is ten minutes, the day before or the morning of, in the actual room, with the actual presenter or their assistant. During it, the presenter connects their own device, sees slide one on the screen, and advances three slides with the clicker. They play any video or sound the deck contains. If anyone joins remotely, the presenter is seen and heard on a test call. That is the whole rehearsal. It is not a run-through of the content, and the technician does not offer views on the slides. It is the presenter learning that the screen works, which is the knowledge that makes them walk in calm. It is also the technician learning which of the three cables the presenter's device needs. That is the knowledge that makes the swap take a minute rather than five.

Presenters resist rehearsals, because they are busy and the room worked last time. The assistant is the route to getting them anyway. "Can you give Ola ten minutes at four, in the boardroom, with your laptop?" from the assistant is a calendar entry; the same request from the desk is a favour. When the presenter genuinely cannot, the assistant rehearses in their place with the presenter's device if it can be spared. In that case, the standby technician notes in the ticket that the presenter has not seen the room. That note is a risk the desk has recorded, not a failing it is reporting. (The presenters who skip the rehearsal are, in my experience, the ones who present from a laptop with eleven minutes of update pending.)

Rehearse the embarrassing things on purpose. Open the deck and check that the first slide is not the speaker's notes view. Check that notifications are silenced on the presenter's device. Check that the screen will not go to sleep in the middle of the chair's introduction. Check that the presenter's desktop background is something the board can see. Every one of these has happened to someone in a boardroom, and none of them is a technical fault. They are the reasons the rehearsal is on the presenter's device rather than the spare.

The Standby Technician and the Quiet Presence at the Back

The standby technician is the named person who did the prep and is, for the duration of the event, within two minutes of the room and doing nothing that cannot be dropped. For a board meeting that usually means a seat outside the room or at the nearest desk, with the assistant's number and a message channel open. It does not mean working the ordinary queue from the corridor, because a technician in the middle of a remote session is not two minutes away. The standby's deputy covers the standby's queue. On a desk of three this costs the queue a person for a morning four times a year. That is written in the coverage calendar so that the cost is a decision and not a surprise.

Inside the room the standby is invisible or absent, and the choice depends on the chair and the assistant. Some boards want a technician in the room at the back; most would rather not have one, and the assistant will say which. If in the room, the standby sits at the back, does not use a laptop with a lit screen, and does not react to anything. In that case, they have an agreed signal with the assistant for when something is wrong, usually the assistant simply looking round. If outside, the standby is reachable in one tap and the assistant knows it. Either way the standby does not approach the table unless asked and does not narrate what they are doing to the room. The whole room should be able to forget that IT exists, which is the highest compliment the desk can receive on a board day and the only one it will get.

When it fails anyway, and some mornings it will, the rule is swap, not fix. If the presenter's laptop will not connect, the spare goes on the cable and the deck is on the screen inside a minute. The presenter then carries on from the cut-off version while the standby takes the laptop out of the room. The screen loses signal: the cable is swapped for the spare cable before anyone looks at a setting. The remote attendee drops: they are moved to the second route. The diagnosis happens afterwards, in the corridor, with the fault in the ticket. In the room, the only move is the one that puts slide one back on the screen in under a minute. A technician troubleshooting in front of a board is a technician who has mistaken the room for a workshop.

The Debrief and the Event Ticket

After the event, the standby collects the spare, removes the deck from it, and writes three things in the event ticket. They are what went wrong, what nearly did, and what the next event's checklist should say differently. The near-misses are the valuable part. Examples include the clicker that was found flat at the room check and the deck that arrived four hours after the cut-off. Others are the non-executive director who had to be moved to the second route, and the presenter who had never rehearsed. Each is a line that makes next quarter's prep slightly better. A desk that writes them down for two years ends up with a checklist that fits its own boardroom exactly.

The debrief also records the hours. A board day costs the desk, in a typical small organisation, somewhere between four and eight hours of a technician's time across the week. The number belongs in the VIP cut of the monthly figures so that the cost of board days is visible beside the cost of the rest of the handling. Measuring it, and reporting the line, is the subject of the last article in this series. The point of counting is not to argue that board days are expensive; they are cheap beside the alternative. It is that a cost that is counted can be planned for. A cost that is not counted is paid by the ordinary queue on the morning of.

A Short War Story: The Updating Laptop at Marlow Shipping

At Marlow Shipping, the finance director, Henrik, walked into the quarterly board meeting with his own laptop, which had been deferring an operating system update for three weeks. He plugged it into the boardroom screen at 08:57 to find it had chosen that moment to install. The desk of four had not been told the board was meeting and had no spare prepared. The technician who ran upstairs, Sunita, spent twenty minutes trying to find a second laptop with the presentation software on it. Sunita then spent another fifteen getting Henrik's deck onto it from his mail. Meanwhile, nine board members, two auditors and the chief executive waited. The chair moved the finance item to the end of the agenda, where it was rushed. The desk lead counted the cost afterwards as a little under seven hours of the most senior time in the company. The cost also included a half-year result presented badly, and an auditor's remark in the following week's letter about "preparedness". The desk asked the company secretary for the board dates the same afternoon, built a spare that month, and has rehearsed every finance director since. A board meeting is the one meeting where the desk cannot be good on the day. It can only have been good the day before.

The Event Prep Checklist

The checklist below is the event ticket's contents, in order, with a name and a time against each line. Copy it into the ticket a week before the event, fill in the top block from the assistant, and tick the lines as they are done. Nothing is ticked on the morning that could have been ticked the day before. The last block is the debrief and is filled in before the standby goes back to the queue, while the near-misses are still fresh. One checklist serves board meetings, the all-hands, investor events and client pitches. The only line that changes is how many people are in the room.

EVENT PREP CHECKLIST — ONE TICKET PER EVENT
Event: ______________________   Date: ____________   Start: ______   Room: ______________
Assistant / organiser: ______________   Standby technician: ______________   Deputy: ______________

A. A WEEK BEFORE (owner: desk lead)
   [ ] Presenters and their devices: ______________________________________________
   [ ] Remote attendees (yes / no); conferencing service: ______________
   [ ] Deck owner: ______________   Cut-off for the final deck: ____________ at ______
   [ ] Anything changed in the room since last time (yes / no): ______________
   [ ] Standby and deputy named; both calendars blocked; coverage calendar updated
   [ ] Queue cover for the standby arranged with: ______________

B. THE DAY BEFORE (owner: standby technician)
   [ ] Room check completed on the room card; result in this ticket
   [ ] Presenter's device connected and showing slide one on the actual screen
   [ ] Clicker works; spare battery in the kit
   [ ] Audio and any video in the deck played through the room speakers
   [ ] Remote test call made to a colleague: seen, heard, slides visible
   [ ] Second route for remote attendees ready (dial-in / second device): ______________
   [ ] Spare laptop: neutral account, patched and restarted, deck loaded, shown on the screen
   [ ] Correct adapter and spare cable on the table beside the spare
   [ ] Rehearsal done with presenter (or assistant) on the presenter's device: ______ minutes
   [ ] Notifications silenced, sleep disabled, desktop fit for the room, notes view off
   [ ] Presenter has NOT rehearsed (note the risk): ______________

C. THE MORNING (owner: standby technician; one hour before)
   [ ] Final room check: screen live, sound live, conferencing joined if needed
   [ ] Presenter's device connected and showing slide one
   [ ] Spare on the table, lid closed, locked; adapter beside it
   [ ] Assistant has the standby's number; signal agreed (in room / outside)
   [ ] Standby within two minutes of the room until the event ends; deputy holds the queue

D. IF IT FAILS: SWAP, NOT FIX
   [ ] Device: spare on the cable, deck on the screen, presenter continues from the cut-off deck
   [ ] Screen: spare cable first; settings last; diagnosis outside the room
   [ ] Remote attendee: moved to the second route; fixed afterwards

E. AFTER (owner: standby technician, same day)
   [ ] Spare collected; deck removed; account signed out
   [ ] What went wrong: ______________________________________________
   [ ] What nearly went wrong: ______________________________________________
   [ ] Checklist changes for next time: ______________________________________________
   [ ] Hours spent on this event, all technicians: ______

Ola got the finance director's deck onto a borrowed laptop at 09:12 that Tuesday. The board started twelve minutes late, which the chair noted and the finance director remembered. The next quarter, Ola had the dates from the company secretary. He had a spare with the cut-off deck on it tested on the boardroom screen the evening before. He also had ten minutes with the finance director and a clicker at four o'clock. On the morning he sat outside the room with a coffee and was not needed, which he found, after the previous quarter, almost disappointing. The board did not notice him at all. That was the point.

Frequently Asked Questions