Draft more miles per engineer — without the grunt work.
Custom machine-vision models do the monotonous steps of pole-and-line inspection. Your team reviews, decides, and ships — instead of clicking through thousands of photos.
Katapult
Teams
GoogleOne system, three disciplines — vision, geospatial, drafting.
DraftLine was built with OSP contractors, not for them. Every surface — from the queue to the writeback — exists because a drafter, a QC reviewer, or a program director asked for it.
Pole-aware neural networks, trained on your field photography.
Detect tangents, anchors, guys, attachments, and hardware classes you define. Low-confidence detections route themselves into the review queue — nothing slips past unnoticed.
Every pole on the map, every node in the graph.
Mapbox-backed views of jobs, nodes, and connections. Drop into a route to see stages, flags, and make-ready status inline — no tab-hopping to find the one that's blocked.
Classifications land in your GIS automatically.
DraftLine writes node classes, attributes, and photo links back into your GIS — matching your schema, not forcing a new one.
A personal queue, ranked by priority and age.
Reviewers and drafters open DraftLine and see exactly what's next — no triage, no assignment meetings, no spreadsheets.
Routing → Prefield → Classifying → Final Review → Complete.
Every job moves through a pipeline you define. Stage-level timers, SLAs, and owner assignments keep routes from stalling in someone's inbox.
Everything a drafting shop needs. Nothing it doesn't.
Custom-trained vision models
We train on your field photography and your class taxonomy — not a generic pole detector.
Geospatial job view
Mapbox tiles, node + connection graph, per-pole drawer. Every job has a map.
Pipeline stages & SLAs
Define the stages your routes move through, and track time-in-stage per job.
Personal work queue
Reviewers and drafters open DraftLine to a ranked list of what's next.
Keyboard-first review mode
Letter hotkeys per class, arrow keys for navigation, one hand on the mouse never required.
GIS writeback
Write node classes, attributes, and photo references back to your GIS system.
Confidence thresholds
You set the bar. Below it, photos route to human review. Above it, they ship.
Team & role management
Admins, reviewers, field crews. Per-org permissions, audit trail on every label.
Built alongside the people who survey, draft, and ship.
“Our reviewers clear what used to be a two-day queue before lunch. The keyboard hotkeys alone earn their keep.”
“DraftLine writes classifications straight to our GIS. I haven't touched a CSV in four months.”
“Program directors finally have a map view that reflects what's actually happening in the field — not what was true last Tuesday.”
Questions contractors and program directors ask us first.
We train on the photography your teams already capture. If you have archived jobs, that's usually enough for a first production model. We tune with you over the first pilot.
Put DraftLine on a real job. See real classifications before you commit.
Pilots run on a slice of one of your existing routes. You'll see model performance, review flow, and GIS writeback on your own data — usually inside two weeks.