DEV3 Crewbolt – Field Service Management Laravel Script with Dispatch Board, PPM Contracts & Technician App

Crewbolt is a field service management system you host yourself, built by DEV3 Technologies on Laravel 12 and Filament 4, with a Flutter technician app. One field-service company (HVAC, plumbing, electrical, fire and security, lifts, cleaning, pest control, facilities) runs it across one or more branches. The demo business is a fictional heating and plumbing contractor, Brightwater Climate & Plumbing.

No live demo: 48 grouped screenshots and two video tours show the marketing site, the dispatch board, the admin panel, the customer portal and the technician app. Install it with the bundled demo data to try every role on your own server.

What the office gets

• A dispatch board with technicians by hour and an unassigned queue sorted by SLA due time. Dragging a job onto a technician checks skills, shift, absences and travel time before it saves, and two dispatchers can never double-book the same slot.
• Work orders from calls, the public request form, the customer portal, quotes or recurring maintenance (PPM) contracts, with priority, status and both SLA due times in one list.
• SLA timers (response and resolution) that run on each branch's business hours and holidays and pause while a job waits on the customer or on parts.
• PPM contracts that generate visits ahead of time, grouped per site and day, without ever creating the same visit twice.
• Customers, sites and assets with QR labels, service history, encrypted access notes and gate codes.
• Quotes sent as a signed approval link, invoices with a pay link, payments, credit notes and void, rate cards with labour bands, call-out fee and parts markup, and service report PDFs sealed on completion.
• Van and warehouse stock: transfers, part requests, purchase orders and van counts that wait for a manager to approve variances.
• Branch isolation: dispatchers and managers see only the branches they are granted. Reports for SLA compliance, first-time fix, revenue and PPM completion; a REST API with scoped keys and webhooks; a signed inbound alarm webhook that raises work orders.

What customers get

A customer portal by magic link (sites, visits, service reports, quotes to approve, invoices) and public quote-approval and invoice pay pages that work on a phone.

The technician app (Flutter source included)

Today's route in order, job detail with access notes and the gate code, a state bar for travel, arrive, pause and complete, checklists with ranges, traffic lights and required photos, parts booked off the van, on-site quotes, customer signature, asset lookup by QR label, van stock count and timesheet. It works offline: changes queue in order and sync later, and a change the office refused waits on a Needs attention screen. The app runs in demo mode out of the box and points at your site when you set its URL. The shown estimate uses the same pricing rules as the server and is checked against shared test vectors.

Built for correctness

Pest tests (288 passing) cover dispatch conflicts, SLA clocks across holidays and DST, PPM generation, offline sync, stock, quotes and pricing; job pricing is asserted against 32 cases produced by an independent oracle. A MySQL race suite runs real parallel requests for double assignment, double quote acceptance, duplicate sync pushes, the last van part, repeated PPM runs, stock transfers, double payment and cancel versus complete.

Good to know

• For one field-service company with one or more branches. It is not a multi-company SaaS.
• Travel time and scheduling suggestions use straight-line distance times a road factor (no paid routing API, no traffic data). Maps use OSM tiles when configured.
• The technician app works offline and syncs. Location is shared only during an active job, in the foreground; the demo uses simulated positions. You must tell technicians and follow local employee-monitoring law.
• Card payments, SMS, mail, push and maps are simulated until you connect real ones. Accounting is a CSV or journal export, not a ledger. There is no AI scheduling and no payroll.
• Service report PDFs and signatures are records, not legal advice on signature validity.
• The app was verified in simulator builds, tests and against the live API, not on a real device; scanning with the camera and push are buyer add-ons. Publishing to the app stores is your step (guide included).

Requires PHP 8.2+, MySQL 8 or MariaDB 10.6+ for a live site (SQLite for evaluation) and a cron entry. Flutter 3 is needed only to build the app.