By Marc Mazure, Founder, CQ

When a landscaping business grows, the problem isn’t that it has less information. It’s that more people have different pieces of it.

That, in my experience, is the real shift when you move from one crew to multiple teams. The headcount grows. The number of jobs grows. But the thing that starts to dominate your day is the flow of operational information — where it lives, who can see it, and whether you can find it again without ringing three people.

Current professional landscaping discussion also places management capability and technology choice alongside growth [1] [2]. The practical question here is not which tool to buy, but what needs to change inside the business as teams multiply.

Why informal coordination works when you’re small

With one crew and a very small office, informal communication can work remarkably well. In conversations I’ve had with landscaping businesses at that stage, the owner often:

• knows where everybody is;
• knows what each job needs;
• knows what happened yesterday;
• remembers which customer called and what changed;
• understands what materials are required next.

Calls, WhatsApp, a few photos and a weekly spreadsheet can hold together because only a small group needs the same information. The owner is close to every moving part.

What changes as the information volume grows

As the business grows from that model, the pattern I’ve repeatedly encountered is simple: you don’t just add people; you add information. More crews bring more live jobs and sites, more photographs, forms, schedule changes, customer conversations, field decisions and records you may need months later.

Growth increases the volume of information being generated. If the method of handling that information doesn’t evolve, the business can become more disorganised as it becomes larger — not because anyone’s slacking, but because the information is now scattered.

The fragmentation problem

Here’s the reality I see in multi-crew companies during demos and discovery calls:

• The owner knows one thing because a client rang them.
• The operations manager knows another because a foreman called them from site.
• A field worker has the best photos on their personal phone.
• The schedule lives in a spreadsheet that not everyone can read when they’re out.
• Site conversations are happening in WhatsApp groups.
• Forms and signed sheets might be in someone’s van or in a different app.

The problem isn’t necessarily a lack of communication. There can be plenty of communication. The problem is that the communication isn’t creating shared visibility.

Different people hold different parts of the truth. You can spend most of the day piecing the business together from messages, calls and photos. It’s operational detective work.

When communication becomes chasing

As the number of crews and jobs grows, informal operations can generate increasing amounts of unnecessary communication. These are the kinds of questions that start consuming management time:

• “Have you uploaded the photos?”
• “Did you get the customer signature?”
• “Where are we with this job?”
• “Has that work been completed?”
• “Where’s the paperwork?”
• “Has anyone spoken to the client?”
• “Can you send me the photos from Tuesday?”
• “What’s happening at that site?”
• “Why hasn’t this crew moved onto the next job?”

These aren’t always meaningful management conversations. Many are simply requests for information. Good communication helps people make decisions. Chasing information is often just the cost of not having visibility.

The goal isn’t to reduce meaningful communication. A larger business will naturally require more of it. The goal is to avoid communication having to grow at the same rate as the team simply because basic facts are difficult to find.

An anonymised real-world example

In a recent conversation I demonstrated CQ to a landscaping company with roughly 25 staff. They were still running day-to-day operations largely through spreadsheets, WhatsApp and phone calls. The owner and operations manager worked from different locations. A member of staff might call the ops manager with a question the owner had already answered — or the reverse. Neither could automatically see the information the other person had received.

The outcome? A lot of management time went on internal calls, passing updates back and forth, answering repeated questions, chasing photos, and trying to reconstruct what had happened on site.

To be clear: there is no universal employee threshold for when you “need software”. That’s not the point. The observation is simply that, around that size for that particular business, the informal information model was becoming the constraint. The volume of operational information had outgrown the way it was being handled.

Why WhatsApp isn’t the problem — and what is

Let me be explicit: WhatsApp is popular on site because it works. It’s fast. It’s easy. It’s great for getting a quick answer or sharing a quick photo with a crew.

The limitation appears when a messaging stream becomes the operational record of the business. A photo dropped into a group today can be helpful. Six months later, when someone asks:

• what happened at the commercial grounds site;
• on which date the team attended;
• who was on the job;
• what work was completed;
• which photographs were taken;
• whether a form or customer sign-off was captured;

scrolling through months of messages is a completely different problem.

It’s worth separating: communication tool versus structured operational record. Use WhatsApp to communicate. But for the business to scale, the operational record has to live somewhere structured, shared and retrievable.

Shared, live and historical visibility

There are three distinct types of visibility that matter when teams multiply.

1) Shared visibility
Can the owner, the operations manager and other authorised people see the same operational information regardless of where they are? It shouldn’t depend on who took the call or who’s holding the photos. For a grounds maintenance firm with five routes running daily, “shared” means both office and managers can see the same site notes, the same completion records and the same photos attached to the same scheduled visits.

2) Live visibility
Can management answer “what’s happening now?” Where are crews today? What’s been completed and what hasn’t? Did the required photos or forms get captured on site? Has something changed that means a job will overrun? For a design/build project in week six, “live” might be seeing that today’s tasks, required pre-pour photos and the material delivery confirmation have all been ticked before concrete is booked.

3) Historical visibility
Can you reconstruct what happened months later? This is crucial. A client can come back three or four months after completion with a question about the work. The business then needs to go back to the original visit(s) and establish: who attended, what was scheduled, what was signed off, what notes were left, which photos were taken and where the forms live.

This is more than communication. It’s how you turn day-to-day activity into an operational memory you can rely on.

The owner-as-information-hub problem

As a business grows, the owner or operations manager can become the company’s information hub. Site worker calls owner. Customer messages ops. Crew posts in WhatsApp. Office asks manager. The hub routes information manually.

Conceptually it looks like this:

• Site worker → Owner → Office
• Customer → Operations manager → Owner → Crew
• Crew → WhatsApp → Office → Manager

It works — until it doesn’t. It creates interruptions, duplicate questions, dependence on specific individuals, and a constant need to chase, search and re-explain. It also makes it hard to delegate or to work effectively if people are in different locations.

The scalable alternative is simple in concept:

More teams → Information captured at source → Information organised against the correct work → Shared visibility → Easy retrieval.

A practical framework: Capture → Organise → Share → Retrieve

Here’s the operating framework I recommend when a business moves from one crew to multiple teams. It’s deliberately simple, and it applies whether you’re a construction-led landscaper, a garden design/build firm or a grounds maintenance provider.

1. Capture

Capture information as close as possible to where the work happens.

• Photos taken on site (before, during, after).
• Site notes and variations agreed.
• Required forms and customer signatures.
• Completed tasks and job status updates.
• H&S or RAMS acknowledgements where relevant.
• For maintenance: completion records and any exceptions (e.g., access blocked, weather-related deferral).

In conversations I’ve had with multi-crew businesses, one of the strongest reactions during demonstrations is to the simplicity of the field app. The worker can see where they’re going, see the relevant job, complete required tasks, upload photos, complete required sheets/forms, provide signatures where required, and update the work — all in one place. The important benefit isn’t “there’s an app”. It’s that the information reaches the right place without someone in the office having to chase it there.

2. Organise

Give the information somewhere specific to live so it can’t be separated from its context. That usually means automatically or deliberately attaching each item to the correct:

• customer, job and site;
• date and scheduled visit;
• project stage (for construction-led work).

Photos should live against the relevant scheduled work. Forms should live against the relevant scheduled work. Notes should live against the relevant scheduled work. If you have to reconstruct a job afterwards from message threads, you’ll burn management time and increase the odds of missing something.

As a business grows, it creates more and more information. If that information doesn’t have a specific place to live, the organisation can get less organised simply because there is more to manage.

3. Share

Make the relevant information visible to the right people without needing to ask for it. The owner and operations manager should be able to see the same operational context regardless of who took a call or uploaded a photo. For maintenance contracts, that might mean the office can immediately see that week’s photos for each site and send a client report the same day without ringing foremen. For construction work, it might mean the project manager can see stage photos and forms before approving the next draw.

4. Retrieve

Design for retrieval from day one. The information should remain useful after the immediate conversation has ended. Days, weeks or months later, you should be able to find the operational record again. That’s what turns daily communication into organisational knowledge — and it’s what allows you to defend decisions, evidence completed work, and learn from outcomes.

How this looks in practice

To make this tangible, here are landscaping-specific examples of the framework across different operating models:

• Garden design/build
• Capture: Required pre-dig photos, underground service checks, signed variation for additional drainage.
• Organise: Attach to “Patio & Drainage – Stage 2” on the project timeline.
• Share: Owner and PM can both see the signed variation and photos before booking extra materials.
• Retrieve: Four months later, when queried about an additional charge, you can pull the signed variation and site photos in minutes.
• Landscape construction (commercial)
• Capture: Daily progress photos, RAMS acknowledgements, delivery notes for paving pallets.
• Organise: Link to the day’s scheduled tasks and the relevant plot/block.
• Share: QS and operations can check progress remotely and approve interim valuations with evidence.
• Retrieve: On practical completion, all records exist against the project stages for handover.
• Grounds maintenance (recurring)
• Capture: Visit completions, site exceptions (locked gate), weekly photos for key sites, client sign-off where required.
• Organise: Tie to the site’s recurring schedule with date stamps.
• Share: Office sees the same completion record and photos without asking foremen.
• Retrieve: Quarterly review with a commercial client? You have visit history and photo evidence for every scheduled week.

Making the framework work in practice

The principle is straightforward: field photos, required forms, schedule changes and signatures should sit against the exact job, visit or project stage. That means the office does not need to chase or manually reconstruct the record later, managers can work from the same context, and the information remains findable months afterwards. CQ is one way a landscaping business can put that principle into practice; the operational outcome matters more than the tool.

Location-independent visibility (without surveillance)

One owner recently described a benefit very simply: he could “see everything whilst on holiday.” The useful point here isn’t monitoring people from the beach. It’s that operational visibility no longer depends on physical location. The owner and operations manager can be in different places and still work from the same set of facts. That supports delegation, reduces dependence on one person being the hub, and keeps decisions moving without a stream of “Have you got the photos?” calls.

What this changes for the owner and ops manager

Moving to a shared, structured and retrievable information model changes the day-to-day job of running multiple teams:

• Less routing of information through individuals. The system holds the context; people don’t have to.
• Fewer interruptions and duplicate questions. Basic facts are visible; calls focus on exceptions and decisions.
• Easier delegation. Managers can hand over confidently because the record lives with the work, not with the person.
• Faster issue resolution. Live exceptions stand out; someone can pick them up without decoding a message thread.
• Stronger client reporting. For maintenance contracts, current and historical photos are instantly available by site and date.
• Better project control. For construction, stage evidence and sign-offs are where you need them for approvals and valuations.
• Real after-the-fact memory. When a client asks about something months later, you can answer with evidence rather than relying on recollection.

The business-growth implication

As teams multiply, communication alone won’t save you. In fact, you’ll probably communicate more than ever — but without structure, it can become chasing. The real operating shift is this:

• From information held by individuals and conversations
• To information that’s shared, structured and retrievable across the business.

As a business grows, communication shouldn’t have to grow at the same rate as the team. It should become more focused on decisions, less on finding out what happened.

If you take nothing else from this piece, take this: information becomes operationally useful when it has somewhere to live and can be found again.

Closing thought and next steps

A larger landscaping business shouldn’t simply create more information. It needs to get better at turning that information into accessible organisational knowledge. That’s what allows you to grow crews without growing chaos.

If you want to explore this further:
- Read our deeper guides on scheduling and project control from the Landscaping Business Growth Hub.

- View our dedicated landscaping business management software page- Or, if you’d like to see how Capture → Organise → Share → Retrieve works in CQ, book a short, no-pressure walkthrough.