PlanSwift - Issues Using Takeoff Boost Tools: Document Quality, Parallels Setup, and Performance Tips

Contents

1. Document Quality Requirements
2. Parallels Setup for Mac Users
3. Performance & Workflow Tips
4. Other Frequently Asked Questions

This guide captures practical guidance for getting the best results from PlanSwift® with Takeoff Boost™. It covers document quality, Parallels setup for Mac users, and performance and workflow tips, and answers common questions raised by customers. Some of these performance issues will be addressed in the planned 64-Bit release due out late 2026.

1. Document Quality Requirements

Plan and PDF quality is the single biggest driver of Takeoff Boost AI accuracy. PlanSwift renders what is in the source file, so a low-resolution document limits how much detail the AI has to work with. When the AI tools struggle, a good first step is to check the quality of the source document.

Resolution targets

Common low-quality sources to avoid

• Scanned or emailed plans, often pixelated or rasterized
• Screenshots of drawings
• Exports from plan-room viewers or mobile apps
• PDFs printed from a web browser
• Files sent through services that auto-compress attachments
• Converted files

How to spot a bad file: If a plan looks blurry or will not focus in PlanSwift, check the source document for low-DPI pixelation first. Open the source PDF in Adobe Acrobat, Edge, or Chrome and zoom to 200%. If it pixelates there too, the file is low-resolution and should be re-sourced at a higher DPI.

Best-fit documents for the AI: Clear wall sections with legible tags and callouts. Large sets with 200+ pages work well when resolution is good. Low-quality plans cause specific failure modes, including wall traces skipping segments, misreading a callout box or window endpoint as a corner, and net-area boxes landing off-target.

2. Parallels Setup for Mac Users

PlanSwift is a Windows-only desktop application. Mac users run it through Parallels. Most Parallels-related issues are virtualization and emulation artifacts, not PlanSwift defects.

See: Can I Run ConstructConnect's Takeoff and Estimating Applications on Apple hardware (a MAC)? for more information.

Which Parallels plan to recommend

For specific configuration questions, point the customer to Parallels directly. ConstructConnect is not affiliated with Parallels and does not license it.

Display redraw and paint artifacts: If the Auto Takeoff control does not stay painted or artifacts appear as the mouse moves, Parallels Coherence mode is the likely cause. Switch Parallels to windowed, non-Coherence mode.

Bootcamp: A recommended alternative when Parallels emulation friction is severe.

Why Apple Silicon (M-series) Macs see more friction: The stack adds multiple emulation layers: M-series chip to Parallels to Windows ARM to 32-bit PlanSwift. The upcoming 64-bit PlanSwift build reduces these layers.

Right-click: See Using Right-Click in ConstructConnect's Takeoff and Estimating Apps when Running in Parallels (MAC Users) for assistance with getting right-click or alternate-click working.

3. Performance & Workflow Tips

These practical tips came directly from customer calls and help PlanSwift and Takeoff Boost run better day to day.

Get the best source file into PlanSwift

• Download the plans from the ConstructConnect Document Viewer to your computer first, then manually load the saved PDF into the PlanSwift job.
• When you load the file into the job, do not convert it to TIF. Keep it as a native PDF so PlanSwift runs off the full-resolution source.
• The PS-Connect download-to-PlanSwift button automatically converts incoming files to TIF; avoid using PS-Connect to preserve native PDF resolution and use the manual download-then-load workflow instead.

Working with the AI tools

• Always human-verify AI output.
• The tools are roughly 97 to 98 percent accurate and improving, but they can still miss items or count a legend or key item as a real count.
• Use modification keyboard shortcuts to clean up misses quickly: double-click a line to add a point, use keyboard keys to move or adjust points, and use delete or backspace to remove points.
• Re-running Auto Takeoff under the same net area name reapplies it to the same region. Rename the area to create a second, separate takeoff.

Specific workarounds

• Pitch: No AI tool calculates pitch. Apply a part or assembly that contains a pitched formula onto the area to recalculate using the pitched value.
• Joist or scripted tools: These do not appear in Reassign Takeoff because their item type is not Area. In Estimating, create a New Area and change it to a joist area, or copy from existing templates.
• Two scales on one sheet: Copy the page to handle the second scale independently.
• Large-job performance: Very large full-home estimates can slow down and crash. By the 10th to 12th area, each can take 5+ minutes to recalculate. The root cause is the current single-threaded, single-core 32-bit build. The upcoming 64-bit multi-threaded release, targeted in late 2026, is the fix. In the meantime, break very large jobs into smaller files.

4. Other Frequently Asked Questions

Related Articles