One Superintendent, How Many Autonomous Fairway Mowers?

How many fairway mowers can one superintendent oversee?

No published study answers this for golf courses yet, and anyone offering one clean number is guessing. One superintendent can supervise as many autonomous fairway units as the alert load, map coverage and travel time on a course allow. The count is set by measurement on your own grounds, not by a brochure.

Vendor material in our research spans a wide range. An oxmaint.com guide written for hospitality says one operator can oversee three to ten or more units through fleet platforms. The guide cites no study behind that figure and covers hotels and resorts, not fairways, so treat it as a sales range rather than a benchmark.

What does the manufacturer supervision claim actually say?

As of November 2026, Toro's product page for its GeoLink autonomous fairway mower describes a user supervising one or more units while performing other work on the course. That is a product claim. It does not describe a full shift, a real alert pattern, or a course with bunkers, cart paths and crew calls to answer.

The same product material says the machine can move fairway to fairway if the property design allows and the route has been mapped, and that manual transport is sometimes needed. Contiguous courses are described as the ideal layout, and the mower has an operator seat and steering wheel for manual work. Each detail changes the math, because any unit that needs manual transport pulls a person off the course.

How much does alert response time limit the count?

Fleet software is where supervision happens. The Husqvarna Fleet Services app sends push notifications when a mower reports an error, and its fleet view flags mowers that need attention for errors, standstills or service needs, according to Husqvarna's app listing and product page. Husqvarna's fleet map also lets an operator select several mowers and send one command to all of them in an area. Those are vendor features we have not tested on a fairway. Navimow's NavimowFleet adds grouping and tagging for larger fleets.

What sets your count is the chain that follows each alert. Measure how long a stopped unit waits before someone acknowledges it, how long the fix takes, and whether the person who fixes it is also needed on a green or at an irrigation valve. A quick acknowledgment does little if the supervisor cannot reach the mower for a long stretch.

Do map coverage, travel and charging decide the rest?

Movement eats supervision time as much as alerts do. Each trip between holes, to a charger, or out to a unit that has left its mapped area takes minutes from the window a supervisor has. Toro's conditional wording on fairway-to-fairway transport exists for this reason: design and mapping decide whether a unit can move on its own.

Charging is the least documented piece. Husqvarna's residential charging guidance calls for at least 6 m (20 ft) of free space in front of the station, set on a fairly level surface. That is home-lawn guidance, not golf data, and our research found no golf-course charging layout or per-charge runtime figure. Put charging spots and the walk from the shop on the trial map.

Where do crew radio duties fit into the shift?

A superintendent does not sit at a dashboard all day. Radio calls, irrigation checks, bunker work and a greens crew that needs a decision mid-morning all compete with the screen. Staffing shows how seriously this gets treated. A job posting from RYAN Lawn and Tree lists monitoring dashboards, alerts and error logs as core duties, plus on-call availability for critical alerts.

The pattern to copy is simple. Name one person who is responsible for alerts during a given window, and write down what that person stops doing while holding the role. If nobody has the alert queue, the count you choose will be wrong from day one.

How should a course run the trial before choosing a unit count?

Run the trial during your site assessment, on real play rather than a demo loop. Start with a small number of units, log everything for enough days to show a normal pattern, then repeat once map changes or seasonal rough shift the load. Record these items for each event:

Then divide the supervisor minutes you really have each hour by the minutes per unit per hour that the log shows. Reduce that figure for radio work and greens duties. The result is your working count, a starting point that the next season's logs should check.

• Alert time stamp, and the time to acknowledgment
• Time from fault to the unit moving again, with the cause
• Travel minutes between holes, including any manual transport
• Charging stops, and how long each takes the supervisor off route
• Radio calls and crew tasks that pulled attention off the screen
• Any unit that left its mapped area or needed a remap

How Service Robot Co. helps set and carry the count

We are OEM-neutral, so the unit count follows the course, not one manufacturer's catalog. Service Robot Co. is a full-service commercial robot integrator for US businesses. We pick the right robots across manufacturers, lease them through financing on a 3-year lease with one fixed lease payment quoted after a site assessment, then deploy, train and service each unit under RoboCare, our service plan, backed by regional service engineers in every state we service.

We use the trial log as the basis for that lease quote, so the number of units matches the alert load you measured rather than a sales estimate. Our service engineers respond when a unit stops under RoboCare, which is where supervision time tends to go when a course has no plan for it.