PDF Takeoff Worked Example: Scale, Area, Length, and Count

Open the PolyPDF Quick Start sample and go to sheet Q-101, a 24-by-18-inch office fit-out plan. The capture for this guide records four kinds of evidence on one page: a known calibration, gross floor area, two wall dimensions, and repeated diffuser symbols. It is a teaching fixture rather than a bid document, so use the workflow—not its quantities—as the template for your project.

• Area question: what is the traced gross floor area?
• Length question: what wall runs were measured?
• Count question: how many visual matches are present, and which of them belong to the plan quantity?
• Output question: can a reviewer see the items, totals, formula, pages, subject, and status before export?

The Q-101 sample includes a green reference line that is exactly 240 PDF points long and represents 20 feet. In Measurements › Scale, choose Calibrate by Drawing Line, trace that reference, and enter 20 feet as the known distance. PolyPDF saves the calibration for this page.

Before adding quantities, draw a temporary measurement over a different labeled span. A second check is what catches a wrong endpoint, a mistyped distance, or an incorrect unit. For a scanned plan, also compare a reference in the other direction because a single proportional scale cannot correct unequal horizontal and vertical stretch.

The scale shown in this sample is intentionally simple for onboarding. A real plan may use an architectural, engineering, or metric preset, or require calibration from its own known dimension.

Choose Area and click around the floor boundary, using enough vertices to follow the intended face. Close the polygon at the starting point. The live Q-101 capture shows a gross floor-area measurement of 5,485 square feet. That number describes the traced sample geometry; it is not an estimate of usable, rentable, finish, or code area unless your boundary definition makes it one.

1. Name the area’s Subject so its worksheet row explains what the polygon represents.
2. Inspect the boundary at corners and openings. Add area cutouts when a void must be excluded rather than mentally subtracting it later.
3. Use Line Measurement, Dimension, Path Length, or Perimeter according to the quantity. An open run and a closed perimeter answer different questions.
4. Give unlike assemblies distinct Subjects. A wall, curb, cable tray, and pipe should not collapse into one length total merely because they share units.
5. Use Status to distinguish accepted work from an item that still needs checking before export.

The capture shows two wall dimensions as visual examples. Their value is not that there are exactly two; it is that each measurement remains an identifiable record that can be selected from the page or reviewed in the worksheet.

For repeated symbols, open Symbol Search, draw a box tightly around one clean example, run the search, and review the candidates before accepting them as counts. The Q-101 capture shows 17 visual matches: 16 diffuser symbols in the plan plus one matching legend example. Exclude that legend match to reach the 16-item plan quantity, then check for partial symbols, similar-looking devices, and objects hidden by markup.

1. Choose a representative symbol with clear linework and little surrounding text.
2. Keep the query box tight enough to describe the symbol, but include the features that distinguish it from nearby objects.
3. Review each candidate overlay rather than treating the match count as an unquestionable total.
4. Accept the reviewed matches so they become ordinary count records on the document.
5. Set the Subject to the actual item, such as Supply Diffuser, instead of leaving unlike count series ambiguous.

Symbol Search auto-count is uncapped in Free. The separate Free limit is three hand-created measurements per document, so a user can test calibration, area or length, and a real auto-count workflow without a paid license.

Open Measurements › Records after placing the quantities. PolyPDF builds worksheet rows from the measurements and counts in the document. Rows keep distinct workspace or space assignment, Subject, Status, quantity kind, unit, and count series separate so unlike work does not become one unexplained number.

Select suspicious rows and return to the page before exporting. The worksheet is a review surface, not a replacement for understanding what each traced boundary or accepted match represents.

Use CSV when the next step is spreadsheet estimating, filtering, or joining quantities to a cost database. Use the PDF summary when a person needs a fixed, readable handoff. PolyPDF exports the current worksheet; it does not certify that the source drawing, scale, boundaries, subjects, or accepted Symbol Search matches were correct.

• Keep the source PDF revision with the export so a reviewer knows which drawing produced the quantities.
• Record assumptions such as gross versus net area, centerline versus face-of-wall length, and whether cutouts were included.
• Spot-check at least one row of each quantity kind against the annotated page.
• After a drawing revision, rerun the affected takeoff rather than silently carrying forward values from the old geometry.

This example demonstrates the software workflow, not a professional estimate or bid. The person preparing the takeoff remains responsible for source documents, scope interpretation, waste factors, assemblies, pricing, and review.