From Revit Model to Planning Set: A Practice Workflow.

Why Revit's Own Sheets Rarely Satisfy a Planning Officer

Revit's sheet views are built for construction coordination. They carry callouts, keynotes and reference tags meant for a contractor reading a working drawing, not for a lay planning officer trying to understand what a scheme looks like from the street and what it will do to the neighbours. That mismatch is the root of most avoidable planning queries.

Planning sets need context the model doesn't hold natively: a street scene showing the proposal against its neighbours, existing versus proposed comparisons side by side, and often a shadow or massing study to support the narrative in a Design and Access Statement. None of that lives inside a typical Revit project file by default, and forcing it out of Revit sheets alone usually means fighting the software rather than producing a clear drawing.

The rejection triggers are well documented across UK local authority validation checklists: a missing north point, an absent or wrong scale bar, no red site boundary line on the location plan, inconsistent line weights between sheets, or a PDF that's been "fit to page" rather than plotted at a stated, measurable scale. Councils flag these constantly because their validation officers are checking a specific list, not admiring the drawing.

The real task, then, isn't "make Revit produce a planning set." It's export clean linework out of Revit, then finish the set somewhere built for presentation and annotation rather than model coordination.

Exporting Clean: DWG and IFC Out of Revit

Autodesk's own documentation is clear that exporting view and sheet sets to DWG or DXF is the standard route for taking Revit content into downstream CAD or presentation workflows. That's the model to follow here: export the site plan, floor plans, elevations and sections as DWG with view-specific overrides stripped out, so the line quality that lands on export is the line quality you actually want on a planning sheet, not a coordination-heavy mess of construction annotation.

IFC export carries more geometric intelligence than DWG, which matters if anyone downstream needs to walk the model rather than just print from it, for example when building a massing study or a site-aware render. DWG is fine for flat linework; IFC is worth having if the next stage needs real 3D.

Linea imports native IFC files from Revit directly, alongside DXF and DWG, all parsed in the browser with nothing uploaded. That removes a conversion step that trips up a lot of practices: no round-tripping through a third format, no re-exporting because the first pass lost layers.

This matters more than it sounds. A typical Revit export drops twenty-odd views into a single model space, all sharing layers, because that's how the source file was organised. Linea's import dialog draws the file before it lands and finds the separate drawings inside it. A click on the plan you actually need crops the import to just that drawing, cut clean at the edge, rather than dragging an entire sheet's worth of overlapping geometry into your next tool.

Building the Context the Model Doesn't Have

UK planning guidance expects location plans built on up-to-date Ordnance Survey base mapping, typically at 1:1250 or 1:2500, showing the site boundary in red and any other land the applicant owns in blue. Revit models almost never carry this cartographic context. There's no reason they should: the model is about the building, not the wider street.

This is where placing the exported geometry into a site-aware environment earns its place in the workflow. Linea's site placement sets the scheme against real ground and surrounding buildings, the piece Revit's own site tools rarely handle well without a lot of manual massaging. Once the model sits in context, fresh sections and elevations can be cut directly from the placed geometry as real linework, not raster snapshots, so they issue on a sheet at a true, measurable scale exactly like a plan should.

For the visual side of a Design and Access Statement, the same placed model can go into Shoot to generate a photoreal massing image for a street scene or context view, with proportions locked to what's actually been drawn rather than freehand illustration. This is the kind of visual planning officers and neighbours respond to: not a polished hero render, but a legible view showing how the proposal sits against what's already there.

Where the source is a PDF rather than a CAD file, Vector's Import brings in a vector-ready PDF exported straight from Revit as real editable linework, removing duplicate geometry and rejoining broken polylines along the way, so the drawing that lands is genuinely usable rather than a flattened trace.

Annotating and Scaling in Vector

Once linework is in Vector, the first job is setting a true real-world scale on the imported drawing, either a standard ratio like 1:100 or 1:200, or calibrated against a known dimension already on the drawing. This is what separates a measurable planning drawing from a picture of one: with a scale set, dimensions and areas report in real metric units rather than paper millimetres, which is exactly what validation checklists are checking for when they warn against scanned or "fit to page" submissions that can't be digitally measured.

CAD exports from Revit are rarely consistent on line weight, especially once several disciplines or several Revit versions have touched the same file. Vector's ISO pen-weight presets and layer controls bring that mess back to a single planning-drawing standard, the kind several councils explicitly require: one title, one drawing number with revision, one paper size, one scale statement per sheet.

North points, scale bars and hatching can go on directly from Vector's Generate tool, or as an imported SVG symbol placed straight onto the sheet. The scale bar regenerates automatically if the scale changes later, which matters more than it sounds: a scale bar that's out of sync with a revised drawing scale is one of the more common rejection triggers on validation checklists, because it looks correct at a glance but measures wrong.

Dimensioning and labelling run through the Type tool and named text styles, so every sheet in the set reads consistently without retyping formatting sheet by sheet. That consistency is a validation issue as much as a presentation one: several authorities require every drawing to carry a title, drawing number, paper size, stated scale and scale bar, and a set where each sheet looks like it came from a different hand invites exactly the kind of query that delays validation.

Assembling the Submission Package in Layout

Layout is where the individual sheets become a submission. Starting from the Design and Access Statement template, one of the seven founding templates, gives a structure already populated with placeholder text and image frames rather than a blank page, which matters when a DAS needs to combine narrative with drawings in a way planning guidance expects.

Finished Vector sheets and Shoot stills bring in as placed images, and the layout grid keeps drawing numbers, scale notes and revision boxes aligned across every sheet in the document. This is where existing and proposed comparisons sit side by side on the same page, which several councils' layout guidance calls out directly as something officers expect to see clearly, not buried across separate PDFs.

Export as a vector multi-page PDF at true sheet dimensions, which is the format most planning portals expect for a bundled drawing submission and single-PDF-per-drawing requirements that many validation checklists insist on. Layout also supports bleed and crop marks if any part of the set needs print production alongside the digital submission.

Keeping the Set Alive Through Revisions

Planning sets rarely stay static. A pre-application comment, a neighbour objection or a design refinement means going back to the model, and the workflow needs to survive that without becoming a manual patch job.

Re-export from Revit and re-import to Linea or Vector when the design changes, rather than hand-editing exported linework to match a moved wall. That's the discipline that keeps the drawing set trustworthy: edited linework drifts from the model quietly, and nobody notices until an officer measures something that doesn't match the plan beside it.

Saved views in Linea let sheets get reissued quickly after the model moves, rather than re-cutting every section and elevation from scratch each time the scheme shifts by half a metre. Layout's document model keeps drawing numbers and page order intact even as individual sheets get swapped for revised versions, so a revision doesn't mean rebuilding the whole submission pack.

Before anything goes to the planning portal, the finished DAS or drawing pack can be shared as a read-only public link for client sign-off, which is a faster review loop than exporting a draft PDF every time a partner wants to check a sheet.

The underlying lesson holds regardless of which tools sit in the pipeline: Revit is excellent at coordinating a building, and largely indifferent to whether a planning officer can read the result. Closing that gap means exporting deliberately, rebuilding context the model never held, and finishing the annotation and assembly somewhere designed for exactly that job.