FieldCamp

Cleaning Business Software — Data Model | FieldCamp

How a residential and light-commercial cleaning business runs in FieldCamp — recurring home plans, deep and move-out cleans, and crews on core records.

A cleaning business runs almost entirely on FieldCamp's core records. Recurring home cleaning, one-time deep and move-out jobs, crews, quoting, billing, and on-site checklists are all there the moment you sign up.

The chain a maid service already lives by — a customer books a clean, you quote it, you schedule a crew on a repeating plan, you bill, and you get paid — is modeled directly as Request → Estimate → Job → Visit(s) → Invoice → Payment.

Almost nothing about this trade needs a new record.

The details that make one clean different from the next — beds and baths, pets, how the crew gets in, what plan the home is on — fit as a few custom fields on the records you already have, and the room-by-room checklist is a Job Form.

What the core already gives you

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

  • Recurring home plans. A Job set to recurring auto-generates its Visits from a weekly, biweekly, or monthly pattern, so a standing home cleaning plan schedules itself.
  • One-time and as-needed cleans. The same Job set to one-off covers a deep clean, a move-in or move-out, or an Airbnb turnover — a single scheduled Visit, no recurrence.
  • Crews on every stop. Each Visit is staffed by one or more team members, matched by skill and service area, with capacity and conflict warnings, and a customer can carry preferred cleaners that route automatically.
  • Route and territory scheduling. Service Areas and the dispatcher assign crews to homes across the day, so a dense same-day route plans itself.
  • Tiered quotes and deposits. An Estimate carries multi-option pricing — the Good / Better / Best pattern, such as standard versus deep versus move-out — with deposits.
  • Invoicing and payments. An Invoice tracks partial and full payments, overdue status, and net terms for commercial accounts; residential cleans are usually a card charged the same day.
  • A priced catalog. The price book holds standard cleans, deep cleans, move-outs, and add-ons like inside-fridge or inside-oven priced by the unit, with cost and price separated.
  • Room-by-room checklists. Job Forms give the crew a digital task list with a progress bar — a standard-clean checklist, a deep-clean checklist, a move-out checklist — and you can require a minimum number of photos before a Visit is marked complete.
  • On-site 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.
  • Lead intake. A Request captures a new inquiry or online booking 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-home residential or single-location commercial account.

A standing residential plan — the same scope billed on the same cadence, round after round — is a recurring Job.

A formal Service Agreement with a term and a renewal date is added through customization, and earns its place for light-commercial accounts that want a contract on the books.

Tailoring it to a cleaning business

Because the core already covers the workflow, tailoring this trade is mostly a matter of adding a few fields and a checklist — not building a heavy object model.

The cleaning-specific detail that makes one quote a three-bed two-bath weekly plan and another a one-time move-out lives as custom fields on the records you already use. The room-by-room checklist is a Job Form, not a pile of fields.

A single custom object earns its place only when one commercial account holds more than one location.

Custom fields worth adding

These attach to the core records — most to the Customer or the Job — and need no new object. Add a field, label it, and it appears on every record of that type.

FieldWhere it fitsWhat it holds
BedroomsCustomerThe bed count the quote and the crew work from
BathroomsCustomerThe bath count that drives time and pricing
Home sizeCustomerSquare footage, when you price by area
PetsCustomerNone, dog, cat, or both — so the crew arrives prepared
Access methodCustomerHome, lockbox, key on file, gate code, or smart lock
Access notesCustomerThe lockbox or gate code and any entry instructions
Cleaning planCustomerWeekly, biweekly, monthly, or one-time
Clean typeJobStandard, deep, move-in, move-out, or turnover
Supplies providedJobWhether the crew brings supplies or the home does
Add-onsJobInside fridge, inside oven, windows, or laundry
First-clean flagJobMarks a heavier first visit versus a maintenance clean
ParkingCustomerDriveway, street, or building notes for the crew

Beds, baths, pets, and access also make routing and reporting sharper. A three-bed deep clean with a dog and a single-bath weekly maintenance run are different blocks of work, and tagging the record lets the dispatcher and your reports tell them apart.

The checklist is a Job Form

The room-by-room scope of a clean — kitchen counters, bathroom fixtures, baseboards, inside windows — is a Job Form, not a long list of custom fields.

A Job Form is a reusable checklist template the crew works through on the Visit, with a progress bar and per-item check-off.

Build one form per clean type — a standard checklist, a deep-clean checklist, a move-out checklist — and attach the right one to the Job. The crew's check-offs and photos are stored on the Visit, so every clean leaves a record of what was done.

You generally do not need a custom object for residential or light-commercial cleaning. The home is the Customer's property address, the plan is a recurring Job, the scope is a Job Form, and the per-home details are custom fields.

A custom object is worth adding only when one commercial account holds several distinct locations — and for nightly multi-building janitorial contracts, the janitorial setup is the better fit.

One-time cleans vs recurring plans vs commercial

The same records serve every kind of clean. What differs is how the Job is scheduled and how completion is gated.

One-time and recurring residential

A one-time clean — a deep clean, a move-out, or a turnover — is a single Job with one Visit. A standing plan is the same Job set to recurring, so a weekly or biweekly home schedules its own Visits. Both lean on the per-home custom fields and a Job Form checklist. Completion is lighter, with signature optional, and payment is usually a card charged the same day. Dense same-day routes are scheduled with Service Areas and the dispatcher.

Light commercial

A small office, gym, or storefront on a standing scope adds a recurring Service Agreement with a term, a billing schedule, and a renewal date, and an Invoice on net terms. Completion is heavier — a checklist sign-off and photo capture at the end. For nightly, multi-building janitorial contracts with quality inspections, the janitorial setup layers Sites, Service Agreements, and Inspections on the same core.

You add the fields and the forms once. One-time and recurring residential work runs on the core as-is; light-commercial accounts add the Service Agreement layer on the same backbone, no rebuild.

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

Built on the customization engine

Everything here is built with the same tools every FieldCamp account has. The per-home details are custom fields on the core records; the room-by-room scope is a Job Form; and each record page is assembled from building blocks.

Add the custom fields — beds, baths, pets, access, cleaning plan, supplies provided — to the Customer and the Job, so the quote, the crew, and the dispatcher all work from the same numbers.

Build a Job Form checklist per clean type — standard, deep, move-out — and attach the right one to the Job, so the crew works a clear scope and leaves a record of it.

Tune completion in stages and workflows — require photos and a signature on commercial cleans — and arrange each page with record layouts.

Built for any size. A solo cleaner running a recurring residential route works on the core records with a handful of custom fields and a checklist. A growing maid service with crews and a few light-commercial accounts adds the Service Agreement layer — on the same backbone, no rebuild.

Coming from Jobber

Most cleaning businesses on Jobber can bring their structure into FieldCamp directly — clients and their properties, requests, quotes, the one-off and recurring jobs, the visits under them, invoices, and the products and services list all have a home here.

Housecall Pro maps the same way.

Jobber is built for SMB simplicity with a fixed, opinionated model. FieldCamp matches that model one-to-one and lets you add your own records, fields, and stages as you grow.

In JobberIn FieldCampNotes
ClientCustomersThe party responsible for billing. FieldCamp keeps billing, service, and property addresses on one record.
PropertyThe customer's service address, or a Property custom object when one client holds several homes or sitesJobber stores properties under a client; a single-home client is the service address, several locations earn their own record.
RequestRequestsInbound inquiries and online bookings, with inspection and quote stages already built in.
QuoteEstimates & InvoicesQuoting with tiered Good / Better / Best options, photos, and deposits.
Job (one-off or recurring)JobsThe work order — one-off for a deep or move-out clean, recurring for a weekly or biweekly plan that auto-schedules its visits.
VisitVisitsEach scheduled stop under a job, with dispatch, en-route, on-site, checklist, photos, and sign-off.
InvoiceEstimates & InvoicesPartial and full payments, overdue tracking, and net terms for commercial accounts.
Products & ServicesPrice BookStandard, deep, and move-out cleans with add-ons priced by the unit, cost and price separated.
TeamTeam MembersThe crews staffed on every visit, matched by skill, service area, and customer preference.
Time trackingCaptured on the VisitCheck-in and check-out with location, so labor is logged against the stop it belongs to.

What you gain. Jobber's model is fixed and simple by design — the records, their fields, and how they connect are set for you, which is part of why it is easy to run.

In FieldCamp you keep that simplicity and add your own records and stages when you need them.

Match your Jobber setup first, then go past it with custom objects and fields — a Property object, a Service Agreement, per-home access details — and your own stages and workflows when a clean needs a step Jobber's structure does not hold.

One honest note. Jobber bills through its own built-in invoicing, and FieldCamp does the same — the mapping here is close to one-to-one.

The difference is not a missing engine; it is that FieldCamp lets you extend the model with records, fields, and stages of your own, where Jobber keeps the structure fixed.

See also

More in the FieldCamp data model.

Hands-on, step-by-step guides from the rest of the FieldCamp documentation.

On this page