Two shops can both run Microvellum and still be nothing alike. That gap lives in your spec groups — and it’s where handoffs quietly fall apart.

If you run Microvellum, your spec groups are the foundation of every successful project. They’re the control panel behind everything you draw, the materials, the hardware, the construction methods, and the behind-the-scenes global variables that decide how a product actually gets built.

Most drafting problems people blame on “the software” are really spec group problems. And when you start handing projects to an outside partner or even onboarding a new drafter internally, spec groups are the exact place it breaks. Here’s why, and what to check before you hand anything off.

Spec groups are supposed to carry your tribal knowledge

The most efficient Microvellum libraries are the ones where a shop’s default construction methods, materials, and hardware are already built into the spec groups. When that’s true, starting a new project and hitting the ground running drawing cabinets and getting to production is quick and efficient. When it’s not, you spend your day fighting the software to get a good result.

The real power of Microvellum shows up when your spec groups and library lower the barrier of entry for your drafters and engineers to get buildable products drawn and out to the floor.

Think about how it used to work. Historically, every person drafting and engineering for you needed to carry all of it in their head, your machinery, the decision trees for each machine, every tool call, the way a product flows through your shop. Questions like “do we edgeband the top edges of uppers and the rear edges of front stretchers?” or “do the shelves need to be 1″ thick on this 32″-wide cabinet?” used to be things a drafter had to stop and ask someone senior to get right and they had to remember to ask in the first place.

All of that can be built into your spec groups automatically, so the person inputting products doesn’t need to know or remember it every single time. That’s the whole point. (I wrote more about intentionally baking your standards into your spec groups in Unlocking Microvellum’s Power.)

Why outsourcing makes the cracks worse

Here’s the problem. Most shops never take or never have the time to set up their spec groups with that tribal knowledge properly built in. Or they go the other direction and make their spec groups so unique that you need tribal knowledge just to navigate them.

Either way, if that logic isn’t communicated and translated to your outsourcing partner, or your new internal hire, it’s a recipe for disaster and a lot of frustration.

The difference is night and day. In a library you know well, switching all your upper cabinets to have valances might be a 30-second task. In someone else’s library, that same change can turn into hunting for a needle in a haystack, reverse-engineering another person’s logic just to figure out where the setting lives.

The real danger: getting the right result the wrong way

Where this goes painfully wrong isn’t when a partner gets the wrong answer. It’s when they get the right end result the wrong way.

Say a drafter uses product-level prompts to give a run of cabinets their valances, when the correct move was a single global variable change in the spec group. The elevation looks right. The job looks done. But now a handful of those cabinets are missing the underlying spec — and when it’s time for engineering, someone else adds a few more cabinets assuming the spec group already had those settings baked in. It didn’t. Now you’ve got inconsistency baked into the project, and nobody knows.

We live in a world where engineers work behind each other on a digital assembly line. It is imperative that each person in that line understands how the person before them completed their work, so they don’t unknowingly undo something they didn’t expect to have been done.

And this is the part that fools people: an elevation can look fine, and actually be fine, right up until it isn’t. The trouble shows up later, when you make changes for field dimensions and release to production. That’s when the shortcuts surface. If I had to edit subassembly prompts to force a fixed shelf where it needed to go in a custom cabinet, I’m now working with a subassembly that may no longer accept product-level instructions down the line. The change that was invisible in the model becomes a real problem the moment someone downstream tries to modify it.

How it should actually be handled

None of this is an argument against outsourcing. It’s an argument for doing the spec group handoff right. Here’s how we do it.

When we onboard a new client, we start by getting their entire configuration — and then we ask them to walk us through how they set up their spec groups, start to finish. That’s the step most people skip, and it’s the most important one. Watching them work tells us everything: whether they build in the project wizard or work straight from the global variables, whether they handle materials with find-and-replace, formula-driven materials, or fully custom project-level materials. Every shop does it differently, and we need to see their way.

From there, we always use the client’s entire library and their spec groups — never a substitute — to guarantee full compatibility. Then, before we run wide, we set up the project, draft a single room, and send back the full Microvellum import of that room for the client to review and confirm everything is correct. Get one room right, and the rest of the project follows.

We keep it in sync from there. On each new project we check whether the client has made any library updates, so our copy never drifts out of date. When possible, we have the client create the project and spec groups themselves and send them to us — it minimizes the back-and-forth of sharing finishes, materials, and hardware at startup, especially when a job deviates from what’s in the architectural specs.

The check that actually catches it

You can’t trust the 3D model or the elevation to tell you spec groups were respected. The real check is this: create a work order from the products, and verify the output materials, hardware, and part sizes in the work order reports against the drawings.

That’s where a right-result-wrong-way shortcut finally shows itself. We build this into our internal QC process, and we also ask clients to review on import. The longer we work together, the more seamless it gets — because the standards keep getting more deeply documented, not less.

Before you hand off a project

If you’re about to give a project to an outside partner — or a new drafter — run this first:

• Is your tribal knowledge actually in your spec groups, or in someone’s head? Edgebanding rules, shelf-thickness rules, default construction — if a person has to remember it, the software should be doing it.
• Can a stranger navigate your spec groups without reverse-engineering them? If switching valances is a needle-in-a-haystack hunt, that’s a warning sign.
• Are you sharing your entire, current library and spec groups — not a stale copy from six months ago?
• Have you walked them through how you set spec groups up, start to finish — wizard vs. globals, and how you handle materials?
• Did you confirm a single-room proof before releasing the whole project?
• On the way back, did you build the work order and check output materials, hardware, and part sizes against the drawings — not just eyeball the model?

The hard truth

Most shops are only familiar with how they use Microvellum, and they’re blind to how varied it can be from one shop to the next. Just because two shops both run Microvellum does not mean drafting or engineering for them is remotely similar or comparable. And this isn’t just a matter of industry experience — there is no “industry standard” inside the four walls of spec groups. Every shop is its own dialect.

That’s exactly why spec groups are where outsourcing breaks. And it’s exactly why, done right, they’re also where a real partnership gets its footing.

This is the work we do every day — extracting a shop’s standards, getting into their spec groups the right way, and making the handoff seamless instead of a guessing game. If you want your drafting to move faster without giving up control of how you build, let´s talk.

Jacob Edmond

CEO