Why Scope-Basis Questions Matter in PlanSwift Workflows

PlanSwift is a widely used digital takeoff tool that helps estimating teams measure quantities from electronic plans. While the software accelerates the measurement process, it does not define the scope of work for the estimator. Teams must establish their own scope basis before, during, and after using PlanSwift to ensure that the quantities generated correspond to the work actually being priced.

Pre-Takeoff Scope Boundary Questions

Before opening a set of plans in PlanSwift, the estimating team should confirm the scope boundary with a structured set of questions. Which sheets are included in the bid set? Are alternate drawings or addenda part of the takeoff? Does the scope cover only base building elements, or does it extend to site work and exterior finishes? Answering these questions first prevents the team from measuring items that fall outside the intended bid scope.

Assumption and Exclusion Questions During Takeoff

As quantities are assembled in PlanSwift, estimators make dozens of small assumptions about measurement methods, layer selections, and scale calibration. Each assumption should be recorded alongside the takeoff. What scale was used for each page? Were overlapping areas deducted or counted twice? Which layers were included and which were excluded? Are there conditions on the plans that are ambiguous or contradictory? Documenting these decisions creates a traceable record that reviewers can follow.

Missing Information and Clarification Questions

Digital takeoff often reveals gaps in the drawing set. Detail references may point to sheets that are not included, schedules may list items that do not appear on the plans, and specifications may reference standards that are not provided. The estimating team should compile a clarification list as they work in PlanSwift. Are all referenced details included in the bid set? Do the specification sections match the drawing set? Are there dimensions that cannot be verified from the provided plans? This list becomes part of the scope-basis package submitted with the bid.

Change Review Questions Before Submission

After the takeoff is complete but before the bid is submitted, the team should conduct a final scope-basis review. Have any plan revisions been issued since the takeoff began? Do the quantities in PlanSwift match the quantities in the estimate spreadsheet? Have all assumptions and exclusions been documented in the bid documents? Has the clarification list been attached? A structured review at this stage catches errors that would otherwise surface after contract award.