Scope Language for Robot-Mowed Client Lawns in Your Contract

What belongs in a robot mowing scope?

A robot mowing scope is the written statement of what the robot cuts, what the crew does by hand, what gets left alone, and what happens when something goes wrong. If the contract cannot answer those four questions in plain language, the first disagreement will be settled from memory instead of from paper.

For most commercial lawns the split is simpler than it looks. The robot mows the open turf zones marked on an approved site map. The crew handles edging along hard surfaces, trimming around trees and fixtures, clearing clippings from walks and drives, and any area the robot is not cleared to enter. Each of those should be named, not implied.

Two clauses deserve as much attention as the mowing itself: how damage is reported, and when robot passes pause. Most disputes start there, and both are easy to leave vague on a first draft.

How does the lease quote fit into the proposal?

The scope should follow the site assessment, not precede it. The assessment walks the property, maps boundaries and obstacles, notes slopes and wet low spots, and identifies the routes a robot would take. Only after that walk can a lease quote be prepared.

Service Robot Co. handles commercial robot leasing through financing on a three-year lease, with one fixed robot lease payment quoted after a site assessment. In the proposal, the quote and the assessment map should sit as referenced attachments, so the scope and the price describe the same ground.

If the property changes after mapping, such as new planting beds, a moved fence line, or an added parking island, the contract should state how that change is priced and approved. Otherwise the proposal keeps describing a lawn that no longer exists.

Which tasks stay with the crew?

Hand work is not a leftover from robot mowing. It is the part of the job robots handle least well, and it is where clients judge the finish. Name these tasks as crew items with their own frequency.

Frequency belongs in the contract too. Edging on a weekly cycle and cleanup after every robot pass are separate promises, and a client who expects one will be surprised by the other.

• Edging along curbs, walks, and hard edges, to the line and height the contract specifies
• Trimming around trees, posts, signs, and landscape beds that the robot cannot approach
• Clearing clippings from walks, drives, and entries after each robot pass
• Turf the mapping marked as robot-restricted, such as steep banks or wet low spots
• Mowing by hand any zone added after the map was approved, until a change order is signed

How should boundary language read in plain terms?

Vague scope wording causes most of the arguments. Phrases such as all lawn areas or routine maintenance leave the crew and the client guessing at the edges. A clearer clause names the approved map, the zone numbers, and the exclusions.

A workable clause reads something like this: the robot mows zones 1 through 4 on the approved site map at the cut height in Exhibit B, and the crew performs edging, trimming, and clippings cleanup in those zones after each robot pass. Areas outside the map are excluded unless a written change order adds them.

Exclusions carry as much weight as inclusions. If irrigation heads, pet relief areas, or event lawns are excluded, put that in the same clause as the inclusions, not in a footnote nobody reads.

How is damage reported under the contract?

A damage clause should define what counts as damage, who reports it, how quickly, and what evidence goes with the report. Scalping, ruts, displaced sprinkler heads, and torn turf are separate problems, and a single word like damage covers too little ground.

Name the reporting path. The crew lead records the finding with dated photographs and the zone on the site map. The account manager notifies the client inside a stated window, and the robot's run record for that zone is attached when it is available, so both sides look at the same timeline.

State what happens after a report as well: an inspection, a repair within an agreed window, or a claims process. Do not promise a repair time the service team has not committed to in writing.

When do robot passes pause?

Pause triggers should be written as conditions, not left to a crew member's judgment on the morning of the mow. Common triggers include saturated or frozen turf, people or animals entering a zone, an event setup, an emergency crew on site, a fault on the unit, or a client request.

Name who has authority to pause. The crew lead can stop a unit on site, and the account manager can extend a hold or cancel a pass. The contract should also say how a missed pass is rescheduled and how paused time is treated, because that changes the work schedule the client was promised.

Write resume rules as well. A robot that stopped for a wet morning should not restart into a soaked lawn just because the calendar says the pass is due.

What promises should the contract leave out?

Keep every promise inside the written scope. Avoid guarantees such as no turf damage ever, round-the-clock mowing, or a hands-off lawn with no crew involvement. Those phrases sound reassuring in a sales meeting, and a real site will eventually test them.

Service coverage belongs in the contract too. Service Robot Co. services each leased unit under RoboCare, backed by regional service engineers in every state we service. We pick the right robot across manufacturers, so the scope can describe the job rather than a single brand, and the service terms can cover the whole lifecycle with one vendor. The contract should say which of those services apply to this lawn and what response to expect.

Before the first mow, read the scope aloud against the site map. Anything the page does not say is not promised, and the crew should be able to point to the line that covers each task.