Drafting Studio
Franchise & Rollout

Site-Adapt Handoff: What Architects Need From Your Prototype Set

Your prototype set is not a permit set — it is a handoff package for a licensed professional taking legal responsibility for your work. Here is what…

Sep 8, 2026 4 min read
Site-Adapt Handoff: What Architects Need From Your Prototype Set
“The handoff is not a file transfer. It is the moment you ask another licensed professional to take legal responsibility for your work — and the package should show you understand what that costs them.”

The Prototype Set Is Not a Permit Set

Here is the opinion that gets us in trouble at rollout conferences: your prototype drawing set is not a drawing set. It is a very expensive suggestion. We have received prototype packages that were beautiful — coordinated, detailed, clearly produced by talented people — and completely unusable for permitting, because nobody designed them for the handoff.

A prototype set has one real job: to give the local architect or engineer of record everything they need to produce a permit-ready, site-adapted set without reverse-engineering your intent. Most of them fail that job, and the failure costs weeks on every single site.

What the Local Architect Actually Needs

The local architect of record is stamping these drawings. That means they are legally responsible for them, which means they need to understand every decision you made and why. Give them a complete MEP design narrative — the loads, the systems selected, and the reasoning behind the selection. Provide equipment selections with basis-of-design data, not just model numbers that may be discontinued or unavailable in their market. Include load calculations with the assumptions stated plainly, so they can verify rather than redo.

And keep a clean, explicit record of what is prototype-standard versus what must be site-verified. The best handoff packages we have seen read like an engineering story, not a pile of CAD files. The worst ones read like a puzzle the local team is expected to solve under a permit deadline.

What to Leave Out

Just as important is what does not belong in the handoff. Do not ship unresolved coordination problems labeled "field verify" — that is not delegation, it is abdication, and the local architect knows the difference immediately. Do not include jurisdiction-specific forms or calculations from the last site; they create the false impression that the work is already done.

And do not bury the prototype's known compromises. Every prototype has them — the panel sitting at ninety-two percent loaded, the duct run that only works if the ceiling is exactly nine feet, the plumbing layout that assumes a fixture the local code may not allow. Document them plainly. A local architect who discovers your compromises on their own will trust nothing else in the package.

The handoff is not a file transfer. It is the moment you ask another licensed professional to take legal responsibility for your work — and the package should show you understand what that costs them.

Drawings unrolled on site, the handoff moment when a prototype set meets local conditions.
Drawings unrolled on site, the handoff moment when a prototype set meets local conditions.

Where Handoffs Usually Break

In our experience, handoffs break in three predictable places. First, the gray zone of responsibility: nobody wrote down who owns the site-specific structural coordination, the utility service applications, or the energy compliance forms, so everyone assumes someone else is doing it — until the permit is due.

Second, the CAD standards collision: the prototype arrives in a layering and xref structure the local firm cannot use, and two weeks burn while drafters translate files instead of designing buildings. Agree on deliverable formats before the first site, not during it.

Third, silence after delivery: the prototype team ships the package and disappears, so the first round of plan-check corrections lands on a local architect with no access to the people who made the original decisions. All three failures are preventable with a written handoff protocol — which, tellingly, almost nobody has.

A Better Handoff, in Practice

Write the protocol before the first site. Name the deliverables, the file formats, the decision log, and the support window after delivery — including who answers the local architect's questions during plan check and how fast. Treat the local architect as a partner absorbing your liability, not a vendor executing your drawings.

Get this right and site adaptation becomes the fastest part of your rollout instead of the part everyone dreads. Get it wrong and you will pay for the same missing information fifty times, in fifty cities, with fifty different architects wondering why the prototype team could not be bothered to explain itself.

We build handoff-ready prototype sets: complete MEP narratives, electrical and mechanical drawings to your CAD standard, and a clean record of what is prototype-standard versus site-variable. Request a quote to scope your rollout program.

Need similar drawings?

Get permit-ready multi-site rollout drawings for your project

Send us your plans and scope — we'll come back with a fixed price and a turnaround date. No obligation.

Get a fixed drafting quote in under 24 hours

Send us your architectural plans and scope. We'll come back with a fixed price and a turnaround date — no obligation.