Product

How SpliceFlow works

A splicing job isn’t one task — it’s a list of enclosures. Vaults, poles, handholes. SpliceFlow sets the job up that way from the start.

A job is a list of enclosures

Progress means something specific: which cans are done, what’s still open, what’s missing for closeout.

Every active job, its enclosures, and closeout status at a glance. Simulated job data.
Counts, photos, notes, and time on that enclosure. Simulated DEMO-1001.
Closeout from that capture. Missing items show on the record.

Log counts and photos at the splice point

At the can, techs record counts, photos, notes, and time on that enclosure — not in a Friday camera roll or a text thread.

DLR stays with the job until a PM attaches the CAD schematic

DLR here is the CAD OSP splice schematic. Paperwork on the job → PM attaches CAD on the enclosure → techs ink that drawing. Not a loss-reading photo. Not a test-report engine.

Closeout from that record

Closeout work starts from that capture — not a Friday scramble.

Simulated DEMO-1001: SpliceFlow enclosure capture. Synthetic job, not a customer site.
Simulated enclosure capture — DEMO-1001, not a customer job.
Simulated DEMO-1001 OSP splice schematic (CAD). Not a customer job.
Simulated DEMO-1001 OSP splice schematic (CAD). Not a customer job.
Simulated DEMO-1001: PM published markup on a job photo, not the CAD schematic. Not a customer job.
PM marks up a job photo and publishes it — not the CAD schematic. Techs ink that schematic after a PM attaches CAD on the enclosure. Simulated DEMO-1001, not a customer job.

Keep the tools you already pay for

Not another PM. Not your OTDR/OLTS. We take the splice slice.

What this page is allowed to say

Invite-only app. Walks use synthetic DEMO-1001 until Tess PASS. No perfect production walk yet.

Register with us

Company invite queue — not a self-serve tech account.

Newsletter

Field notes for splicing crews