Government

Written for a reader who was not there

Most cleaning documentation is written for a client who walks the building and already knows roughly what happened. Public-sector documentation is read by someone else entirely — an auditor, a procurement reviewer, a records request, occasionally a council committee — months later, with no context beyond what the record itself contains.

That changes what adequate looks like. “The second floor was serviced Tuesday” is normal in a commercial log and inadequate here. The record has to answer at the level of a specific area on a specific date, with an attributable person, and it has to be exportable in a form that holds up without anyone from either side narrating it.

Every completion is captured that way through digital checklists, which is the same mechanism as our other accounts — the difference is retention and export format, agreed at contract stage.

What was not done is part of the record

The most important property of an auditable record is that it can show a gap.

Rooms are locked. Areas are in use. A courtroom is sitting, an office is closed, a space was reallocated without anyone telling the cleaning contractor. In a conventional operation, those simply do not appear — the log shows what was completed and is silent about the rest, which reads as a claim that everything was performed.

Here, uncompleted scope is recorded as uncompleted, with the reason, and rescheduled. It is mildly uncomfortable and it is the entire point: a record that cannot show a shortfall cannot be used as evidence of anything.

The same logic governs proof of service across the company, and it is why Our Mission is phrased around surfacing failures rather than around promising they will not occur.

Scope compliance against the contract

Public-sector cleaning disputes are almost never about whether the vendor cleaned. They are about whether what was delivered matches what was specified — a frequency that drifted, an area quietly dropped, a scope interpreted generously in one direction.

Contracted scope is tracked against performed work, and the variance is visible to both sides continuously rather than reconstructed at renewal from two sets of recollections.

Vetting and access

Background verification is set to what your facility requires, with records held against the account. Where a building needs clearance beyond standard commercial vetting, that is scoped explicitly before a contract starts — this is a category where discovering the requirement late is a genuine problem for both parties.

Access control, escort requirements, key and badge procedures and restricted-area rules are followed as written and covered in site induction. Our staff do not improvise around an access system.

Public-facing areas

Service counters, lobbies and public restrooms degrade during opening hours and need attention while the building is occupied — the same day-scope reasoning as corporate offices, with usage counting driving frequency where sensors are installed. Disruptive work stays outside public hours.

Certification and reporting

Protex Verified™ requires a dual signature — supervisor and client — which fits public accountability well, since it produces a certification neither party issues alone. Reporting formats and retention periods are agreed to match your own accountability process rather than to a standard template.