Lawn Care Software — Data Model | FieldCamp

How a lawn care business runs in FieldCamp — recurring mow and treatment routes, residential subscriptions, commercial grounds, and per-visit billing.

A lawn care business runs almost entirely on FieldCamp's core records. Weekly mowing routes, scheduled treatment programs, crews, online sign-up, and recurring billing are all there the moment you sign up.

The chain a lawn care operator already lives by — a homeowner signs up for a season of mowing, you put them on a repeating route, a crew mows and edges the yard, and the card on file gets billed each visit — is modeled directly as Customer → Job → Visit → Invoice → Payment.

Most of this needs no setup. A few touches — lot size, the gate code, the services on each visit, and the plan tier — are added as custom fields, with an optional treatment record for programs that apply fertilizer and weed control.

This page is focused on the recurring mow-and-treatment side of the trade — routes, subscriptions, and per-visit billing. If your work leans toward installs, hardscape, and multi-site grounds contracts, the adjacent Landscaping setup covers the Property and Service Agreement layer that side leans on.

The two share the same backbone.

What the core already gives you

Most of a lawn care business is covered by records that work on day one, with no setup.

Recurring mow and treatment routes. A Job set to recurring auto-generates its Visits from a weekly, biweekly, monthly, or seasonal pattern, so a maintenance route schedules itself.
Crews on every stop. Each Visit is staffed by one or more team members, matched by skill and service area.
Route density and territory. Service Areas cluster stops by zip code and zone, and the dispatcher orders the day so a crew covers a dense route with less drive time.
Subscriptions and recurring billing. A recurring Job plus a Service Agreement carries the season's term and cadence; Invoices bill per visit or monthly and track paid, partial, and overdue.
Tiered quotes and deposits. An Estimate carries Good / Better / Best packages — basic mow, mow plus treatment, full program — with deposits.
Online sign-up and quotes. A Request captures an inbound sign-up or quote and converts into a Job, Estimate, or Invoice in one step.
A priced catalog. The price book holds mowing, edging, fertilizing, aeration, and cleanup priced by the unit, with cost and price separated.
Arrival and completion. Visits track en route, arrived, working, and done with check-in and check-out location, an optional signature, and before-and-after photos.

The Customer record already separates service, billing, and property addresses, and marks each account as an individual or a business — enough to tell a residential lawn from a commercial site.

There is no separate "subscription" record to build. A lawn care plan is a recurring Job for the mowing or treatment cadence plus a Service Agreement for the season's term, renewal, and cancellation — both already in the model.

Tailoring it to lawn care

Most of what this trade needs that core does not already name is a handful of fields, not new records.

Pricing keys off lot size and frequency; the crew needs the gate code to get in; each visit may bundle a different set of services; and the account sits on a plan tier.

These ride directly on the core records as custom fields — no new object required.

Field	On record	Field type	What it holds
Lot size	Customer	Single choice	Small, medium, large, or extra large — the lot bucket that drives price
Lawn area	Customer	Number	Mowable square footage, for measured pricing
Gate code / access	Customer	Text	The gate or lockbox code the crew needs
Access notes	Customer	Long text	Locked gate, pet warnings, where the dog stays
Plan tier	Customer	Single choice	Mow-only, mow plus treatment, or full program
Mowing height	Job or Visit	Number	The deck height this lawn is cut at
Services this visit	Job or Visit	Multiple choice	Mow, edge, blow, trim, fertilize, weed control, aerate

The gate code is the field a route crew reaches for first. Put it on the Customer so it shows on every Visit the route generates, rather than re-typing it on each stop.

The services-per-visit detail also works well as a Job Form: a short per-visit checklist — mowed, edged, blown, clippings cleared, gate latched, photo taken — captured on site and stored on the Visit, with the photo requirement turned on for the completion step.

The optional record: a treatment application

The fields above cover a mow-only operation completely.

The one place a real record earns its keep is a lawn program that applies fertilizer and weed control — because in most states a chemical application is a line you have to be able to produce for recordkeeping.

If you run treatment rounds, a Treatment is a custom object — one record per application, capturing the product, rate, target, and the certified applicator.

It is built the same way as the Chemicals record a pest-control business keeps; lawn care just narrows it to turf products and weeds.

A Treatment is captured on the Visit it happened on, so a treatment history builds up under every customer and route without a separate logbook.

Field	Field type	What it holds
Product name	Text	The product applied, such as a granular fertilizer or a pre-emergent
EPA registration number	Text	The product's registration number, for regulated weed-control products
Round	Single choice	Which application in the program — round one through six, or a spot treatment
Application method	Single choice	Granular, liquid spray, or spot spray
Rate or dilution	Text	The spread rate or mix used
Target	Multiple choice	Crabgrass, broadleaf weeds, grubs, or a feeding round with no target
Areas treated	Multiple choice	Front, back, side yard, or named zones
Quantity used	Number	The total amount applied, in the unit below
Unit	Single choice	Pounds, ounces, or gallons
Application date	Date	The day the round was applied
Applicator	Link to a team member	The certified team member who applied it
Visit	Link to a visit	The visit this round was captured on

The customer and the property are not retyped onto the Treatment record. They come from the visit it links to, so every record rolls up to a real account and address on its own.

The diagram below shows the lawn care layer — the core records, the custom fields that ride on them, and the optional Treatment object hanging off the Visit.

A Customer holds the recurring Job and the plan.

Each Job is scheduled as Visits, each Visit is staffed by a crew and priced from the price book, and a Visit on a treatment round captures the Treatment records made on it — so each round builds a dated history instead of one overwritten note.

A mow-only business does not build the Treatment object at all. The lot-size, gate-code, and plan-tier fields on the Customer are all the tailoring it needs. The Treatment record is for operators running fertilizer and weed-control programs.

Residential subscriptions vs commercial grounds contracts

The same backbone serves both sides of the business. What differs is which pieces carry the weight, and how completion is gated.

Residential subscriptions

One customer to one lawn. The recurring Job is the subscription, the lot-size and plan-tier fields drive price, and the gate code gets the crew in. The Service Agreement is light — often just the season's cadence and an easy cancel-anytime term. Completion is a quick mow, a clippings-cleared note, and an optional photo. Dense same-day routes are ordered by Service Areas and the dispatcher.

Commercial grounds contracts

Property managers, HOAs, and facilities groups. One account holds many sites and a formal multi-season scope, so the Service Agreement carries the weight — defined scope, a billing schedule, and renewal. Completion is heavier: a checklist sign-off and photos required as proof. Sites with many distinct lawns lean on the Landscaping Property record.

You build the fields once. Residential accounts lean on the recurring Job and the Customer fields; commercial accounts lean on the Service Agreement and heavier completion.

The completion difference does not need a second workflow. The same Visit workflow can require a signature and photos for commercial sites and leave them optional for residential — one pipeline, configured per account.

A customer's recurring Job is scheduled as visits; a mow visit cuts and edges the lawn and bills per visit, while a treatment visit captures the application that builds the treatment history — both running on the same route.

Built on the customization engine

Everything here is built with the same tools every FieldCamp account has.

The lawn care fields are custom fields on the core records; the optional Treatment is a custom object with its own fields; and each record page is arranged from a library of building blocks.

Add a field, rename a stage, or arrange a page to match how your routes actually run, using custom objects and fields, stages and workflows, and record layouts.

If you give the Treatment record a short lifecycle — recorded, then reviewed before a round is final — that is a workflow on the object, set up the same way every other stage flow is.

Built for any size. A one-truck operator runs a dense residential mow route on the core records plus a few Customer fields. A multi-crew company running fertilizer programs adds the Treatment record; a commercial grounds operation leans on Service Agreements and the Landscaping Property layer — all on the same backbone, no rebuild.

Coming from Service Autopilot

Most lawn care operations on Service Autopilot can bring their structure into FieldCamp directly — the clients, the properties you service, the recurring services and the jobs they generate, the routes, the crews, and the estimates and invoices all have a home here.

The difference is that in FieldCamp you own and shape the model, rather than fitting your operation to a fixed one.

In Service Autopilot	In FieldCamp	Notes
Client	Customers	The account responsible for billing. FieldCamp keeps service, billing, and property addresses on one record, and marks each account as a residential or commercial.
Property	The customer's service address for a single-site home, or a Property as a custom object when one account holds several sites	A single home rides on the customer's service address; model the property as its own record when a commercial account has many sites.
Recurring service	A recurring Job for the cadence, plus a Service Agreement for the season's term	The recurring Job auto-generates its visits on a weekly, biweekly, monthly, or seasonal pattern; the Service Agreement carries the renewal and cancellation.
Route	Service Areas	Stops cluster by zip code and zone, and the dispatcher orders the day so a crew covers a dense route with less drive time.
Job / Visit	Jobs and Visits	The Job is the work order; each Visit is a scheduled stop with dispatch, en-route, on-site, photos, and sign-off.
Crew / Team	Team Members	Staffed onto each visit, matched by skill and service area.
Estimate / Invoice	Estimates & Invoices	Quoting with Good / Better / Best and deposits, per-visit or monthly invoicing, and payments.
Chemical / treatment tracking	A Treatment record, built as a custom object on the visit	One record per application — product, rate, target, and the certified applicator — building a dated treatment history under every route.
Automations	Automations	Follow-ups, reminders, and status-driven actions, built as rules on the records they run on.

What you gain. In Service Autopilot the structure is set for you — the records, their fields, and how they relate.

In FieldCamp every one of those records is yours to rename, extend, restage, and relayout, so you can match your old setup first and then go past it with custom objects and fields and your own automations.

One honest difference. Service Autopilot ships built-in recurring billing and route automations that run on their own schedule.

FieldCamp models the recurring side as a recurring Job plus a Service Agreement, with route ordering handled by Service Areas and the dispatcher, and follow-up logic handled by automations; the recurring billing runs through the standard invoice flow rather than a separate billing engine.

If automatic billing cycles are central to how you charge, plan that part of the move deliberately.