Office and Facilities Management for Administrative Assistants

Most administrative roles in small and mid-size companies absorb a substantial chunk of facilities work without anyone formally describing it that way. The lease comes up for renewal and someone has to track the dates. The badge system needs new cards every other week. The supply closet is always almost empty. The HVAC has been making a sound for two days. None of these are dramatic; all of them produce visible failure if they go untended. This page is for the admin who has — by accident or by accumulation — become the person who keeps the office actually working.

The vendor relationship advice in the vendor management section still applies. This page covers the wider scope: the building, the systems inside it, the people who maintain those systems, and the calendar of recurring obligations that quietly compound if no one is tracking them.

The Calendar of Recurring Obligations

The first move when you inherit facilities responsibility — formally or informally — is to build a calendar of every recurring obligation tied to the office. Most of these arrive without notice the first time and produce panic. The same items, on a calendar with reminders set six weeks in advance, become routine.

Items that belong on the calendar

• Lease milestones. Renewal date, notice deadlines (the date you must give notice if not renewing — almost always months before the lease end), rent escalation review, and any options-to-extend windows.
• Insurance renewals. Building, contents, business interruption, cyber, professional liability — whichever apply. Renewal dates tend to scatter across the year; centralizing them prevents lapses.
• Compliance and inspection cycles. Fire safety, elevator, alarm system, sprinkler, electrical, HVAC servicing. Some are landlord obligations; some are yours. Knowing which is which is half the work.
• Permits and licenses. Business permits, signage permits, occupancy permits, food-handling permits if you have a kitchen, and any local registration that has an annual or biennial renewal.
• Service contracts. Cleaning, security, IT support, copier and printing, water cooler, plants, pest control, waste management. Each has its own renewal cycle and its own way of becoming expensive when on autopilot.

Build this once, in a single shared document, and put a 60-day reminder on every renewal. The work to maintain it after that is small. The work to recover from a lapsed permit or an auto-renewed contract you never reviewed is much larger. The conversation that happens in the 60-day window — what to actually say to the vendor to get better terms — is the focus of vendor renewals and negotiation.

Access and Security

Building access is one of those areas where the cost of attention is small and the cost of inattention shows up in surprising ways — a former employee's badge that still works, a vendor with after-hours access that no one remembers granting, a new hire who couldn't get into the building on their first day because no one ordered the badge. The new-hire side of that — making sure the badge, the laptop, and the desk are ready before they walk in — is in onboarding new employees: the admin's playbook.

The badge audit

Run a quarterly audit against the active employee list:

• Pull the full list of active badges from the access system.
• Match against current HR-confirmed headcount.
• Investigate any badge that does not match — former employees, contractors whose engagement ended, named badges issued to people no one recognizes.
• Deactivate, document, and report.

The audit takes an hour and finds problems that are otherwise invisible. The first one is always the most surprising; subsequent audits get faster.

Visitor and contractor protocols

Two patterns to standardize:

• Visitor sign-in. Even a simple log — name, company, host, time in, time out — produces an audit trail when something goes wrong. Many companies have moved to a digital visitor system; if yours has not, a paper log at reception is sufficient.
• Contractor escort policy. Cleaners, IT contractors, repair technicians, delivery drivers — decide explicitly which categories require an escort and which do not, and write the rule down. Without a written policy, the practice drifts toward whoever happens to be at reception that day.

The Day Something Breaks

Most facilities admin work is preventive. The visible part is reactive — the day the elevator stops, the printer dies before a board meeting, the building loses power, the air conditioning fails on the hottest day of the year. The discipline that produces a calm response is the discipline of having pre-built the contact list, the escalation path, and the decision criteria before you need them.

The emergency contact one-pager

A single laminated page, posted somewhere visible, listing:

• Building management's main number, after-hours number, and emergency number.
• Power utility and gas utility outage numbers.
• The 24-hour locksmith.
• The 24-hour plumber and electrician.
• HVAC service contractor.
• IT support after-hours line.
• Local non-emergency police line.
• Insurance claims line.

None of these numbers help you when they live only in your phone, where your colleagues cannot find them in your absence. Print the page. Update it twice a year. Keep one copy at reception, one in your desk manual, and one taped inside a cabinet that everyone knows about.

The decision criteria

Most facilities incidents fall into one of three response categories:

1. Wait it out. A minor outage, a brief disruption, something the building is already aware of. Update people in the office, set expectations, and let the systems work.
2. Activate a vendor. Something is broken and a contractor needs to come fix it. Authorize the call, document the incident, and follow up on the invoice.
3. Escalate to leadership. Something is broken in a way that affects business operations significantly — a major outage, an evacuation, an injury, a security incident. Get your executive on the phone fast.

The middle category is where admins under-act and over-act both. Under-acting waits for permission that does not need to be asked; over-acting wakes the executive at 11 PM about a problem that could have been handled in the morning. The line is calibrated by experience; document each incident afterward to inform future calls.

Supplies and Pantry

Office supplies and pantry stocking sound trivial and quietly consume hours of admin time if not systematized. The fix is simple: move from on-demand reordering to scheduled review.

• Set a recurring weekly walk-through. Same day, same hour, fifteen minutes. Note what is low, what was over-ordered last cycle, what nobody is using.
• Use a single supplier per category wherever possible. Office supplies, pantry, paper, ink — consolidating reduces the number of accounts and invoices to track and usually unlocks volume pricing.
• Set par levels, not "as needed." A par level is the threshold below which you reorder. Coffee at three pounds, paper at two reams per printer, hand soap at four bottles total. The discipline removes guesswork.
• Keep a "do not reorder" list. Items that were tried and rejected. Without this list, the same regrettable item gets reordered by whoever is covering for you the first time.

Office Moves and Reconfigurations

The largest facilities project most admins handle is an office move or significant reconfiguration. These are full project-management exercises that benefit from being treated as such — see the workflow tools that pair well with project work. Two specific things to flag for office-move projects in particular:

• The internet and phone cutover is the single highest-risk item. Coordinate with the carrier four to six weeks ahead. The day of the move, you want the new space already provisioned and tested — not waiting for an installer.
• Critical operations need a coverage plan for moving day. If billing runs Tuesday morning and you are moving Tuesday morning, billing runs from somewhere that is not the new office. Identify the workflows that cannot pause and pre-arrange a fallback for each.

Working With Building Management

For most office tenants, the relationship with the building's property management team is one of the most consequential professional relationships you maintain — and one of the most undervalued.

• Know the names. The property manager, the building engineer, the security lead, the cleaning supervisor. First-name basis solves problems faster than ticket systems do.
• Do not save every issue for the formal channel. A friendly heads-up about a flickering light fixture lands differently than a formal maintenance ticket and is more likely to get attention.
• Document significant items in writing afterwards. The conversation you had in the lobby is real; the email summary you sent immediately afterwards is what survives turnover when the property manager moves on.
• Pay attention to building communications. Notices about elevator maintenance, fire-system testing, alarm tests, or scheduled outages need to flow to your team before the disruption, not during it.

The Quiet Compounding Habits

Three small habits compound into the difference between an office that runs and an office that limps:

• The end-of-week walkthrough. Five minutes, every Friday, walking the floor with the eye of a visitor. Burned-out bulbs, dusty conference rooms, broken chairs, walls that need touch-up paint, signage that has gone crooked. Note them; act on them next week.
• The incident log. Every facilities issue, however minor, gets one line in a running log. Date, what happened, what was done, what it cost. After a year, the log is the single most useful document in any conversation about renewing a contract or budgeting for the next year.
• The vendor scorecard. Two lines per vendor at year-end: what was good, what was not. Use it to decide who stays in the rotation and who is up for renegotiation. The act of writing it forces clarity that "we'll keep them, they're fine" does not.

Facilities work is not glamorous. Done well, it is the foundation that lets the rest of the business operate without friction — and the foundation of an admin's reputation as the person who keeps things running. The recurring obligations, vendor relationships, and incident histories all belong in the desk manual; the rapid-response disciplines pair naturally with the broader thinking in handling difficult calls and escalations.