Centrov connects cleaning checklists, guard shift records, recorded time and supporting photos to the building and work. The office reviews relevant evidence before sharing the client-facing service record.
Proof of service records the work behind a cleaning visit or security shift. It can include check-in and check-out time, location context, completed checklists and supporting photos. For cleaning, the record should explain completed tasks and inaccessible areas. For security, it should distinguish attendance, observed conditions and actions taken. A timestamp alone does not verify every task or guarantee a building is safe.
Illustrative cleaning workflow
For a fictional evening clean, the office reviews what happened at the building before sharing the appropriate service information with the client.
| Record | Illustrative visit | Why it matters |
|---|---|---|
| Assignment | Evening clean · 18:00–00:00 | Identifies the job and expected visit |
| Time | Recorded start, finish and approved hours | Connects the work to the scheduled shift |
| Checklist | Agreed tasks and recorded exceptions | Makes missing or incomplete requirements visible |
| Supporting photos | Evidence attached to the visit | Adds context for review; a photo alone does not prove quality |
| Office review | Review the record and resolve exceptions | Client-facing evidence follows approval |
The client-facing record should explain the service without exposing wages or private workforce details. Location evidence depends on the enabled workflow and device permission.
Photos and explanations lose their value when nobody can reliably connect them to the job and visit.
The client-facing record should reflect approved work rather than exposing every internal note or correction.
Time and service evidence are easier to explain when they remain close to the invoice source.
The worker sees the shift and job instructions in the phone experience.
Check-in and check-out are written against the actual shift.
Checklists and supporting evidence remain attached to the service record.
Managers inspect and approve the operational record.
Approved evidence can support the client record and the related invoice.
The record identifies the job, visit and worker context behind the proof.
Internal operational review happens before client-facing use.
The job retains the approved record across future visits and contracts.
For an illustrative overnight guard shift, the office can review recorded time, checklist answers, site notes and supporting photos. A completed checklist records the guard’s submission; it does not independently verify every event at the building. Review any separate patrol or incident record before publishing selected information for the client.
See a fictional security client-report example →Centrov can record location context for field check-in and check-out where the business enables that workflow and the device permits location access.
Yes. Supporting photos can be attached to the work record for review. Selected patrol visit photos are published to the client only after office review.
No. Client-facing service information is separated from private workforce and profitability data.
Bring a real job or contract if you want to examine the numbers and handoffs. It is optional.
A 30-minute walkthrough with a real person. Use our example or bring a contract — entirely optional.