Why the PDF is the format that actually matters
Clients don't open drawing files — they open PDFs. A PDF renders identically on a phone, a laptop, and a printout, attaches cleanly to email and quotes, and reads as a finished document rather than a work file. Whatever tool a drawing gets built in, the exported PDF is the actual deliverable a client interacts with.
That means the PDF deserves the last five minutes of attention before it goes out: a complete title block, readable labels at the size a client will actually view it, and dimensions on everything the client is paying for. See construction proposal template for how the PDF fits into the overall bid package.
Prepare the sheet before exporting
Fill in the title block completely — project name, client name, your company, date, and scale. In SiteBuildHub Draft, the title block sits on every sheet automatically once your company name is set in settings, so it appears on every drawing without re-entering it.
Then sweep the drawing: every feature the quote prices should be labeled, every critical distance dimensioned, and anything ambiguous annotated directly on the sheet. The client should be able to understand the drawing without a follow-up phone call.
- Complete title block: project, client, company, date, scale
- Labels on every priced feature
- Dimensions on the measurements that drive cost
- A note flagging anything that still needs on-site verification
- Consistent drawing name matching the quote
Export the PDF
In SiteBuildHub Draft, the PDF export opens a clean print view of the sheet — border, title block, and disclaimer included — and "Save as PDF" in the browser's print dialog completes the export. Landscape orientation is pre-set to fit most drawings. The PNG export works the same way when an image is needed to embed inside a proposal document instead.
Name the file like a professional document: "Smith-Residence-Deck-Plan-2026-06-29.pdf" beats "drawing(3).pdf" in every inbox, and it makes the file findable months later when a related question comes up.
- 1
Complete the title block
Project, client, company, date, and scale filled in before export.
- 2
Sweep the drawing for labels and dimensions
Every priced feature labeled, every critical distance dimensioned.
- 3
Export as PDF
Clean print view with border and title block, saved through the browser's print dialog.
- 4
Name the file professionally
Project and date in the filename, not a generic "drawing(3).pdf".
- 5
Send with a specific request
Reference the drawing directly in the message and ask for confirmation on one specific detail.
Keep the record straight: saved drawing vs. sent PDF
Keep the exported PDF in the job folder alongside the saved, editable drawing — see how to organize construction drawings for your crew for the naming and version-control system this depends on. The saved drawing is for revisions; the PDF is the record of exactly what was sent and approved on a specific date. If the client requests a change after reviewing the PDF, update the saved drawing, export a new revision, and get fresh approval on that version — don't edit the sent PDF's underlying drawing and assume the earlier approval still applies.
This distinction matters most when a scope question comes up weeks or months later. A dated, revision-numbered PDF that the client explicitly approved settles a "but I thought that included X" conversation far faster than a memory of what was discussed. Attach the exported PDF directly to a construction proposal so the drawing and the written scope stay connected.
Common mistakes
- Sending a drawing without a complete title block, making it hard to identify later
- Attaching the PDF with no context in the message, so it gets skimmed instead of reviewed
- Editing the underlying drawing after a client approved a specific PDF, without version-tracking the change
- Exporting at a resolution or orientation that's hard to read on a phone screen