Quality Systems
Levels of Development: Scope Discipline for Regulated Facility Design
How the BIM Levels of Development framework, applied by partners like PharmOut, gives regulated facility projects a shared language for design maturity and scope.
Regulated facility design projects — cleanroom retrofits, greenfield GMP manufacturing builds, laboratory fit-outs — share a recurring failure pattern: design effort is committed before the scope is properly confirmed, the client did not fully know their requirements at project inception, and new information part-way through triggers rework that nobody budgeted for. The Levels of Development (LOD) framework, originally a BIM design-maturity standard, gives regulated design partners such as PharmOut a practical tool for avoiding all three.
What LOD actually standardises
LOD is not primarily a geometry standard — it is a design-maturity standard. It answers a specific question at each project stage: at this point, how much do we know, and how much should we trust this information?
- LOD 100 — Conceptual: massing, orientation, indicative only. Reliable for direction and order-of-magnitude cost; not reliable for specific dimensions or specifications.
- LOD 200 — Approximate geometry: generic systems, approximate size and location. Reliable for general arrangement and rough cost; not reliable for equipment placement or regulatory compliance detail.
- LOD 300 — Specific geometry: defined dimensions, quantities, and specifications, with regulatory requirements (GMP, HVAC classification, containment zones) incorporated.
- LOD 350 — Construction documentation: systems coordinated across disciplines, interfaces defined.
- LOD 400–500 — Fabrication and as-built: field-verified final conditions, aligning with qualification documentation (IQ/OQ/PQ) in a GMP context.
The three problems this framework addresses
Front-loading: investing significant effort in high-detail deliverables before the conceptual stage has been validated by the client. In a staged framework, this risk concentrates at the boundary between scope confirmation and detailed design — committing to detailed work on an unconfirmed brief is the direct mechanism by which rework occurs later.
Client uncertainty: most clients know their outcome — a licensed, compliant facility — without yet knowing the full path to it. Regulatory requirements are not always visible until they are encountered. A staged framework accommodates this by making sign-off at each level a formal gate: the client does not need to know everything at the concept stage, only to confirm what is known so far is correct.
Rescoping: without a staged framework, design changes driven by new client information get absorbed as "normal project activity" — the design team bears the cost. A staged framework changes that: if a client approved an early-stage scope and then changed direction, that is a documented design variation, not a design error, and post-approval changes become billable.
The reverse brief
A reverse brief is produced by the design team, not the client, at the end of discovery: "Based on what you have told us, here is what we understand your project to be. These are our assumptions. Please review, correct, and confirm." It converts the client's words into the design team's interpreted understanding, made explicit so errors of interpretation are caught before they become errors of design — and it maps naturally to the transition from initial brief to a confirmed requirements package.
Practical application
The discipline generalises well beyond physical design: define the expected level of detail at each stage gate in the contract itself; treat early-stage requirements packages as a client-confirmed document rather than an internal input; treat stage sign-off as a documented contract milestone, not a verbal understanding; and price early discovery and scoping stages as standalone engagements rather than absorbing them into detailed design.
The underlying discipline — do not do high-detail work until an earlier stage is confirmed — applies equally to validation projects, GMP consulting engagements, and regulatory submissions. Agreeing what level of detail will be delivered, delivering it, confirming it, and only then proceeding is not a slowdown. It is the mechanism by which regulated projects stay on scope and on budget.