Photo-validated scope — before the truck rolls.
Treadscope reads the photo and the contractor notes against the manufacturer spec library and returns a verdict — "Ready for first cut" or "Review needed" — with cites attached. The substrate, material, moisture, and underlayment all surface in the same ticket the foreman reads the morning of the measure.
- Photo in, notes in
- Spec-library match
- Verdict with cites
Inline preview
The verdict chip the foreman sees the morning of the measure.
The screenshot below stands in for the live /scope/[id] view — the verdict chip plus the four spec-library flags in the same card the dispatch team reads at booking time.
Photo uploaded at /scope with the contractor note attached.
Verdict rendered against the Forbo spec library — each line below is the citation the matcher attached when the notes were checked.
- substratePlywood subfloorForbo-TDS-002
- materialEngineered hardwoodForbo-MAT-004
- moistureRH within spec — no flagForbo-MOI-001
- underlaymentStair-nose profile requiredForbo-UND-001
/scope/[id] screenshot once the asset ships.How it works
From a phone photo to a verdict in three steps.
No eyeballing on the dispatcher's end. No hand-off to the call-center. The notes and the spec library do the work; the foreman reads the result on the morning of the measure.
- 01
A photo and a few notes at /scope.
The foreman snaps a job-site photo and types a short note about the substrate, material, and access. The submission lands in the queue with the contractor notes attached — never a hand-off to the call-center.
- /scope
- POST /api/scope-submissions
- 02
A spec-library match against the photo.
Treadscope runs the notes through the manufacturer reference library — substrate, material, moisture, and underlayment each checked against the right TDS line. Cites are attached to every flag so the verdict is auditable, not vibes.
- /admin/specs
- runScopeCheck()
- Forbo-TDS-002
- 03
/scope/[id] returns a verdict.
The detail ticket lands as "Ready for first cut" when substrate and material are both detected and no warning condition was raised — otherwise it reads "Review needed" with the cites that explain why.
- /scope/[id]
- GET /api/scope-submissions/[id]
The math
Why a mis-scoped install costs more than a callback.
An installation that misses the substrate is the same calendar week the crew booked. The truck rolls, the substrate is wrong, the day is gone — and the homeowner is back on the phone asking why the second appointment is two weeks out. Call it a callback, a re-order, a customer who doesn't take the second call. Multiplied by the weeknight voicemails the home page describes as the missed-call math, it's the wedge of margin a dispatch board leaks in a single quarter.
The missed evening call is where margin goes. The scope check is the same logic applied earlier in the week, to a cheaper question — the substrate call, not the staffing call. Treadscope reads it before the truck is loaded, not after the day is lost.
Get on the early list
Get on the scope-check early list.
The waitlist is how we decide which crews see the photo-validated scope wedge next. Drop your email — Treadscope follows up before the next booking cycle, not after.