Office Manager

I keep a running list that separates urgent from important, because those two categories get confused constantly in an office setting. A broken printer feels urgent to whoever is standing in front of it, but it rarely is compared to something like a contract renewal deadline or an upcoming audit. I triage quickly by asking what actually breaks if it waits an hour versus what breaks if it waits a day, and I communicate honestly with people rather than silently reordering things, since most frustration comes from feeling ignored rather than from the wait itself. I also batch similar small tasks, like approvals or quick questions, into set windows during the day so I am not constantly context switching, which is where a lot of time actually gets lost. At my last role I was the single point of contact for a 40 person office, and the batching approach was what let me actually get to strategic work like vendor negotiations instead of only ever being reactive.

I treat vendor relationships as ongoing, not transactional, because the vendors who know they are dealing with someone consistent and reasonable are the ones who prioritise you when something goes wrong. I keep a simple tracker of contract renewal dates, service level expectations, and who my main contact is at each vendor, so nothing lapses by accident. When negotiating, I come prepared with what comparable services cost elsewhere, which gives me a real basis for a conversation rather than just asking for a discount. I also make a point of giving honest feedback when service dips, early and directly, rather than letting frustration build until a renewal decision. In my last role I renegotiated our office supplies and cleaning contracts within the same quarter and brought total spend down by about 15 percent without dropping service quality, mostly by consolidating two vendors into one with better volume terms.

I treat discretion as a default setting, not something I turn on only for obviously sensitive topics, because in an office manager role you see salary information, HR matters, and leadership discussions that are not always flagged as confidential but clearly should be treated that way. I never discuss what I have seen with colleagues, even casually, and I am careful about where documents are physically left or screens are visible. If I am ever unsure whether something is meant to stay private, I default to treating it as private and ask the relevant manager directly rather than guessing. I also keep any sensitive digital files properly access restricted rather than in a shared drive everyone can browse. Trust is the core of this role, and it only takes one slip to lose it permanently.

I have used Google Workspace and Microsoft 365 daily for scheduling, documents, and shared calendars, and I am comfortable setting up shared folders and permission structures so the right people have access without a mess of duplicate files. For team communication I have used Slack, and I set up dedicated channels for facilities requests so they do not get buried in general chat. I have also managed expense tracking through tools like Expensify and basic budget tracking in spreadsheets, reconciling monthly against actual invoices rather than just approving submissions on trust. For meeting and event coordination I use shared calendar tools with room booking built in, and I always build in buffer time between back to back meetings because a schedule with zero slack breaks the first time something runs long. I pick up new tools quickly because the underlying logic across most office software is similar once you know one system well.

When I joined my last company, new hire onboarding was handled ad hoc: a laptop request here, a building access request there, often with a day or two gap before someone had what they needed to actually start working. I mapped out every step from offer acceptance to first day and built a single checklist with owners and deadlines for each item, IT, facilities, and HR all working from the same document instead of separate email threads. I also built in a two day buffer before start date as a hard deadline rather than a suggestion. Within two months, every new hire had full building access and a working laptop by their first morning, up from roughly 60 percent before the change. It took an afternoon to build and saved recurring frustration for both new hires and the teams waiting on them.

Two team members were in an ongoing disagreement over shared desk space after we moved to a hybrid schedule, and it had started to affect the wider team's mood since people were picking sides without meaning to. I spoke to each of them separately first, to understand what they actually needed rather than what they were saying in the moment, and it turned out one needed a quiet space for client calls while the other just wanted consistency in where they sat. I proposed a simple fix: a bookable quiet room for calls, and a fixed desk assignment for the other person, which addressed both underlying needs rather than forcing a compromise neither wanted. Both agreed, and the tension dissolved within the week. I learned that most desk conflicts are really about a different unmet need dressed up as a scheduling problem.

Our office lost power during a storm on a day we had an important client visit scheduled for that afternoon. I first confirmed with the building management how long the outage was expected to last, which turned out to be uncertain, so I did not wait on that answer. I quickly booked a nearby meeting space with wifi and moved the client meeting there, notified everyone affected with clear instructions, and arranged for a colleague to redirect anyone who showed up at our office in the meantime. Power came back about three hours later. The client never knew there had been an issue, because the alternative venue was booked and confirmed before I told anyone the original plan had changed. Staying calm and moving to a backup plan immediately, rather than waiting to see if the problem resolved itself, was the difference.

I build a simple annual budget broken into categories, supplies, facilities, software subscriptions, events, with monthly actuals tracked against it in a spreadsheet, so variance is visible early rather than discovered at year end. I review recurring subscriptions quarterly specifically to catch tools nobody is using anymore, which is one of the most common places budgets quietly leak. I flag anything trending significantly over budget to my manager as soon as I notice it, with a reason and a proposed fix, rather than waiting for a scheduled review. In my last role I identified about £2,000 a year in unused software licenses this way, simply by cross checking active user counts against what we were being billed for. Budget tracking only works if someone actually looks at it regularly, not just files it after building it.

I start by identifying the must have attendees versus the nice to have ones, because trying to find a slot that works for everyone often means the meeting never gets scheduled at all. I use shared calendar tools to spot genuine overlaps rather than emailing back and forth, and for larger events I build a simple run sheet with timings, owners, and a clear point of contact for anything that goes wrong on the day. For anything involving external guests or a venue, I confirm details in writing at least a week ahead and again the morning of, since assumptions are where most event logistics actually fail. For a recent all hands with about 80 people across two office locations, I coordinated catering, AV setup, and a livestream link for remote attendees, and the only real issue on the day was a projector cable, which I had a backup for because I had walked through the room the day before.

I try to give leadership the information they need to make the trade off themselves rather than silently deciding for them, since they often do not realise two requests are actually in conflict until someone points it out. If my manager asks for something with a tight deadline while I am already committed to another priority they set, I flag it directly: here is what I am currently working on, here is the new request, which one takes precedence. Most of the time that clarifies things in thirty seconds and avoids me either dropping something important or missing the new deadline without warning. I also try to build in a buffer on recurring commitments so a single urgent request does not derail everything else, and I keep leadership informed proactively on anything at risk of slipping rather than waiting to be asked.