A useful PDF plan review checklist for iPad field work has five checks: confirm the issued plan set, select the active sheet, confirm that page's scale before measuring, pin the observation to its location, and inspect the outgoing handoff. It is a review routine, not a permit or code-compliance checklist. The goal is to make sure the next person can recover the same sheet, condition, and decision from the local PDF.
That distinction matters on site. A screenshot or a marked-up crop can answer a quick question, but it often drops the revision, nearby detail, page scale, and context needed to act. Start with the issued PDF in Files, then give every note and measurement a recoverable place in the plan set.

The five-check PDF plan review checklist
Use this short sequence when the job is to inspect a condition, resolve a question, or leave a clear field observation. If your team has a contract, safety, or jurisdiction-specific review procedure, keep using it; this checklist only governs how the active PDF plan is handled on iPad.
| Check | What to verify | Why it matters before you continue |
|---|---|---|
| 1. Source | Filename, issue or revision, and full page set | Avoids reviewing an old attachment or a detached page |
| 2. Sheet | The plan, detail, section, or schedule that carries the question | Keeps the observation on the page another reviewer will open |
| 3. Scale | A known dimension and page-specific calibration when measurement matters | A readable PDF is not automatically a measurable plan |
| 4. Evidence | A direct note, markup, and only the photo or measurement that clarifies it | Turns a vague field memory into a located observation |
| 5. Handoff | The reviewed export opened once as the recipient will receive it | Catches missing pages, unclear cues, or a note without context |
Search results for “plan review checklist” mostly lead to permit-submission and code-compliance forms. Those are important for their own purpose. For a field reviewer with an issued PDF already in hand, the missing step is usually the connection between the current sheet, the real condition, and a readable result. That is the narrow workflow this checklist covers.
1. Confirm the local PDF is the issued source
Open the PDF from the shared location your team trusts, then check the filename, issue date or revision convention, and page count. Apple's Files guide for iPad is a useful baseline for locating and previewing a local document. The practical plan-review rule is simpler: do not start from a crop in chat if the question depends on the wider set.
Before walking the site, ask:
- Is this the current issued set, not a saved individual page?
- Does the set include the plan, detail, section, or schedule likely to answer the question?
- Can you name the revision rule that tells you this is the right issue?
If you are comparing a field condition with a plan, that first check is part of the evidence. A perfectly placed note is still unhelpful if it lives on an obsolete or incomplete file.

2. Name the active sheet before you mark it up
A floor plan, enlargement, reflected ceiling plan, and detail can all be relevant to one condition. They are not interchangeable. Read enough of the sheet number and title block to identify the page, then follow any reference that changes the answer before placing the observation.
For multipage sets, use the page that best locates the condition as the home for the note. If a detail provides the instruction but the floor plan identifies the room, say that in the note rather than forcing both ideas into a detached screenshot. Reviewing a multipage construction plan set on iPad covers the page-to-page routine in more depth.
This is also where a local plan-review tool earns its place. In PlanInspect, each page of a multipage PDF is a reviewable sheet, so you can return to the relevant page when an observation, markup, or measurement needs context instead of treating the PDF as a stack of unrelated images.
3. Confirm page scale before relying on a measurement
Only measure when the decision needs a measurement. When it does, scale confirmation comes before the ruler. Autodesk's calibration guidance makes the same foundational point: establish scale from a known distance on the sheet before measuring.
Use this compact scale check on the active PDF page:
- Choose a labeled distance you can independently trust on that page.
- Enter the issued ratio only when it applies to the PDF page, or calibrate between two points on the known distance.
- Check a second known dimension before relying on the result.
- Repeat the process on a different sheet when its scale differs.
In PlanInspect, scale is stored per PDF page, and distance or area measurements follow only after that scale is confirmed. Supported vector strokes can assist with point placement; a scanned PDF can still be reviewed and calibrated, but it does not supply vector paths to snap to. For the full scale-first method, read how to calibrate a PDF plan on iPad or how to measure a PDF plan on iPad.
4. Record one clear observation at the location
Apple's Preview and Markup tools are useful for ordinary PDF annotation. A plan review often needs more discipline than simply drawing a circle: the reviewer needs to make clear where the condition is, what was observed, and which evidence makes the statement understandable.
Use a note that can stand on its own:
- Identify the plan location in plain language when the page may be revisited later.
- State the observed condition, not a guess about its cause.
- Add a focused markup that points to the exact place.
- Attach a photo only when it makes the condition easier to verify.
- Keep a calibrated measurement with the note only if that measurement changes the review decision.
PlanInspect supports notes, photos, pen, highlighter, text, and markups on local PDFs. It is not a replacement for full CAD editing, PDF OCR or text search, automatic revision comparison, PDF optional-content layers, locked-PDF support, takeoff counts, volumes, spreadsheets, or live collaboration. That boundary keeps this workflow focused on a plan-aware review and a deliberate handoff.

5. Open the exported handoff before you share it
The review is not complete when the markup is placed. It is complete when the recipient can open the result and understand the source, sheet, location, and requested next step without calling back for a screenshot.
Before sharing, open the exported PDF or report once and check:
- The source page is visible under the review overlay.
- The note and marker still point to the intended location.
- Any supporting photo or measurement is present and legible.
- The recipient can tell which plan issue and page the observation belongs to.
PlanInspect can export reviewed multipage PDFs while preserving the source PDF page beneath the review overlays. If you are choosing a broader local workflow for an issued set, start with the PlanInspect PDF plan viewer. If your team needs a format decision first, the plan viewer explains when the active source should remain a PDF and when the original DWG context matters more.

A practical first-run test on site
Try the checklist with one live, low-risk question before standardizing a team workflow. Open the current PDF locally, name the active sheet, confirm the scale only if you need a measurement, add one precise observation, then inspect the exported handoff. That test reveals whether the iPad workflow preserves context from first open to final share.
For a local PDF plan review on iPad, PlanInspect brings those steps together without a required account or cloud conversion: open the issued plan, review it page by page, confirm scale, annotate the condition, and export the result when it is ready to leave the site.
