Image source: Panumas/adobe.stock.com.
PlanGrid served as a widely used field collaboration tool, enabling contractors to access sheets, markups, RFIs, and reports from the jobsite. But five years ago, Autodesk paused further development. The platform is now in “maintenance mode,” meaning it will remain functional for now but will not receive updates or new features. Autodesk Build, part of the Autodesk Construction Cloud (ACC), is the designated successor. It incorporates many of PlanGrid’s core features while adding tools for document control, project management, scheduling, and cost tracking, and integrating with other Autodesk tools.
In a recent webinar hosted by IMAGINiT Technologies, Enablement Engineer Scott Burke outlined what users can expect when making the transition from PlanGrid to Autodesk Build, emphasizing the expanded capabilities and strategic advantages of the newer platform.
PlanGrid Legacy
PlanGrid was built to simplify construction document access and markup in the field and was adopted on more than a million construction projects globally. It offered essential tools for document sharing and field collaboration, such as sheet management and sharing, task tracking (issues and punch lists), RFIs and submittals, field reports and checklists, and photo and document storage. While it was fast and accessible, especially for smaller teams or trade partners, Burke described the program’s limitations, explaining it did not support 3D models or BIM workflows, had limited permissions (admin, collaborator, or power collaborator), could not view AutoCAD and Revit files; lacked scheduling, commissioning, and email tracking tools; and offered few integration options with accounting or planning tools.
“It did a lot of things well,” Burke noted, “but it's missing many functions that a full construction platform needs.”
Autodesk Build: The Construction Platform
Autodesk Build is not simply an upgrade to PlanGrid; it’s a comprehensive construction management platform that addresses PlanGrid’s shortcomings while introducing new capabilities. It integrates with other Autodesk tools, such as
- Autodesk Docs for core document management,
- BIM Collaborate Pro for cloud-based authoring,
- Autodesk Takeoff for 2D and 3D quantification,
- Build for project and field management, plus
- Other tools for bidding, submittals, cost estimation, and facilities management.
Feature Chart: PlanGrid Compared to Autodesk Build
Feature |
PlanGrid |
Autodesk Build |
BIM/model viewing |
Not supported |
Full model interaction and markup |
Permissions |
Limited roles only |
Granular control by user, folder, or role |
Sheet comparison |
Basic |
Advanced 2D/3D revision comparison |
Task tracking (Issues) |
Manual |
Fully assignable, traceable, reportable |
File support |
Mostly PDFs |
AutoCAD, Revit, PDFs, Word, Excel, etc. |
Photo tagging |
Manual |
AI-generated auto-tags |
RFIs/Submittals |
Basic status tracking |
Configurable workflows and stamps |
Meetings & minutes |
External tools required |
Built-in with agenda and item tracking |
Scheduling |
Not included |
View Primavera/MSP + internal task planning |
Reporting |
Minimal |
Automated, filterable, cross-project |
Document and Sheet Control. Users can view and interact with a wide range of file types—including AutoCAD DWGs, Revit models, MicroStation files, PDFs, and Microsoft Office documents—without needing the native software. Files can be marked up, versioned, compared, and linked to issues, RFIs, or forms.
Autodesk Build continues the sheet-based workflows familiar to PlanGrid users. Sheets are organized by discipline and revision, and changes can be compared across versions.
The “Issues” module is more robust in Build. Burke recommends thinking of issues as action items, which may include punch list items, safety concerns, or clarification requests. “These are not just problems—they’re action items,” Burke emphasized. “You can filter, track, assign, and close them all from one place.”
Forms, Field Reports, Photos. While the forms interface may look familiar to PlanGrid users, Autodesk Build adds more functionality. Conditional logic allows automatic issue creation from form responses, and users can create forms from smart PDFs or structured templates. Forms can be linked to related assets, documents, or photos, building a connected record of project data.
Photos are uploaded to a central project gallery and Build uses AI to identify objects in photos and apply tags (e.g., “fireproofing,” “baseboard,” “door”). Each photo can be linked to multiple forms, issues, or markups, building traceability across project activities.
RFIs and Submittals. Autodesk Build brings structure to submittal and RFI workflows. RFIs can include documents, photos, and reviewer annotations, and all activities are logged for transparency and accountability. Submittals support multi-step reviews, customizable reviews, including stamped document and collaborative markups.
Users can share, collaborate and connect project schedules with field and office teams from within Autodesk Build. Image source Autodesk.
Scheduling and Planning. While Build does not replace scheduling software, users can view imported schedules from Microsoft Project or Primavera. In addition, users can create internal work plans as subtasks tied to broader schedule items which can be helpful for coordinating day-to-day activities on site.
Build helps you share, collaborate, and connect project schedules with field and office teams. Image source Autodesk.
Meetings, Email, and Communication. Meeting records include attendance, discussion items, and ongoing tasks. Items can roll forward from one meeting to the next until resolved. Build also supports integration with Microsoft Teams and Zoom for live meetings.
Build centralizes team communication by recording meeting minutes and automatically carries forward unresolved items, integrates Teams or Zoom meeting links, tracks email threads using a project-specific email address and makes it easy to attach files, sheets, or issues to correspondence.
Asset Tracking and Commissioning. Assets can be sourced from models or added manually. The platform includes commissioning tools and asset tracking capabilities. Teams can monitor installation progress, link assets to models and documents, and track completion through startup, testing, and turnover stages.
Reporting. With customizable dashboards and scheduled reports, Build can help teams anticipate problems, not just react to them. Reports (e.g., overdue RFIs, punch list summaries) can be scheduled to send automatically to individuals or companies each week. Dashboards offer insight into safety, quality, cost, and design trends across projects. At the company level, executives can view cross-project performance, costs, and risk indicators.
Cost Management and Budgeting. Autodesk Build includes a cost management module that supports budget creation, contract administration, change orders, and forecasting. While not intended to replace a general ledger, it can integrate with accounting systems and provides teams with tools to manage construction budgets in real time.
Autodesk Build can help you maintain a real-time view of your construction project budgets. Image source: Autodesk.
How to Approach Your Transition
There is no automated migration of projects from PlanGrid to Autodesk Build. Burke emphasized that each is a separate environment and suggests this transition plan:
- Complete existing work in PlanGrid.
- Start new projects in Autodesk Build.
- Archive old PlanGrid data by downloading files and uploading to a new Build “placeholder” project.
- Transfer forms and checklists manually, using built-in export/import functions.
For teams preparing to transition from PlanGrid to Autodesk Build, working with an experienced implementation partner can help reduce disruption and ensure a smoother rollout. A partner like IMAGINiT Technologies can assist with practical planning—such as deciding which projects to finish in PlanGrid and how to structure new ones in Build.
IMAGINiT can also guide the process of organizing and exporting legacy data for archival or reference. In addition, partners can provide structured training tailored to different user roles, help configure templates and permissions based on company workflows, and offer support during the early adoption phase to address questions or adjust processes. This kind of hands-on guidance can be especially valuable for firms with complex project portfolios or limited internal resources dedicated to software transitions. With experience supporting Autodesk users across many industries, IMAGINiT can help teams adopt Autodesk Build effectively.
Final Notes
While Autodesk Build introduces more complexity, it also offers greater control, integration, and visibility across construction projects. Autodesk Build represents more than just a successor to PlanGrid—it’s a strategic shift toward a more integrated and intelligent construction management platform. With real-time access to project data, flexible workflows, and seamless collaboration across teams and file types, Build enables construction professionals to manage complexity with greater confidence and efficiency.
“It’s not just a replacement,” Burke noted. “It’s a platform for managing more of the project lifecycle—from early design to closeout.”
For more on making this transition, watch the full webinar from IMAGINiT or reach out to an IMAGINiT specialist for more details.
***
This article was sponsored by IMAGINiT Technologies.
Searching for more information about Architecture, Infrastructure, and Construction?
Click here!