Client Case:
- Other — Commercial Landscaping & Grounds Maintenance
- VIC — Melbourne Metropolitan & Outer Suburbs
- Medium (21-100)
- Already Certified
- $1M-$5M
From Quality Coordinator to No Quality Coordinator: How a Melbourne Landscaper Made the Role Redundant in 12 WeeksFive regions. Five team leaders running five different ways. A $68K quality coordinator maintaining documents nobody in the field had seen. TMCS made the role unnecessary.
The Situation
Company Background
Greenline Property Services maintains parks, sports fields, road verges, garden beds, and public open space across Melbourne’s eastern and south-eastern suburbs. Five regional teams, each led by a team leader, running council grounds maintenance contracts across five local government areas. The owner — Dean — started mowing commercial properties twenty years ago with a ute and a trailer. Revenue sits around $1 million. Twenty-five people: Dean, one admin person in the office, five regional team leaders, and roughly eighteen field workers — about a third full-time, the rest casuals on the Gardening and Landscaping Award.
Dean won his first council contract eight years ago. Then a second. Then a third. Every new contract required ISO 9001 certification. He got certified through a consultant who built a documentation package. The auditor was happy. The certificate went on the wall.
Two years ago, the consultant told Dean he needed a quality coordinator to maintain the system. Dean hired one. Complaints kept rising.
Internal Context
The quality coordinator sat in the office. She maintained the quality manual, updated document revisions, tracked internal audit schedules, prepared management review PowerPoints, and filed corrective action reports. She did her job well — the surveillance auditor said the documentation was excellent.
The five team leaders had never opened the quality manual. They ran their regions the way they had always run them — each one differently. The eastern suburbs team leader did pre-start checks every morning. The south-east team leader did them when he remembered. One team leader trained new casuals for a full day. Another handed them a whipper snipper and pointed at the nature strip. Mowing heights, garden bed standards, weed treatment schedules, sports field line marking — five different approaches across five regions.
Council complaints were rising 22% year-on-year. Dean found out about complaints two or three weeks after they were lodged — when the council contract manager called him directly. The quality coordinator tracked audit non-conformities. She did not track operational complaints because the system was not designed to capture them. The system was designed to pass an audit. It passed every audit. And complaints kept rising.
Market Context
Three of Dean’s five council contracts were up for renewal within twelve months. Council procurement had changed — it was no longer cheapest price wins. Tender evaluations now weighted quality system maturity, complaint history, and demonstrated continuous improvement. Two competing landscapers were already certified with documented lower complaint rates. Dean’s complaint rate was rising, and he had no data to explain why, where, or what he was doing about it.
The Victorian local government sector was also tightening environmental requirements for grounds maintenance contractors — chemical application records, water usage tracking, native species management plans. Dean’s quality coordinator maintained the ISO documentation but had no mechanism to capture operational environmental data from five field teams across five councils. The councils wanted evidence of systematic management. Dean had a certificate and a folder of procedures his team leaders had never read.
Risks and Opportunities
Main Risk/ Opportunity:
Three council contracts up for renewal in 12 months — rising complaint rate and no quality data to defend performance at tender evaluation
Other Risks and Opportunities:
Three council grounds maintenance contracts worth $680K combined — all up for renewal within 12 months, all requiring quality performance evidence at tender
Council complaint rate rising 22% year-on-year — no root cause data exists because the quality coordinator tracks audit findings, not operational complaints
Two competing landscapers already certified with lower complaint rates — councils evaluating quality system maturity, not just price
Casual workforce turnover at 45% — no onboarding standard, each team leader trains differently, service inconsistency across regions
Context Barriers
Main Barrier:
Every consultant said the solution was a quality coordinator — the company hired one two years ago and complaints kept rising because the role maintained documents, not quality
Other Barriers:
Quality coordinator hired two years ago on consultant advice at $68K/year — complaints continued rising because the role maintained documents, not management architecture
Quality coordinator had no authority over team leaders and no visibility over field operations — she audited paperwork in the office while quality failed on site
Five team leaders ran five different approaches to the same service — no common standards, no shared data, no mechanism for the owner to compare regional performance
Owner assumed rising complaints meant he needed more quality staff — not that the $68K role was compensating for a system that was never designed to manage quality
The Intervention
Diagnosis
The quality coordinator was not the problem. She was a symptom of the problem. The ISO consultant who designed the original system built it around clause structure — not around how Greenline actually delivers grounds maintenance across five regions. The system described what an auditor checks. It did not describe what five team leaders need to manage. So when complaints rose, the consultant’s answer was predictable: hire someone to manage quality. That answer is The Quality Manager Myth.
ISO 9001:2015 deliberately removed the requirement for a management representative — the dedicated quality person — because the standard’s architects understood that quality is a management function, not a staff function. When quality is delegated to a coordinator, it becomes that person’s job to maintain the system. Everyone else’s job is to do their work. The two never connect. The coordinator maintains documents in the office. The team leaders manage their regions in the field. The documents describe one reality. The field operates in another. The auditor sees the documents. The council sees the field.
Dean’s real problem was structural. He had five regions operating as five independent businesses with no common management architecture. No defined authority boundaries for team leaders. No measurable guidelines flowing from Dean’s strategic priorities to each region’s operations. No mechanism for complaints to be captured at the source, root-caused, and fixed through standard procedure updates. He had a quality coordinator maintaining a parallel documentation universe and a business running without a management system. The $68K salary was not solving the problem. It was funding the illusion that someone was looking after quality while the architecture that should deliver quality did not exist.
Phase 1: Strategic Level - Management by Guidelines
- Weeks 1–3
The owner defined four strategic guidelines with measurable control items — complaints, contract retention, productivity, and turnover by region
We started where TMCS always starts: does the leader know the difference between their authority and their responsibility? Dean had authority over his means — five teams, the equipment, the casual workforce, the supplier relationships. But he had never defined what he was responsible for in measurable terms. “Keeping councils happy” is not a control item. “Doing good work” is not a target. He was managing contracts, not results. And the quality coordinator was maintaining documents, not management.
We defined the business. Not a mission statement — a business definition. Greenline’s products: grounds maintained to council specification, on schedule, within budget. Clients: five local councils, each with specific service level agreements. Four markets: customers (the councils and the communities who use the parks), financial (the bank, the accountant — a $1M business running on thin margins), labour (team leaders are hard to find, casuals turn over at 45%), and community (residents adjacent to every site who complain about noise, chemical spray, and missed mowing schedules).
From this, Dean established four strategic guidelines for the year — each with a control item, a target, a current state, and a gap:
Guideline 1: Reduce council complaints by 50% within 12 months. Control item: complaints per region per month. Target: below 3 per region. Current state: averaging 7.2 across all regions — but nobody knew until we counted them, because the quality coordinator was not tracking operational complaints.
Guideline 2: Retain all three expiring council contracts. Control item: tender submission quality score. Target: shortlisted on all three. Current state: no quality performance data existed for any tender submission.
Guideline 3: Increase crew productivity to reduce overtime reliance. Control item: scheduled tasks completed per crew day. Target: 92%. Current state: unknown — no measurement existed.
Guideline 4: Reduce casual workforce turnover below 20%. Control item: annualised casual turnover rate. Target: 20%. Current state: 45%.
Four guidelines. Each with a number. Dean’s non-delegable responsibility: own these guidelines, review them monthly, and not delegate the system to a quality coordinator or a consultant. The quality coordinator had been maintaining documents for two years. None of those documents contained a single one of these numbers.
Phase 2: Tactical Level - Guideline Deployment
- Weeks 3–8
Each region became a management unit — team leaders defined their own control items through dialogue, not from the quality coordinator’s documents
Each of Dean’s five regions is a management unit — a small business inside the business. Team leader, field workers (mix of full-time and casual), assigned council area, defined service scope. Each region has its own council client, its own seasonal demands, its own site conditions, its own workforce mix. Pretending they are identical and writing one set of procedures from an office in Ringwood is why the quality coordinator’s documents were irrelevant to every team leader.
We did not hand the team leaders a copy of Dean’s four guidelines and tell them to implement. That is a mandate, not deployment. Each team leader sat with Dean and defined their own unit:
Region mission: deliver grounds maintenance to council specification, on schedule, with zero valid complaints and zero safety incidents. Their control items — derived from Dean’s strategic guidelines through dialogue: complaints per month in their region, scheduled task completion rate, casual turnover in their crew, and overtime hours. Each target accounts for local conditions — the region with sports fields has different seasonal peaks than the region with road verges.
Their authority: how to schedule the week, how to allocate crew to sites, how to train casuals, how to handle a council request within scope, when to bring in additional casuals for peak season. These are the means — they own them. Their responsibility: the control items. These are the results — they answer for them.
This was the moment the business changed. Five team leaders who had been running their regions independently — with a quality coordinator in the office maintaining documents they never saw — now had defined decision boundaries and measurable results they owned. The quality coordinator’s role had been to maintain a parallel system. There was no longer a parallel system. There was one architecture, and every team leader was inside it.
Monthly reviews. Each team leader presents their control items — trending up or down, on target or off. Not a report emailed to Dean — a nested review. Dean opens the strategic review and all five regional results are already inside. The quality coordinator had been preparing a quarterly management review PowerPoint. Nobody had ever made a decision from it. The nested monthly reviews replaced it entirely.
Phase 3: Operational Level - Daily Work Routine Management
- Weeks 6–12
Field crews wrote their own procedures for each service type — replacing the quality coordinator’s office documents with standards teams actually use
This is where 90% of the work happens. Below the line. SDCA — follow the standard, check the results, correct deviations.
The quality coordinator had written procedures from the office based on what the ISO standard requires. They described quality policy, document control, and management review — not how to mow a sports field, how to treat a garden bed, or how to set up a whipper snipper line on a nature strip. The team leaders ignored them because they described an audit, not their work.
Standard procedures were rewritten by the people who do the work. Each team leader and their crew documented their own operational standards for each service type: park mowing (heights, patterns, clipping disposal), sports field maintenance (line marking, turf renovation, irrigation checks), garden bed maintenance (weeding, mulching, planting schedules), nature strip and road verge maintenance (safety setup, mowing, weed spraying), and tree and shrub care (pruning standards, green waste handling). Each procedure was drafted by the team that does the work, refined until everyone agreed, and signed off by the team leader. A standard is a documented commitment used repeatedly by the people who do the function. If they did not write it, they will not follow it. The quality coordinator wrote procedures from an office. That is why they lived in a folder.
Visual management. Each team leader runs a weekly scoreboard — visible to the crew. Complaints this week. Tasks completed versus scheduled. Safety observations. Open issues. Dean sees the aggregated view across five regions on a single dashboard. Same data, different scope, nested.
Anomaly treatment. This is what the quality coordinator’s system never had. A complaint is an anomaly. A missed mowing schedule is an anomaly. A chemical application without the correct record is an anomaly. Before TMCS, complaints went from the council to Dean’s phone two weeks later. Now: the team leader captures the anomaly on the day it occurs. Contains it — fixes the immediate problem for the council. Investigates — was the standard followed? Does a standard exist for this situation? If the standard was followed and the complaint still occurred, the standard needs to change — that is a PDCA trigger. Dean reviews anomaly reports weekly across all five regions.
The first month, the five teams reported 31 anomalies. Dean was alarmed. Those 31 things were happening before — they just had no names, no owners, and no deadlines. The quality coordinator tracked audit non-conformities in a spreadsheet. She never saw a single one of these 31 operational problems because her system was not designed to see them. By month three, four chronic problems accounted for 58% of all council complaints: inconsistent mowing heights between visits, missed garden bed weeding cycles on corner sites with low visibility, sports field line marking done without checking council fixture schedules, and casual workers spraying without current chemical application records. Four problems. Four PDCA projects. Four updated procedures deployed across every region. Complaints dropped 64% by month five.
The Results
Outcomes
Outcome Summary:
The quality coordinator role was made redundant at week ten. Not because she was incompetent — she maintained the documentation system exactly as the original consultant designed it. The role was eliminated because the system no longer needed it. Quality was no longer maintained by a person in an office. It was maintained by five team leaders who owned their region’s results through defined control items, standard procedures they wrote themselves, and anomaly treatment that captured problems on the day they occurred.
Council complaints dropped 64% across all five regions within five months. For the first time, Dean could see complaint data by region, by service type, by crew, and by root cause category — in real time, on a dashboard, not in a quarterly PowerPoint prepared by someone who had never set foot on a council site. Four chronic root causes were identified and eliminated through PDCA projects that updated field procedures across every affected region.
All three expiring council contracts were renewed. Dean’s tender submissions included quality performance data — complaint trends by region, root cause analysis, procedure updates triggered by operational data, crew productivity metrics — that no competing landscaper could match. Two council procurement officers commented that it was the first time a grounds maintenance contractor had submitted evidence of a management system that connected to actual operational performance.
Casual workforce turnover dropped from 45% to 18%. Standardised onboarding across all five regions — written by the team leaders, not by the quality coordinator — meant every new casual received the same induction, the same safety briefing, and the same clear expectations from day one. Team leaders reported that defined authority made their job easier: they knew what decisions were theirs and what results they were accountable for.
The $68K quality coordinator salary was redirected to field equipment upgrades and a training budget for team leaders. The system that runs quality across five regions adds no headcount. It runs through the people who do the work — which is exactly what ISO 9001:2015 intended when it removed the management representative requirement.
Main Outcome:
Quality coordinator role eliminated. Complaints down 64%. All three council contracts renewed. Owner sees five regions through one dashboard.
Secondary Outcomes:
Quality coordinator role eliminated — $68K annual salary redirected to crew equipment and training that directly affects service quality on site
Council complaints reduced 64% across all five regions — root cause data visible by region, service type, crew, and complaint category for the first time
All three council contracts renewed — tender submissions included quality performance data no competing landscaper could match
Casual workforce turnover dropped from 45% to 18% — standardised onboarding and defined team leader authority reduced first-month attrition
Owner dashboard showing all five regions in real time — weekly reviews replaced quarterly management review PowerPoints nobody acted on
Leadership Outcome:
Dean said he hired a quality coordinator because every consultant told him he needed one. She cost $68,000 a year. She maintained documents his team leaders had never opened. Complaints kept rising. When we asked what the quality coordinator actually managed, the answer was documents — not quality. The rebuild did not give Dean a better quality coordinator. It gave him five team leaders who each own their region’s results through measurable control items, standard procedures they wrote themselves, and anomaly treatment that captures problems the day they happen. The quality coordinator’s role was made redundant because the architecture that should have existed from the start made it unnecessary. Dean now sees five regions through one dashboard and reviews results monthly — not through a quarterly PowerPoint prepared by someone who had never visited a council site.
The Statistics That Really Matter
64%
Complaint reduction
3 of 3
Council contracts renewed
$68K/yr
Quality coordinator salary saved
45% → 18%
Casual turnover
12
Weeks to rebuild
Other Case Studies
Related ISO Management Systems Problems
