Morpholio Trace + Vectorworks: Make Construction Drawings Beautiful Again
What the Morpholio Trace acquisition could mean for the future of Vectorworks — and the way we design
For years, architectural software has been moving in one direction: towards greater precision, greater coordination and increasingly information-rich models.
That has been a good thing.
But there has also been a trade-off.
The closer we get to construction documentation, the further our drawings can sometimes get from the way designers actually think.
A sketch becomes a CAD drawing.A CAD drawing becomes a model.The model becomes documentation.
By the time a project reaches construction documentation, much of the looseness, hierarchy and visual character of the original design process has disappeared.
The acquisition of Morpholio by Vectorworks in 2026 could start to change that.
At first glance, bringing Morpholio Trace into the Vectorworks ecosystem might seem relatively straightforward: an iPad sketching application connected more closely to a BIM platform.
But there is a much bigger possibility here.
What if Vectorworks is no longer just where the design gets documented, but part of a continuous loop between sketching, modelling, communicating and documenting?
And perhaps more importantly:
Could this make construction drawings beautiful again?
From drawing to BIM — and back again
The traditional digital design workflow is largely linear.
You start with an idea, develop it, build a model and eventually produce drawings.
In practice, however, designers don't work like that.
We draw something.
Then we redraw it.
We trace over it.
We move something.
We circle something.
We sketch an alternative.
We show someone.
They mark it up.
We change it again.
The process is iterative, visual and often deliberately imprecise.
This is one of the reasons sketching remains so valuable despite decades of increasingly sophisticated CAD and BIM software.
Morpholio Trace has always occupied this space particularly well: the digital equivalent of putting tracing paper over a drawing, aerial photograph, plan or model and simply drawing over it.
The interesting development is what happens when that environment is directly connected to Vectorworks.
Vectorworks can send scale-accurate drawings and viewports into Trace, where they can be sketched over and annotated. Trace work can then return to Vectorworks as PDF, image or vector-based content, creating a much more fluid connection between the two environments.
Instead of:
Sketch → CAD → BIM → Documentation
we start to get:
Sketch ↔ BIM ↔ Sketch ↔ Documentation
That small change in the diagram represents a potentially very large change in workflow.
The missing front end of BIM
One way of looking at this is that BIM has traditionally been exceptionally good at the back end of design.
Once decisions have been made, BIM is brilliant at turning those decisions into coordinated information.
Walls have dimensions.
Plants have species and quantities.
Levels have elevations.
Objects have data.
Schedules update.
Drawings coordinate.
Changes propagate.
But what happens before those decisions have been made?
This is where BIM software can sometimes feel uncomfortable.
Early design is messy.
You might not know exactly where a path goes.
You might not know whether a wall should be 600 mm or 900 mm high.
You might want to try three different arrangements of trees without spending twenty minutes modelling each one.
You might simply want to draw a line and see what happens.
That is where a tool like Trace becomes interesting.
It potentially provides a design interface for the BIM model rather than a separate alternative to it.
The model remains the source of structured information, but the designer is free to interact with it in a much more natural way.
A landscape architecture workflow
For landscape architects, the possibilities are particularly interesting.
Consider a relatively typical residential or public-realm project.
01 — Start with the site
Bring the survey, aerial imagery, existing plan or Vectorworks model into Trace.
Draw over it.
Mark:
existing vegetation
views
access
movement
drainage
sun
privacy
opportunities
constraints
existing structures
At this stage, nobody cares whether the line representing a path is exactly 1,500 mm wide.
It is a thought.
02 — Test ideas
Now start sketching design options.
Move the path.
Try another terrace.
Shift the trees.
Draw a retaining wall.
Circle the area that could become a lawn.
Try a different relationship between the house and garden.
This is the part of design where the ability to quickly test an idea is often more valuable than the ability to model it perfectly.
03 — Bring the useful geometry into Vectorworks
Once the design starts to settle, the geometry can move back into Vectorworks.
Now precision becomes useful.
The path becomes an actual path.
The retaining wall gets a level.
The planting becomes planting.
The site model gets developed.
Objects can carry information.
The design starts becoming a coordinated BIM environment.
04 — Go back to sketching
But the sketching doesn't necessarily stop.
Send a viewport back into Trace.
Draw over the developing design.
Try another option.
Annotate a meeting.
Sketch a change during a site discussion.
Mark up a detail.
Show a client what could happen.
Then return to Vectorworks.
This is fundamentally different from treating sketching as something that happens before the real design work.
Sketching becomes part of the real design work.
The construction documentation loop
This is where I think things get particularly interesting.
Construction documentation is often treated as the final, highly technical stage of a project.
But good documentation is also a form of communication.
A good landscape plan needs to tell a contractor what to build, but it also needs to communicate hierarchy, intent and spatial relationships.
There is no reason those things need to be mutually exclusive.
Imagine a workflow where the same project can move between different levels of abstraction:
Loose sketch
→ diagram
→ developed design
→ BIM model
→ technical plan
→ construction detail
→ markup
→ revision
→ final documentation
The underlying project doesn't have to become a completely different thing every time.
The level of information changes.
The geometry becomes progressively more resolved.
The communication becomes progressively more specific.
That feels much closer to the actual design process.
Make construction drawings beautiful again
There is a broader question here about what we expect construction drawings to look like.
Somewhere along the way, technical documentation became synonymous with sterile documentation.
Black lines.
Standard symbols.
Dense dimensions.
Schedules.
Notes.
Everything technically correct, but often visually disconnected from the design thinking that produced it.
There is absolutely nothing wrong with rigorous documentation. In fact, good documentation should be rigorous.
But rigour and beauty aren't opposites.
A well-composed construction plan can be both technically precise and visually intelligent.
Lineweight can communicate hierarchy.
Graphic structure can communicate spatial relationships.
Planting can be legible rather than simply dense.
Details can explain rather than merely comply.
And drawings can retain some of the character of the design process without compromising their technical purpose.
The opportunity presented by Trace is therefore not simply "we can sketch in Vectorworks now."
It is potentially much more fundamental:
The visual language of design could become part of the digital workflow rather than something we discard on the way to documentation.
Is this the biggest workflow change Vectorworks has seen?
That might be overstating it.
Vectorworks has undergone plenty of major changes over its history, from CAD to object-based modelling, BIM, rendering, cloud collaboration and increasingly sophisticated site and landscape tools.
But Morpholio raises a different question.
Not:
What new objects can Vectorworks model?
But:
How should a designer interact with the model in the first place?
That is potentially much more significant.
The traditional assumption has been that the designer needs to learn how to communicate with the software.
Perhaps the future is the opposite.
Perhaps the software increasingly needs to learn how designers communicate with each other.
And then there is AI
This becomes even more interesting when AI enters the picture.
The most useful role for AI in this workflow may not be generating photorealistic images of gardens that could never actually be built.
It could be much more mundane — and much more valuable.
Imagine drawing a rough path over a site.
The software recognises it as geometry.
A rough tree symbol becomes a planting object.
A handwritten note becomes structured information.
A sketch indicating a level change becomes a proposed grading intervention.
A redline becomes a model revision.
The gap between what the designer draws and what the BIM model understands starts to shrink.
Morpholio has already begun moving in this direction with features such as AI-assisted scale detection in Trace.
The longer-term possibility is a BIM environment that doesn't require every design thought to be translated manually into software commands.
You draw.
The software understands.
You refine.
The model develops with you.
The end of the linear workflow?
The most interesting consequence of the Vectorworks–Morpholio relationship may therefore be that the traditional workflow diagram starts to disappear.
Instead of:
CONCEPT
↓
DESIGN
↓
BIM
↓
DOCUMENTATION
↓
CONSTRUCTION
we could have something closer to:
DRAW ↔ MODEL ↔ COMMUNICATE ↔ DOCUMENT ↔ DRAW
The model sits in the middle, but it isn't necessarily the place where every creative decision has to originate.
That distinction matters.
Because designers don't think in BIM objects.
They think in spaces, relationships, sequences, problems, opportunities and ideas.
Sometimes the fastest way to communicate one of those ideas is still a line drawn on a piece of paper.
Or, increasingly, on an iPad.
What this could mean for landscape architecture
Landscape architecture has always been particularly suited to this kind of workflow.
Our work sits between architecture, engineering, ecology and the living landscape.
We deal with things that are inherently difficult to reduce to fixed geometry: growth, movement, shade, views, habitat, seasonal change and human experience.
A purely object-based workflow can struggle with that ambiguity.
Drawing doesn't.
The possibility of moving seamlessly between drawing and structured BIM information could therefore be especially valuable for landscape architects.
It could allow us to retain the messiness of design thinking while gaining the coordination and reliability of a modern BIM workflow.
And perhaps that's the real opportunity presented by Morpholio Trace.
Not making BIM less technical.
Not replacing Vectorworks.
Not replacing drawing.
But allowing all three to work together.
The future might look surprisingly familiar
There is a temptation to think the future of design software must look radically different.
More automation.
More AI.
More generative design.
More photorealistic visualisation.
More complex models.
But perhaps one of the most useful developments is actually much simpler.
Make it easier to draw.
Make it easier to think.
Make it easier to test an idea.
Make it easier to communicate.
Then make it easier for that idea to become a properly coordinated piece of construction information.
If Vectorworks and Morpholio can make that loop genuinely seamless, the result could be more than a convenient iPad workflow.
It could represent a shift in how we think about BIM itself.
And maybe, after years of making our digital drawings increasingly precise, coordinated and information-rich, we can finally make them beautiful again.
Comments