Cleaning a Government Building: Security and Compliance Come Before the Mop

Cleaning a government building looks like cleaning any other commercial facility from the outside — trash removal, restrooms, floor care, common areas. What's different is everything that has to be true before the cleaning even starts: who's allowed in, when, unsupervised or not, and what happens to the documentation proving all of that was followed. Treat it as a standard janitorial contract and the compliance gaps show up during the first audit, not the first inspection.

Security Is the First Line of the Scope

In a private office building, the scope of work usually starts with what gets cleaned and how often. In a government building, it starts with who is authorized to be there and under what conditions — because most government facility cleaning happens after hours, when a crew is often the only non-security personnel in the building. Every subsequent decision about staffing, scheduling, and access flows from that security requirement, not from the cleaning task list.

This ordering matters for how a facility should evaluate proposals, too. A vendor's response should demonstrate an understanding of the security requirement before it gets to the cleaning specifics — how they'll manage access, how staffing changes get communicated to building security, and how they coordinate with whatever security presence the facility already has on-site. A proposal that jumps straight into mop frequencies without addressing any of that is written by a vendor who hasn't done this kind of work before.

Background Checks and Cleared Personnel

Personnel assigned to a government facility should go through screening that exceeds a standard commercial hire check — identity verification, multi-jurisdiction criminal history, and in some cases a facility-specific clearance process managed by the agency itself. This isn't a one-time formality. It needs to be re-run on a defined cycle and applied consistently to every person who might cover a shift, including substitutes and float staff, not just the primary assigned crew.

It's worth understanding the difference between a vendor's internal background-check standard and a facility-specific clearance the agency itself administers. Some government buildings require every contractor employee to go through the agency's own badge or clearance process in addition to the vendor's own screening, which adds lead time to onboarding new staff. Build that lead time into your staffing plan and ask the vendor upfront how they handle a sudden staffing gap when a replacement hasn't cleared the agency's process yet.

Vetting and re-vetting crews

A vendor should be able to produce, on request, a current roster of every individual cleared to work in the facility along with the date of their last screening. If a crew member leaves the account or a new hire is added, that roster needs to update before the person's first shift — not retroactively after someone notices an unfamiliar face in a restricted hallway.

Sensitive Areas and Restricted Access

Not every space in a government building gets treated the same way. Records rooms, server closets, evidence storage, and offices handling sensitive material typically require either escorted cleaning, restricted-hours-only access, or exclusion from the routine scope entirely, with those areas handled separately by agency staff or specially cleared personnel. The RFP or contract should name these areas explicitly rather than leaving "sensitive areas" as an undefined category the crew has to guess at on-site.

A useful exercise during onboarding is a joint walkthrough with agency security staff to physically mark every restricted area on a floor plan before the crew's first shift, rather than relying on a written description alone. Floor plans age, offices get reassigned, and a room labeled "storage" on a five-year-old drawing may now house something that requires a different access protocol — a physical walkthrough catches that discrepancy before it becomes an incident.

Escort requirements

If any part of the facility requires an escort, define who provides it, during what hours, and what happens if the escort isn't available on a given night — because "we'll skip that room" is not an acceptable default answer for a documented compliance requirement. Build the escort logistics into the contract itself, not into an assumption that it'll work itself out.

It also helps to define what happens on nights when scheduled maintenance, an unrelated agency event, or a security incident changes normal access patterns. A crew that shows up expecting standard access and finds a wing locked down needs a documented fallback — skip and reschedule, notify a specific contact, or wait for clearance — rather than an ad hoc decision made on the spot by whoever happens to be on shift that night.

After-Hours Protocols and Chain of Custody

After-hours cleaning in a secured building requires a documented chain of custody for keys, access cards, and alarm codes — who holds them, how they're logged in and out, and what the protocol is if one goes missing. This isn't excessive caution; it's the same standard applied to any contractor with unsupervised access to a secured facility, and a vendor unfamiliar with government work will often not have a formal process for it at all.

Key and access control

Ask specifically how the vendor manages physical keys or access credentials between shifts — a shared master key with no log is a real liability in a government facility, while individually assigned, trackable credentials with a check-in/check-out log is the standard a compliant vendor should already have in place.

If the facility uses electronic access badges rather than physical keys, ask how quickly a departing employee's credential gets deactivated. A key can be physically collected on someone's last day; a badge that isn't deactivated promptly stays active in the system indefinitely, and that's exactly the kind of gap that surfaces during a security review of a facility's access logs.

Compliance Documentation and Audit Trails

Everything above only matters if it's documented in a form that survives an audit — cleared-personnel rosters, training records, inspection logs, and access logs should all exist in a retrievable format, not in someone's memory or a filing cabinet at the vendor's office. Ask how records are stored, how long they're retained, and how quickly they can be produced if the agency requests them during a compliance review.

It's worth building a specific retention period into the contract itself — many agencies require records to be kept for a set number of years after a contract ends, and a vendor should be able to commit to that in writing rather than treating it as a best-effort courtesy. Ask, too, whether records are stored digitally with backup, since a filing cabinet at a vendor's office is a single point of failure if there's ever a dispute or an incident review months after the fact.

Why This Standard Protects Everyone

None of these protocols exist to slow a cleaning contract down for its own sake — they exist because a government building carries risk that a standard commercial lease doesn't, and the cleaning vendor is one of the few outside parties with routine, unsupervised access to it. A vendor who treats these requirements as the baseline rather than an inconvenience is signaling that they understand what kind of facility they're working in, and that understanding is what actually keeps a long-term government cleaning relationship out of trouble.