2026-01-28 - Digital Documentation for Architects

Week 2 – Working Drawings, Standards, and Assignment Expectations

1. Week 2 Overview & Housekeeping

The second week of Digital Documentation for Architects focused on setting clear expectations around assignments, software setup, and professional standards.

Sean opened by:

• Clarifying the number of required submissions (eight, not six)

• Addressing scheduling conflicts and reminding students to rely on the module website for accurate class times

• Reinforcing the importance of following setup instructions for Revit, Autodesk Construction Cloud (ACC), and the Desktop Connector

The week’s core themes were introduced, with practical exercises deferred to the hands-on session to allow more time for explanation.

2. Software Setup: Non-Negotiables

Before progressing further into documentation, Sean stressed that everyone must be fully set up.

This includes:

• Installing Revit

• Installing and configuring the Autodesk Desktop Connector

• Activating Autodesk Construction Cloud accounts

• Ensuring all software is accessed using official student credentials

These tools form the backbone of the workflow and are required for both collaboration and submission.

3. ArchD A1 Working Drawings Assignment (Weeks 1–6)

A major portion of the session focused on the primary working drawings assignment, which will run over the next six weeks.

Key requirements:

• All drawings must be produced on ArchD A1 sheets

• A provided sheet template must be used

• Both the Revit model and PDF output must be submitted

• Submissions are made via the module website by providing a file path or URL

Sean emphasized that this mirrors real-world practice, where models and issued drawings are always submitted together.

4. Submission Rules & Late Penalties

Clear submission rules were outlined to avoid confusion later in the semester.

Important points:

• Late submissions incur a 1% deduction per day

• All files must follow ISO 19650 naming conventions

• Students must use their three-letter initials as the originator code

• Students must be able to explain the naming convention used in their package

The message was clear: accuracy, consistency, and professionalism matter just as much as drawing quality.

5. Assignment Timeline & What’s Coming Next

Sean outlined how the documentation package will grow over time.

Upcoming components include:

• Floor plans (current focus)

• Roof, floor, and basement plans (reviewed next week)

• Site plans (issued individually to each student in Week 4)

• Elevations and sections later in the semester

Each student will receive a unique site plan to discourage duplication and encourage individual engagement.

6. Practical Session Focus: Floor Plans & Sheets

The class activity for the week—creating floor plans and setting up sheets—was postponed to the practical session.

This session will focus on:

• Creating views correctly in Revit

• Applying standard scales (typically 1:50)

• Laying out drawings on sheets

• Ensuring drawings meet architectural conventions

• 
  

7. Drawing Standards & Levels of Information

Sean stressed that students must demonstrate a sufficient level of documentation in their drawing packages.

This includes:

• Room tags, wall tags, and door tags

• Revision tags and revision clouds when drawings are updated

• At least one detailed drawing (e.g. a stair or construction detail)

• Correct line styles (solid, dashed, annotation lines)

Students were reminded that drawings must communicate clearly without verbal explanation.

8. Consistent North Arrows & View Orientation

A key technical discussion focused on north arrows and drawing orientation.

Key principles:

• North arrows must be consistent across the entire package

• The main building entrance should generally be shown at the bottom of the page

• Orientation clarity is more important than aligning every drawing to true north

Common mistakes will be addressed in future lectures and practical demonstrations.

9. Site Plans: Accuracy & Line Styles

Sean introduced site plan conventions and standards that will be expanded on in Week 4.

Key concepts:

• Solid lines for visible elements

• Dashed lines for hidden or overhead elements

• Clear annotation hierarchy

• Accurate representation of roof overhangs and external features

These conventions are critical for professional and readable site documentation.

10. File Naming & ISO 19650 in Practice

The importance of international file naming standards was reinforced.

Sean:

• Showed examples from multiple architectural practices

• Explained how poor naming causes confusion on multi-disciplinary projects

• Emphasized that consistent naming is a professional responsibility, not an academic formality

ISO 19650 compliance is required for all submissions.

11. What’s Coming in Week 3

The session closed with a preview of the next lecture.

Upcoming topics include:

• Standard drawing scales

• Types of architectural drawings

• Title blocks and legends

• Dimensions and annotation styles

• Revision management and issue workflows

Students were encouraged to review the lecture content carefully and submit any questions via email or Microsoft Teams.

12. Final Reminders

Sean closed with a reminder that:

• Progress comes from steady, consistent effort

• Last-minute fixes almost always lead to mistakes

• Attendance and engagement matter

• Learning documentation is about discipline, clarity, and humility