Capture the splice once.
Closeout comes with it.
Enclosures (closures), splices, photos, and time in one splice log. DLR stays with the job until a PM attaches the CAD schematic on the enclosure, so as-builts, closeouts, and production reports are not a Friday scramble.
Built by a working splicer. Not a software company guessing at the workflow.
One splice log, at the enclosure
Spreadsheets, group texts, and shared drives weren't built for splicing work. SpliceFlow is.
Counts, photos, notes, time
Office sees the same record the tech just logged. One job, one enclosure, one source of truth.
Photos sit on the enclosure. DLR is on the job
A PM attaches the CAD schematic on the enclosure (A/B, ticks, span IDs). Until then it is paperwork on the job, not a drawing already on the can.
As-builts, closeouts, production
Built from what was captured. Missing items show on that record.
Counts and photos on that enclosure
Photos and counts sit on that can. DLR is paperwork on the job until a PM attaches CAD on the enclosure.
Closeout from that record, not a Friday scramble
- Status without the phone tagThe office sees the same enclosure record.
- Documentation that's actually therePhotos and counts on the enclosure. DLR on the job, not in a text thread.
- Closeouts that don't bounceMissing items show on that record and on the packet, not after the invoice.
Fast enough to use with gloves on
- Log it once, at the splice pointCounts, photos, notes. DLR stays with the job.
- No end-of-week paperwork pileCloseout comes from that enclosure record, not a Friday pile.
- Works the way splicing worksTrays, ribbons, closures, DLR — the app speaks the trade.
From the founder
“I splice fiber for a living. SpliceFlow exists because good crews and good coordinators still lose hours every week chasing photos, DLR, counts, and closeout paperwork across three apps and a text thread. This is the job record both sides of that handoff actually needed.”
FAQ
What this page is allowed to say today.
What gets captured at the enclosure?
Counts, photos, and time on the enclosure. DLR is the CAD OSP splice schematic: paperwork on the job until a PM attaches it on the enclosure (A/B, splice ticks, span IDs, fiber counts). Simulated DEMO-1001. Not a test-report engine.
Does this replace my PM or tester?
Keep the PM and tester tools you already pay for. We take the splice those tools don’t hold. Invite-only — the public door is this waitlist.
Is this a live production walk?
Walks use a synthetic golden job. We do not claim field-proven, a live customer job, or a perfect production walk yet.
What do you mean by DLR?
On this site, DLR is the CAD OSP splice schematic (A/B, splice ticks, span IDs, fiber counts). It lives as paperwork on the job until a PM attaches it on the enclosure. Simulated DEMO-1001. We do not parse OTDR .sor files or run a test-report engine. Not a loss-reading photo. Not Device Level Ring. Not Dynamic Line Rating.
Join the waitlist
If you run splicing work, you go to the front. We will write when a walkthrough is ready.
No spam. No date. We will be in touch.