The clearest construction field report starts on the plan, not in a disconnected list of photos and comments. Open the current DWG drawing or issued PDF plan, confirm the active layout or page, pin each observation where it belongs, attach only the evidence that changes the decision, and check the export as the recipient will see it. That sequence keeps the location, condition, and requested next action together.
It also makes a useful boundary clear: a marked-up plan is a review artifact, not a change to the CAD source or a replacement for a controlled revision process. Use annotations to communicate what you observed. Let the project’s approved design and document-control workflow decide what changes next.
The short workflow: source, location, evidence, action, output
Use this five-part test before calling an annotated plan or report ready to share:
| Part | What to capture | Why it matters to the recipient |
|---|---|---|
| Source | Project, revision, DWG layout or PDF page | Prevents a polished comment from being attached to the wrong plan |
| Location | One identifiable point, room, grid, detail, or sheet area | Lets another person find the condition without a phone call |
| Evidence | A concise observation, useful photo, measurement, or markup | Shows what was seen instead of asking readers to infer it |
| Action | Verify, repair, clarify, approve, or monitor | Turns a redline into a decision someone can own |
| Output | A marked plan, image, or report that opens correctly | Makes the handoff usable outside the review session |
PlanInspect supports this drawing-first review for local DWG drawings and multipage PDF plans on iPhone, iPad, and Mac. You can add notes, photos, pen marks, highlighter, text, and markups, then export a reviewed handoff. PDF measurements need an active-page scale confirmation first; DWG review depends on the right layout and visible layers. The report should preserve those format-specific checks rather than hiding them.
If the first decision is which source to use, start with DWG versus PDF for site review. For a broader choice of native local workflows, see the PlanInspect plan viewer.
1. Confirm the source before making the first mark
Annotations are only as reliable as the plan beneath them. Before walking the site or writing the first note, identify the source and its context:
- For a DWG, confirm the filename and revision, switch to the intended model space or layout, and reduce visual noise with the relevant layers.
- For a PDF, confirm the issued plan set and active sheet. If a distance or area will influence the observation, calibrate that page from a known dimension and verify a second known distance before relying on the result.
- For either format, name the review date and the real question: defect, clarification, verification, closeout item, or design query.
Do not begin from a screenshot if the recipient may need layout, sheet, page, scale, or nearby-detail context later. A screenshot can be a helpful supporting artifact; it is rarely the authoritative review source.
Apple’s Files guidance for iPad is useful for keeping the source and outgoing artifacts in a named project location. For PDF-specific setup, the PDF plan viewer workflow explains why the active page and its scale deserve their own check.
2. Place one observation where a teammate can recover it
The strongest annotation is not the most colorful one. It is the one a teammate can find, understand, and act on without reconstructing your walkthrough from memory.
Keep each observation focused:
- Mark the exact room, grid, detail, component, or area on the plan.
- State the visible condition in plain language.
- Add a measurement only when the source context and scale support it.
- Say what needs to happen next, without guessing at an unverified cause.
For example, “Door D-204 at Grid B4: clear opening measured 780 mm; plan indicates 900 mm; verify frame installation before closeout” gives the reader a location, observation, evidence, and next action. “Door wrong” gives none of those.
In PlanInspect, keep annotations in the review layer rather than treating them as CAD authoring. The app is designed to review local plans, measure, annotate, and export; it does not claim full CAD editing, automated revision comparison, or live multi-user collaboration. For the iPad-specific markup sequence, read how to annotate a DWG without changing the original.
3. Add evidence that clarifies the decision
Evidence should reduce ambiguity, not create a second pile of files. Add a photo when it proves a condition that a plan mark cannot explain on its own: damage, a clearance conflict, a missing installation, an existing-site constraint, or a completed item worth confirming.
Use a short note to connect that photo to the plan. A good field item normally answers four questions:
- Where is it? The drawing location or active PDF sheet area.
- What is visible? A factual condition, not a theory.
- What supports it? One useful photo, measurement, or markup.
- What happens next? A clear verification, repair, decision, or owner follow-up.
This is the gap between generic PDF markup and an actionable field report. Autodesk’s PDF markup guidance describes creating markups and downloading selected markup content; Bluebeam’s markup workflow likewise emphasizes annotating drawings and exporting markup data. Those are valid capabilities, but a field recipient still needs the observation, its evidence, and its plan location to agree.
For a DWG-centered version of that pattern, add site notes and photos to a DWG on iPad explains when a photo earns a place beside the drawing note. If the work is a broader walkthrough, the iPad-to-Mac field report workflow covers the deliberate transfer and desk-side quality pass.
4. Choose the output for the next person’s job
Do not export every possible format by default. Pick the output that gives the recipient what they actually need:
| Recipient needs | Best handoff | Keep with it |
|---|---|---|
| A quick visual decision on one area | Marked plan PDF or image | Project, sheet/layout, revision, and the key note |
| A list of observations with supporting photos | Notes report | Location reference for every item and only the useful photos |
| Further drawing review | The identified source DWG or issued PDF plus reviewed output | Clear revision naming and the current review artifact |
| A field-to-desk quality pass | Named source and export package | Review date, unresolved questions, and original evidence where needed |
For a multipage PDF, the preserved source page and its annotations are often more useful than a separate screenshot bundle. For a DWG, the source may still be needed to inspect layouts, layers, or drawing context. In either case, distinguish the source from a frozen output. Autodesk makes the same distinction in its export documentation: downloading a source copy and exporting content with markups are different actions.
If a recipient only needs a final read-only handoff, a reviewed PDF or notes report may be enough. If they must validate a point against the original plan, send the identified source too. Neither choice implies automatic synchronization; transfer and version control remain deliberate team responsibilities.
5. Run a recipient-first quality check before sharing
An export button is not a quality check. Open the completed file outside the editing surface and inspect it as if you had not attended the walkthrough.
Use this checklist:
- Does the title or package name identify the project, source revision, review date, and format?
- Can every observation be found on the intended layout or PDF page?
- Do note numbers, plan callouts, photos, and captions agree?
- Is any measurement labeled with enough context to understand its scale basis?
- Do the report’s words separate what was observed from what still needs verification?
- Does the marked plan remain legible at normal viewing size?
- Does the recipient need the live DWG or PDF source in addition to the output?
On Mac, this is a natural point to reopen the source beside the handoff and check that the sheet, location, and wording still align. Plan review across iPhone, iPad, and Mac gives each device a defined role without claiming invisible state sync between them.
What PlanInspect does—and does not—turn into a report
PlanInspect helps a review team open local DWG drawings and multipage PDF plans, retain plan context, add notes and markups, attach photos, measure where the source supports it, and export a reviewed PDF, image, or report. It is useful when the report should grow from the plan rather than be rebuilt in a separate form after the fact.
It is not a promise of CAD source editing, OCR, PDF text search, password-protected PDF support, PDF optional-content layer controls, automatic revision detection, spreadsheet/XFDF export, cloud sync, or a live collaboration system. If the project needs one of those systems, use the approved workflow alongside the reviewed PlanInspect output.
A simple operating rule for the next walkthrough
Keep the original plan identifiable until the last recipient has what they need. On site, use the active layout or PDF page to locate the observation. At the desk, use the source to verify that the outgoing note, photo, measurement, and markup still point to the same place. Then share a fixed PDF, image, or report only when it answers the recipient’s job.
That small rule prevents two common failures: a note that can no longer be found on the plan, and a technically successful export that does not explain the decision. It also keeps review practical. You do not need to turn every redline into a full project-management record; you need to make the next action clear enough that a teammate can recover the context without starting the review over.
FAQ
Can I annotate a DWG or PDF plan without changing the source?
Yes. In PlanInspect, annotations are review overlays. They help communicate notes, photos, measurements, and visual markups while the original local DWG or PDF remains the reference. They do not turn the app into a full CAD authoring workflow.
Should I export a marked plan or a notes report?
Export a marked plan when the visual sheet context is the primary deliverable. Export a notes report when the reader needs an indexed list of observations and photos. When more review is required, provide the identified source DWG or PDF alongside the reviewed output.
Can a PDF plan be measured before it is annotated?
Yes, but confirm the active PDF page’s scale first. Calibrate from a known dimension, verify another known distance, then retain that context with the observation. Scanned PDFs can require manual point placement because they do not provide vector geometry for snapping.
Does annotating a plan create a formal revision or a live collaboration thread?
No. Annotations communicate a review observation. They do not create a controlled CAD revision, automatic revision comparison, automatic cloud synchronization, or live multi-user collaboration. Follow the project’s document-control process for those decisions.