Crews, vans and jobs — one board runs the week
Field service is a scheduling problem wearing a job-costing problem wearing an invoicing problem. Coordinator runs all three on one system — people and equipment on the same calendar, costs on the job, invoice on completion.
Free. No card. About two minutes to set up.
The schedule lives on a wall and in seventeen messages. When someone's sick, dispatch is an hour of phone calls.
Materials on a card statement, hours on paper, the quote in an app. Job profitability is a feeling, not a number.
The work finished Tuesday; the invoice went out 'when someone got to it' — two weeks and one awkward call later.
The job arrives ready to schedule
A call or a website form becomes a job from your template — site visit, quote, work, invoice — with the customer created and their photos already attached. Ask for pictures in the form; they upload straight from a phone camera.
- Estimate goes out as a hosted page; the customer signs by typing their name
- Accepted quote converts to the job's invoice with one click
- Job templates carry your standard checklists — permits, materials, walkthrough, cleanup
Crew and equipment booked together, clash-proof
Assign work to Tuesday's shift — whoever's on it owns it — and reserve the van and the lift on their own calendar lanes. One engine holds people and things, so double-booking is blocked before it happens, not discovered on site.
- Recurring shifts with role requirements: '2 crew, 1 licensed electrician'
- Offered shifts get claimed by qualified teammates in one tap — no group text
- Approved time off takes people out of shifts and dispatch automatically
- Book 'a van' and bind the specific unit at the yard — rental-car style
The site runs on phones
Site photos dropped on the job become named, filed records — 'Harbor site — Photo — Aug 14', not IMG_4821. Completed-work forms gate the job's completion, and equipment checks out and in with condition and mileage.
- Check-out / check-in ledger: who took it, when it came back, what shape it's in
- A unit checked in as 'needs service' pauses its own bookings and spawns the repair task
- Location metadata is stripped from customer-uploaded photos automatically
Invoice while the truck's still warm
Materials arrived as bills (forward the supplier email — it lands as a draft, read by AI on your own key). Hours came from the crew's time entries. It's all already on the job, so the invoice is a review, not a reconstruction.
- Hosted invoice with card payment straight to your own account
- Fuel and supplier charges categorize themselves from the bank feed
- Margin per job, per crew, per service line — continuously
- Work for a builder on the network? Your invoice is their bill, and their sign-off closed the job
The pieces, mapped to your business
Shifts, role staffing, swaps, time off, dispatch
Vans, lifts, tools — calendars, check-out/in, maintenance loops
Job templates, site checklists, completion gates
Quotes signed on-site, bills by email, job costing, fast invoicing
Site photos, inspection forms, completed-work sign-off
GC ↔ sub: shared jobs, sign-off, invoice→bill
Asked by businesses like yours
The crew's view is small on purpose: today's jobs, their shift, a timer, and a camera button that files photos on the right job. The office sees the rest.
State drives everything: a unit marked broken or dirty pauses its own bookability, creates the fix-it task, assigns it to the least-loaded qualified person, and flips itself back to available when the work completes.
If the builder is on Coordinator, your shared job mirrors into their workspace: they see progress, their sign-off closes the work, and your invoice lands directly in their books. Getting paid stops being a paperwork project.
Put next week on the board
Set up your shifts and job templates, invite the crew free, and retire the whiteboard.
Free. No card. About two minutes to set up.