The Reality of Practicing Structural Engineering in Scotland

The Structural Engineers Registration (SER) scheme is the only government-approved certification scheme for structural design in Scotland. Operated under the Building (Scotland) Act 2003, it is administered by Structural Engineers Registration Ltd, a wholly owned subsidiary of the Institution of Structural Engineers.

It does not get the airtime that the BSA does, but it should. For any structural engineer practicing in Scotland, the SER is the route to a building warrant, the basis on which the firm can compete for work, and the framework that holds individual engineers personally accountable for the structures they put their name to. And the consequences of getting it wrong are about to become considerably more serious.

This is a piece about what the SER actually requires, where the structural engineering industry is falling short, and what we think it takes to close the gap.

Under the SER, Approved Certifiers of Design examine structural designs and certify that they comply with Standards 1.1 (Structure) and 1.2 (Disproportionate Collapse) of Schedule 5 of the Building (Scotland) Regulations 2004. In practice, the scheme provides a streamlined route to a building warrant. The Approved Certifier reviews the structural design, confirms compliance, and issues a certificate that accompanies the warrant application. Without one, a building warrant application must be checked in full by the local authority, which significantly delays approval.

The audit and record-keeping obligations sit at the heart of the scheme. Under Clause 37(2) of the Building (Scotland) (Procedure) Regulations 2004, Approved Certifiers must keep records of how compliance was established. Approved Bodies (the firms they work for) must maintain adequate records of every project certified: reports, calculations, drawings, details, specifications, document issue sheets, and relevant correspondence. They must agree to be audited by SER when requested.

Audits cover evidence of scoping, certification plans, design review checklists, change documentation, and evidence that the certifier had adequate knowledge and experience for the project type. Members are subject to audit at any time. SER operates a rolling audit programme, with audits triggered by complaints, by the Scottish Registration Board, or as routine checks. A clean audit means the next one is in three to five years. A bad one means more frequent audits, sanctions, or removal from the register.

The Building (Scotland) Act 2003 currently caps the maximum fine for offences at £5,000. However, the Scottish Government has consulted on aligning Scottish penalties with the regime introduced in England and Wales under the Building Safety Act 2022. The proposed changes include a maximum fine of £50,000, a maximum custodial sentence of two years, and the option for either or both.

The consultation analysis noted widespread support for the increases, with local authorities arguing that current fines are too low to act as a deterrent and are disproportionate to the risk posed to public safety. Non-compliance is moving from a footnote to a genuine professional, financial, and personal risk.

Beyond the headline penalties, the existing professional consequences are severe enough on their own. An Approved Certifier found to have certified work that does not comply, or who has not maintained adequate records, can be suspended or removed from the SER register. For any firm whose Scottish work depends on certification, that is existential.

We have been working closely with a Scottish structural engineering practice that specialises in historic buildings, listed refurbishments, and bespoke domestic work, with a project archive that goes back thirty years. Three decades of project data, hundreds of sites, many of them estates and buildings the firm has been returning to for twenty years or more.

When we asked them what they actually do for SER record-keeping, the answer was instructive: they print everything. The calculation pack, the drawings, the design review markups. The certifier signs every page. The whole thing goes in a physical file, which goes in a box, and the box does not get touched again. When the audit comes round every five years, the box comes out. That is the master record. They want a paper trail that cannot be tampered with, lost, or quietly edited.

This is not because the firm is technologically behind. It is because the digital alternative, as it stands, is not trustworthy enough to be the record of last resort. Where files get edited, folders get reorganised, and things get deleted, a box of signed paper does not.

The real cost is not the printing. It is everything that sits around the certified file. When a client shows up with a major retrofit project, the firm has to dig through two decades of paper records, drawings, reports, letters, and emails to reconstruct what was done and why. Most of the institutional knowledge sits in the heads of engineers, which makes way for catastrophe when an engineer changes firms. While files may be well organised by the standards of any small practice, they are still not searchable in any meaningful way. As the director put it, AI search is a different category of tool from what file systems and email can offer.

So a significant portion of the working week goes into surfacing things the firm has already surfaced before. The same precedents, the same details, the same client correspondence, retrieved from scratch every time. For a small practice running seventy or more new projects a year on top of long-running estates, that overhead is real money.

The SER audit requirements create a significant documentation burden that the structural engineering industry handles inconsistently. Every certified project must have a complete, auditable trail of how compliance was established, from scoping through to final certification. In practice, this means maintaining detailed records across calculations, models, drawings, and design review checklists for every project. No standardised product or process comprehensively provides for this.

The legacy tools in the market, Aconex and Autodesk Construction Cloud, focus on document management and cross-team collaboration. Emerging players such as Speckle focus on data exchange between design tools. Neither category addresses the structural engineering-specific problem: maintaining a continuous, searchable record of design decisions, change impacts, and compliance evidence across the full project history, in a form that holds up under audit and can be queried when an old client comes back.

The result is that every firm independently figures out its own approach. Some run a tidy paper system, as our design partner does. Others rely on shared drives, Excel checklists, and email threads. While none of these approaches are wrong, none of them, on their own, provide a firm the kind of searchable, auditable, institutional memory that the SER scheme implicitly demands and that the next thirty years of practice will require.

There is also a direct cost to all of this. According to AED Consulting, a structural engineering practice based in Scotland, the additional documentation, checking and record-keeping required for SER certification typically adds approximately 15% to engineering fees on each project. For firms managing dozens of projects, the cumulative overhead is significant. With proposed penalty increases on the horizon, the calculus changes. Documentation stops being administrative tax. It becomes the line between a firm that can operate in Scotland and one that cannot.

At Bite, we believe that Scottish structural engineering firms need a purpose-built compliance and intelligence layer that integrates with how engineers already work, including the ones still working largely on paper.

The first thing Bite does is take project data, in whatever format it currently lives in (scanned calc packs, PDF drawings, Word reports, email threads, server folders going back to the nineties), ingest it, and make it searchable through natural language. Engineers can ask the question they actually have ("did we do anything like this on a Category B listed refurb in the last ten years, and what was the floor build-up?") and get a synthesised answer that points back to the source documents. The institutional memory comes out of people's heads and out of the filing cabinet, and becomes something the whole firm can rely on.

The second thing Bite does is build the audit trail in the background. Every file added, every change made, every decision logged, recorded automatically as a byproduct of how the firm already operates. When the SER audit comes round, the trail is already there. When a design change cascades through a project, Bite identifies every affected calculation, drawing, and document so nothing slips through before a certificate is signed.

We are developing this in close collaboration with structural engineering firms across the UK, with a particular focus on the practices in Scotland whose day-to-day reality is shaped by the SER scheme. We are not building in isolation and then asking engineers to adapt. We are embedding with teams, mapping their workflows, and building to their specifications.

The question is not whether Scottish firms will adopt tooling to meet the SER requirements. It is who defines the standard, and Bite is building that standard now. An automated audit trail, a searchable archive, and a centralised view of the firm's accumulated knowledge are not productivity features. They are how the next generation of Scottish practice will be done.

If your firm is working in Scotland, certifies under SER, and is thinking of how to tighten their project information management, please get in touch. We work closely with every firm we partner with to map their workflows, tools, and pain points before we build anything. The result is a setup that is bespoke to how your team actually operates, plugging into the toolstack and the archive you already have.

Get in touch at [email protected], or reach out to any of us directly. We would love to hear from you.