FieldCampLandscaping Data Model — Properties & Contracts | FieldCamp
How a landscaping and lawn care business runs in FieldCamp — recurring routes, crews, quoting, billing, plus a Property and Service Agreement record layer.
A landscaping and lawn care business runs almost entirely on FieldCamp's core records. Recurring mowing and maintenance, crews, route scheduling, quoting, billing, and on-site capture are all there the moment you sign up.
The same chain a lawn care operator already lives by — a customer signs up, you quote a package, you schedule a crew on a repeating route, you bill, and you get paid — is modeled directly as Request → Estimate → Job → Visit(s) → Invoice → Payment.
Two things this industry needs are bigger than a field, so the setup adds them as their own records: a Property for each physical site you service, and a Service Agreement for the seasonal contract that governs scope, term, and billing.
FieldCamp works for any size, from a single-truck operator running a dense residential route to a multi-location franchise holding commercial grounds contracts — residential or commercial, and everything can be tailored.
What the core already gives you
Most of a landscaping business is covered by records that work on day one, with no setup.
- Recurring mowing and maintenance. 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 and territory scheduling. Service Areas and the dispatcher assign crews to stops across the day.
- Tiered quotes and deposits. An Estimate carries multi-option packages — the Good / Better / Best pattern — with deposits.
- Invoicing and payments. An Invoice tracks partial and full payments, overdue status, and net terms.
- A priced catalog. The price book holds mowing, mulch, fertilizing, and cleanup priced by the unit, with cost and price separated.
- On-site arrival and completion. Visits track en route, arrived, working, and done with check-in and check-out location, an optional signature, and photos.
- Structured on-site capture. Job Forms handle per-visit checklists, chemical-application logs, and safety inspections.
- Lead intake. A Request captures a new inquiry and converts into an Estimate, Job, or Invoice.
The Customer record already separates billing, service, and property addresses, and marks each account as an individual or a business — enough for any single-site account.
A residential account with exactly one site can run on the Customer's property-address field alone. The Property record below earns its place the moment one account has two or more sites — which is most commercial grounds work.
What landscaping and lawn care adds
On top of the core records, the landscaping setup adds two custom objects built on FieldCamp's customization engine. Each is a real record with its own fields, its own connections to the core records, and its own page layout.
Property — the service site
A Property is the physical site work is performed at.
It is its own record so a single commercial account — a property manager, an HOA, or a facilities group — can hold dozens of sites, each with its own access notes, measurements, and visit history.
A Property belongs to a Customer, gathers the Jobs done at that site, and rolls up the Visits performed through those jobs. Residential accounts use one Property lightly, or skip it; commercial accounts use it fully.
| Field | What it holds |
|---|---|
| Property name | A label for the site |
| Site address | The structured service address with directions |
| Property type | Residential, commercial, HOA, or municipal |
| Lawn area | Mowable square footage |
| Bed area | Mulch and planting-bed square footage |
| Lot size | Acreage of the lot |
| Access notes | Gate codes, locked gates, pet warnings |
| Gate code | The site gate or lockbox code |
| Service frequency | Weekly, biweekly, monthly, seasonal, or as-needed |
| Site photos | Reference photos of the site |
| Site map | A property map or measurement screenshot |
| Account | The Customer this site belongs to |
| Agreement | The Service Agreement covering this site |
A Property page is arranged from building blocks: a header, the field group above, the address with a map pin and directions, an access brief, the related table of Jobs at this site, its service history, and a gallery of site photos.
A Property can carry a light status of active, on hold, or inactive. For most teams a Property is a reference record, so a simple status is enough — no full workflow needed.
Service Agreement — the maintenance contract
A Service Agreement is the recurring or seasonal contract that governs scope, term, and billing cadence. It is its own record because it has a real lifecycle — draft, active, renewal, expired — that a simple attachment cannot express.
An agreement belongs to a Customer, can cover many Properties, and spawns the recurring Jobs that fulfill it.
| Field | What it holds |
|---|---|
| Agreement name | A label for the contract |
| Contract type | Fixed-price on a schedule, fixed-price on completion, open billing, or time-and-materials |
| Scope | The seasonal scope of services |
| Start date | When the term begins |
| End date | When the term ends, for seasonal terms such as April–November |
| Billing cadence | Monthly, per-visit, quarterly, or seasonal lump sum |
| Contract value | The total contract amount |
| Visit frequency | Weekly, biweekly, monthly, or seasonal |
| Auto-renew | Whether the agreement renews on its own |
| Signed contract | The signed agreement document |
| Annualized value | A calculated rollup based on the contract value |
| Account | The Customer who signed |
| Properties | The sites this agreement covers, one or many |
A Service Agreement page is arranged from a header, the field group above, terms and conditions, the signed-contract attachment, signature capture, the related table of Jobs it spawned, the tiles of covered Properties, a financial summary, a record-history timeline, and a status banner showing active, expired, or renewal.
The Service Agreement lifecycle
A Service Agreement moves through named stages. It starts as a draft, goes out for signature, becomes active, flags when renewal is due, and ends as expired — with a side route to cancel.
Two automations ride on those stage changes. When an agreement becomes active, FieldCamp creates the first recurring Job for the covered Property and notifies the account owner. When renewal comes due, it sends a renewal reminder.
The recurring billing run — generating each month's invoice for every active agreement on a calendar — is a separate scheduled automation rather than a stage change. The Service Agreement defines the terms; the timed billing is handled by automations outside the contract's own workflow.
Residential vs commercial
The same two records serve both sides of the business. What differs is how heavily each is used and how completion is gated.
Residential maintenance routes
Usually one customer to one property, so the Property record is optional — the Customer's property address is almost enough. Agreements are often informal seasonal packages, and a recurring Job alone may cover the work. Completion is lighter, with signature optional. Dense same-day routes are scheduled with Service Areas and the dispatcher.
Commercial grounds contracts
One customer to many properties, so the Property record is essential — a property manager may hold fifty sites under one account. Each site runs on a formal multi-season maintenance contract with defined scope, a billing schedule, and renewal, so the Service Agreement is essential. Completion is heavier, with photo capture and a checklist sign-off.
You build the two records once. Residential accounts use the Property lightly and lean on recurring Jobs; commercial accounts use both fully.
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.
Built on the customization engine
Both records here are built with the same tools every FieldCamp account has. The Property and Service Agreement are custom objects with their own fields; the agreement's draft-to-expired path is a custom workflow; and both record pages are assembled from building blocks.
Add a field, rename a stage, or arrange a page to match how your crews actually work, using custom objects and fields, stages and workflows, and record layouts.
You can also add landscaping fields directly to core records without a new object: a mowing height and service type on a Job or Visit, and a residential-or-commercial marker on a Customer for routing and reporting.
Built for any size. A one-truck lawn care operator runs a dense residential route on the core records as-is. A multi-location franchise holding commercial grounds contracts adds the Property and Service Agreement layer — on the same backbone, no rebuild.
Related records
The recurring work order at the center of a maintenance route — line items, scheduling, and status.
The crew stops under a Job, with dispatch lifecycle, signatures, photos, and on-site forms.
Tiered package quotes and the invoices and payments that follow.
Recurring maintenance contracts that schedule the next Job and drive renewals.
The account a Property and Service Agreement belong to, with separate service and billing addresses.
How the core records connect, and how to make them your own.
Coming from Aspire
Most landscaping companies on Aspire can bring their structure into FieldCamp directly — customers, the properties under them, the contracts and bids, the scheduled work, the crews and routes, and the service catalog all have a home here.
Aspire's spine is Property → Opportunity/Contract → Work Tickets. FieldCamp maps that onto Customer → Property → Service Agreement → Job → Visit(s) — the same flow, with the records named for what they are.
The difference is that in FieldCamp you own and shape the model, rather than fitting your shop to a fixed one.
| In Aspire | In FieldCamp | Notes |
|---|---|---|
| Customer | Customers | The account responsible for billing. FieldCamp keeps billing, service, and property addresses on one record. |
| Property | A Property — its own custom object under the customer, with site address, measurements, and access notes | Aspire's one-customer-to-many-properties split; model it as its own record when a customer holds several sites. |
| Opportunity / Contract (estimate or bid) | Estimates & Invoices for the bid, plus Service Agreements for the recurring maintenance contract | A one-time enhancement bid is an Estimate; a recurring maintenance contract is a Service Agreement that scopes term, billing cadence, and renewal. |
| Work Ticket | Jobs and their Visits | The Job is the work order generated from the contract; each scheduled trip a crew makes is a Visit, with dispatch, on-site capture, and sign-off. |
| Route / Crew | Service Areas and Team Members | Service Areas hold territory and route scheduling; team members are staffed onto each Visit, matched by skill and area. |
| Service / Item | Price Book | Mowing, mulch, fertilizing, and cleanup priced by the unit, with cost and price separated. |
| Time & materials | Line items and job logs on the Job | Labor and material lines carry onto the Job; the T&M contract type is one of the Service Agreement billing models. |
| Invoice | Estimates & Invoices | Partial and full payments, overdue tracking, and net terms. |
What you gain. In Aspire the structure is fixed — the objects, their fields, and how they relate are set for you.
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 stages and workflows.
One honest difference. Aspire is built around deep job costing — budget-vs-actual on every work ticket, with hours, equipment, and material costs tracked live against the estimate as a job runs.
FieldCamp covers the core of that: cost and price are separated in the price book, line items and job logs capture actual labor and materials on the Job, and billing runs through the standard estimate and invoice flow.
The continuous budget-vs-actual reporting Aspire centers its product on is lighter in FieldCamp. If real-time margin tracking per ticket is central to how you run, plan that part of the move deliberately.
Related guides
Hands-on, step-by-step guides from the rest of the FieldCamp documentation.
Junk Removal Software — Data Model | FieldCamp
How a junk removal business runs in FieldCamp — on-demand hauls, volume-based truckload pricing, before-and-after photos, crews, and disposal fees, all core.
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.