Dartboard Energy

Dartboard is a documentation and closeout layer, not a monitoring or dispatch system, and reading it as anything else leads to a bad purchase. The product does one loop extremely well: the job arrives as a work order, PDF, or FSM record; the tech narrates out loud through AirPods while physically working; Dartboard tracks required fields (in the vendor's example, closer replaced, dimensions 90" x 50", right-hand reverse handing, LCN 4040XP hardware, after photo); it interrupts for anything missing before the tech leaves; and it writes the completed documents back. The interruption is the highest-value part, because a missing after photo is a return trip, and a return trip is a truck roll you already paid for once. The integration posture is unusually pragmatic for this category. Rather than demanding an API project before go-live, Dartboard accepts the PDFs a shop already uses — work order.pdf, PM checklist.pdf, Door survey.pdf, service manual.pdf in the vendor's own list — and works from those on day one, with software connection later or not at all. That collapses the usual "we'll evaluate it next quarter after IT" delay into a single crew pilot. It also means the ceiling is a PDF: structured FSM write-back is the richer path, and that depends on which FSM you run, which the vendor's homepage leaves as a generic "built to integrate with" strip rather than a published list. Where it fits: HVAC, door, electrical, and general service contractors with defined PM checklists and a real completeness standard. Door work suits it especially well because the required record is a fixed set of attributes — handing, dimensions, fire rating, hardware — which is exactly the kind of checklist a voice agent can hold in its head and a human cannot at 4pm on their sixth job. Where it does not fit: shops already closing out same-day with clean paperless workflows will see little upside, and techs who won't narrate their work aloud all day will fight the tool rather than use it. Highly non-standard diagnostic work with no fixed scope gives Dartboard nothing to check against. Two honest caveats buyers should price in. First, this is a spoken-log product, so its output quality is bounded by how well a tech describes the work — quiet techs get thin reports. Second, treat the pilot as an operational change, not a software install: someone has to decide which jobs, which crew, and what "complete" means before the first tech puts the AirPods in. Buy it for the closeout loop. Don't buy it expecting dispatch, scheduling, or invoicing, because it explicitly isn't those.