
Scottish Castle BIM Case Study for Reliable Design
- Space Captures Team

- 1 day ago
- 6 min read
A castle rarely offers the clean, repeatable geometry assumed by a typical existing-conditions survey. Walls taper, floor levels change unexpectedly, rooms have been altered across centuries, and roof spaces can be difficult to access safely. This Scottish castle BIM case study considers how a precision-first survey and modelling workflow can give a heritage design team dependable information before decisions are made.
The objective is not to make an old building appear regular in Revit. It is to document what is there, distinguish reliable geometry from reasonable interpretation, and issue files that support design, coordination and heritage discussions without creating false confidence.
The Brief: Make an Irregular Building Usable
Consider a representative refurbishment project involving a listed Scottish castle. The design team needs measured floor plans, elevations, sections, roof information and a Revit model to assess proposed repairs, accessibility improvements and new building services. Existing record drawings are incomplete, and several areas have been altered since they were produced.
At first glance, the brief may sound familiar. Yet a castle changes the level of risk. A 50 mm discrepancy in a modern office fit-out can be inconvenient; the same discrepancy at a vaulted opening, stair landing or retained stone arch can affect intervention details, clearance assessments and approvals. The team needs more than attractive drawings. They need evidence-based geometry.
A useful BIM brief therefore defines the intended uses before survey work begins. Is the model needed for concept design, planning support, consultant coordination, quantity review, or construction-stage setting out? The answer affects the required level of detail, the survey coverage and the modelling effort. Modelling every stone may look impressive, but it is not automatically useful or proportionate.
Why Castle Geometry Resists Assumptions
Historic castles are often the product of additions, repairs and changes of use rather than a single coherent build. External walls may be substantially thicker than expected. Window reveals can vary from room to room. A corridor that appears straight on an old plan may drift across its length, while a stair may have unequal treads created by settlement or historic adaptation.
Laser scanning provides a dense record of these conditions, but capture alone does not resolve the problem. The point cloud must be registered carefully, checked against survey control and reviewed by people who understand which features matter to the design team. A poorly managed point cloud can still lead to a model that is visually convincing but dimensionally unreliable.
Roof geometry deserves particular attention. Turrets, parapets, skewed valleys, battered walls and uneven roof planes can make conventional roof-plan assumptions unreliable. If access is limited, the survey strategy may need a combination of terrestrial scanning, targeted photography and external capture methods. The appropriate approach depends on site constraints, conservation requirements and the level of information needed.
Scottish Castle BIM Case Study: The Documentation Workflow
The most dependable workflow begins with a clear scoping conversation. Before attending site, the documentation team should establish the accessible areas, key design questions, required outputs, coordinate system, drawing scales and Revit version. It is also sensible to identify exclusions early, such as inaccessible upper levels, concealed voids or areas occupied by stored collections.
Capture the building as it stands
On site, high-accuracy 3D laser scanning records the main structure, circulation routes, internal spaces, façades and accessible roof areas. Additional measured checks help verify critical dimensions where the design will be sensitive to clearance, alignment or interface conditions.
For a complex heritage property, scan positions need thoughtful planning. A long corridor, for example, may require enough overlap to avoid registration drift. Small rooms, deep window embrasures and winding stairs require sufficient coverage to prevent shadow areas. The aim is not simply to collect more scans. It is to collect the right evidence for the agreed deliverables.
Photography is equally useful as a visual reference. It supports interpretation of material changes, openings, decorative features and building elements that may be difficult to read from point cloud data alone. It also helps the modelling team identify where a surface is genuinely irregular rather than obscured by scanning limitations.
Turn point clouds into controlled CAD information
Once registered, the point cloud becomes the reference dataset for measured drawings. Plans are cut at agreed levels, with additional plan cuts where split levels or complex stair arrangements require them. Elevations and sections are selected to reveal both the architectural form and the areas most relevant to the proposed works.
Quality control is essential at this stage. Drawing geometry should be checked against the point cloud, critical measurements should be independently reviewed, and uncertainties should be flagged rather than silently simplified. This is particularly important where historic fabric does not fit standard drawing conventions.
The result might include floor plans, roof plans, elevations and sections in DWG and PDF formats. These drawings give the wider consultant team a quick, legible basis for discussion, while the point cloud remains available for detailed verification where required.
Build a Revit model that serves the project
The Revit model should reflect the brief, not a generic definition of BIM. For early feasibility, an LOD100 or LOD200 model may be sufficient: accurate massing, principal walls, floors, roofs, openings and circulation, with geometry positioned to the surveyed conditions. This can support option studies and spatial coordination without excessive production time.
For developed design and consultant coordination, an LOD300 model may be more appropriate. Walls, floors, structural openings, roofs and key fixed elements can be modelled with greater definition, while irregular geometry is represented faithfully enough to support design interfaces. In selected locations, LOD400 detail may be justified where a new intervention meets sensitive existing fabric.
There is a trade-off. A higher level of development can improve coordination, but it also increases programme and cost. It may not add value if the model is only being used for broad option testing. Conversely, a low-detail model can be inadequate where new steelwork, lifts, services routes or accessibility upgrades must fit within constrained historic spaces. The right answer depends on the decisions the team needs to make.
What the Design Team Gains
A well-executed BIM model does not remove all heritage uncertainty. Concealed construction, decay behind finishes and inaccessible voids will still need investigation. What it does provide is a dependable geometric baseline that reduces avoidable assumptions.
Architects can test layouts against actual wall thicknesses and room proportions. Structural engineers can understand the relationship between floors, openings and principal wall lines. Building services consultants can assess routes through restricted spaces before proposing impractical solutions. Heritage consultants can review interventions in the context of the building’s recorded form.
The commercial benefit is just as practical. Fewer return visits are needed to confirm routine dimensions. Internal drawing production is reduced. Design conversations become more focused because the team is working from a shared record rather than competing versions of the building.
Where BIM Can Mislead on Heritage Projects
BIM is valuable, but it should not be treated as a complete record of every historic condition. A model has to simplify. The risk arises when simplification is not visible to the people relying on it.
For example, a visibly uneven stone wall may be represented as a consistent plane within an agreed tolerance. That is often appropriate for planning a room layout, but it may not be sufficient for designing a new connection. Likewise, a decorative ceiling may be shown as a general surface when the brief does not require ornament modelling. These decisions should be documented clearly in the model scope.
Good heritage BIM therefore combines useful model geometry with transparent limitations. The delivery should explain what has been captured, what has been modelled, the expected tolerance, and where site verification remains necessary. This protects the client from over-reliance and gives every consultant a clearer basis for using the files correctly.
Selecting the Right Documentation Partner
For a Scottish castle or any listed, geometrically complex building, the lowest survey fee is rarely the only meaningful comparison. The more relevant questions concern capture methodology, model scope, quality checks, communication and whether the provider understands design use cases.
Ask how irregular walls, vaults, roof forms and difficult-access areas will be handled. Confirm whether the Revit model will be built from registered point cloud data, what LOD is proposed, and how critical dimensions are checked. It is also worth agreeing file formats, naming conventions, coordinates and delivery milestones before site work starts.
A specialist documentation partner should be straightforward about what is achievable within the programme and budget. Clear scope is not a limitation. It is what turns a survey deliverable into a dependable design resource.
For heritage teams, the most useful starting point is simple: capture the existing building carefully, model only what the project needs, and keep the evidence available for the decisions that matter most.




Comments