Operations · App Starter
Field Service Template
A working field service system — dispatch board, work orders, mobile tech view — generated into a codebase you own.
Describe how your crews work, and Dual7 generates this field service system around it: six connected entities, a drag-to-assign dispatch board, and a technician view built for a phone in a crawlspace. It ships as a full-stack app in your repository — priced like software you own, because it is.
- 6 core entities
- Dispatch board
- Code you own
- Vibe + Governed modes
01 · Data model
What's inside: the data model
Field service runs on one question asked forty times a day: who is where, doing what, with which parts. This starter generates six connected entities so the dispatch board, the tech's phone, and the office all answer it from the same tables.
| table | what it holds |
|---|---|
customers | Who you serve — sites, contact details, service history, and every job ever run at the address. |
jobs | The unit of scheduling: a visit with a customer, time window, assigned technician, and status. |
technicians | Your field team — skills, service areas, and working hours that drive assignment decisions. |
work_orders | What the job actually requires and what happened — tasks, findings, parts used, photos, sign-off. |
parts | Materials and components with cost and truck or warehouse stock, consumed against work orders. |
service_agreements | Recurring maintenance contracts that auto-generate scheduled jobs and set response terms. |
02 · Screens
Signature modules
Dispatch board
01A day-and-week grid of technicians and time slots — drag a job onto a tech and the assignment, notification, and schedule update happen together. Unassigned jobs queue at the edge with their time windows visible, so the morning scramble is a sorting task, not a phone tree.
Job status flow
02Jobs move through a defined lifecycle — scheduled, dispatched, en route, on site, complete — with timestamps at every transition. The office sees reality without calling anyone, and the day's history is data you can query, not a story reconstructed at five o'clock.
Mobile tech view
03Techs get a phone-first view of their day: the route, the customer's history before knocking, the work order to complete on site, photo capture, and customer sign-off. Built for one-handed use between a ladder and a van — because that's where it gets used.
03 · Process
How it works
- 1You
Describe your operation
Tell Dual7 what you service, how many techs you run, how jobs arrive, and what a completed visit has to capture. The trade-specific details are exactly what shapes the build.
- 2Vibe mode
Generate and refine in Vibe mode
Get the working system in minutes, then adjust conversationally: add a checklist to work orders, a second time window, a photo requirement before sign-off. Every change is code you can inspect.
- 3Governed mode
Roll out through the governed pipeline
When real trucks run on it, ship through Dual7's approval gates to your infrastructure — job history in your database, an audit trail behind every change.
04 · Fit
Who the Field Service starter is for
Owner-operators graduating from the whiteboard
At four techs, the whiteboard and the group chat start dropping jobs. This starter is the smallest real dispatch system — same columns as the whiteboard, plus status you don't have to ask for and history you don't have to remember.
Service companies squeezed by per-tech pricing
Field service platforms price per technician per month, which taxes growth precisely when trucks are the expensive part. A generated codebase flips it: adding tech number nine costs a login row, not another subscription seat.
Operations managers with a process the platforms don't fit
Two-visit diagnostics, mandatory safety checklists, warranty flows, photo evidence before invoicing — when your process is your reputation, bending it to a vendor's workflow is backwards. Here the process is the spec the system is generated from.
Businesses tired of paying rent on their own history
Ten years of job records at every address in town is the moat. When that history lives in a subscription you've stopped controlling, so does the moat. Own the schema and the history compounds in your database instead.
05 · Yours
Customize it, own it
Make it yours
The generated system is the trunk; your operation grows the branches. Rename jobs to visits, calls, or tickets and the screens follow. In Vibe mode, add what your trade needs conversationally — equipment model and serial fields, a safety checklist that blocks completion, before-and-after photo slots, a callback flag that routes to the original tech.
Bigger moves are ordinary changes to your own code: an estimates entity that converts to jobs, invoicing generated from completed work orders, truck-stock replenishment from parts usage, or a customer portal showing upcoming visits. The app has no runtime dependency on Dual7 — your team can extend it as long as trucks roll.
Why a starter, not a subscription
Field service software rents you a window into your own operation — per-tech pricing, your job history behind their API, integrations sold back as add-ons. This starter generates the dispatch board, work orders, and mobile views as source code in your repository, deployed on your infrastructure with every job record in your database. The system that runs your day belongs to you the way your trucks do.
The honest trade-off is operational: you run the app your business depends on. Dual7's governed pipeline is built for exactly that stake — approval gates so changes don't land mid-dispatch, an audit trail of what shipped and when, and regeneration when the operation outgrows the current structure.
06 · Industries
Industry versions
Field Service template — frequently asked questions
What do I get when I start from this field service template?
A working full-stack field service system in a codebase you own: customers, jobs, technicians, work orders, parts, and service agreements, with a dispatch board, status tracking, and a phone-first tech view. It deploys on your infrastructure with your history in your database.
Do technicians need a separate mobile app?
No — the tech view is a phone-first web experience in the same codebase: today's route, customer history, work-order completion, photos, and sign-off. One system to run, and every tech's browser is already installed.
Can it handle recurring maintenance contracts?
Yes — service agreements are a core entity that generate scheduled jobs on their cadence and carry response-time terms. The spring tune-up wave appears on the board weeks ahead instead of in a panicked April spreadsheet.
Does it track parts and truck stock?
Parts carry cost and stock by warehouse or truck, and work orders consume them, so job costing and restocking both read from real usage. If you need deeper purchasing, it pairs with the inventory starter on the same conventions.
Is this for auto repair shops too?
Shops with bays, vehicles, and repair orders have their own shape — that's the dedicated auto repair starter. This starter is built for mobile service: techs traveling to customers, dispatch windows, and work done at the customer's site.
Related
Dual7 App Starters
Build your Field Service on your terms
A working field service system — dispatch board, work orders, mobile tech view — generated into a codebase you own. Describe your version to start — the output is a project you own.