“We Have CAD at Home”: A Landscape Architect's Resistance to Revit

• It’s overwhelming. Learning a whole new software ecosystem, plus training staff, plus completely rethinking workflows? Not for the faint of heart.

• We already have a 3D workflow. We not only render, but design, in 3D using SketchUp or Rhino. We know its quirks, and we have all the extensions. Why learn a new and more cumbersome platform when we have everything we need right here?

• Most civil engineers still use Civil 3D! Which is, you know ... still AutoCAD. So if they’re not in Revit, why should we be?

• Revit users (looking at you, architects) export hot garbage. Sorry, not sorry. The Revit base files we receive are often a nightmare: poorly managed layers, missing geometry, and a lineweight hierarchy that would give a graphic designer a nervous breakdown. Not a good look for our first exposure to Revit.

• Control issues. Working inside someone else’s model? With their standards and their protocols? That’s not just uncomfortable – it’s existentially threatening. We often feel as if we’re the only consultants looking at the whole picture, calling out conflicts and overlooked details. Being asked to fit in to someone else's model feels … limiting. And risky.

• The 3D “benefits” seem … not super relevant. We’ve been working our magic in 2D for years. While we’ve adapted AutoCAD to suit our needs, Revit is clearly not built for landscape architects. We’ve all heard how it struggles with terrain. And how many times have you seen that exact tree elevation placed poorly in some architect’s model?

• Cost. We already pay for a cornucopia of industry-standard software. Revit is pricey. Adding another subscription to the pile? Oof. That’s a bitter pill.

But … we know it’s the future.

I hate to say it, but the world is moving forward, and you know it. If you’re still putting off integrating Revit into your toolbox, this is your wake-up call:

• Technology evolves. We can either evolve with it or risk becoming the technologically averse principal who needs you to send them a PDF because they “don’t want to open CAD.’”

• Your CAD knowledge isn’t wasted. In fact, it’s a massive head start. No, it won’t make learning Revit easy, but it will give you a solid foundation.

• Civil 3D integrates with Revit. Meaning civil engineers are already coordinating their utility clearances with other disciplines in 3D. You need to be in there too, running Revit’s interference check to make sure that stormline doesn’t smash into your tree rootball. Yes, “Rootball Clash Detection” exists (with the Planting F/X plugin, anyway).

• Everyone working with the same model means fewer surprises. This one’s a no-brainer. You catch conflicts early, you collaborate more efficiently. You may not all work live in the central model (that’s a call for the BIM manager), but what landscape architect has ever complained about a more holistic view of the project?

• BIM requirements are becoming standard. Whether we like it or not, more RFPs are requiring BIM Level 2 deliverables, which means the final product needs to be one file. You don’t want to be that one consultant the team has to drag into the 21st century, or leave it to another consultant to translate your design into Revit.

• Working in Revit is worlds different from working with exported Revit bases. Just trust me on this one. The chaos we’re used to seeing in those janky DWG exports? That’s what happens when a complex 3D model gets flattened, sliced, and shoved into a 2D format it was never really meant for. (Yes, it can be done cleaner, but have you tried explaining that to an architect?) When you’re on the inside, things start to make sense. Suddenly you’ll understand why architects use this software. Not that you’ll feel the same way, but a little cross-discipline empathy never hurt anyone.

• No more messy base files. Still want to hang out in AutoCAD? Imagine this: You export your own base files from Revit. As clean as possible, layered, and just the way you like it. How much time and headache did you just avoid? (If you’re not sure, ask your staff.)

• Use both. That’s right. You don’t have to go all in. Some projects might be better in CAD, some better in Revit. With the Planting F/X plugin, you can even share project information between both softwares. That flexibility is the new workflow.

• Integrated 2D/3D Design Revit might not be perfect for landscape, but it plays nicely with tools like Enscape, Twinmotion, and D5, making quick 3D visualizations part of your everyday process – not some separate, outsourced ordeal. Just think of the efficiency!

• Training exists – and it's good! I highly recommend “Revit: Landscape Architecture BIM Techniques” by Jim Cowan, available on Linkedin Learning. If in-person learning is more your style, check out our free “New to Revit Bootcamp” at the 2025 ASLA conference in New Orleans!

• Revit still has plenty of room to grow. But let's be honest, so does CAD. Yet where are Autodesk's efforts in development and improvement? That's right – Revit.

• Students are learning Revit. They may still have a lot to learn about the industry, but many fresh-faced new hires already know Revit. This is an opportunity to leverage their skills without the emotional baggage tied to 15 years of CAD standards. Let them prototype a project, and make sure you know enough about Revit that you don’t hit a workflow wall.

• Tools like Land F/X offer Revit plugins designed specifically for landscape architects. As a result, you can have integrated schedules and notations just like in CAD. In fact, the similarity of the Planting F/X plugin between CAD and Revit is extremely intentional on our part. We want the transition to be as painless as possible. We also provide a vast library of free training resources on our site. And that Planting F/X license you already have? It works with both AutoCAD and Revit (plus SketchUp and Rhino), with no added cost.

• Maybe … you don’t. Despite all the points above, some landscape architects – especially in the world of residential design – are able to get the job done with their CAD and SketchUp workflows and be perfectly successful at it. There’s zero shame in sticking with what works. That said, if you’re looking down the road and find you’ll want to be designing commercial, public work, multi-story residential, campus work, or anything with an elevator, you need to get serious about Revit.

TL;DR

Yes, Revit is clunky in places. Yes, the learning curve is real. But sticking our heads in the sand isn’t going to make it go away. BIM modeling is here to stay.

Start with a pilot project. Take a training. Add a Revit subscription and start to feel it out. Use CAD when it makes sense. Use Revit when it makes more sense. You don’t have to abandon everything you know – just be willing to expand it.

Besides, there’s something satisfying about being able to say, “Yeah, I can work in both.” Who knows? Maybe one day landscape architects will host the central Revit model.

Share your thoughts, tips, and tricks in the comments. Because if there’s one thing we landscape architects excel at, it’s finding creative ways to make tools actually work for us – even if we grumble about it along the way.

Resources to get started

• BIM Techniques for Landscape Architects (Linkedin Learning)

• New to Revit Bootcamp - ASLA 2025

• Land F/X: Getting Started with Planting F/X for Revit

• F/X CAD: A more affordable CAD option that integrates with Land F/X