Sample blueprint (pre-generated — no API calls)
Field Service Ops
Dispatch board, technician workflows, and proof-of-work automation for contractors.
Highlights real-world ops complexity: mobile technicians on unstable networks, strict job-state transitions, and proof-of-work media with SLA automation.
Advanced outputs (CLAUDE.md, .cursorrules, Master Prompt)
Recommended Tech Stack
Primary stack: - Next.js 16 web app + TypeScript strict. Reason: one codebase for dispatch dashboard and mobile technician web UI. Alternative: React Native app for technicians if offline-first native features are required. - UI: Tailwind + shadcn/ui + TanStack Table + DnD kit. Reason: dispatch boards and dense job tables are easier with these primitives. - Auth: Clerk RBAC (owner/dispatcher/technician). Reason: fast role scaffolding and secure session handling. - DB: Postgres + Prisma. Reason: strong consistency for job status and assignment history. - Storage: S3/R2 for proof photos via short-lived signed URLs. - Mapping: Mapbox Distance Matrix and geocoding. Reason: ETA and route hints without building custom mapping stack. - Messaging: Twilio SMS + Resend email fallback. - Queue/jobs: Trigger.dev or QStash for reminders, SLA alerts, and follow-ups. - Observability: Sentry + structured logs with jobId/tenantId correlation ids. Why this stack: - Balances low ops with strong operational reliability. - Supports exportable contracts and reproducible dispatch workflows.
Quick FAQ for this example
What does this example optimize for?
Fast dispatch decisions and reliable technician execution under poor connectivity.
Does it cover customer communication too?
Yes. It includes notification dedupe, opt-out handling, and follow-up automation.
Can I adapt it to logistics or maintenance?
Yes. The assignment/state-machine model is reusable across most field operations products.
Copy this URL to share the sample blueprint.