For Service-Business Operators
What to Put in a Lawn Mowing Contract (and What to Leave Out)
Most lawn mowing disputes are not about mowing. They are about a week that got skipped in July, a rate that went up without warning, a gate that was left open, or an invoice that showed up after the customer thought the season was over. Every one of those is a sentence someone forgot to write down in March.
A residential mowing agreement does not need to be long. It needs to answer the questions that come up later, in plain language, on one or two pages a homeowner will actually read before signing.
The twelve clauses that earn their space
1. Who the parties are. Full legal business name, the customer's name, and the service address. The service address matters on its own line, because the billing address is often different — a rental, a parent's house, a property managed from another state.
2. What "mowing" includes. Say it explicitly: cut, trim around obstacles, edge hard surfaces, blow off walks and drive. If edging is every visit, say so. If it is every third visit, say that instead. This single clause resolves the most common complaint in the trade, which is a customer who assumed edging was included and an operator who assumed it was extra.
3. What it does not include. Bed weeding, shrub trimming, leaf cleanup, dog waste pickup, hauling brush the customer piled up. List them and price them separately, or list them and say they are quoted on request.
4. Frequency, stated as a range. "Weekly during the growing season" is better than a fixed day. Grass does not grow on a calendar. Weekly with a stated fallback — "every 7 to 10 days depending on growth and weather" — protects you in a dry August when the lawn genuinely does not need cutting, and it protects the customer in a wet June.
5. The season start and end. Not dates. Conditions. "Service begins when growth resumes in spring and ends after the final cut of the season, typically late October." A date will be wrong every year. A condition never is.
6. Price and what triggers a change. The per-visit price, and one sentence saying the rate holds for the current season and may be adjusted for the following season with advance written notice. Thirty days is the common courtesy. Put the number in the contract so you never have to argue about whether notice was adequate.
7. Payment terms. When the invoice goes out, when it is due, and what happens if it is late. Vague terms produce slow payment. "Invoiced monthly, due on receipt" is clear. "Net 15" is clear. "Payment expected promptly" is not a term.
8. Skip and access conditions. What happens when the gate is locked, the dog is out, the yard is full of toys, or a car is parked on the turf. The fair version: you attempt the service, you document why you could not complete it, you notify the customer, and you either return within a stated window or the visit is charged as attempted. Pick one and write it down.
9. Weather. Rain does not cancel the season, it shifts the schedule. One line: service may be delayed by weather or ground conditions and will be completed as soon as conditions allow.
10. Property condition and damage. You are responsible for damage you cause. You are not responsible for hidden irrigation heads, invisible dog fence wire, unmarked utilities, or landscape lighting buried in the turf. Ask the customer to mark them. Give them a place on the form to do it.
11. Cancellation. How much notice each side gives. Two weeks is standard and cuts both directions, which is the part that makes it feel fair rather than one-sided.
12. Signatures and date. Both parties. A signature line at the bottom converts a quote into an agreement.
The three clauses that cause more trouble than they solve
A long liability disclaimer in legal English. Homeowners read three paragraphs of capitalized indemnification language and decide you expect something to go wrong. Keep the damage clause to the two plain sentences in item 10. If you need real liability language, that is a conversation with an attorney and an insurance agent, not a template download.
An automatic multi-year renewal. It reads as a trap even when you do not mean it that way, and in a small town the reputation cost is real. A season-by-season agreement that you renew with a friendly letter in March converts about as well and never generates a complaint.
A penalty rate that you will not actually enforce. A 5% monthly late fee you never charge teaches the customer that nothing in the document is real. Either set a late fee you will apply consistently, or leave it out and rely on clear due dates.
The one line that decides whether you get paid in November
Put the final-cut and final-invoice language in the agreement in the spring, not in a text message in the fall.
The pattern that causes trouble: an operator finishes the last cut in late October, sends the invoice in early November, and the customer — who mentally closed the books on lawn care six weeks earlier — treats it as a surprise. Nothing was done wrong. The expectation was just never set.
The fix is one sentence in the agreement: "The season concludes with a final cut, typically in October. A final invoice follows within 10 days." Now November's invoice is something the customer agreed to in March.
A quick self-check on any agreement you are about to use
| Question | Where the answer should live |
|---|---|
| What exactly is included in a visit? | Scope clause, itemized |
| What is explicitly excluded? | Exclusions list, itemized |
| How often, and what if growth is slow? | Frequency as a range, not a fixed day |
| When does the season start and end? | Stated as a condition, not a date |
| What is the price, and can it change? | Price clause with notice period |
| When do I invoice and when is it due? | Payment terms with a real due date |
| What if I cannot get into the yard? | Access and skip clause |
| Who pays for a cut sprinkler head? | Property condition clause, with a marking line |
| How does either side get out? | Cancellation notice, same for both |
| Did both people sign it? | Signature block |
If any row sends you looking for the answer in your memory instead of on the page, that is the clause to add before the next customer signs.