Ben SnapeMost UK architectural practices have accumulated an extremely cluttered tech stack. Architects add one tool at a time in response to immediate problems, all without a plan. Revit because the sector uses it. Google Drive or Dropbox because someone set it up. A separate invoicing tool because the previous one was slow. A WhatsApp group because a client prefers it. A project tracking spreadsheet because no one could agree on anything better.
The result, in most practices, is a fragmented set of tools that overlap in some areas, leave gaps in others, cost more than they should, and expose the practice to risks that no one has formally assessed.
A tech audit is how you take stock of all of it and decide what to do.
This post explains what a tech audit is, what it should cover, how to run one, and why it is worth doing from a business perspective.
What is a tech audit?
A technology audit is a structured review of all the hardware, software, subscriptions, and digital processes your practice uses to operate. Its purpose is to give you a complete picture of what you have, what it costs, how well it is actually being used, where the gaps are, and where the risks lie.
It is different from an IT support call or a one-off software review. A tech audit takes a step back and looks at the entire digital infrastructure of the practice as a system, not as a collection of individual tools.
The right output is a prioritised roadmap of what to keep, what to consolidate, what to replace, and what to address immediately.
A tech audit can be conducted internally by the principal or practice manager, or with external input from an IT consultant or managed service provider with AEC sector experience.
Why architecture practices need tech audits
Architecture practices have a more complex technology environment than most businesses of comparable size.
A ten-person practice might be running Revit and AutoCAD simultaneously across different projects, maintaining licences for Enscape, Lumion, or similar visualisation tools. At the same time they would be using a combination of BIM 360 or Procore for file coordination on live projects, generic cloud storage for everything else, a separate accounting package, an emailing tool, and something, usually improvised, for client communication and project management.
Each of those tools creates obligations: licence terms, data protection, integrations, version control. Some of them have security implications, particularly in remote and hybrid working arrangements that became standard post-2020.
And across most practices, nobody has an accurate count of how many subscriptions are active, how much is being spent in aggregate, or whether the tools are actually being used by the people they were purchased for.
Beyond compliance, there is a deeper issue. Firm management mistakes that limit revenue are very often technology mistakes. Not because the wrong CAD software was chosen, but because the practice management layer of the tech stack is neglected or patchy.
When project information is scattered across email threads, shared drives, WhatsApp groups, and personal laptops, the practice pays for it in administrative overhead, communication failures, unbillable hours, and disputes.
A tech audit addresses all of this. it is a digital transformation exercise with a practical output.
Signs you’re overdue a tech audit
These are the clearest signals that one is overdue:
- You cannot quickly list every active software subscription and its annual cost.
- Your team uses tools that were never centrally approved.
- File versions often get lost, overwritten, or duplicated.
- New starters take weeks to get fully operational.
- You are paying for seats that people do not use.
- You are about to hire, take on a major project, or respond to a public sector tender.
What a tech audit covers
1. Hardware
The inventory starts with what the practice physically runs on: workstations, laptops, tablets, monitors, servers, NAS drives, mobile devices.
2. Design and production software
This is the layer most practices pay most attention to, but often less systematically than they think. The audit should cover every CAD and design application in use.
3. Practice management and operations software
This is the layer that most architectural practices handle least well. It encompasses project management tools, task tracking, fee management, invoicing and billing, CRM, and quote systems.
4. Communication and collaboration tools
Email is the backbone of most practices’ external communication, but the audit should document everything around it. Beyond email, the audit covers: instant messaging platforms (Microsoft Teams, Slack, WhatsApp), video conferencing, client portals, and any collaborative document editing environments.
The key question here is where the boundary lies between communication that is captured and searchable against a project record, and communication that vanishes into personal inboxes and chat histories.
5. Data storage and file management
Where does the practice’s data actually live? The audit needs to answer this honestly across: local workstation storage, internal servers or NAS drives, cloud storage (Microsoft OneDrive, SharePoint, Google Drive, Dropbox, iCloud), project-specific CDEs, and any personal cloud accounts in de facto use.
For each location, assess: who has access, whether backups exist and are tested, what the disaster recovery position is if a system fails, and how data is protected in transit and at rest.
6. Cybersecurity status
Architectural practices are targeted by cybercriminals because they hold commercially sensitive design IP, personal client data, client financial information, and in some cases security-sensitive building information.
The firm’s cybersecurity should be assessed against UK Government Cyber Essentials as it is increasingly becoming a prerequisite for public sector contracts.
See our post on cybersecurity for architecture firms for more tips on the topic.
7. GDPR and data protection compliance
The Information Commissioner’s Office provides clear guidance for small businesses. The UK Data (Use and Access) Act 2025 has also introduced some updates to the UK GDPR regime, so start by reviewing both of these documents.
8. Software licences
This section of the audit is about legal compliance and commercial waste. The core questions are: is every piece of software in active use properly licensed, is the licence type correct for how it is being used (commercial vs. educational is a common gap), are licence assignments up to date, and are renewal dates being managed proactively rather than reactively?
How to run a tech audit: a practical process
Step 1: Build the inventory
Start by assembling a complete list of every tool the practice uses.
Do not rely on memory or accounts payable alone, because both will be incomplete. Circulate a simple survey to every member of the team asking them to list every app, platform, or tool they use in their work, including personal-account tools they use for practice purposes.
This is how you find the the so-called shadow IT: the personal Dropbox, the free AI tool, the project management app one job architect adopted three months ago.
Step 2: Map the cost
Consolidate the inventory against actual spend.
Pull every relevant line from the practice’s bank statements, credit card statements, and direct debits for the past 12 months.
Match each payment to an inventory item. The total will almost always be higher than anyone expects, and you will almost always find subscriptions that nobody actively manages any more.
This single step commonly uncovers 10–20% in software spend that can be immediately reviewed.
Step 3: Assess actual usage
Cost alone is not the measure. A well-priced tool that nobody uses is waste; an expensive tool that saves ten hours a week is valuable.
For each item in the inventory, assess actual usage: how frequently it is used, by how many people, for what tasks, and whether its use is consistent with what it was purchased to do.
Step 4: Identify gaps and redundancies
With the inventory, cost, and usage picture assembled, the gaps and redundancies usually become obvious.
Common findings in architectural practices include:
- several overlapping cloud storage environments in active use;
- a project management tool that is partially adopted but widely circumvented;
- no structured system for client communication archiving;
- design software seats assigned to people who left six months ago;
- no single source of truth for project financial status, etc.
Step 5: Assess security and compliance
Work through the cybersecurity and GDPR elements mentioned above. The easiest structure is to map against Cyber Essentials’ five controls for the security review and against the ICO’s small business checklist for the GDPR review. Both are publicly available and practical.
Step 6: Build a roadmap
The output of a tech audit should be not just a list of problems, but a prioritised action plan.
Structure findings into two categories: immediate actions and strategic projects. Assign owners and target dates to each.
How often to audit
Annually is the right cadence for most practices: at the same time each year, ideally aligned with the practice’s financial year-end or a quieter project period.
The full process as described above should take a principal or practice manager a focused day to complete for a practice of up to 20 people.
The first time will take longer. All the next reviews are quicker because the baseline exists.
How tech audits affect business growth
A tech audit is not primarily a cost-cutting exercise. Done well, it is a strategic investment in the practice’s operational capacity.
Tech audits remove the friction that prevents good work from being profitable. Fragmented tools, poor document management, and informal communication processes all create operational bottlenecks that consume capacity without producing value.
They make you a better-run business. Clients notice the difference between a practice that is operationally together and one that is not.
The architect who can quickly produce a clear fee proposal, respond to a document request in minutes, and maintain organised project communication is demonstrating competence that extends well beyond drawing skill. This matters for reputation, referrals, and for the kind of client relationships that generate repeat work.
Tech audits help make better decisions about AI tools and emerging technology. Every month brings new tools claiming to transform architectural practice, and the practices that adopt them thoughtfully get the most benefit. A tech audit gives you the baseline to make those decisions well.
Last but not least, tech audits let you track KPIs properly, because it helps bring reliable data to light. A tech audit often reveals that the data exists somewhere, but is trapped in silos that don’t intersect: e.g. in invoicing tools, time tracking logs, and project management spreadsheets
PlanMan and tech audits
The first tech audit an architecture firm runs almost always reveals the same problem: the design and production layer is well-served, but the practice management layer is not.
PlanMan is built specifically to address that gap for UK architects and town planners. Our software consolidates the practice management layer into a single, purpose-built platform with the following main features:
Project management where each project has a structured workspace covering stages, tasks, milestones, and progress.
Document management module that has all project documents, correspondence, drawings, contracts, and certificates stored in one place per project with version control and cloud access from any device, including the mobile app.
Client communication and instant chat where all client-facing correspondence and project-level messaging stored against the relevant project. The audit trail for a dispute, a PI claim, or a contract administration question is built automatically rather than reconstructed from personal inboxes.
Quote management and invoice management features that get you fee proposals and invoices generated directly from project stages, with integration to Xero, FreshBooks, Sage, and payment collection via Stripe and GoCardless. The billing workflow becomes a coherent part of the project record rather than a separate system that has to be reconciled manually.
Co-consultants module is an important addition because external consultants, specialist subcontractors, and clients can be given controlled access to the project environment via granular permission groups, with a clear record of what was shared and when. This addresses both the collaboration gap and the GDPR data-sharing documentation requirement simultaneously.
Client management replaces the scattered spreadsheets and email history that most practices rely on to track client relationships, project history, and pipeline.
When a tech audit reveals that the practice management layer is fragmented, PlanMan is where you consolidate it.
Start your free 30-day trial and see how much of your current tech stack it replaces.