WORK & EXAMPLES

See the structure before you share sensitive project data.

These public examples are synthetic demonstrations. They show how GDRS connects location, STA, drawing references, assets, evidence, QA/QC, and handoff information without exposing customer drawings, coordinates, network IDs, or proprietary project records.

Illustrative workflow: source record → referenced feature → deliverable.

Synthetic source

Drawing / Redline

AB-04Authorized project record
→
Referenced feature

Asset / STA

HH-012STA 120+00Sheet AB-04Status: Reviewed
→
Controlled output

KMZ + Index

Asset layerSTA / sheet layerSource indexQA exceptions

Illustrative closeout package.

A closeout assignment may combine several controlled outputs. Exact content is project-specific.

Illustrative Sample

Closeout requirements matrix

ItemStatusSourceOwner actionRedlinesReviewedR2 PDF—KMZOpenField listResolve label
Synthetic Demonstration

Final KMZ structure

01 Route / Reference02 Assets03 Repairs / Changes04 STA + Sheets05 Approved Evidence
Illustrative Sample

QA/QC exception log

EX-004Asset: HH-012Issue: ID conflictStatus: Client review
Splicer Closeout Example

Customer-supplied evidence → organized documentation package.

This synthetic example shows the documentation relationship without displaying live carrier, project, CLLI, location, fiber, test-result, or template information.

Synthetic Example — Not Customer Data

Intake inventory

SPAN-07 / Fiber 12Source: PDF reportContext: A→B · 1550 nmStatus: Mapped
Synthetic Example — Not Customer Data

Source-to-report mapping

SPAN-07_A-B_F012_1550.pdfTarget: Closeout workbookRow: Fiber 12Status: Cross-Checked
Synthetic Example — Not Customer Data

Exception record

IMG_1042.jpgFiber 13Issue: Direction not shownStatus: Exception

Incoming evidence

IMG_1042.jpg
report-final2.pdf
fiber12_new.pdf
test_export.sor
→

Controlled closeout structure

Span-07/
  Reports/
  Native-Files/
  Source-Register.xlsx
  Exceptions.xlsx

Explore Fiber Splicer Closeout Documentation

Public examples are intentionally limited.

GDRS does not publish live customer coordinates, source drawings, logos, IDs, internal notes, or confidential metadata without authorization. Synthetic examples demonstrate the workflow; they are not represented as completed client work.

A controlled project review can use a representative, authorized sample after scope, confidentiality, and data-transfer requirements are agreed.

Want to compare this structure to your project requirements?

Start with a non-confidential deliverable checklist and a description of the records you already have.

Request a Project Review