Every semester starts the same way. A clean file, a clear idea. Then the project starts changing — daily. Ideas shift, concepts fluctuate, the massing adapts. You test a variation, keep the old one "just in case," import a site model, borrow a detail from last semester's project, duplicate a tower instead of blocking it.
Very quickly, your file becomes a Frankenstein file.
You know the symptoms. Orbiting lags. The file is 1.5GB and you don't know why. There are 5,000 objects you didn't know existed, layers named "Layer 01" through "Layer 47," and three versions of the same facade, two of them hidden, one of them floating a mile from the origin. Design takes many iterations — that's normal, that's the job — but every iteration now costs you twice: once to design it, once to fight the file.
Then review week arrives, and the second tax comes due: presentation.
The presentation tax
This is where most students lose the most time, and it's the complaint I hear everywhere — in studio, on forums, from students who write to me. It goes like this:
You model, then you stop modeling, then you Make2D a view, then you export it at some scale to Illustrator for line-weight processing. The export doesn't fit the artboard. Or it fits but half of it falls off. Or it fits and the line weights are wrong, because the weights you set on layers don't match what prints — the display mode has its own say, and PrintDisplay doesn't match the PDF either. So you test-print. For days.
And then the design changes — because of course it does, it's the day before the review — and the whole round-trip starts over. Re-export, re-link, re-format. Every revision means redoing production work instead of design work. Students describe it the same way every time: tedious, time-consuming, and it eats the precious hours you don't have.
Here's the uncomfortable truth underneath all of it: none of these are talent problems. They're system problems. The file is a Frankenstein because nothing in it has a role. The line weights are a fight because they're set object by object instead of by layer. The Illustrator round-trip is endless because there's no layout setup holding scale, grid, and weights in one place. The file is bloated because nobody purged it, blocked the repeats, or separated the site context from the project.
It all comes down to good practice and a systematic workflow
Not a trick. Not a plugin. A system you set up once and reuse every project:
Layers by role, not by accident. Cut, visible edge, annotation, context — when every project uses the same layers, weights follow automatically, and a new team member (or future-you, at 2am) can read the file.
Blocks for anything that repeats. Windows, columns, trees, facade panels — one block, instanced everywhere. It's the single biggest cure for the bloated file, and it makes global edits instant instead of a search-and-replace hunt.
One layout setup, held once. Page size, scale, title block, one grid — set it in a layout template and every sheet inherits it. Your portfolio stops looking like five different people made it, and a design change updates every sheet instead of triggering a re-export marathon.
Print display modes that match the print. Test once, on paper, at full size: can you tell what's cut, what's near, and what's far in three seconds? If yes, you're done forever. If no, your heaviest line isn't heavy enough — fix it in the mode, not in Illustrator.
Purge as a habit, not a rescue. Purge unused blocks and layers, Save Small when the file starts creeping, keep heavy context (site, people, entourage) in a separate referenced file. The students with fast files aren't lucky. They maintain them.
Do this once, properly, and the next project doesn't start from scratch — it starts from a system. The iterations still happen; that's design. But they stop costing you double. The file stays legible at week twelve. Review week becomes about the work, not the production.
That's what I built the Rhino Starter Kit to be: the template with print-tested line weights, layers organized by role, four display modes for linework, shadows, rendered, and hybrid views, a material and tree library, facade studies, and a sample project so you can see the whole system working before you touch it. Set it up once, and every semester after that starts from a system instead of a Frankenstein: https://www.archidood.com/rhino-starter-kit
