QA/QC & VALIDATION APPROACH

Make the source, assumptions, checks, and exceptions visible.

GDRS uses record-based QA/QC to improve consistency and traceability while keeping a clear boundary between documentation review and professional field, survey, engineering, or locating verification.

QA/QC is part of the deliverable—not a hidden final step.

1

Source & authorization review

Identify the records approved for use, their revision/state, intended purpose, and known limitations.

2

Naming & schema standardization

Apply consistent asset IDs, folders, labels, attributes, and source references according to the scoped requirements.

3

Alignment, STA & sheet review

Check the agreed route/alignment framework, station references, drawing links, and control information used for the assignment.

4

Geometry & attribute checks

Review features for expected placement, duplicates, missing values, naming conflicts, and inconsistent attributes.

5

Cross-source reconciliation

Compare drawings, redlines, KMZ/KML, asset lists, reports, photos, and other authorized records for agreement or conflict.

6

Exceptions & revision control

Log unresolved uncertainty, client questions, decisions, superseded information, and controlled revision history.

Record-based validation.

GDRS can confirm whether the deliverable consistently reflects the authorized records and agreed reference framework used for the assignment.

  • Source record identified.
  • STA/sheet/asset relationships checked.
  • Naming and attributes reviewed.
  • Missing or conflicting information logged.
  • Revision history retained.

What it does not mean.

A clean deliverable does not convert record information into survey, locate, engineering, or owner acceptance authority.

  • Not a substitute for survey control.
  • Not a utility locate or SUE determination.
  • Not independent proof of field position.
  • Not an engineering review or stamp.
  • Not a guarantee of owner/prime acceptance.
Fiber Documentation Boundary

Documentation QA/QC is not technical fiber-test analysis.

Documentation QA/QC may include when scoped

  • Required field presence and source legibility.
  • Span, site, cable, fiber, direction, wavelength, file, and report identifier consistency.
  • Source-to-report cross-reference and file/folder counts.
  • Template population, naming, formatting, revision, and transmittal controls.
  • Missing, unreadable, duplicate, unmatched, unsupported, or conflicting-item flags.

Not included in the standard documentation service

  • Performing the field test or operating test equipment.
  • Determining whether the test method or equipment setup was correct.
  • Interpreting OTDR events or altering traces.
  • Establishing loss budgets, thresholds, or independent pass/fail determinations.
  • Certifying fiber performance or guaranteeing owner/carrier/customer acceptance.

See Splicer Documentation Workflow

Exception handling protects the usefulness of the record.

When two authorized sources disagree, the goal is not to choose whichever value looks cleaner. The conflict is documented and routed for resolution by the responsible party.

Illustrative QA/QC Record
ExceptionFeatureSource ASource BEX-004HH-012STA 120+00STA 120+18

Example only: a real project exception would include the applicable source references, review status, responsible party, resolution, and revision history.

Related GDRS Insight

Infrastructure field data validation

A detailed example of record-based correlation across photos, GPS/coordinates, KMZ/KML, redlines, asset IDs, and as-built records.

Read the Insight

Need a deliverable that shows what is known—and what still needs resolution?

Define the sources, required output, and acceptance path before production begins.

Request a Project Review