Side-by-Side Modeling: Reusing Previous Projects as “Live” References Instead of template file

[alghgifari]

Hi

I work in a small office mainly designing similar two-story residential houses, so I’ve started using a “Side-by-Side” workflow instead of relying on a template file.

My Workflow:

1. Save As: I start by doing a “Save As” from a previous project that’s close to the new brief.
2. Live Reference: I keep the old model inside the same file, just moved off to the side, while I build the new design in its proper position.
3. Attribute Pickup: I use the Eyedropper/Syringe (Alt+Click) to quickly grab wall composites, window settings, floor heights, etc. I also copy furniture and lighting directly from the old model when needed.
4. Layout Integration: Since the layers and Layout Book are already set up for a similar house, I just need to update the view
5. Cleanup Before Export: Once everything is ready for export (PDF/DWG), I just delete the old project geometry from the file.

It’s honestly been faster for me than building everything from Favorites or constantly rebuilding a template, but I’m starting to wonder about long-term file size and stability.

Questions for the community:

• Does anyone else work like this, and is it actually a good long-term workflow?
• My file keeps getting bigger over time—what’s the best way to reduce/clean it up?
• At what point do you think it’s better to switch back to a proper template-based (.tpl) workflow?

thanks.

[alghgifari]

I actually tried the Hotlink method once, but I gave up on the idea almost immediately.

It completely destroyed my DWG setup. Because of the way Archicad handles Hotlink Master IDs, it started showing the Hotlink ID instead of the actual Element IDs I needed. Since my final handoff is in AutoCAD, having incorrect or 'infected' IDs on my layers and blocks makes the file useless for the rest of the team.

[alghgifari]

"Au contraire indeed! 🤣

I fully realize that being a solo Archicad user is the only reason my 'rule-breaking' works. If I had to manage 100 users, I’d be a template tyrant too—I can only imagine the chaos if everyone brought their own legacy files into the mix!

Since I’m on my own, my focus is purely on getting the work out to Structural and MEP engineers who live in AutoCAD. I’ve streamlined my process so that 90% of the documentation happens in Archicad, and then I just do a final pass after exporting to fix 'ByLayer' settings for the DWG deliverable.

But this leads to my second point: honestly, documentation often feels faster and easier in AutoCAD than in Archicad. If the final handoff is just a flat CAD file, what is the point of pumping hours into a 'perfect' BIM template? For me, if the workflow gets the job done and the engineers are happy, why over-complicate it?

I’d love to know your input—does the strict template actually save you time on the documentation side, or is it just about keeping 100 people from breaking the file

[jl_lt]

Engineers should not be happy, the Architect is the one that should be happy.

[Stefan L_]

---

@alghgifari  schrieb:

I can only imagine the chaos if everyone brought their own legacy files into the mix!

---

They do it anyway.

They know their last (and still running) projects by heart.

Copy&Paste.

😔

[Josh Verran]

Hi Alghgifari

In a previous practice I worked at, I found that trying to maintain the template while delivering a live project at the same time was inefficient.

Something to consider is adding a template version number to the Project Info and keeping a separate document with a running list of improvements under each version. It’s a simple, low-tech system, but it also gives you a useful record of which template version each project started from. As things came up during projects, I noted them there, then updated the template at suitable milestones and struck through the completed items.

There’s obviously a lot that goes into maintaining a template, but if I had to pick a few key things, it would be versioning, keeping a clear change list, and regularly checking library warnings and attribute growth rather than letting problems build up over time.

[Rubia Torres]

Hi @alghgifari ,

Some tips to clean up your file:

• Make a backup PLN, open it with Open & Repair and save it under a new name. This can clean up some issues that might build up on legacy files
• Remove embedded objects and attributes that you are unlikely to use going forward
• Keep standard libraries linked externally where possible. The Embedded Library should generally contain only project-specific assets
• Check for missing or duplicated library parts
• ⁠Remove redundant publisher sets, layouts, views, viewpoints (3D Documents, sections/elevations, schedules, worksheets, etc). 3D Documents and stored drawings are frequent source of bloat > review/clean up the Drawing Manager
• Using goodies like Check Duplicates Add-on and Polygon Counting Tool - https://www.graphisoft.com/en-de/downloads/add-ons/goodies/ 

Hope this is useful to your case.

Best regards,