This is the BIM Boot Camp finale, bringing together the full Plannerly workflow from templates and smart documents through structured scope, automated verification, file management and lessons learned. The companion guide below walks through how Docs, Scope, Verify and File Manager work as one connected system to replace scattered tools, unread BIM execution plans, disconnected spreadsheets and manual approval processes.
Why a connected workflow changes how teams deliver projects
Over the course of the BIM Boot Camp, each session has focused on a specific part of the delivery workflow: planning information requirements, creating collaborative contracts, tracking deliverables through a smart CDE, and automating model checking with COBie handover. This final session brings all of those pieces together into a single end-to-end demonstration, starting from a blank project and building through templates, documents, scope, contracts, verification and file management in one continuous flow. The goal is to show that these are not separate tools bolted together. They are parts of the same structured system, and the data flows between them automatically.
The session opens with a recap of the challenges that brought everyone here: BIM execution plans that nobody reads, scope spreadsheets that nobody understands, delivery processes that nobody can verify, and handover workflows that create more stress than value. The solution is not more spreadsheets or more tools. It is a database-driven approach where Docs provides structured, collaborative documentation with section-level accountability, Scope provides a shared requirements database with responsibility matrices and timeline views, Verify automates model checking against contracted requirements, and File Manager collects, names and organises every deliverable with automatic versioning and permission-based access.
The demonstration starts by creating a new project from scratch. A template provides the starting point, and within seconds the project has structured documents, pre-defined scope, team permissions and classification standards ready to go. Team members are added with role-based permissions that control exactly what each person can see and edit. Document sections are assigned to specific team members for collaborative input, with statuses that control visibility so in-progress work stays private until it is ready to share. Smart fields populate automatically across all documents from a single entry, and AI assists with grammar correction, description generation and checklist creation directly within the workflow.
The scope section shows how requirements are structured using the buildingSMART data dictionary for consistent classification and coding. Each task card holds geometry requirements, information requirements, document placeholders, checklists, team assignments, milestone dates and full activity history. The timeline view turns these tasks into a Gantt chart with dependencies, constraints and lag times, so teams understand not just what needs to happen but when and in what order. Work packages filter the full database down to specific sets of deliverables that carry across from Scope to Verify to reporting.
Once requirements are agreed, the system combines documents and scope into a single contract document with automatic formatting, hyperlinked content, team directories and e-signature workflows. The same data can be exported as an information delivery specification for machine-readable downstream use. Verification then connects models from Autodesk Construction Cloud or direct uploads to contracted requirements using rule-based linking that evaluates compliance percentages automatically. Consultants can run the same checks on their own models before submission, enabling a self-QA workflow that catches issues before they reach the manager. File Manager then collects all deliverables with automatic naming conventions, status-based folder filtering and version control.
The result is a workflow where teams report up to 80% time savings on agreement creation alone, because templates, smart fields, collaborative sections and automated formatting eliminate the manual overhead that traditionally consumes weeks of administration on every project.
How the full workflow connects
- Start from templates – Create a new project from company templates that include documents, scope, classification standards and team structures, all continuously updated through the bidirectional template learning loop
- Build your team – Add team members with role-based permissions that control access to documents, scope, verification and file management at a granular level
- Collaborate on documents – Assign document sections to specific team members with status-based visibility, threaded comments, version tracking and AI-assisted content creation
- Define structured scope – Create requirements using buildingSMART data dictionary classifications, with geometry definitions, information requirements, checklists, document placeholders and AI-generated descriptions on every task card
- Plan with timeline views – Switch from grid to timeline to set dates, dependencies, constraints and lag times so every team member understands the delivery sequence
- Create work packages – Filter scope into targeted work packages that carry across modules, giving each team member a focused view of their responsibilities
- Contract and sign – Combine documents and scope into a formatted contract with automatic table of contents, team directories, requirement grids and e-signature workflows
- Verify against models – Connect models from ACC or direct uploads and use rule-based linking to check deliverables against contracted requirements with automated compliance scoring
- Manage files automatically – Collect all deliverables in File Manager with automatic naming, status-based filtering, permission controls and version management
- Learn and improve – Feed unscoped tasks and document changes back into templates so every project improves the next one through continuous template evolution
What you will learn
- Template-driven project setup – How live templates with smart fields and structured content let teams create new projects in seconds rather than weeks, with up to 80% time savings on agreement creation
- Section-level document collaboration – How assigning accountability at the section level with status-based visibility replaces the traditional workflow of emailing entire documents back and forth for review
- Database-driven scope management – Why structured requirements in a shared database with classification standards, AI-generated checklists and timeline views outperform spreadsheet-based task planning
- Integrated contract creation – How documents, scope grids, timeline views, team directories and progress reports combine into a single contract document with e-signatures, all generated automatically from existing project data
- Self-QA verification workflows – How consultants can run automated model checks against their own deliverables before submission, catching issues before they reach the manager and reducing the volume of formal issue tracking
- Automatic file management – How naming conventions, status-based folder filtering, version control and permission-based access remove the manual overhead of organising project deliverables
Common questions
How quickly can a new project be set up from templates?
A new project can be created and populated with documents, scope, team structures and classification standards in minutes. The template import process lets you select specific folders, milestones and content to bring in, so you are not forced to use everything. Smart fields populate automatically from project-level data, and team assignments from the template carry across with the imported scope. The result is that a project that might take weeks to set up manually in spreadsheets and word documents is ready to start in a single session.
Can team members only see what is assigned to them?
Yes. Permissions can be configured so that team members only see scope assigned to their team, only access documents relevant to their role, and only edit content they are responsible for. When a team member opens the project, it appears as though the application was built specifically for them. Managers retain full visibility across all teams and content while each consultant works within their own filtered view.
How does the contract document stay connected to the live project data?
The contract is generated from the same database that drives scope and verification. It includes hyperlinked references to specific tasks, team directories pulled from project membership, requirement grids filtered by work package and timeline views showing delivery schedules. When the underlying data changes, a new version of the contract can be generated to reflect those changes. E-signatures are managed within the system with full audit trails, so there is no need to download, upload or email documents for signing.
What is the self-QA workflow for consultants?
Consultants with editor permissions in the Verify module can connect their own models and run the same automated checks that the manager would use. They can see which information requirements are met, which properties are missing and which elements need attention. This means they can fix issues before marking tasks as completed, reducing the back-and-forth that typically consumes time during formal review cycles. Only managers can set the verified status, so the approval authority remains controlled.
How does File Manager handle automatic naming and organisation?
You define naming conventions using project fields like project ID, version number and unique identifiers. Files uploaded or generated within the system are automatically named according to these rules. You can also create filtered folders based on status, document type or any other metadata, so approved contracts automatically appear in one folder while in-progress deliverables appear in another. Versioning happens automatically as new files are uploaded, and permission-based access controls who can view or download each file.
Explore further
- Docs: smart documents, automation and accountability – Full help documentation for collaborative document creation and management
- Scope: structured information requirements and digital agreements – Help documentation for requirements management, work packages and timeline views
- Verify: task tracking, model checking and quality assurance – Help documentation for automated verification and compliance workflows
- File Manager: smart CDE workflows and connected project data – Help documentation for file management, naming conventions and version control
- What are smart fields and why you will love them – How database-driven placeholders automate document content across your project
- AI features for AEC documents and contracts – How AI supports description generation, checklists and grammar correction within the workflow
- Using the timeline for efficient task coordination – Training on timeline views, dependencies and delivery scheduling
- E-sign AEC project documents – How e-signature workflows integrate with contract documents and approval processes
- Simplifying BIM model checking automation – How automated verification connects deliverables to agreed requirements
- Advanced: exporting reports and managing the final handover – Deeper training on report generation and handover workflows
- Free BIM and ISO 19650 training – All Plannerly training courses from basic through expert certification
- BIM Boot Camp – The full Boot Camp course page with all sessions and resources