How to Evaluate an OSP Drafting Company Before You Award the Work

A procurement team awarded OSP drafting from a polished PDF sample. After the purchase order went out, the native file would not open in the receiving template, so production started against a package the owner's CAD environment could not use.

This article is a buyer method for testing that trail before an SOW. Apply it first to a sample package; a limited pilot is the next use if the sample holds. Follow one representative asset or route segment from source evidence through controlled output, then through comment closure and QA. Choosing a full OSP engineer is a separate award, as is the decision whether to outsource OSP drafting.

OSP Drafting Company Qualification Starts With Evidence

Evaluate an OSP drafting company with 7 Draftech buyer gates applied to one sample package. Those gates inspect source control and native CAD/GIS delivery, then revision history and QA evidence, then the construction issue and as-built readiness, before an SOW; they are Draftech method, scoped to the owner's requirements rather than a universal telecom code.

Name the stage you are buying before you compare firms. Permit drawings go to a reviewer who is not scoring construction-issue sheets. A conversion of legacy plant is a different workstream from a redline update. If the SOW folds a final record package into the same "drafting" label, two bidders can look comparable while answering different work.

The controlling owner requirements come next. Utility standards sit beside them. Agency submittal rules and the receiving system of record still have to be named, because a drawing that satisfies one reviewer can still fail the GIS load. We treat those instruments as project law. We do not invent a nationwide OSP drafting code to stand in for them.

For covered Rural Utilities Service telecommunications construction, 7 CFR 1753.7(a) describes plans and specifications as the contract form together with applicable RUS specifications. It also includes the additional documents needed for a clear, accurate, complete understanding of the construction. 7 CFR 1753.7(c) then says that where RUS has not prepared a standard, the borrower uses project-specific engineering requirements prepared by its engineer, subject to RUS review for major construction. That is a scoped RUS example.

Keep drafting production separate from professional and owner decisions. If the work requires sealed engineering or licensed survey certification, the contract must assign those duties to qualified professionals. A CAD audit can confirm file conformity, but it cannot grant a permit or accept the owner's record. A drafting company can be excellent at production and still be the wrong award when the SOW leaves required engineering unnamed.

Draftech performs engineering and design in-house; documentation is in-house as well, and when a program includes construction, that construction is full turnkey work delivered by Draftech-managed subcontract crews under Draftech management and QA/QC. We do not describe those crews as in-house construction, and we do not undersell the model as management-only.

Qualify the Inputs Before Judging the Drawing

An input register has to exist before you score linework. The register should identify source and issue or date, then owner and status; record intended use with any limitations, and keep unanswered questions in the same register. If those fields are missing, the drafter is guessing and the guess is being drawn as fact.

Identifiers still have to agree across the sources the bidder was given. Survey records and base maps often use different names for the same pole than utility records or design notes, and existing GIS can add another name. We want to see how the firm detects it. Silent renaming leaves the mismatch hidden.

Source conflicts need a raise path. A missing as-found height should stay missing until a decision owner fills it. A utility record that disagrees with a field note should stay in conflict until someone with authority picks the controlling source. The bidder should show 1 documented discrepancy with a decision owner and a disposition, then the resulting drawing state. If the sample package contains no conflict, pick a different sample.

FHWA's Guide for Digital As-Builts Using Simplified Digital Workflows, FHWA-HIF-24-062, July 2024, section "1. Develop Requirements," tells agencies to consider data users; intended use; collector; collection timing; verification process; format; accuracy; completeness. We use that list as an interview script for OSP drafting inputs, and the same guide's PDF page 22 states that its contents are non-binding except for cited law. Treat it as agency guidance rather than a telecom mandate.

Do not prescribe a universal source hierarchy. A county GIS layer may control a conversion job. A current survey is often the controlling source on a construction issue, while an owner plant record may control a redline update. The project decides precedence. The bidder's job is to make that precedence visible and to stop when it is not.

Put CAD and GIS Delivery Controls in the SOW

We treat the delivery package as 4 parts, each tied to a real handoff. Production needs native files that reopen in the adopted template, while reviewers need plots they can mark without a CAD license.

The receiving system adds a different test: its exchange file must preserve identifiers and geometry after import. Keep an archive copy that can be reopened later as the record. A single PDF can replace this package only when the contract says so and every receiving user has confirmed that it supports the intended work.

Owner-provided templates and data specifications belong in the SOW when one exists, and software and version constraints belong there only when the receiving environment actually imposes them. State CRS and units, then identifiers and required attributes; relationships and export behavior belong in the same specification. If the owner has no template, say that, and require the bidder to document a structure that stays stable from sample through production.

File presence on a share is only a drop, so the recipient environment still has to run an open/import test. The native sample has to open and the GIS export has to load, and identifiers have to survive. Geometry that looks right in the bidder's viewer can still fail a topology check after import.

CAD conformance and GIS validation answer different questions from engineering review. Autodesk's About CAD Standards describes associating a DWS file with drawings and checking named objects such as layers; text styles; linetypes; dimension styles; multileader styles. That is a product capability. Engineering content still needs a separate review. Esri's branch-versioning documentation describes reconcile identifying conflicts and posting moving resolved edits to the target version, and Esri's dirty-area documentation describes network edits not yet reflected in topology, cleared through validation when no error remains. Those ArcGIS controls are inspectable when ArcGIS is in scope. Other GIS stacks need their own.

Esri's Identify data quality requirements page separates completeness; logical consistency; spatial accuracy; thematic accuracy; temporal quality; usability. We use that split so a buyer does not ask for one unsupported "accuracy score." Test the dimensions the receiving use actually needs.

Once those recipient-system and native-output requirements are written, Draftech's telecom CAD and GIS design services can produce the controlled files against that same SOW. The service is the production path after the buyer's gates are defined.

Use Seven Qualification Gates on Sample Evidence

The matrix below is Draftech company guidance for qualifying an OSP drafting company. It is company method rather than law or an industry standard, and it is unweighted. A failed gate leads to clarification before a controlled pilot or a hold. The same miss does not automatically prove the firm is unqualified for every other job.

Use 1 representative sample that contains at least one source discrepancy and one CAD/GIS exchange. Fold in one review comment and one handoff condition. Take acceptance criteria from the owner's actual requirements. Do not grade the sample against a Draftech layer schema, color system, CRS, or filename convention that the contract never adopted.

We read the table as a preview of the evidence trail rather than a vendor scorecard. If a gate is unclear, ask for the missing artifact before you expand volume.

Audit Revision Traceability and Reproducible QA

A tidy filename only proves naming discipline. The useful trail records why geometry moved and who had authority to move it. Engineering controls design revisions; an agency permit comment can require a response, but it does not rewrite owner intent by itself.

Owner comments and field RFIs arrive through different workflows, and neither should alter the drawing until the responsible authority accepts a change. The same rule applies to field redlines: they become as-built updates only after acceptance. Mixing all of these events under one "rev C" stamp hides the decision that actually moved the geometry.

Demonstrate forward tracing and reverse tracing on the sample. Forward tracing starts at a comment and should point to the changed object or sheet; it should name the disposition and the reviewer and record the resulting issue and any unresolved exception. Reverse tracing starts at an issued sheet and should point back to the comment or change that created it. If either direction breaks, the register is only a log of files.

Superseded issues must remain recoverable without appearing current. A field user who can open last week's sheet as if it were released is working from the wrong instruction. Keep the prior issue and mark it superseded.

For covered RUS outside-plant major construction by contract, 7 CFR 1753.47(a)(2) and (b) describe plans and specifications that identify applicable construction specifications. Those documents include the contract; specified supporting standards; special assembly-unit descriptions or guide drawings where used; key maps; detail maps; cable-layout maps. 7 CFR 1753.49(b) and (c) then describe closeout documents that can include final inventory documents; change-order listings; acceptance-test results; final staking sheets; correction summaries; final maps where applicable, with final inspection and engineer review of closeout documentation. Use that only as a scoped RUS closeout trail.

QA/QC evidence has to be reproducible by another reviewer. CAD presentation checks are not GIS or data checks, and cross-format reconciliation is still not engineering review. A requirement-to-check map has to name reviewer identity and role. Findings and dispositions belong on that map, with rerun evidence and a named release state. "Second drafter review" is a staffing note, and it still does not replace the map.

Automated checks are useful within their limits. A DWS audit can expose a layer violation, and Utility Network validation can clear a dirty area; neither tells the team whether an easement was interpreted correctly or a collected attribute matches installed plant. Run the machine checks, then leave content judgment with the field and engineering reviewers who own it.

One limitation in our own sample-package reviews is that a native file can still look complete while the receiving import has not been run on the owner's system. That is a weakness we watch for. Name, before the pilot starts, the person who may convert a field redline into an engineering change. If that seat is blank, the redline has no lawful path into the drawing.

Implementation detail for layer naming and CRS discipline, with version control, lives in our CAD/GIS documentation controls. This article asks whether the bidder can implement the owner's adopted controls. It leaves schema choice to that owner.

Write OSP Drafting Company Release Authority Into the Award SOW

The award decision belongs in the SOW. We start with a named owner for each receiving environment, because the team must know which record controls each deliverable. Changes to engineering intent still require the assigned authority, usually the engineer of record unless the contract says otherwise, and nothing leaves the drafting desk without an authorized release.

The contract also needs a practical route around silence or conflict. Name the person who takes an exception when the first reviewer is unavailable. At closeout, the data-handback clause should identify the required formats, the retention window and the person who confirms custody of the current native and GIS record.

If any of that responsibility is left to "the team" or postponed until kickoff, the award is not ready.

A drafting transmittal can close while agency closeout is still unfinished, and owner operational acceptance can wait on operations after both. FHWA-HIF-24-062 section 7 Record Changes covers recording deviations and reconciling questions with designers or asset stewards. Section 8 Close Out Project covers reviewing and confirming markups and asset-data submissions before acceptance. Section 9 Post-Processing addresses handoff to operations, where further quality checks may follow before teams add attribution and integrate the records into their systems of record. Use that guide as a responsibility script. It is non-binding except where it cites law.

ASCE describes 75-22 as addressing useful forward records of utility location and attributes for newly installed or relocated facilities. Adopt it when the project adopts it. Do not treat it as mandatory because a proposal mentioned it.

The execution workflow for route drawings and materials lives in our OSP construction-handoff documentation. Permits and GIS are in that same workflow, and RFIs and redlines sit there too, with release status. Here the question is narrower: is that path already contract text, or is it still a kickoff topic?

Stop comparing binders once the sample proves the workflow. The next decision is a signed SOW that turns the accepted controls into contract text before volume production begins.

Active in 24 states. Available across all 50 U.S. states. Engineering stays in-house. Where a program includes full turnkey construction, Draftech delivers it through Draftech-managed subcontract crews under Draftech QA/QC and safety oversight.

A drafting sample is one way to judge a firm. A permitted package is a better one. Draftech engineers the first 20,000 linear feet of a qualifying route at no cost, through permit drawings and agency approval, so a buyer can compare a real issued set against the binder before awarding anything. The free design request page lists what that package contains.