FieldCamp

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.

A junk removal business runs almost entirely on the records FieldCamp gives you the moment you sign up. On-demand hauls, crews, volume pricing, before-and-after photos, and on-site payment are all there with no setup.

The chain a hauler already lives by — a customer books a pickup, a crew rolls a truck out, you price the load by how much space it fills, you shoot before-and-after photos, and you collect on the spot — is modeled directly as RequestEstimateJobVisitInvoice → Payment.

Almost nothing here needs a new record. The few trade-specific touches — the volume estimate, item categories, the dump fee, and access notes — are a handful of custom fields and a price book set up by truckload, not a custom object.

What the core already gives you

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

  • On-demand jobs. A one-off Job is the default shape — a single pickup booked, scheduled, dispatched, and billed — so a same-day haul needs no special configuration.
  • Volume-based pricing. The price book holds your truckload tiers — minimum, quarter, half, three-quarter, and full truck — as priced items a crew picks on site, alongside per-item, stairs, and long-carry add-ons.
  • Crews on every job. Each Visit is staffed by one or more team members, so a two- or three-person crew is assigned to the truck that runs the job.
  • Before-and-after proof. Visits track en route, arrived, working, and done with check-in and check-out location, and photos captured on site — the before-and-after shots that close out a haul.
  • On-the-spot quotes and bills. A Request captures the inbound booking and converts in one click to an Estimate or a Job; the Invoice bills the load and takes card payment in the field.
  • Disposal and dump fees. Dump, recycling, and donation fees are line items on the Job, drawn from the price book, so each haul carries the disposal cost that protects its margin.
  • Route density and territory. Service Areas cluster pickups by zone, and the dispatcher orders the day so a truck stacks nearby jobs and dump runs efficiently.

The Customer record already separates service, billing, and company addresses, and marks each account as an individual or a business — enough to tell a homeowner from a property manager or a contractor.

Volume pricing does not need a custom object. A truckload tier is a price book item with a price; a crew adds the tier and any add-ons as line items, exactly the way the catalog is built to work.

The estimate's Good / Better / Best option also fits a "haul only" vs "haul plus heavy items" quote with no extra setup.

Tailoring it to junk removal

What this trade needs that core does not already name is a short list of fields, not new records.

A booker needs a rough volume estimate to size the truck, the crew needs to know the item categories and where to get in, and a heavy load may carry a disposal surcharge.

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

FieldOn recordField typeWhat it holds
Volume estimateRequest or JobSingle choiceMinimum, quarter, half, three-quarter, or full truck
Item categoriesRequest or JobMultiple choiceFurniture, appliances, electronics, yard waste, construction debris, mattresses, hot tub, estate cleanout
Heavy / bulky itemsJobLong textPianos, safes, hot tubs, and other items needing extra crew or equipment
Dump / disposal feeJobCurrencyThe disposal surcharge on this load, on top of the truckload tier
Access notesCustomer or JobLong textStairs, gate codes, long carry, elevator, parking, and where the items sit
Job photosVisitFileThe before-and-after shots captured on the haul

Put access notes on the Customer when a property is serviced more than once — a recurring commercial account, say — so stairs, gate codes, and parking show on every Visit. Put them on the Job for a one-time residential pickup.

The on-site documentation is also a Job Form: a short per-visit checklist — items confirmed, volume marked, before photos, after photos, dump receipt, customer sign-off — captured on the truck and stored on the Visit, with the photo requirement turned on for the completion step.

How it fits together

Even though junk removal adds no custom object, it is worth seeing how the core records carry the work — the truck, the crew, the load, and the disposal cost all live on records you already have.

A Customer books a pickup as a Request, which converts to a Job, optionally through an Estimate.

The Job is scheduled as a Visit run by a crew, priced from the truckload tiers and dump fees in the price book, and billed on an Invoice paid in the field.

There is no separate "load" or "haul" record to build. The Job is the haul, the Visit is the truck rolling out, the volume and item fields describe the load, and the price book tiers price it — all on the core model.

On-demand vs recurring commercial

The same backbone serves both sides of the business. What differs is whether the work is booked one haul at a time or runs on a standing schedule.

On-demand residential

The bread and butter — a homeowner books a single cleanout or pickup. It is a one-off Job with a volume estimate, item categories, and access notes; the crew shoots before-and-after photos, adds the truckload tier and any dump fee as line items, and collects on the spot. The Request and the dispatcher handle same-day and same-week bookings.

Recurring commercial

Property managers, builders, retailers, and estate companies who haul on a schedule. A recurring Job auto-generates its Visits on a weekly or monthly cadence, billing carries a purchase-order number, and a Service Agreement holds the standing terms and rate. The same volume and item fields describe each pickup.

You set up the fields and the price book once. On-demand work leans on the one-off Job and the Request; recurring commercial work reuses the same records on a repeat schedule — no second model.

The completion difference does not need a second workflow either. The same Visit workflow can require a before-and-after photo on every haul and add a customer signature on commercial accounts — one pipeline, configured per account through stages and workflows.

A booking becomes a Job, optionally quoted first, scheduled as a crewed Visit priced from the truckload tiers, and billed on an Invoice paid in the field.

Built on the customization engine

Everything here is built with the same tools every FieldCamp account has. The junk removal fields are custom fields on the core records, the truckload tiers and dump fees are price book items, 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 hauls actually run, using custom objects and fields, stages and workflows, and record layouts.

Built for any size. A one-truck operator runs on-demand hauls on the core records plus a few fields and a truckload price book. A multi-location franchise hauling for property managers adds recurring jobs and agreements — on the same backbone, no rebuild.

Coming from Jobber

Most junk removal businesses on Jobber can bring their setup into FieldCamp almost record for record.

The on-demand shape — a client books a haul, a crew rolls a truck out, you price the load, and you bill on the spot — lines up one to one with the core records here.

The difference is that in FieldCamp the model is yours to extend past that 1:1 match when you need to.

In JobberIn FieldCampNotes
ClientCustomersThe party responsible for billing. FieldCamp keeps service, billing, and company addresses on one record.
PropertyThe customer's service address — or a custom object under the customer for a multi-site accountA single-site homeowner uses the service address; model a Property as its own record when one account hauls from several locations.
RequestRequestsThe inbound booking or online-booking intake, with one-click conversion to a quote or a job.
QuoteEstimates & InvoicesOn-site quoting, including a "haul only" vs "haul plus heavy items" comparison.
JobJobsThe haul itself — one-off for a single pickup, or recurring for a commercial account.
VisitVisitsThe truck rolling out, with dispatch, check-in, and before-and-after photos.
InvoiceEstimates & InvoicesThe bill for the load, with field card payment and overdue tracking.
Products & Services (volume / truckload pricing)Price BookTruckload tiers, per-item charges, and dump fees as priced line items a crew picks on site.
TeamTeam MembersThe crew assigned to the truck, carrying skills and service areas.

What you gain. In Jobber the records and how they relate are set for you.

In FieldCamp every one of those records is yours to rename, extend, and restage, so you can match your Jobber setup first and then go past it with custom objects and fields and your own stages and workflows — a volume estimate on the request, item categories on the job, a dump-fee surcharge, or a before-and-after photo required at completion.

One honest difference. For a straightforward on-demand hauler, the move is close to 1:1 — the records carry over directly.

The difference is not what Jobber covers and FieldCamp does not; it is that FieldCamp lets you keep shaping the model as the business grows, where Jobber's stays 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