🔁 Service Agreements

Service agreement software that generates the work — and the bill.

Define the recurrence once. Forz auto-generates the jobs and the invoices, tracks every covered device on its own inspection interval, and keeps technician certifications on file — so contracted work never slips.

12 months of billing scheduled in advance Included in every plan iOS & Android

The problem with the old way

Contracts tracked in spreadsheets

The agreement promises quarterly visits, but the schedule lives in a spreadsheet someone has to remember to check. One missed row and a contracted customer goes a year without service.

Work delivered, never billed

The visits happen, but the invoice depends on someone remembering to raise it each cycle. Every forgotten cycle is contract revenue you already earned and never collected.

Inspection intervals out of sync

Monthly visuals, annual functional tests, 5-year internals — every device at every site runs on its own clock. Tracking those clocks by hand is how due dates get blown.

How service agreements works in Forz

Recurring jobs from one definition

Set the cadence once — daily, weekly, biweekly, monthly, quarterly, every 6 months, or annually — with a next date and optional end date. Forz generates each job automatically with the configured job type, customer, description, and line items, numbered and ready for your normal dispatch workflow.

Recurring invoices with a review buffer

Bill agreements on weekly, biweekly, monthly, every-3-month, every-6-month, or yearly cycles. Forz pre-generates 12 months of scheduled items and creates each invoice as a draft up to 5 days before its date, so the office reviews before anything goes out.

Per-device inspection intervals

Pick from 14 frequencies — daily up to every 7 years. Due dates are set automatically when a device is created, the next date is calculated from each completed inspection, and one device can carry multiple inspection types, like a monthly visual plus an annual functional test.

Systems and devices behind every agreement

Organize covered equipment into configurable system types — Fire Alarm, Sprinkler, Fire Suppression, and Emergency Lighting by default — with barcoded devices, location descriptions, and custom fields, so techs know exactly what the contract covers at each site.

Certificates on the technician profile

Track certifications, licenses, and training per technician, with PDF or image attachments, so dispatchers can verify qualifications before assigning specialized agreement work.

Proof customers pull themselves

The customer portal gives agreement customers passwordless access — a 6-character email code — to download inspection PDFs and see active jobs and outstanding invoices, instead of calling your office for the report.

Frequently asked questions

Forz runs service agreements on two building blocks instead of a bolted-on contracts silo: recurring jobs and recurring invoices. Define each recurrence once — the job side carries the job type, customer, description, and line items; the invoice side carries the customer, contact, site, payment term, and line items — and Forz generates both automatically on their own cadences. Each generated job gets its own number and flows through your normal scheduling, dispatch, and completion workflow, so agreement work is handled exactly like any other job instead of living in a parallel system.

Yes. Recurring invoices run on weekly, biweekly, monthly, every-3-month, every-6-month, or yearly cycles. Forz pre-generates 12 months of scheduled items, and a daily background process creates each invoice in Draft status up to 5 days before its scheduled date — a built-in review buffer before anything reaches the customer. Invoice emails carry a token-based payment link, no customer login required, that opens a Stripe-powered checkout accepting credit and debit cards and US bank accounts (ACH). When the customer pays, Forz records the payment and flips the invoice to Partially Paid or Paid automatically, and invoices sync two-way with QuickBooks Online.

Yes. Every covered device belongs to a system at a customer site, and its device type drives the inspection schedule. Forz supports 14 frequencies — daily, weekly, biweekly, monthly, quarterly, semi-annual, annual, and every 2 through 7 years — with the initial due date set automatically when the device is created and the next due date calculated from each completed inspection. A single device can carry multiple inspection types with independent due dates, like a monthly visual plus an annual functional test on a fire alarm pull station. Technicians record Pass, Fail, or Bypass results with optional photos in the field, and customers can download the inspection PDFs from the customer portal.

See service agreements in action

Get a personalized demo and watch how it works on your real workflows — in 15 minutes.

Free data migration Free 15-minute demo — no commitment