Drawing Issues, Revisions and the Drawing Register

Managing drawing issues, revisions, and the drawing register is one of the most consequential administrative responsibilities in architectural practice. It sits at the intersection of design management, contractual obligation, and professional liability.

When handled well, it creates a clear, auditable trail of every decision made during a project. When handled poorly, it causes construction errors, disputes, and – in serious cases – legal exposure for the architect and the practice.

This guide covers everything architects, architectural assistants, and students entering practice need to understand about formal drawing management: from defining what a drawing issue actually is, to setting up a register, managing revisions, and working within modern BIM environments.

What Is a Drawing Issue?

A drawing issue is the formal act of releasing a drawing to another party for a defined purpose. It is not simply saving a file or sending a PDF – it is a documented, purposeful transfer of information that carries professional and contractual weight.

Every time a drawing leaves the practice, that act should be recorded. The recipient, the date, the revision status, and the purpose of the issue all need to be captured and retained.

Issue Types and Purpose Codes

Purpose codes define why a drawing is being issued, and they determine how the recipient is expected to use it. Using the wrong code – or no code at all – creates ambiguity that can have serious downstream consequences.

The most common issue purpose codes used in UK practice are as follows. For Information (FI) means the drawing is being shared for reference only, with no action required. For Comment (FC) invites the recipient to review and respond before the drawing is finalised.

For Construction (FC or CON) signals that the drawing is authorised for use on site. For Tender (FT) means the drawing forms part of a tender package. For Approval (FA) requests sign-off from a client, authority, or consultant.

Some practices use numeric codes instead of letter abbreviations – for example, S0 for work in progress, S1 for shared for coordination, S2 for shared for approval, and S3 for authorised for construction. These align closely with the status codes defined under ISO 19650.

Choosing the right code protects the architect. A contractor who builds from a drawing issued For Comment only has no contractual basis for claiming that the information was authorised.

Who Can Issue Drawings?

Not everyone on a project team has the authority to formally issue drawings. Most practices operate a sign-off hierarchy that defines who can approve and release drawings at each stage of a project.

Typically, a project architect or senior architect carries the authority to issue drawings to contractors and clients. Architectural assistants may prepare and check drawings, but formal issue usually requires a senior review and countersignature.

On larger projects, a document controller or BIM coordinator may manage the mechanics of issuing through a Common Data Environment, but the professional responsibility for the content of the drawing remains with the architect of record.

Practices should have a written protocol that sets out these responsibilities clearly. This prevents junior team members from inadvertently releasing unapproved or uncoordinated information.

Understanding Drawing Revisions

A revision is a change made to a drawing after it has been formally issued. Revisions occur throughout the life of a project – driven by design development, client changes, consultant coordination, planning conditions, or site queries.

Understanding how to manage revisions clearly and consistently is fundamental to keeping a project legally and technically coherent. Every revision must be documented, labelled, and communicated to all affected parties.

Revision Numbering and Lettering Conventions

There is no single universal standard for revision labelling in UK practice, but there are well-established conventions that most practices follow. The two most common systems are alphabetic (A, B, C…) and numeric (1, 2, 3…).

Alphabetic revision codes are most common for design and production drawings, with the first issued version carrying no revision code, and subsequent revisions labelled A, B, C, and so on. Some practices begin at revision 1 rather than leaving the first issue unmarked.

Numeric systems are sometimes preferred in BIM workflows, particularly where ISO 19650 conventions are in use. Hybrid systems – such as P1, P2 for preliminary revisions and C1, C2 for construction issue revisions – are also widely used to distinguish between design stages.

Whatever system a practice adopts, it must be applied consistently from the first issue to the last. Changing conventions mid-project is one of the most disruptive mistakes a team can make.

Revision Clouds and Delta Markers

Revision clouds are graphical annotations drawn directly on the drawing to indicate which area has changed. They appear as a cloud-shaped boundary – a series of convex arcs – surrounding the revised portion of the drawing.

A delta marker – a small triangle or circular tag – is placed adjacent to the revision cloud and keyed to the revision table in the title block. This tells the reader which revision introduced the change and allows them to trace the history of any given element.

Revision clouds should only reflect what changed in the most recent revision. Previous clouds are typically removed when a new revision is issued, though some practices retain all clouds cumulatively on complex drawings. Either approach is valid, provided it is applied consistently.

Understanding how these graphical conventions relate to the broader architectural title block is essential – the title block is where the revision history table lives, and it must be kept accurate and up to date at every issue.

Managing Minor vs Major Revisions

Not all revisions carry equal weight. A minor revision might correct a spelling error in a room label or update a north point. A major revision might alter a structural grid, change a facade material, or shift a stair position.

Both must be formally recorded and issued, but major revisions require a higher level of coordination before release. The architect must assess the knock-on effects across all related drawings and consultant packages.

A useful practice is to flag major revisions explicitly in the transmittal notes, alerting recipients to the significance of the change. This is especially important when a revision has cost or programme implications for the contractor.

The Drawing Register: What It Is and Why It Matters

The drawing register is the master record of every drawing produced on a project. It captures the full history of each drawing – its number, title, current revision, issue dates, and who has received it.

It functions as both an internal project management tool and an external contractual record. In the event of a dispute, the drawing register is often the first document examined to establish what information was available to a contractor at any given point in time.

What Information a Drawing Register Should Contain

A well-structured drawing register should contain, at minimum, the following fields for each drawing: drawing number, drawing title, scale, originator or author, current revision, status or purpose code, date of first issue, date of latest issue, and a distribution log showing which parties received each revision.

Additional fields that improve the register’s usefulness include the CAD or BIM file reference, the responsible consultant discipline, the RIBA work stage at which the drawing was first produced, and any linked drawings or references.

The distribution log is particularly important. It records which revision was sent to which recipient and on which date. This information is essential if a contractor later claims they were working from an outdated drawing.

Understanding how the drawing register relates to the wider architecture design process helps students see that information management is not a bureaucratic afterthought – it is integral to how a project is delivered.

Drawing Register Formats: Spreadsheet vs Software

Many small and medium-sized practices manage their drawing registers using spreadsheets – typically Microsoft Excel or Google Sheets. This is a perfectly workable approach provided the register is maintained diligently and kept in a shared, version-controlled location.

The risks of a spreadsheet-based register include version conflicts when multiple team members edit simultaneously, manual errors in logging revisions, and the absence of an automated audit trail. On larger or more complex projects, these risks compound quickly.

Dedicated project management and BIM collaboration platforms – including Autodesk Construction Cloud, Procore, Aconex, and Viewpoint – automate much of the register function. They log issues, track revisions, record transmittals, and maintain a searchable archive of every drawing version.

The choice of format should reflect the scale and complexity of the project, the requirements of the client or contractor, and the practice’s own internal capability. Some clients – particularly public sector bodies – will specify which platform must be used.

Setting Up a Drawing Numbering System

A logical drawing numbering system is the foundation of any well-managed project information structure. A well-designed system allows anyone on the project team to identify a drawing’s discipline, location, and type from its number alone.

Setting up the numbering system is a task that should happen at the very start of a project – ideally during the pre-design or briefing stage. Retrofitting a numbering system onto an existing set of drawings is messy and error-prone.

Common Numbering Conventions and Standards

In the UK, BS EN ISO 19650 provides a framework for naming and managing information across the project lifecycle. While it does not prescribe a single drawing numbering format, it does establish principles for consistent, structured naming that most practices now follow.

A typical ISO 19650-aligned drawing number might be structured as: Project Code – Originator – Volume/System – Level/Location – Type – Role – Number. Each segment communicates specific information about the drawing’s identity and context.

For smaller projects, a simplified version of this structure is often sufficient. The key is that the system is agreed, documented, and shared with all project contributors at the outset. Consultants producing drawings under the same project should ideally use a coordinated numbering convention.

Structuring Numbers by Discipline, Level, and Type

Within any numbering system, three variables are the most important to encode clearly: discipline, building level, and drawing type. Discipline codes identify who produced the drawing – for example, A for Architecture, S for Structural, M for Mechanical, E for Electrical.

Level codes indicate which floor or zone the drawing relates to – for example, 00 for ground floor, 01 for first floor, B1 for basement level one. This is particularly useful on multi-storey or multi-block projects where drawings can number in the hundreds.

Drawing type codes classify what the drawing shows. Common examples include GA for General Arrangement, SK for Sketch, DT for Detail, EL for Elevation, and SEC for Section. Combining these three variables into a structured number creates a system that is both human-readable and machine-sortable.

These conventions align closely with guidance on structural grids and coordination drawings, where consistent referencing across disciplines is essential to avoid clashes and misinterpretation on site.

Issuing Drawings: The Formal Process

Issuing drawings formally is a process that involves more than sending an email with a PDF attached. It requires a structured workflow that creates a clear, traceable record of what was transmitted, to whom, and for what purpose.

The formal issue process should be followed consistently on every project, regardless of size. The discipline developed on smaller projects builds the habits that prevent serious failures on larger ones.

The Transmittal Sheet

A transmittal sheet is a formal document that accompanies every drawing issue. It records the project name and number, the date of issue, the sender and recipient details, the purpose of issue, and a list of every drawing included in the package – with its number, title, revision, and status.

The transmittal sheet is a contractual document. It creates a record that the specified drawings were sent, in the specified revision, at the specified time. This record can be decisive in disputes about whether a contractor had access to current information.

Transmittals should be numbered sequentially throughout the project, and copies should be retained in the project archive. Recipients should be asked to acknowledge receipt, either by countersigning a hard copy or by confirming electronically.

Managing Distribution Lists

A distribution list defines which parties receive which types of drawings. On a complex project with multiple consultants, contractors, subcontractors, and client representatives, keeping this list accurate is a significant management task.

Distribution lists should be established at project outset and reviewed at each RIBA work stage. Personnel change, subcontractors are appointed, and the scope of information required by different parties evolves as the project progresses.

A common approach is to maintain a distribution matrix within the drawing register – a grid showing which drawing types are issued to which parties. This prevents both under-distribution (leaving parties without information they need) and over-distribution (sharing sensitive information with parties who should not have it).

Understanding how drawing distribution fits within the broader framework of RIBA work stages helps architects plan their issue programme and anticipate when major drawing packages will need to be prepared and released.

Superseding Old Drawings and Controlling Obsolete Versions

When a new revision of a drawing is issued, the previous revision must be formally superseded. This means clearly marking the old drawing as obsolete and ensuring that all recipients are notified of the supersession.

In digital workflows, superseded drawings should be moved to an archive folder and clearly marked – for example, with a diagonal watermark reading “Superseded – Do Not Use”. In CDE platforms, the previous revision is typically locked and archived automatically when a new revision reaches the appropriate status.

The real-world consequences of failing to manage obsolete drawings can be severe. Contractors working from a superseded revision may install elements that no longer comply with the current design, requiring costly demolition and reconstruction. The architect may face liability if the supersession was not properly communicated.

BIM and Digital Workflows: The Modern Drawing Register

Building Information Modelling has significantly changed the way drawing issues, revisions, and registers are managed. In a BIM environment, the drawing is no longer a standalone document but an output generated from a coordinated three-dimensional model.

This shift means that revisions are often driven by model updates rather than manual editing of 2D sheets. The register and the issue process must be structured to reflect this, with clear protocols for model ownership, clash detection, and drawing extraction.

Common Data Environments (CDEs) Explained

A Common Data Environment is a shared digital space where all project information is stored, managed, and exchanged. It replaces the ad-hoc exchange of files by email with a structured, auditable system that all project contributors can access.

CDE platforms include Autodesk Construction Cloud (formerly BIM 360), Aconex, Viewpoint, Procore, and Trimble Connect, among others. Each platform provides workflows for uploading, reviewing, approving, and issuing drawings, with automated audit trails at every step.

Within a CDE, drawings move through defined status zones: Work in Progress (WIP), Shared for Coordination, Shared for Approval, and Authorised for Construction. These zones map directly onto the purpose codes used in traditional paper-based issue processes.

The use of CDEs is increasingly specified by clients and contractors on medium to large projects. Architects who are unfamiliar with these platforms are at a practical disadvantage in competitive tender situations. Familiarity with architectural diagrams and digital coordination tools is becoming a core competency for early-career architects.

ISO 19650 and Information Management Requirements

ISO 19650 is the international standard for managing information over the whole life cycle of a built asset. In UK practice, it has largely replaced the earlier PAS 1192 suite of standards, and it provides the framework within which BIM projects are structured and managed.

Under ISO 19650, each project must have an Employer’s Information Requirements (EIR) document – now called an Exchange Information Requirements (EIR) – that defines what information must be produced, in what format, to what level of detail, and at what point in the project programme.

The standard defines a formal information management process that covers naming conventions, status codes, approval workflows, and archive requirements. For architects working on public sector or large commercial projects, compliance with ISO 19650 is often a contractual requirement rather than a best practice recommendation.

Understanding these requirements is increasingly part of the practical knowledge expected of architects at all career levels, not just BIM managers and information managers.

Case Studies

Case Study 1: Heathrow Terminal 5 – Large-Scale Drawing Management

The construction of Heathrow Terminal 5, completed in 2008, involved one of the most complex drawing management challenges in UK construction history. The project generated tens of thousands of drawings across architecture, structure, and building services, coordinated between BAA, Richard Rogers Partnership (now Rogers Stirk Harbour + Partners), and hundreds of contractors and subcontractors.

The T5 Agreement – an innovative project delivery framework developed specifically for the project – placed the risk of construction cost overruns with BAA rather than individual contractors. This required an unprecedented level of information transparency, which in turn demanded rigorous document management protocols.

The project used an early Common Data Environment to manage drawing issues and revisions, with structured naming conventions applied across all disciplines. The lessons from T5 directly informed the development of the PAS 1192 standards that preceded ISO 19650.

Case Study 2: The Shard, London – Coordinating International Consultant Teams

The Shard, designed by Renzo Piano Building Workshop and completed in 2012, presented significant drawing coordination challenges arising from its mixed-use programme and the involvement of consultant teams spread across multiple countries.

Renzo Piano Building Workshop coordinated with structural engineers, facade specialists, MEP consultants, and multiple fit-out contractors, each producing drawings that needed to be integrated and cross-referenced within a coherent drawing register.

The project required clear issue protocols to manage the interface between design development drawings from the architect and construction information produced by specialist subcontractors. This case illustrates how drawing management becomes increasingly critical as the number of contributing parties grows.

Case Study 3: Brock Commons Tallwood House, Vancouver – BIM-Driven Issue Management

Brock Commons Tallwood House, completed in 2017, is an eighteen-storey mass-timber student residence at the University of British Columbia. It was one of the world’s tallest timber buildings at the time of its completion, and it was delivered using a fully integrated BIM workflow.

The project team used the model as the primary coordination tool, with all drawing revisions generated directly from the model rather than manually drafted. This approach significantly reduced the lag between design decisions and drawing issue, and it provided a clear, model-based audit trail for every revision.

The project demonstrated that BIM-driven issue management reduces coordination errors and compresses the time between revision and site communication – a measurable efficiency gain with direct implications for programme and cost.

Case Study 4: Sydney Opera House Restoration – Retrospective Drawing Registers

The ongoing conservation and upgrade of the Sydney Opera House, originally designed by Jorn Utzon and completed in 1973, has presented unique drawing management challenges. Many of the original construction drawings were incomplete, inconsistent, or simply absent from the archive when restoration programmes began.

Project teams working on the restoration have had to build retrospective drawing registers from a combination of original drawings, photographic records, and as-built surveys. This process of reconstructing an information baseline is time-consuming and carries inherent uncertainty.

The case underlines the long-term value of a well-maintained drawing register. The absence of comprehensive records on the original building has added significant cost and complexity to every subsequent intervention – a lesson with clear implications for current practice.

Case Study 5: Small Practice Example – Managing Revisions on a Housing Development

A small architectural practice working on a phased residential development of twenty-four units provides a relatable example of drawing register management at a more accessible scale. The project involved three construction phases, each requiring a distinct set of drawings and a clear record of which revision was issued to the main contractor at the start of each phase.

The practice used a shared Google Sheets register, structured with separate tabs for each phase. Drawing numbers encoded discipline, block, level, and type. Transmittals were issued as PDFs with sequential numbers, and a copy of each was stored in a project folder alongside the drawings it referenced.

This straightforward system – maintained consistently throughout the project – provided a complete record of every drawing issue when a dispute arose over whether a particular revision had been issued before groundworks began on the second phase. The transmittal record resolved the question immediately, protecting the practice from a potentially costly liability claim.

Common Mistakes to Avoid

Even experienced architects and well-organised practices make drawing management mistakes. Most common errors fall into three categories: failures of process, failures of consistency, and failures of communication.

Issuing Without a Transmittal Record

Sending drawings by email without a formal transmittal is one of the most common and most damaging mistakes in practice. It creates no auditable record of what was sent, in what revision, for what purpose, or to whom.

In a dispute, an email thread is a poor substitute for a formal transmittal. Email chains can be incomplete, ambiguous about which attachment relates to which drawing, and easily challenged as evidence. A properly completed transmittal sheet removes that ambiguity entirely.

Even on small, informal projects where the client is a personal contact, the practice of issuing transmittals should be maintained. Professional liability does not diminish because the relationship feels relaxed.

Inconsistent Revision Conventions Across a Project

Changing revision conventions mid-project – switching from alphabetic to numeric, or introducing new status codes without updating the project’s document management protocol – creates confusion for contractors and consultants.

On a live construction site, a contractor encountering an unfamiliar revision code may proceed on the assumption that a drawing is current when it is not, or may delay work while seeking clarification. Either outcome has cost and programme implications.

The revision convention should be documented in the project’s drawing management protocol at the outset, shared with all contributors, and adhered to without deviation for the project’s duration.

Failing to Supersede Obsolete Drawings

Obsolete drawings remaining in active circulation on site are a genuine safety and quality risk. A subcontractor installing ductwork from a superseded MEP drawing, or a groundworker excavating to a foundation depth shown on an old structural drawing, may cause damage that is costly to remedy and potentially dangerous.

The responsibility for ensuring that superseded drawings are recalled and replaced rests with the issuing party – typically the architect on their own drawings, and the relevant consultant on theirs. This responsibility does not disappear once a drawing has left the office.

Formal supersession notices, combined with robust CDE workflows and clear watermarking of obsolete documents, are the most effective tools available. Architects who take this responsibility seriously protect both the project and their own professional standing.

Conclusion

Drawing issues, revisions, and the drawing register are not peripheral administrative tasks. They are central to the professional delivery of a building project and to the architect’s legal and contractual accountability throughout that process.

A well-managed drawing register provides clarity for the entire project team, protects the architect in the event of disputes, and ensures that the people building the project always have access to the most current authorised information. These are not marginal benefits – they are fundamental to successful project delivery.

The shift towards BIM and Common Data Environments has automated many of the mechanical aspects of drawing management, but it has not diminished the professional responsibility that underpins them. Understanding the principles – why transmittals matter, why revision conventions must be consistent, why supersession must be formally managed – is what allows architects to use these tools effectively rather than simply mechanically.

Whether working on a small housing extension or a large commercial development, the discipline of rigorous drawing management separates practices that deliver with confidence from those that find themselves exposed when things go wrong. Building these habits early – as a student, as an architectural assistant, as a newly qualified architect – is one of the most valuable investments a practitioner can make.

For those developing their wider practice knowledge, exploring the full scope of working drawings and understanding how drawing management integrates with construction documentation will provide essential context for the principles covered in this guide.