# Fiber Documentation Vendor Qualifications: How to Verify Control Before Award **Title tag:** Fiber Documentation Vendor Qualifications: 8 Tests 2026 **Meta description:** Fiber documentation vendor qualifications: test evidence lineage, stable asset IDs, native files, QA/QC, change control, security, and closeout readiness. **Author:** Devin Martinez **Published:** September 10, 2026 **Last updated:** September 10, 2026 **Category:** As-Built & Documentation **URL:** https://draftech.com/blog/fiber-documentation-vendor-qualifications **Primary keyword:** fiber documentation vendor qualifications **Word count:** 3100 **Read time:** 12 minutes ![Two utility field professionals document a damp sidewalk corridor beside a closed handhole.](../../blog/img_fiber_documentation_vendor_qualifications.webp) --- A documentation vendor drops a 48-page PDF on the table, every sheet labeled FINAL. The GIS screenshot looks finished. When the owner asks the vendor to open the native drawing for 1 splice closure and name the field observation that supports the fiber count, the room goes quiet. This article is a pre-award proof test. ISP staff can run it. Electric cooperatives and telephone cooperatives apply the same method under their own systems, joined by municipal owners and grant-funded network owners along with EPCs and primes. If the work is private, one extra instrument may apply. A municipal charter or a federally assisted award can apply a different one. BEAD work follows the executed subgrant, whereas RUS-financed work follows the applicable RUS contract. ## Fiber Documentation Vendor Qualifications Mean Reproducible Control Fiber documentation vendor qualifications are the pre-award proof that a candidate can reproduce 1 installed-network claim from source evidence through a stable asset identifier. The chain also needs an editable native record and a documented QA disposition. Add a controlled revision identity and an acceptance-ready release package. Run that on 1 owner-defined sample. Technical capability answers whether the vendor can produce the record at all. Project fit is narrower, because the method has to match the owner's systems and schema, and the access rules and schedule have to survive those systems. Procurement sits outside both of those tests, because the buyer still has to award under its own rules. Final deliverable acceptance remains a later owner act. No universal fiber documentation vendor certification turned up in the federal materials we reviewed. MBE status is a company credential when it applies, and PE licensure is a professional credential when the jurisdiction and the sealed document actually require it. A contract can name a software badge or a SOC 2 report. ISO 27001 and FedRAMP work the same way when the owner requires them. A PE seal leaves field accuracy unproven unless the sealed document actually covers those facts. The 8 tests below are Draftech's owner-side buying framework rather than a law or a standard, and they are not a certification scheme or a federal checklist, so a vendor can pass every test we describe and still lose a procurement because insurance or bonding sits outside the record process. One thing I have always found too easy to over-weight is a software logo slide that never opens a native file. We refuse to treat the logo as lineage. ## Build the Qualification From Intended Use Start with the owner's system of record. Write the users and the asset classes on the same sheet as the security constraints and the acceptance authority, because if those 4 items are blank every bidder is guessing and the sample then proves a vendor's house style instead of the owner's future use. Name who supplies field evidence and who may approve changes, then name who accepts the final baseline. A vendor cannot invent the owner's authority. FHWA-HIF-24-062, Guide for Digital As-Builts Using Simplified Digital Workflows (July 2024), is nonbinding transportation guidance. It asks agencies to identify data users and intended uses, then collection responsibility and a verification process. Those are sound questions for a telecom procurement. They are not FHWA mandates on an ISP. FHWA-HIF-24-098 (November 2024) makes the same transportation-agency point. Use the intended-use list to decide what the sample must prove. If operations will import the GIS, the sample must survive that import, and if construction closeout needs native CAD, the sample must open without the vendor's private environment. Leave GIS field lists to the owner's schema, and leave coordinate systems and positional tolerance there too. For the installed-record inventory itself, use [what fiber as-built drawings should include](/blog/fiber-as-built-drawings-what-to-include). That page owns the families, and this page only asks whether the vendor can control them before award. ## Run a Controlled Sample, Then Apply Eight Proof Tests Where procurement rules permit it, run a paid pilot or a clearly bounded proposal sample. Give every candidate the same issued source data, then the same field observation or change, under the same owner naming and schema rules, and require the same expected outputs and the same security channel. Ask the same acceptance questions, then compare the returns. Require each candidate to return the artifacts below. - **Source register:** observation date, collector or method, affected asset, supporting authority. - **Native files:** the actual working CAD or GIS files, plus database or test files and stated dependencies. - **Reviewable output:** the sheet or export an owner reviewer can mark without the vendor present. - **QA record:** who checked it, what failed, who corrected it, who rechecked it. - **Change disposition:** observed fact, authorized change, entered value, unresolved exception. - **Release manifest:** requirements mapped to evidence, plus exceptions the vendor cannot close. Buyers must not ask vendors to reveal another client's confidential records. A redacted method sample is useful, but another owner's route geometry is not. For federally assisted procurement, apply the buyer's documented process and conflict rules. 2 CFR 200.318 applies to recipients and subrecipients purchasing under a federal award. It does not govern every private purchase. Where it applies, the recipient or subrecipient must use documented procedures and oversee contractors. Conflicts have to be addressed and responsible contractors have to be selected, and procurement-history records have to be retained. > **Sample boundary.** Do not qualify a documentation vendor by asking it to open another client's plant. The sample uses owner-issued data. That is the whole point. We use the table below as Draftech selection guidance rather than a federal form. Blocking conditions are owner-defined, because we do not assign industry weights or pass percentages, and we do not assign sampling rates or maturity levels. Bidirectional traceability is the test. **Table: Eight Draftech proof tests for fiber documentation vendor qualifications** | Proof test | What the buyer asks the vendor to demonstrate | Evidence to inspect | Fail or escalation signal | | --- | --- | --- | --- | | Evidence lineage | Trace 1 installed-network claim back to the field observation that supports it. An approved design or change and a test record are valid sources too | Source register with date and collector or method, plus the affected asset and disposition | No identified source or authority | | Stable asset IDs | Follow 1 pole or structure across every applicable record. A cable segment and a closure use the same ID. A fiber path and a terminal do too | Callouts and GIS objects, plus the photo index and splice records. Include test or change files | Matching depends on filenames or sheet position | | Native/source files | Open and edit the working files without the vendor's private environment, then export and re-import them | Native CAD or GIS files plus database or test files and stated dependencies | PDFs or flattened exports only | | QA/QC | Show who checks completeness and technical relationships, then close 1 defect through an independent recheck | Checklist and marked sample, plus correction evidence and an independent recheck | No marked review or disposition | | Version control | Identify the exact candidate reviewed and what changed. Identify who approved it and which revision now governs | Revision history and transmittal, plus the controlled release identifier | Same-name overwrites, or approvals not tied to exact bytes | | Security and access | Explain least-necessary access plus sharing and storage. Cover incident handling and backup or recovery, and cover offboarding | Access matrix and authentication method, plus subcontractor access and the return or deletion procedure | Shared credentials or public links. No exit plan | | Change handling | Process 1 authorized field change and show every dependent drawing and object. Show the affected schedule and path, and the evidence link | Change record and impact map, plus updated outputs and unresolved exceptions | Silent choice between conflicting sources, or only the visible drawing updates | | Acceptance and closeout readiness | Assemble a frozen sample release against the owner's stated requirements and explain every exception | Requirements matrix and native plus reviewable files, plus the exception register and receiving-system test | Folder completeness treated as acceptance | Once a vendor can show that chain, [test as-built accuracy before release](/blog/how-to-ensure-as-built-accuracy-in-fiber-projects) owns the six-test accuracy method, so we will not reteach those tests here. Ask the vendor to demonstrate them on the sample, because capability to run an accuracy method is a qualification question and the later release decision still belongs to the owner. One limitation of our preferred sample exercise is that a well-rehearsed vendor can overfit the sample and still fail a later route. We still run it. A portfolio cannot show lineage. We do not recommend awarding documentation work on a PDF demo alone. ## Prove Access Control and Change Handling Name who can open route geometry and structure details, then keep fiber-path access on a separate named-user list. Customer data requires named users, and location data plus credentials sit under that same rule. A SOC 2 report stays optional unless the owner or the contract requires it, and ISO 27001 is optional on those same terms, as is FedRAMP. Authentication and secure transfer have to be covered in that access plan, and subcontractor access belongs in the same conversation as backups and incident notification. Return or deletion at the end of the engagement is the exit half, and audit logs are useful where they exist. They are not a universal federal requirement. Where 2 CFR 200.303 applies, recipients and subrecipients must establish and document effective internal control over a federal award and maintain it. 2 CFR 200.303(e) requires applicable recipients and subrecipients to take reasonable cybersecurity and other measures to safeguard PII and any agency or pass-through-designated sensitive data. That duty sits on the award, not on every private ISP contract. NIST CSF 2.0 (NIST CSWP 29, February 26, 2024) provides adaptable outcomes for supplier risk; the abstract (printed p. i) and the body on printed page 1 both state that the CSF does not prescribe how outcomes must be achieved. That statement is not a mandatory vendor certification. ### Make the Vendor Move One Authorized Change Give the vendor 1 reroute or an identifier correction; a splice change or a conflicting source can serve as the prompt. Observed fact, authorized change, entered value, and unresolved exception must remain four distinct states. If the vendor collapses those 4 states into a single new drawing, the change was not controlled. The vendor must identify all dependent outputs before editing, because an update to only the visible sheet leaves the other records stale. Preserve the prior accepted or reviewed revision, and do not overwrite it under the same filename. An exception is required when authority or evidence is insufficient, and the newest timestamp should not automatically control. Stable IDs must survive drawings and GIS, and splice evidence and test evidence have to keep those same IDs. FOA Standard for Installing Fiber Optic Cable Plants, 2025 Version 1, Section 13.1, supports documenting routes and GIS locations with exact fiber paths, while contract and owner requirements still decide mandatory fields and tests. We will not convert that section into a nationwide OTDR .sor rule. If the native files stay trapped in a hosted environment the owner cannot enter, the sample already failed native-file control. > **Exit test.** If former users still hold access, or if the owner cannot open the native files without the vendor, do not award on the drawings. ## Check Acceptance Readiness Without Taking the Owner's Signature Ask for a frozen release candidate and a requirements-to-evidence manifest with native or source files and reviewable exports. Name dependencies and revision identity, plus exceptions and receiving-system results. A vendor that cannot freeze a sample cannot freeze a route. Folder completeness is not the test. Import success proves neither technical acceptance nor contractual acceptance. Successful delivery proves receipt or technical processing only, unless the governing procedure expressly makes that event the acceptance. The [ISP as-built acceptance decision](/blog/fiber-as-built-deliverables-for-isps) owns that later call. This page only asks whether the bidder appears capable of producing such a package, so the sample is a capability demonstration rather than closeout. When an independent documentation workstream is the right buy, [fiber as-built documentation services](/services/as-built-documentation) is the Draftech path. Engineering and design stay in-house, and record-document work stays in-house. Construction, when included, stays full turnkey through Draftech-managed subcontract crews under Draftech QA/QC and safety oversight. We remain a single point of accountability for the work we take, and we do not take an owner approval the contract assigned elsewhere. For RUS Form 515 outside-plant work, 7 CFR 1753.49 identifies scoped closeout records. The list includes final inventories and change orders, plus acceptance-test reports and final staking sheets, with correction summaries and maps on that list too. Keep that list off private projects and non-RUS projects. 7 CFR 1753.18 addresses engineer and architect contract closeout certifications for scoped RUS major construction, and that certification is not a generic documentation-vendor credential. NTIA's BEAD Final Proposal Guidance for Eligible Entities, Version 2.1 (July 18, 2025), addresses Eligible Entity retention of subgrantee records, including submitted network designs and diagrams. That is Eligible Entity Final Proposal guidance, not a universal private-project closeout specification. ## Choose the Documentation Vendor Decision by Buyer Type Select the vendor against the owner's systems and the controlling instrument, and keep the 8 Draftech proof tests while changing which tests block the award. Before award, write custody transfer and access revocation into the contract, including credential return. The clause must confirm that retained records stay retained and that deleted records are actually gone, and it must name the person authorized to accept the final handback. An unsigned exit is not an exit. **ISP or co-op:** prioritize operations-system compatibility and path identity, then native-file custody and vendor-exit test. If the NOC cannot retrieve a fiber path without calling the original collector, the hire already failed even if the drawings look complete. **Municipality or public owner:** procurement-history retention sits apart from records-access rules, and public-sector security is a different public-owner test. Name an acceptance authority for the handback. **EPC or prime:** Interface ownership and subcontractor access have to be tested, along with change turnaround and upstream or downstream transmittals. Subcontractor credentials must die when the prime's access dies. **Grant-funded owner:** map the exit terms to the executed award or subaward and to pass-through instructions, because national BEAD documents reviewed do not create 1 documentation-vendor credential or 1 national fiber as-built schema. NTIA's BEAD Restructuring Policy Notice (June 6, 2025) removes specified non-statutory NOFO obligations and prohibits Eligible Entities from reimposing removed obligations as BEAD requirements. Read the executed subgrant. **RUS borrower:** use the applicable RUS contract and closeout provisions; a generic co-op checklist does not replace them. Form 515 closeout records apply when the financing and the contract, together with the construction method, bring 7 CFR 1753.49 into scope. ### Fiber Documentation Vendor Qualifications Scope Guards 2 CFR Part 200 obligations apply to recipients and subrecipients and to covered federal-award procurement; they do not apply universally to private projects. Where 2 CFR 200.334 applies, the general retention clock runs 3 years from submission of the recipient's or subrecipient's final financial report, subject to the stated exceptions. That clock is not 3 years after project completion. 2 CFR 200.337 gives identified federal and pass-through authorities access to pertinent records for as long as those records are retained. FHWA examples remain nonbinding transportation guidance, and RUS records apply only within the relevant RUS financing and contract, with the construction method that brings them into scope. The sources above do not create a hash requirement or a two-reviewer QA rule, and they do not create a sampling rate or a universal native-file format. Active in 22 states. Available across all 50 U.S. states. Draftech's in-house engineering and documentation team can assess evidence gaps, and we can write the exit terms into an owner-reviewable as-built workstream. Construction stays full turnkey through [Draftech-managed subcontract crews](/vendors) with applicable management and QA/QC oversight. Engineering stays 100% in-house. **Name the handback before you trust the vendor.** Send [Draftech](mailto:info@draftech.com) the custody-transfer terms, including access revocation and credential return, plus how retention or deletion will be confirmed and who is authorized to accept the handback. That is the clause that survives the drawings. > **Set the documentation exit terms before you award the record.** ## Frequently Asked Questions ### What qualifications should a fiber documentation vendor have? Look for demonstrated control of the 8 Draftech proof tests, covering evidence lineage and stable asset identifiers plus editable native files and QA/QC findings. Revisions and access sit in that same set, and field changes plus acceptance-ready releases complete it. Platform experience and similar-project samples matter. No universal federal fiber documentation vendor certification was found in the guidance reviewed, and credentials follow the contract and the named funding instrument. ### Should a vendor provide native CAD, GIS, and test files? Require native or source files when later editing or validation depends on them, including system import and contractual closeout. Define exact formats and versions in the SOW, including dependencies and schemas plus reference files and ownership. A PDF may preserve a reviewed view, but it does not replace editable data or raw test evidence when those artifacts are required. Name the 1 receiving system that opens the files. ### How can an owner test evidence lineage before hiring a vendor? Give each candidate the same representative field observation and design baseline, plus the same approved change and the same owner rules. Ask the vendor to produce 1 controlled record and trace it in both directions, from the final object to its source and from the source back to every affected object and drawing. Include the schedule and the photograph with the test and disposition. ### Do BEAD projects require a specific documentation vendor certification? The national BEAD documents reviewed do not establish a universal documentation-vendor certification or 1 national fiber as-built schema. BEAD buyers must use the current NTIA terms and their Eligible Entity's approved program, with the executed subgrant agreement and current reporting instructions sitting with those terms. A GIS rule or photo rule from 1 state does not become a nationwide requirement. The executed subgrant still controls. ### Who accepts a documentation vendor's final package? The authority named by the contract or owner procedure accepts it, and a subgrant or applicable agency process can name that authority instead. A vendor can recommend release and provide QA evidence, but it cannot grant owner acceptance to itself. Agency acceptance stays outside the vendor's reach, as do lender and program acceptance. Successful delivery or GIS import proves receipt only, unless 1 governing procedure makes that event the acceptance.