At some point on every envelope package, somebody asks for the drawings as CAD. What comes back is usually a PDF, because the PDF is the document of record — it is what was issued, reviewed, and permitted. So you convert it, the file opens with snappable lines and editable text, and the problem looks solved.
It is worth doing. It is also the most over-trusted step in a Florida submittal package, because a converted PDF looks finished and is not.

The short version
A conversion turns a PDF into editable linework. It does not turn it into verified geometry.
You get lines you can snap to and text you can retype. You do not get dimensions that tie to a real building, layers that carry the drafter’s intent, or any guarantee that the sheet you converted is the one that governs. The takeoff, the shop drawing, and the anchor layout a reviewer compares against the product approval still have to be checked — against the approval, against the design pressure, and against the sheet the file came from. Conversion shortens the drafting. It does not shorten the checking.
Two different things get called “a PDF”
The result depends almost entirely on what you started with.
- A vector PDF, exported from Revit or AutoCAD. The linework is already vector, so a converter maps it to drawing entities and the geometry comes back close to the original. What you still do not get is meaning: every line arrives as a line, and nothing in the file knows which ones are a frame, a sill, or a dimension extension.
- A raster PDF, a scan or a photographed print. There is no geometry to extract. Anything that comes out is traced from pixels — curves become polylines, thin lines disappear at low resolution, and hatch turns into noise.
Both produce a file that opens. Only one produces something you can measure with any confidence, and neither tells you what it is looking at.
Failure one: the scale you think you have
A drawing PDF has a page size in inches and a plotted scale — 1/8" = 1’-0", 3/16" = 1’-0". When a sheet is exported “fit to page” or “scale to fit”, that relationship is broken: the page still prints, but a frame on it no longer equals the building it describes.
A three percent shrink is invisible on screen. On a 40-foot elevation it is 14.4 inches — wider than most of the frames you are pricing. Nobody catches that in a thumbnail.
Test it before you measure anything: run a measurement between two dimension extension lines on a wall the architect dimensioned, and compare it to the string. If they disagree, the file is not to scale. Set the insert scale, then measure. And do not stretch the geometry until it agrees with the text — the linework is the artifact, the dimension string is only a claim about it.
Failure two: dimensions that were never in the file
A dimension string in a PDF is text sitting near two extension lines. It is not a measurement. The 12’-0" you read is a label someone typed; the lines behind it can measure 11’-10", and nothing in the file reconciles the two. A converter carries both across as independent objects — the number and the geometry arrive as strangers.
The practical consequence is that every dimension that matters is a second measurement job. Derive it from geometry, or take it from the schedule and the approval, but do not inherit a number because it was printed on a sheet. This is the same discipline that decides whether the schedule or the wall section wins a disagreement: the schedule is the source for sizes, the drawing is the source for conditions, and neither is a source for a dimension it never carried.
Notes have the same problem. “Verify in field,” “match existing,” “see structural” are instructions, and they survive conversion as words with nothing attached to them.
Failure three: which sheet actually governs
Revision clouds, delta triangles, addendum tags, “not used” marks — all annotation. Flatten a set into one file and they remain as lines, but they lose their relationship to the sheet and detail they were revising. An addendum sheet ends up looking exactly like its neighbours.
Convert only the sheets that govern, and name them by revision. A file called A-501 has no memory of having been revised twice, and the set you were handed often contains both the superseded sheet and its replacement — two nearly identical pages, one of which wins.
Failure four: layers that carried the intent
A drawing’s meaning lives in its layers: structural background, demolition, keynotes, hidden linework, dimensions, tags. A PDF has no layers in that sense, only a paint order and optional content groups. What survives depends on how the file was exported, not on how the drawing was built — and work that sat on an off layer is not in the PDF at all.
So a converted file can look complete and be missing exactly the background that would have told you there is a beam over the opening. That is not a defect in the conversion. It is a limit of the source document, and no amount of redrawing gets it back.
The two checks that still belong elsewhere
Neither of these lives in the CAD file, and neither is something a conversion can supply.
Is the assembly the approved one? A Florida product approval under Rule 61G20-3, F.A.C., approves a product or system for compliance with the structural requirements of the code — a specific tested assembly, with its size, configuration, and anchorage, not a product category. A Miami-Dade NOA and a state product approval are different documents covering different jurisdictions, and either one constrains what your redraw is allowed to show. Change the frame depth, the anchor pattern, or the substrate and you have drawn a deviation, neatly and in a clean file.
Does the drawing carry the right design pressure? Pressures come from the wind speed. Under FBC 8th Edition §1620.2, the HVHZ three-second-gust speeds are 165 / 175 / 186 / 195 mph in Miami-Dade and 156 / 170 / 180 / 185 in Broward, for Risk Categories I through IV. Design pressure scales with the square of the wind speed, so the Miami-Dade to Broward gap at RC II is only about 6%, while the RC III to RC IV step inside a single county is larger than most people assume. The 9th Edition, effective December 31, 2026, moves the basis to ASCE 7-22 — so a file converted today may be drawn to pressures the code stops asking for on the next permit.
When conversion is the right buy, and when it isn’t
Right: a vector PDF, a known revision, a handful of sheets, and geometry you need to edit rather than decorate. Redraw the sheet, then check it.
Wrong: a scan of a print, a set with no revision control, or an opening whose number will be used to order material. The rough opening is not in the NOA — and it is not in the converted PDF either, unless someone detailed it. If a dimension is going to be fabricated from, measure the building or buy the precision capture. A traced line is not a field measurement.
The habit that keeps it honest
Convert for editing, check for accuracy, and record where the file came from. The redraw should carry a note naming its source sheet and revision; without it, the next person in the chain treats a derived file as a primary document, and the error compounds one handoff at a time.
That note, and the check behind it, is what a redraw-and-check deliverable is for: the geometry comes back editable, and the comparison against the approval and the design pressure comes with it rather than three weeks later at plan review. What the team delivers around that is set out in what we do.