The Digital Troublemaker's Toolkit

This video explains why broken workflows persist in construction and what it takes to build a practical digital toolkit that supports better BIM management, information management, approvals, accountability, and collaboration across real projects. The written guide below covers how Word, Excel, PDFs, and email create fragile project management paths, why stitching together multiple modern tools still leaves manual gaps, what an industry-specific connected platform offers compared to generic approaches, how centralised templates and structured permissions standardise best practices, and why a practical training plan and a strong business case are essential for leading lasting digital change.

Why your digital construction toolkit needs to be more than a collection of disconnected tools

By this point in the course, you understand why wanting change is not enough. Good intentions, better workflows on paper, and new tool introductions all fail without a structured system underneath them. The question now is what that system should actually look like. This video compares three approaches to building a digital construction toolkit: the legacy approach, the stitched-together approach, and the connected platform approach. Understanding the difference between them is critical to making the right choice for your organisation.

The legacy approach is the one most teams know all too well. Someone creates a document in Word. Notes get added in an Excel spreadsheet. Everything is emailed around. A third person PDFs it. Someone else saves a copy in SharePoint. Another person updates a completely different version on their desktop. The result is a fragile project management path where one small failure can bring the whole system crashing down. In construction and digital project delivery, this is not just about lost time or minor mistakes. These are multi-million dollar projects involving multiple companies, dozens of contracts, tight margins, and zero room for failure. One missed approval, one wrong file version, or one miscommunication can have consequences that ripple across the entire project. Trying to hold this together with Word documents, PDFs, emails, and folders is like trying to hold a construction project together with duct tape. It works until it does not, and the failure is usually expensive.

The second approach is what many teams adopt when they recognise the legacy method is broken. They stitch together a stack of modern tools: Trello for task management, Airtable for tracking some workflows, Monday.com for project timelines, and an online folder for file storage. Each individual tool is better than the 1990s approach, but the combination still creates a juggling act. Every extra tool adds another gap that has to be bridged manually. Data does not flow between the tools. Approvals are still informal. Requirements defined in one tool have no connection to the documents or contracts in another. And the person responsible for keeping it all together, typically the BIM manager or information manager, spends more time managing the tool stack than managing the actual information. The stitched-together approach is better than legacy, but it is not the foundation for structured information management (opens in a new tab) that real construction projects demand.

The third approach is to build on a platform designed specifically for the construction industry's needs. Not a generic project management tool adapted for construction, but a system purpose-built for the way multi-party, phased, contractual project delivery actually works. This is where the components of the Plannerly platform come together. The Docs module (opens in a new tab) provides structured, collaborative document management with accountability built into every section. No more hunting through email threads to find who approved what. The Scope module (opens in a new tab) turns information requirements into a structured database where every item has an owner, a status, and a traceable connection to the deliverable it relates to. The Contract module (opens in a new tab) connects agreements to the requirements and documents they govern, creating enforceable, traceable records rather than static PDFs. The File Manager (opens in a new tab) acts as a connected common data environment with proper version control and file organisation. And the Verify module (opens in a new tab) automates model checking against the requirements defined in Scope, closing the loop between what was asked for and what was delivered.

A connected platform also solves several problems that no combination of generic tools can address. Centralised templates (opens in a new tab) mean that your company's approved best practices, document structures, and standard content live in one trusted location. When a new project starts, the team can import from templates (opens in a new tab) rather than starting from scratch or copying files from the last project and hoping they are current. Permissions (opens in a new tab) are controlled at a granular level, giving the right people access to the right content at the right time while protecting sensitive data. Accountability (opens in a new tab) is not an afterthought but a built-in feature: every requirement, every document section, and every deliverable has clear ownership and a traceable history of who did what and when. And lessons learned are captured throughout the project life cycle so that each project builds on the knowledge gained from the last one.

The ability to selectively reuse project content and scope (opens in a new tab) from previous projects is one of the most practical advantages of a connected platform. Rather than treating every project as a blank slate, teams can carry forward the requirements, templates, and best practices that worked well on previous deliveries. This means every project gets faster, smoother, and smarter without the inefficiency of rebuilding everything from scratch. When combined with automated tracking that replaces manual status chasing, the entire approach shifts from reactive firefighting to proactive, structured delivery.

Having the right platform is essential, but the video makes an equally important point about what comes next: you cannot lead change you do not fully understand. Before bringing others along, you have to walk the path yourself. This is why the course provides two essential resources to guide you through real change. The first is a practical training plan that ensures your team understands not just what to do but why it matters. The second is a business case that helps you show leadership the value of smarter workflows and secure their backing. Together, these give you the foundation to stop chasing approvals and start leading with clarity and confidence. Real change does not happen overnight. It happens one conversation at a time, one smarter step at a time, and one stronger foundation at a time. And it always begins the same way: one person choosing to lead.

How to evaluate and build your digital construction toolkit

1. Audit your current workflow - Map out how documents, approvals, requirements, and files actually move through your projects today. Identify every manual handoff, every email-based approval, and every place where information is duplicated or disconnected. This reveals the true cost of your current approach.
2. Assess the limitations of stitched-together tools - If you are using multiple generic tools, identify the gaps between them. Where does data not flow? Where do you bridge manually? Where do approvals fall through? Every gap is a risk point that a connected platform eliminates.
3. Centralise your templates and best practices - Move your company's approved document templates, scope structures, and standard content into a single trusted library (opens in a new tab). Ensure that every new project starts from a consistent, current baseline rather than a copy of the last project's files.
4. Set up structured permissions - Use granular permissions (opens in a new tab) to control who can view, edit, and manage content across internal and external team members. Protect sensitive data while keeping project information accessible to the people who need it.
5. Define requirements as structured data - Replace PDF-based requirement documents with a structured requirements workflow (opens in a new tab) in the Scope module. Assign ownership, set statuses, and connect each requirement to the deliverable and contract it relates to.
6. Connect documents to contracts and approvals - Use the Contract module (opens in a new tab) and digital approvals (opens in a new tab) to create a traceable link between what was agreed and what is being delivered. Eliminate the email-based approval chain that creates confusion and blame.
7. Capture and reuse lessons learned - Build a practice of capturing lessons learned throughout the project and importing refined scope and content (opens in a new tab) into future projects. Every project should make the next one faster and smarter.
8. Walk the path yourself before leading others - Complete the training programme (opens in a new tab) yourself before asking your team to follow. You cannot advocate for a process you have not experienced. Understanding the full workflow gives you the credibility and confidence to lead the change.
9. Build the training plan and business case - Use the training plan template and the business case template to create the two foundational documents that make lasting change possible: a plan that builds team understanding and a case that secures leadership backing.

What you'll learn

• Why legacy workflows are dangerous, not just inefficient - How the fragile chain of Word documents, Excel sheets, emailed PDFs, and desktop copies creates real project risk on multi-million dollar, multi-party construction projects where one missed approval or wrong file version can have cascading consequences.
• Why stitching tools together is not enough - How combining multiple generic tools like Trello, Airtable, and Monday.com creates a juggling act where every additional tool adds another manual gap, and why the person managing the stack spends more time bridging tools than managing information.
• What an industry-specific platform provides - How a connected platform built for construction project delivery centralises templates, controls permissions, builds in accountability, manages structured workflows from requirements through to verification, and captures lessons learned for reuse.
• Centralised templates and reusable content - Why storing your company's approved best practices in one trusted location and selectively reusing project content from previous deliveries makes every new project faster, more consistent, and less dependent on individual memory.
• Training plans and business cases - Why these two resources are the foundation of lasting change, how the training plan builds team understanding beyond software skills, and how the business case gives leadership the rationale to support and champion the transformation.
• Leading by walking the path first - Why you cannot lead change you do not fully understand, and why completing the training yourself before bringing others along gives you the credibility and practical knowledge to drive real, lasting transformation in your organisation.

Common questions

Explore further

• The Digital Troublemaker's toolkitThe full lesson on the tools and resources available to help you build your digital construction toolkit and lead the change in your organisation.
• Digital construction business caseHow to build the argument for connected workflows in terms that leadership can act on.
• Full BIM workflow: 80% less adminA practical demonstration of how the connected platform approach reduces manual administration and improves project delivery.
• How to centralise BEP informationPractical guidance on moving from scattered Excel and ACC workflows to a centralised, structured approach. (opens in a new tab)
• BIM Boot CampA structured programme that walks you through the full connected workflow so you can experience the path before leading your team along it. (opens in a new tab)