A facility manager does not need a surveillance feed to know whether a cleaning vendor delivered the contracted service. The manager needs a small, reliable set of records that answers what was scheduled, what building or area was covered, what work was completed, what was missed or unsafe, who reviewed the exception, and what happens next. Proof of work is useful when it supports a contract decision; it becomes noise when it collects personal data that nobody can interpret.
ISSA quality-management materials commonly frame cleaning quality around a defined scope, measurable specifications, inspection, corrective action, and communication. That approach is better than asking for “more photos” because it starts with the outcome the facility bought. The vendor and the buyer should agree on evidence before a dispute, including what a timestamp, checkpoint, photo, or supervisor sign-off can and cannot prove.
StockPoint gives a facility manager a client-facing view of per-building punch verification, photo and PIN evidence, live checkpoint status, and exceptions, with GPS shown at honest accuracy rather than as false precision. The platform can help connect service proof to the vendor’s payroll and audit record, but it should not turn a cleaner’s private movement history into a customer dashboard.
Define the result before demanding the evidence
Begin with the service specification. A nightly restroom clean, a weekly floor-care visit, and a quarterly high-dusting project require different evidence. The specification should identify the areas, frequency, quality standard, access window, supplies or methods that matter, and the process for reporting a condition the vendor cannot safely address.
Time evidence answers whether the assigned crew arrived and departed within the agreed window, subject to the contract’s tolerance. It does not prove that every task was completed. Location evidence can show that the work was associated with the building or a checkpoint, but a GPS estimate may be less reliable indoors or around dense structures. Task evidence and an inspection are needed for quality.
Write the evidence rule in ordinary language. “The vendor will provide a building-level arrival and departure record, a supervisor-reviewed checklist or inspection, and photos only for agreed exceptions or completed specialty work” is clearer than “the vendor will provide all data.” If the buyer expects a report every morning, price the labor and system support required to create it.
Use several modest signals instead of one magical signal
A useful attendance record identifies the building, date, assigned service window, worker or crew identifier as appropriate, punch events, and any correction. The client may not need a worker’s home address, continuous location history, or personal phone data. The vendor should be able to show that an authorized person reviewed an exception without exposing unrelated employee information.
A building PIN or checkpoint can corroborate presence at a designated location. A photo can show a condition such as a completed floor, a stocked supply area, or an unresolved spill, but a photo has framing and timing limits. A supervisor sign-off can show that someone reviewed the result; it is not proof that the supervisor personally inspected every surface unless the process says that happened.
StockPoint’s photo and PIN verification is most defensible when it is paired with a defined assignment and a human exception workflow. The client portal can show the status the contract calls for, while the vendor keeps the fuller payroll and audit record. Avoid using “GPS verified” as a substitute for the work specification; honest accuracy is more credible than a precise-looking dot.
Photos should answer a question, not create a new risk
Photos deserve a narrow purpose. Require them for agreed quality conditions, specialty work, damage discovered on arrival, or a corrective action. Do not require a worker to photograph every room if a checklist, inspection, or sample-based quality program answers the buyer’s question with less intrusion. A camera may also capture people, personal documents, security information, or customer property that should not enter a portal.
Set a retention rule before using photos. The vendor and facility should know who may view them, how long they are needed for a service dispute or insurance matter, and how they are deleted or archived. The rule should account for the contract, applicable privacy obligations, and the employer’s need to retain related wage and personnel records. A client should not keep an employee’s entire route history just because one exception photo was useful.
A photo does not prove a clean result by itself. ISSA quality concepts emphasize specifications and inspection, and the buyer should decide whether the inspection is visual, measured, sample-based, or complaint-driven. If a client uses a photo to issue a service credit, give the vendor a fair path to explain access restrictions, an emergency, a changed scope, or a condition outside the vendor’s control.
Treat exceptions as part of the service
The most important proof may be an exception record. A missed task, locked room, broken dispenser, unsafe chemical storage, or late arrival should have a reason, owner, and next action. A green completion status with no way to explain a blocked area is less useful than an amber exception that tells the facility manager what was attempted and what decision is needed.
Use a shared vocabulary for status. “Completed,” “completed with condition,” “not accessible,” “not safe to perform,” and “corrective action pending” mean more than a percentage that hides the underlying event. The vendor’s supervisor should review the worker’s note, avoid blaming the worker for a building access issue, and set a reasonable closeout time.
A client portal can show live checkpoint status without claiming that the client is watching the crew. The facility manager should be able to see what needs attention, open an approved photo or note, and acknowledge a resolution. The portal should also preserve who changed a status and why, because silent edits make both parties distrust the record.
Make the vendor accountable without managing the vendor’s employees
Facility managers should separate service accountability from employment control. It is reasonable to define the result, access rules, building security requirements, inspection method, and escalation contact. It is a different matter to direct an individual cleaner’s minute-by-minute method, discipline the worker, set the worker’s break, or change the vendor’s staffing decisions. The vendor should own employment, payroll, training, and supervision unless the parties have taken on a different legal relationship with advice.
The DOL’s recordkeeping guidance requires employers to maintain accurate time and wage information for covered employees, but the facility manager is not the vendor’s payroll clerk. A buyer can request an attestation that the vendor maintains required records or a project-level report that supports invoice review without demanding every employee’s personal file. The contract should state the purpose and field limits of any audit access.
StockPoint helps preserve the boundary by giving the facility the agreed proof view and the vendor the fuller worker and payroll view. If a client sees a missed checkpoint, it can ask the vendor’s supervisor for a resolution rather than instructing a cleaner directly. That model improves accountability while reducing the risk that a well-intentioned manager becomes an informal dispatcher.
A worked example: evidence that supports a fair invoice decision
Proof of work should be tested against a real dispute before the contract is finalized. Imagine a weekly floor project at a 40,000-square-foot building. The vendor reports a 10:00 p.m. arrival, a project checkpoint, two progress photos, a supervisor inspection at 1:00 a.m., and an exception that a storage corridor was inaccessible. The facility can decide whether the evidence is enough to accept the invoice, request access, or issue a targeted correction without alleging that the entire visit did not occur.
Now imagine the same job with only a green “complete” badge. The manager has no way to distinguish a missed corridor from a missing device event, and the vendor has no place to show that access was denied. The first record is not perfect, but it supports a fair decision. The second invites a dispute over assumptions.
The numbers in this example are illustrative, not a service standard. Each facility should set the scope, inspection frequency, evidence fields, and service-credit rule with the vendor. Use the building-service vendor audit guide and the RFP language guide to make the evidence contract-specific rather than universal.
Design for the user who must act on the record
Set an access and governance model. Name the facility users who can see status, the vendor users who can correct a record, the retention period, the escalation contact, and the process for a security or privacy incident. If the building has sensitive areas, define where photography is prohibited and what alternative evidence is acceptable.
Review the report with the people who will actually use it. A night manager may need unresolved access exceptions before opening, while procurement may need a monthly summary and invoice reconciliation. Do not force every audience to receive every field. The best report may have a live operational view, a supervisor exception queue, and a limited monthly scorecard.
Bilingual workforce surfaces are valuable when the vendor’s workers need to understand assignments, correction requests, or pay-related records. They should not be used to shift responsibility for the contract onto workers who cannot control the customer’s evidence standard. The vendor’s supervisor remains accountable for review and communication.
Put the evidence standard in the contract
A sound requirement names the evidence, its purpose, its limits, and the dispute path. Ask for building-level time and location context, defined task or inspection evidence, photos only where they add value, documented exceptions, supervisor review, and a retention rule. Avoid requirements that demand continuous tracking or indiscriminate images without a clear operational reason.
StockPoint’s features can give a facility manager client-visible status and proof while preserving the vendor’s connected punches, payroll preparation, per-worker locking, and audit history. The product does not decide whether a cleaning result meets an unspoken standard, and it does not replace the buyer’s contract administration. Good evidence makes the conversation narrower and more factual.
Sign up at getstockpoint.com to give your cleaning vendor and facility team a shared record of building assignments, proof-of-work photos, checkpoint status, exceptions, and reviewed corrections. You get a practical client portal and an audit-ready operating layer without requiring invasive surveillance as a substitute for a well-written scope.