Job Completion & Sign-Off Capture

The problem this kills

Your tech finishes a job and the proof of work is scattered everywhere - notes on a clipboard, parts scribbled on a job ticket, photos buried in someone's phone, and a customer signature that may or may not exist. By the time the job reaches billing, half the details are missing or contested. You invoice late, you invoice wrong, or you eat a dispute because there's no clean record of what was actually done and that the customer agreed to it.

The fix isn't another expensive field-service suite you'll spend months rolling out. It's a small, focused tool that does exactly one thing well: captures a complete, signed, photo-backed record of each visit on the tech's phone, and won't let it reach billing until a supervisor has approved it.

What you'll build

A mobile-friendly web app your field team logs into. A technician opens their assigned job, records the work performed, logs the parts used, snaps and attaches photos, and captures the customer's signature right on the screen before leaving the site. The completed record lands in a review queue. A supervisor checks the work, parts, photos, and sign-off, then approves - and only then is the job released to billing. Approved jobs export as a clean CSV in exactly the columns your invoicing system expects, and the customer automatically receives a tidy completion summary by email.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent (Claude Code), which then builds the whole tool with you, step by step, in plain language. You don't write code - you answer questions and paste prompts.

Crucially, the plan opens by interviewing you about your business - your dispatch process, the systems and spreadsheets you use today, how your jobs and parts are named and numbered, your typical and busy-season volumes, your approval rules, and your messy edge cases (no-shows, partial work, a customer who won't sign). It reflects a short tailored spec back to you for a thumbs-up, then builds the data model, validations, and every later step around your answers - not a generic template.

Inside you'll find: the full discovery interview, the exact stack, an architecture diagram, and the build broken into copy-paste prompts - login, the mobile job form, photo and signature capture, the supervisor approval queue, the billing CSV export, and the customer completion email. It closes with a "how to know it works" checklist and a no-integration fallback so you can ship today.

The governance it includes (this is the point)

This isn't a toy form - it's built to be trustworthy from day one:

• Login so only your team can use the tool.
• Row-level security so each company only ever sees its own jobs and data.
• A complete audit trail - who recorded, who approved, and exactly when.
• A hard human-in-the-loop approval gate - nothing reaches billing until a supervisor reviews and approves the completed record.
• A required signature (or a logged exception explaining why there isn't one) before approval is even possible.
• Duplicate guards keyed on the job ID, so one job can only ever produce one completion record.
• Photos and signatures stored privately in Storage behind RLS - never publicly accessible.

Who it's for

Field technicians who need a fast, phone-friendly way to close out a visit with proof - and the supervisors and back-office staff who review the work and invoice it. If you run HVAC, plumbing, electrical, appliance repair, pest control, landscaping, or any visit-based service, this is for you.

You've got this - paste the first prompt and let the agent interview you.