Revit for Architecture Students: A Practical Project Guide

What Revit is

Revit is a building information modelling (BIM) application published by Autodesk. Instead of drawing lines that look like a wall, you place a wall object that knows its type, thickness, material layers, height and host relationships. Plans, sections, elevations, 3D views and schedules are all live views of that single model, so a change to the wall updates every drawing that shows it.

That is the practical difference from CAD drafting: in AutoCAD you maintain each drawing; in Revit you maintain one model and generate drawings from it. The cost is that early modelling decisions propagate, which is why setup discipline matters more than tool tricks.

How architecture students commonly use BIM tools

• Studio design projects — developing and documenting a scheme from concept through to presentation drawings.
• Technology and construction modules — detailing wall build-ups, junctions and assemblies.
• Environmental modules — exporting geometry for daylight, energy or shading analysis.
• Quantity and specification exercises — using schedules to extract areas, door counts and material quantities.
• Final-year and thesis projects — coordinating a larger scheme with consistent drawing sets.

Many students combine tools: massing and form exploration in Rhino or SketchUp, documentation in Revit, visualisation in 3ds Max or a real-time renderer, and 2D detailing in AutoCAD where a supervisor asks for it. Choose the pipeline your studio expects rather than the one you saw in a tutorial.

Starting a project

1. 1Start from your school's template if one exists; it carries the expected units, title blocks, line weights and view templates.
2. 2Set project units (Manage → Project Units) before modelling — millimetres for most UK and EU work, feet and inches for US conventions.
3. 3Enter project information (Manage → Project Information) so title blocks fill themselves.
4. 4Set the project location and true north if you will run any solar or shadow study.
5. 5Link or import the site survey or CAD base as a link, never a bound import, so it can be updated or removed cleanly.
6. 6Save immediately into a structured folder with a version-numbered file name, and keep backups off your laptop.

Model at full real-world size. Scale is a property of a view, not of the model — set it in the view's properties, and never scale geometry to make a drawing fit a sheet.

Levels and grids

Levels are the horizontal datums that host floors, walls and ceilings; grids are the vertical reference planes that organise structure. Both are created in an elevation or plan view respectively, and both should be established before you model anything substantial.

• Create levels in a section or elevation view; name them meaningfully (Ground Floor, First Floor, Roof) rather than Level 1, Level 2.
• Creating a level with the Level tool generates an associated plan view; copying a level does not — a frequent source of missing views.
• Set finished floor level versus structural level intentionally and be consistent, or floor and wall heights will drift.
• Place grids in a plan view; they propagate through levels automatically. Number and letter them conventionally.
• Pin levels and grids (Modify → Pin) once agreed, so they cannot be dragged by accident.

Walls

Walls are system families: you edit the type, not the individual instance, to change construction. Duplicate an existing type before editing its structure, or you will silently change every wall of that type in the project.

• Set the base constraint and top constraint to levels rather than typing an unconnected height, so walls follow level changes.
• Build up the layers in Edit Type → Structure with real materials and thicknesses; this is what makes sections readable.
• Watch the location line (wall centreline, core face, finish face) — mixing them is the main cause of misaligned walls.
• Use Attach Top/Base to tie walls cleanly to roofs and floors instead of guessing heights.
• Curtain walls are a separate wall type with grids, mullions and panels; use them for glazed facades rather than faking them with thin walls.

Doors and windows

Doors and windows are hosted components: they cut their opening automatically and move with the wall. Load the families you need from the library (Insert → Load Family) rather than modelling openings manually with voids.

• Set the sill height and head height through the instance properties rather than by dragging.
• Press the spacebar while placing to flip the swing direction before clicking.
• Duplicate a family type to create a new size rather than stretching an instance.
• Keep type marks consistent — they drive your door and window schedules later.
• Deleting the host wall deletes its doors and windows; that is expected behaviour, not a bug.

Floors, roofs and ceilings

Floors are sketch-based: you draw a closed loop of boundary lines and finish the sketch. An unclosed or overlapping loop is the reason Revit refuses to create the floor, and the error dialogue usually highlights the offending line.

• Use Pick Walls when sketching floors so the boundary updates if walls move.
• Build floor layers in the type structure — structure, insulation, screed, finish — so sections cut correctly.
• Roof by Footprint suits pitched and flat roofs defined in plan; Roof by Extrusion suits profiles defined in elevation, such as curved or asymmetric forms.
• Set the slope through the boundary line's slope-defining property, not by dragging vertices.
• Ceilings are placed in ceiling plan views; students frequently model them in the wrong view type and then cannot find them.
• Use Shape Editing (Add Point, Add Split Line, Modify Sub Elements) for drainage falls on flat roofs and terraces.

Components, families and stairs

Components — furniture, sanitaryware, fittings, planting, people — are loadable families placed into the model. Keep them proportionate: an overloaded model of high-detail downloaded families becomes slow, and slow models get abandoned near deadlines.

• Load only the families you will actually show; purge unused ones (Manage → Purge Unused) before submission.
• Stairs and railings are their own tools with run, riser and tread rules; check your building regulations' rise and going limits rather than accepting defaults.
• For a bespoke element, prefer creating a simple loadable family in the Family Editor over in-place modelling, because it can be reused and scheduled.
• In-place families are fine for genuinely one-off geometry but bloat the file if overused.

Views: plans, sections, elevations and 3D

In Revit, views are how you communicate, and view control is where student drawings usually fall short. Each view has its own scale, detail level (Coarse, Medium, Fine), visual style, view range and visibility settings.

Plans

If elements are missing from a plan, check the View Range before anything else: cut plane, top and bottom offsets determine what is seen and what is cut. Crop the view to the area you want on the sheet and use Annotation Crop to control tag overflow.

Sections

Cut sections where the building is most informative — through stairs, level changes, double-height spaces — not simply through the middle. Set the far clip offset so you show the depth you want. Building sections, wall sections and detail sections are separate section types with their own view templates.

Elevations

Exterior elevations come from the four default elevation markers; interior elevations are placed inside a room and are automatically bounded by it. Control line weights through Object Styles and view templates so elevations read with hierarchy rather than uniform thin lines.

3D views

Duplicate the default 3D view for each purpose and name them — presentation axonometric, section perspective, working view. Use a Section Box to cut the model for a section perspective, and lock your camera views (Save Orientation and Lock View) so a stray orbit does not lose a composed image the night before a crit.

Use view templates. Applying a template to all plans at once is the difference between a coherent drawing set and thirty individually tweaked views.

Sheets and title blocks

1. 1Create sheets from the View tab, choosing your school's title block family.
2. 2Drag views from the Project Browser onto the sheet; set the view scale in the view, not on the sheet.
3. 3Align views across sheets using guide grides so plans stack consistently between drawings.
4. 4Rename views and set the title-on-sheet so drawing titles read professionally.
5. 5Number sheets in a logical series (A-100 plans, A-200 elevations, A-300 sections) and keep the sheet list as a schedule.
6. 6Export to PDF at the correct paper size with line weights checked on a test print before the final export.

A single view can be placed on only one sheet. If you need the same plan twice, duplicate the view — duplicating as a dependent view keeps geometry linked while allowing separate cropping.

Schedules

Schedules are live tables generated from model data: door schedules, window schedules, room and area schedules, material takeoffs, sheet lists. They are one of the strongest arguments for modelling in BIM, because they cannot drift out of step with the drawings.

• Create with View → Schedules → Schedule/Quantities and choose the category.
• Add fields, then use Sorting/Grouping with itemised instances turned off to produce a summarised table.
• Schedules are editable: changing a value in the schedule changes the element in the model.
• Place rooms properly (with room-bounding walls) before expecting area schedules to be correct.
• A schedule with blank rows usually means missing type marks or unplaced rooms, not a software fault.

Project organisation and file hygiene

• Organise the Project Browser with folders by view type or design phase so you can find views quickly.
• Adopt a naming convention for views, sheets and families in week one and keep it.
• Use worksets only if collaborating; for solo student work they add complexity without benefit.
• Keep CAD and image files as links in a single folder alongside the model.
• Purge unused families and audit the file periodically to control file size.
• Save incrementally with dated version names and keep at least one off-machine backup; corrupted files near submission are common and recoverable only from backups.

Common student mistakes

• Drawing lines in a plan view instead of modelling elements, then wondering why sections are empty.
• Modelling in the wrong units or scaling geometry to fit a sheet.
• Using unconnected heights instead of level constraints, so nothing updates when a level moves.
• Editing a wall type without duplicating it first and changing the whole project.
• Ignoring view range, then troubleshooting 'missing' walls for an hour.
• Downloading heavy families until the model becomes unusably slow.
• Leaving all sheet composition to the final night, when line weights and crops still need work.
• No backups.

Preparing your final presentation

1. 1Decide the drawing set first: which plans, sections, elevations, perspectives and details tell the argument of the scheme.
2. 2Apply consistent view templates so line weight, detail level and graphics match across the set.
3. 3Add people, planting and context at a sensible level of detail to communicate scale.
4. 4Compose sheets with a clear hierarchy — one dominant drawing per sheet, supporting drawings around it.
5. 5Export to PDF or image at high resolution and check line weights on a physical test print.
6. 6Rehearse the narrative: what problem the scheme answers, how the plan works, and what the section reveals.

If a physical model is also required, plan it in parallel — our guide to planning and building an architecture maquette covers scale selection, materials and build sequence.

Where support helps

Students most often need help with model setup, families, complex roofs, controlling views and getting a coherent drawing set onto sheets under time pressure. We provide tutoring and technical guidance for Revit, architecture projects, AutoCAD, 3ds Max and 3D modelling in English, Arabic and French. We teach the workflow and review your model with you; the design and the submitted work remain yours.

Frequently asked questions