Ocean Growth Security runs a quality management system across guarding, cleaning, event staffing and specialist services. In practice that means every contract has a written standard, someone whose job is to check it, and a record of what was found.
Quality management in a service business is not a certificate on a wall. It is the difference between a client who knows whether the work was done and a client who finds out when something goes wrong.
What “quality” means on a contract
A service standard only works if it is specific. For each contract we agree:
- The scope — which areas, posts or tasks are covered, and which are explicitly excluded.
- The frequency — how often each task is performed, expressed as a number rather than “regularly”.
- The standard — what “done” looks like, described so two different people would judge it the same way.
- The evidence — what is recorded: post logs, patrol checkpoints, inspection checklists, cleaning records.
- The remedy — what happens when a standard is not met, and how quickly.
Inspection, not assumption
Every contract has a named supervisor who inspects on a set cycle rather than only when a complaint arrives. Guarding inspections check the post order is being followed, the log is current, patrols were walked and the guard is properly presented. Cleaning inspections use a written checklist per area. Event deployments are inspected before doors open and reviewed afterwards.
Inspection results are logged. That matters for two reasons: a recurring failure shows up as a pattern rather than as an argument about one bad morning, and a client can see the record rather than taking our word for it.
Complaints and corrective action
Complaints are treated as data. Each one is recorded with the date, the area, what was reported and what was done. Where the same issue appears twice, the response changes — the schedule is adjusted, the team is re-briefed or the personnel change. Repeating the same corrective action against a recurring failure is how a service quietly declines.
Escalation routes are agreed in writing at the start, so a client knows who to call and how quickly someone responds, rather than working it out during an incident.
Records and reporting
Clients receive reporting on an agreed cycle covering attendance, inspections completed, findings, incidents, and any outstanding actions. Where a client has their own reporting format or a building management system that needs feeding, we work to theirs rather than insisting on ours.
Records are retained so that a question asked six months later — what happened that night, was that patrol walked, was that area cleaned — can be answered from the file. See also health and safety and how we work.
Measures we track
- Attendance and post coverage — including late cover and any shift left short.
- Inspection completion — whether the checks that were promised actually happened.
- Complaint volume and repeat rate — a falling repeat rate is the honest indicator of improvement.
- Incident trends — by site, by time and by type, which often shows a physical problem rather than a staffing one.
- Staff turnover on a contract — high turnover destroys consistency, and consistency is most of what a client is buying.
Frequently asked questions
Do you have ISO certification?
Ask us for the current position and we will tell you exactly what is certified and what is not, rather than implying more than exists.
How often will we see an inspection report?
On a cycle agreed with the client — monthly is typical, with incident reports as they occur.
What happens if we are not happy with the service?
Tell your supervisor or account contact. The issue is logged, corrected, and the correction is recorded so it can be reviewed rather than repeated.
Can you report in our format?
Yes. Many clients have their own template or a building system that needs populating, and we work to it.