AC1 Lecture 10 Nov 4, 2026
From BIM Models to Professional Architectural Documentation
As Assignment 2 progresses, the focus shifts from collecting and modelling measured survey information to organising and presenting that information as a professional architectural documentation package.
This session explored the principles of BIM publication, drawing production and document management. Using a presentation prepared by a former lecturer, we examined how information extracted from BIM models can be transformed into a structured, coordinated and professionally formatted publication.
An important distinction throughout the session was that the objective is not simply to present a BIM model, but to communicate the information contained within it effectively.
1. Understanding the Documentation Workflow
A successful architectural documentation package requires more than a collection of drawings exported from Revit. It must present the project in a logical sequence, with consistent formatting and a clear hierarchy of information.
The publication workflow should consider:
How information is organised and structured.
How drawings, photographs and supporting documents are incorporated.
How pages are laid out and formatted.
How external assets and linked information are managed.
How the final document is exported, checked and distributed.
Students were introduced to the use of dedicated publication software, including Adobe InDesign, Affinity, DesignCraft and Scribus. Canva was also discussed as a cloud-based alternative.
Regardless of the software selected, the objective is to establish a consistent publication system that can be applied across the entire document.
2. Structuring the Final Documentation Package
The final submission should communicate the project from its initial definition through to the completed survey documentation and findings.
The recommended structure includes:
Cover Page – Project title, group identification and relevant project information.
Project Definition – An introduction explaining the project and the subject of the survey.
Scope and Purpose – An explanation of what the survey and documentation exercise set out to achieve.
Executive Summary – A concise overview of the project and its principal outcomes.
Measured Survey Records – Field sketches, notes and supporting survey information.
Evidence Trail – Photographs and other supporting material demonstrating the survey process and the origin of the information.
Architectural Drawings – Plans, sections, elevations and other relevant technical drawings.
Glossary – Explanations of relevant technical terminology where appropriate.
Findings and Conclusion – A summary of the survey results and any relevant observations.
The document should read as a coherent publication rather than a collection of unrelated sheets. Each section should contribute to the overall understanding of the project.
3. Establishing a Consistent Graphic Identity
One of the key principles discussed was the importance of consistency throughout the final document.
Each group should establish a simple graphic style guide before assembling its publication. This should define:
Typeface and font hierarchy.
Primary and secondary colours.
Heading and body text styles.
Page margins and spacing.
Image placement and caption formatting.
Drawing presentation and annotation styles.
Landscape pages may benefit from a newspaper-style column layout, particularly where large drawings need to be combined with supporting text and images.
Students should avoid formatting each page independently. Instead, establish reusable page templates and consistent styles that can be applied throughout the document.
This will improve both the visual quality and the efficiency of the publication process.
4. Preparing Architectural Drawings for Publication
Architectural drawings must be presented according to recognised technical drawing standards. A drawing should not simply look correct on the page; it must communicate accurate information at an appropriate scale.
All relevant architectural drawings should include:
A north arrow where applicable.
An appropriate scale reference.
A fully populated title block.
Clear drawing titles and identification.
Consistent line weights and graphic conventions.
Legible dimensions, annotations and symbols.
Particular attention should be given to drawing scales. Students should ensure that drawings are exported and placed at their intended scale, rather than resized arbitrarily to fit the page.
The session emphasised that professional documentation standards apply regardless of the size or complexity of the project. These are fundamental requirements of architectural drawing production.
5. Exporting High-Quality Drawings from Revit
A significant part of the session focused on the quality of drawings exported from Revit, particularly the differences between vector and raster output.
Vector graphics preserve lines and text as scalable elements, allowing drawings to remain sharp when enlarged or printed.
Raster graphics are made up of pixels and can become blurred or visibly pixelated when enlarged beyond their original resolution.
Where possible, students should use vector-based PDF export settings when producing architectural drawings from Revit.
However, certain visual effects, particularly shadows, can cause parts of a drawing to be rasterised during export. The session demonstrated a workaround:
Export the drawing once with shadows enabled.
Export the same drawing again without shadows.
Bring both exports into publication or PDF aggregation software.
Superimpose the two versions to retain the visual effect of the shadows while preserving the quality of the underlying linework.
This technique can help maintain a high-quality presentation without compromising the clarity of technical drawings.
6. Document Assembly and PDF Production
Once the drawings and supporting materials have been prepared, they must be assembled into a single, coordinated publication.
Students should pay attention to the relationship between the page layout and the information being presented. Large drawings may require dedicated pages, while supporting photographs, notes and explanatory text can be arranged around them.
The final PDF should be checked carefully before submission.
Important considerations include:
Ensuring all pages follow the established graphic style.
Checking that fonts display correctly.
Verifying that hyperlinks and linked assets work.
Confirming that drawings retain their intended scale and line weights.
Checking that no images or information are missing.
Optimising the file size without unnecessarily reducing image quality.
Ensuring the pages follow the correct sequence.
This final checking process, often referred to as pre-flight or pre-publication checking, is an essential part of professional document production.
7. File Naming and Information Management
The session revisited the importance of applying consistent file naming conventions, building on the ISO 19650 principles introduced earlier in the course.
Files should be identifiable and organised in a way that makes their purpose, status and revision clear.
Avoid informal naming practices such as:
final_final
final_latest
new_final_version
Instead, use the agreed project naming convention and include appropriate revision identifiers or dates where necessary.
For example, revision references such as R1 and R2 make it easier to distinguish between successive versions of a document.
Consistent naming is particularly important when multiple group members are contributing to the same project.
8. Managing Group Contributions and Collaboration
The session also addressed how groups should organise the production of their final documentation.
Two possible approaches were discussed:
Centralised document approach
All group members contribute to a shared document or coordinated working file. This allows information to be assembled progressively, but requires clear rules for editing and file management.
Designated editor approach
One group member takes responsibility for assembling and formatting the final publication, while the remaining members provide their respective drawings, information and supporting materials.
Whichever approach is selected, groups should establish a reliable backup system and ensure that all contributions are properly coordinated. The aim is to avoid duplicated work, conflicting versions and the loss of information during the final stages of production.
9. Assignment 2: Submission Requirements
The submission structure was clarified during the session. Students are now expected to produce three distinct deliverables:
Submission 1 – Measured Survey Field Notes
The original survey records, including field measurements, sketches, photographs and supporting information.
Submission 2 – Collaboration Workflow Document
A document explaining how the group organised and executed the project. This was previously discussed as a presentation, but is now to be developed as a written document.
Submission 3 – Final Documentation Package
The completed architectural publication, incorporating the project information, measured survey evidence, technical drawings and supporting documentation.
The collaboration workflow document and final submission will receive both individual and group assessment components. Students should therefore ensure that their own contributions and understanding of the process are evident.
The Revit model must also be included as part of the final submission.
10. Developing the Publication System
As a practical exercise, groups were encouraged to begin developing a publication system for their projects, with a target document length of approximately 30–40 pages.
This should include the relevant floor plans, sections and other supporting information, organised into a consistent and professional document.
Rather than waiting until all modelling is complete before considering presentation, groups should begin developing their page layouts and graphic standards now. This will make it easier to identify missing information, coordinate drawing requirements and maintain consistency as the project progresses.
Groups were also reminded to submit their draft project execution plans as soon as possible. These drafts will allow feedback to be provided while there is still time to make improvements.
Preparing for the Next Stage
As the class moves further into the practical development of Assignment 2, students should prioritise the following:
Submit the draft group project execution plan through the Assignment 2 submission link.
Establish a publication style guide for the group.
Begin developing reusable page layouts and document templates.
Organise the measured survey information and supporting evidence.
Prepare Revit drawings for high-quality PDF export.
Check that all drawings include the required technical information.
Agree on a file naming and revision-management strategy.
Decide how the group will coordinate contributions to the final document.
Ensure the Revit model is included in the planned deliverables.
The remaining sessions will continue to focus on practical Revit and cloud collaboration workflows to support the completion of the assignment.
Central Theme
Professional BIM practice is about communicating information, not simply producing models. A successful architectural publication brings together accurate technical drawings, reliable survey evidence, coordinated digital information and a consistent graphic language to produce a clear, structured and professional document.
