Field service

The field-service preset is for an app in the style of ServiceTitan or Jobber. The office quotes a job, a dispatcher puts the work order in a technician's slot on the board, and the technician works through the day plan, fills in the checklist on site, records the parts used and has the customer sign.

ConfigCopy Anchor Link

import { defineConfig } from "better-supabase/config";

export default defineConfig({ preset: "field-service" });

npx better-supabase init --preset field-service starts a new project from it, and npx better-supabase apply --preset field-service adds it to one you have (CLI).

BlocksCopy Anchor Link

The preset is saas plus these blocks, and whatever they require:

How the blocks connectCopy Anchor Link

A work order sits at an asset location or an address. board returns the scheduled work orders per technician and day with the backlog, and technicianDay returns one technician's jobs in route order. The technician moves a job to en route, on site and done, and records each part with the catalog variant and stock location it came from, since catalog and inventory are installed (dispatch).

A quote the customer accepts becomes an invoice. The checklist is a form submission linked to the work order, and the signature is taken on a frozen version, so what the customer signed never changes.

With ReUICopy Anchor Link

• Event Calendar for the dispatch board, one row per technician.
• Data Grid for the backlog, with Filters on priority and customer.
• Stepper for the on-site flow: checklist, parts, photos, signature.